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 Blueshift has a feature that allows you to reference a shared asset with 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)You can read more about it here.

...

Examples

Branding Shared Asset:

...

Unsubscribe Link Shared Asset:

...

Main shared asset that references both assets from above:

...

Using the main shared asset to build a template:

...

As you can see the template only references the main shared asset to dynamically build the content. The list code used from the transaction is LISTCODE4 which drives what brand/service name, editor, and domain/website is displayed.

...

...