Summary / TL:DR: This will show you how the nested shared asset feature works in Blueshift and provides a few examples on how they can be utilized.
Headline (if needed)
To keep your email code clean, you can reuse the code in a shared asset in other shared assets. This is referred to as nesting. The shared asset that is used in another shared asset is called a ‘nested shared asset’.
Consider the following points when nesting shared assets:
You can only use a shared asset of the same type inside another shared asset. For example, a shared asset template of type HTML can include another shared asset template of type HTML only.
You can nest shared assets up to 1 level. For example,
Shared asset A does not reference any other assets. Shared asset B references shared asset A. Hence the nesting depth is 1 (B ←A), which is acceptable.
If we have shared asset C, it cannot reference shared asset B as the depth would become 2. (C← B ← A).
However, shared asset C can reference shared asset A (C ←A). In other words, it is possible to reference a shared asset in multiple shared assets.
The Templates using this asset section of the shared asset displays all the other shared assets that include this shared asset along with email templates that use the shared asset.
Example: Shared asset A does not reference any other assets. Share asset B references shared asset A. Hence the depth is 1 (B ← A).
Wrap up
Still need help?
We know this can be frustrating. To get further help open a Jira ticket.
Cannot find the article you’re looking for?
Suggest a new article here!