AMP version of the message
You can add an AMP version to email messages with sending conditions:
- instant
- scheduled
To do this you need to:
- go to Mailings → Messages → Message editor
- create HTML-version of the e-mail using any of the available methods (choose a template, create it in HTML-editor, etc.).
- click the button of adding AMP-version in the message preview:
In order for the recipient to see the AMP-version of the email, a number of conditions must be met:
- AMP-versions of e-mails is supported only by Gmail, Mail.ru and Yahoo. Any other mail clients will receive HTML or text version
- The sending domain must have correct DNS. Pay special attention to:
- SPF
- DKIM - the domain from email must match the domain of the DKIM signature.
- DMARC - policy settings should be set in blocking mode - quarantine or reject
- Sending domain for the last 3 months must send at least 5000 emails per month
- The sending domain must be verified:
- в mail.ru - if there are contacts in the database with this mailbox
- в gmail - If there are contacts in the database with this mailbox.
- Note: gmail asks that you do not use placeholder strings in the email sent for verification: {name} and {count} or test strings such as [Test] , [Proof mail] and [Sample]. In this case, we recommend that you refrain from using dynamic content in the AMP version
- в yahoo - if there are contacts in the database with this mailbox
- AMP-version must be correctly written. Syntax highlighting works in the AMP editor: unclosed tags will be highlighted in red. Additional requirements can be found at the links below:
otherwise the AMP version will not be delivered and the recipient will only see the HTML version of this email.
In order to check if an email has AMP-version, you can go to Mailings → Messages → Message details → “Information” tab → Message details section:
Dynamic content in the AMP version
You can add dynamic content to the AMP version of an email using the button {{}}:
When generating dynamic content, variables like {{}} will be ignored in the AMP version if they are written inside a tag <template> - this is done so that you can use external variables from your JS script.
Note, gmail asks that you do not use placeholder strings in the email sent for verification: {name} and {count} or test strings such as [Test] , [Proof mail] and [Sample]. In this case, we recommend that you refrain from using dynamic content in the AMP version.
Features of AMP version
Some platform features work only on the HTML version of the email and do not apply to AMP:
- click map works only for the HTML version and does not take clicks in AMP into account
- editing links after sending an email will only work for the HTML version of the email
We do not recommend using the AMP version and the “Display images as attachments” feature at the same time. Sending images as attachments may cause a DKIM error (due to changes in message structure), and without DKIM authentication, AMP will not display correctly according to Gmail rules.
When creating a split test version of an email: the state of the AMP version is copied relative to the previous version of the email. In each version, you can edit and save the state of the AMP version independently.
You can save an AMP-version email as a template and reuse it as needed.
UTM tags and URL parameters added through the interface in the message editor will be substituted for links in the AMP version.
To remove the AMP version from an email, open the AMP version editing window, select and delete all text. Save the changes using the “Save” button.
AMP version statistics
• In Message details
Statistics for AMP and HTML versions of one email are recorded and displayed separately.
The statistics table for the AMP version is displayed only if the AMP version was added to an instant or scheduled email message.
You can view the statistics in the Mailings → Messages → Message details → Reports. On the “Table” tab you will see reports on activity metrics in the email separately for HTML and AMP versions.
Since some of the metrics for HTML and AMP are common - they will simply be duplicated in both tables. We're talking about:
- Sent
- Delivered
- Bounces
- Complaints
Unique for AMP metrics:
- Opens- non-unique AMP-version opens
- Unique opens - unique AMP opens
- Clicks - non-unique AMP clicks
- Unique clicks - unique AMP clicks
- Clicked - unique contacts, that clicked in AMP version
- Unsubscribers - number of unsubscribes in AMP version
The clicks map is bound only to the HTML version of the email, activity in AMP is not counted or displayed on it.
Orders made through clicking on tracking links from the AMP version of the email are not yet recorded and are not counted in the general statistics.
• In reports on messages
Statistics in general reports (sections: Reports → Dashboards and Reports → On messages) are displayed without duplication.
For example: if one contact opened one and the same email in both HTML and AMP 1 time, the general reports and dashboard will show:
- Opens - 2
- Unique opens - 1
• In scenarios
Activity in the AMP version is taken into account in the logic of the initial “Message” block:
- Open - counts contacts who have opened any version of the email. Including those who have opened only the AMP version
- Click -
- Any link - counts contacts who clicked any version of the email. Including those who clicked only in the AMP version
- A selected link from the list - the list displays links of both HTML and AMP versions of the e-mail. Clicks in either version will be counted to trigger a script on that block.
• In segments
Activity in the AMP version of the email is taken into account when setting up segmentation for messages in conditions:
- Sent
- Open
- Clicked - including clicking on a specific link
- Delivery bounces
- Unsubscribe - from the Email channel with an unsubscribe reason from the email
If the message was sent/opened/clicked etc. in any of the email versions, the segment will find the relevant contacts.