Email inserts

Common tags available in email communication

You can use all tags from Insert usage.

Opening a message in the browser

You can generate a URL that opens the message in a browser.

{{ synerise-open-in-browser }}

The URL is generated as plain text. If you want it to display as a hyperlink, add HTML, for example:

<a href="{{ synerise-open-in-browser }}">Click to open the message in a browser</a>

You can generate a URL that revokes the customer’s email communication agreement.

{{ synerise-resign-link }}

The URL is generated as plain text. If you want it to display as a hyperlink, add HTML, for example:

<a href="{{ synerise-resign-link }}">Unsubscribe</a>

If the email communication includes links, you can track their additional parameters (such as UTM) and click events.

  • If your link is stored as a jinja variable and then used as a variable in the HTML, you must use a preparelink tag to generate a link with the parameters:
    {% set a = "/" %}
    <a href="{% preparelink %}{{a}}{% endpreparelink %}">Link text</a>
  • If the link is defined in the template as plain HTML, the parameters and tracking are added automatically when parsing the HTML. You don’t need to use the insert:
    <a href="">Link text</a>

Example of a parsed link:

/?snrs_medium=email&snrs_action=newsletter.click&snrs_test=false&snrs_var=4715029&snrs_cp=6b716f86-a14d-4b8c-8795-872f7432a046&snrs_cl=b5d8c721-c2b7-42ac-9cd5-7714dedf73bf&snrs_category=client._DEVICE_.browser.mail&snrs_he=1940871749&snrs_redir=1

Validation

Whenever you use Jinjava in email communication, verify that it displays correctly for a few different test customers to make sure that the logic you applied covers all scenarios. If Jinjava fails to render, the communication is not sent to a customer at all.

If the sending failed, a message.notSent event is saved to the customer’s profile, with additional information in the extra property. This works both for test emails and already launched communications.

WARNING: If a tag is not opened/closed properly it is treated as plain text and does not cause an error.
Example: Missing } in {{ synerise-resign-link }

In the following example, a typo (missing w letter) when calling synerise-open-in-browser tag caused a wrong interpretation of the tag and a rendering failure.

{
    "action": "message.notSent",
    "eventUUID": "e0096c9d-8abc-4c4e-b75f-efa3c56934b0",
    "createDate": 1620912890658,
    "label": "dfbbb5f6-abf6-4c79-87db-f893359ffa5d",
    "params": {
        "clientId": 1382495929,
        "auth.internal": false,
        "info": "rendering failed",
        "testDelivery": true,
        "id": "dfbbb5f6-abf6-4c79-87db-f893359ffa5d",
        "campaignName": "Test",
        "extra": "Missing synerise-open-in-broser value",
        "time": 1620912890658,
        "title": "Test"
    }
}
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker