---
schema_version: "1"
id: 5668f4b1c35691e22ebe081fbceee325c4cf546511146f1c81edec58b38a6e84
title: Views
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-apis/views.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/views.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 49d7438aa9d215a7ef54511faf0e68827fc3b8e640d6af478a73bb0961dc4ebc
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# Views

For multi-channel assets, use a channel view to hold the different content for the different channels. This allows the asset to parse and render its content differently based on the channel it’s used in. Use a generic `html` view as a fallback in case the channel view used to render the asset isn’t found in the views.

Add views to the asset as an object under the `views` attribute. Each key under views represents a channel view and contains an asset for this channel.

## Sample Asset with Views

```json
{
  "name": "NTO Welcome Series Email",
  "channels": {
    "email": true,
    "web": false
  },
  "views": {
    "html": {},
    "text": {},
    "subjectline": {},
    "preheader": {},
    "viewAsAWebPage": {),
    "subscriptioncenter": {},
    "forwardHTML": {},
    "forwardText": {}
  },
  "assetType": {
    "name": "templatebasedemail",
    "id": 207
   }
}
```

## Related Items

- [Asset Model](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/asset-model.md)
- [Asset Model Example](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/asset_model_examples.md)