Partials
Partials use a simple tag and a > prefix. Use partials to pull in content at runtime. All partials include one of three identifiers for content stored in the Portfolio or Content Builder repository for your account:
| Identifier | Description |
|---|---|
| Key | String value identifying key for content, such as Key |
| ID | String value identifying ID for content, such as id:348021. |
| Name | String value identifying file path for content, such as mycontent/descriptions/mens/shoes. The Name identifier isn't supported in Content Builder. |
Partials accept an optional string parameter identifying content as originating in Portfolio or Content Builder:
portfolio(Default)contentbuilder
If the string parameter is undefined, the partial assumes that the content originates from Portfolio. Content originating from Content Builder must have the string parameter defined, otherwise the partial inserts a blank during rendering.
Partials insert content into a template when a message publishes. You can force the content to refresh again at send time using the optional refresh tag.
To return the results of a variable, use the var: prefix. This prefix treats the value of the variable as stored content and link wraps the results as applicable.
To syndicate content from an external web page during rendering, use the get: prefix and insert the applicable URL.
Include an optional static tag to apply the content at the message level and not per each recipient.
If you don't include a prefix in the template (aside from the > character), Guide uses these rules to locate content:
- Uses the data field within the data context as indicated by the identifier.
- Uses content syndication to pull in the applicable content as indicated by the URL identifier.
- Uses stored content as indicated by the key, id, name in the identifier.
- If Guide can't match any value, it replaces the template with a blank.