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.
Blueshift has a feature that allows you to reference a shared asset with in another shared asset. 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:
Only the main shared asset is referenced within the template which is used to build the content dynamically. This include things such as the brand/service name, editor, and domain/website.
The list code used from the transaction is LISTCODE4 and so you can see the content that was rendered based on that.
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!