Code snippets

Tokens

You can use email provider tokens/tags/variables throughout your template and emails as you normally would and they will be read by your ESP when exporting your emails to it.

This includes using tokens in text, links, and images as you build and edit emails in the visual editor. Note that images may appear to be broken if a token is used for an image's path.

Example:

Hello *|FNAME|*

<div class="block-edit">Hello *|FNAME|*,</div>

Code blocks

If you would like to use custom code within an email or page, like for segmenting content, you can use be-code-edit to have anything within it output as raw code. It can also be enabled as a reusable section or component. This allows for separating your logic from content. With content using tokens/tags/variables.

Example:

<code class="be-code-edit" >
%%[ IF @member=="True" THEN ]%%
</code>

Note that code used within the code block in a template may cause your code to break. Actual code should only be added when building or editing an email or page within the visual editor.

To include saved snippets for your team to use, you can enter your code in the visual editor and pin it for reuse, or save a layout with the code throughout an email or page.

Code outside the body

Adding data-area="head" will place the code within the head tag on export. This code area should be placed at the very top, right after your opening body tag.

Hiding code

If you want to prevent certain areas from being seen in Blocks Edit when working in the visual editor, wrap your code with the block-hide option to essentially comment it out while viewed in the editor.

Example:

<!-- block-hide -->
<p>Content</p>
<!-- end-block-hide -->

When the email or page is exported, the hidden code gets output without being commented out.