Best Practices: Snippets

Snippets are particularly useful for boilerplate like email footers or common text items. You can make them dynamic too.

We use snippets primarily for 3 use cases:

• Flexibility with email templates: If you have an email template with different sections, but you do not have content for each section, you can replace it with a blank snippet. Just go in Snipper designer and create a blank snippet. This will make sure that you don't have to delete any section in the email, and layout doesn't break.
• Universal Sections: Though I mostly recommend using Universal Tokens, but there are cases where we need universal snippets. As an example, the complete footer section for your landing pages or email. You can create that using a snippet in the design studio, and then use this snippet in all the assets you create. This would be helpful when you have to make any edits. You can directly edit and update the snippet, and approve all he associated assets using that snippet.
• Dynamic Content: You can always use segments in the snippets. This is helpful when you want to create a single footer snippet for all the asset but also show multi-lingual version as per the segment.

These are some of the use cases. I am sure there would be many more.