> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/amp-email.md).

# AMP Email

AMP emails are interactive emails: carousels, accordions, tabs and other parts that the reader can use inside the inbox, without opening a website. In Smartico you add an AMP version to any email and choose, for each email, whether it is sent. Every other email of your label stays as it is, so you can send AMP only for selected campaigns, for example promotions.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FLwmXOQp543JZF2Ys8aGN%2FAMP%20email%20example.gif?alt=media&amp;token=a4a968f4-6eb8-4535-9a79-038b44f1c14a" alt=""><figcaption></figcaption></figure></div>

## How AMP emails work

An email with AMP carries two versions of the same message:

| Version          | What it is                                             | Who sees it                                                                                 |
| ---------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
| **HTML version** | Your normal email (**Mail content**)                   | Every inbox that does not show AMP: Outlook, Apple Mail, and Gmail when AMP cannot be shown |
| **AMP version**  | The interactive version of the email (**AMP version**) | Gmail, Yahoo Mail and Mail.ru, when the sender is registered for AMP                        |

The inbox decides which version to show. If the AMP version cannot be shown (the sender is not registered, the email landed in Spam, or the AMP code is invalid), the reader sees the HTML version. Because of this, the HTML version is always sent and must be a complete email on its own.

## Before you start

* **Register your sender with the inbox providers.** Gmail shows AMP only from senders that Google approved for AMP. The email must pass SPF, DKIM and DMARC, and Gmail never shows AMP in the Spam folder. Yahoo Mail and Mail.ru have their own registration.
* **Use a Mailgun or SendGrid gateway.** Only these gateways deliver the AMP version. Recipients who get the email through any other gateway, or through a data-guard proxy, receive the HTML version only. See [Email Gateways Guide](https://help.smartico.ai/welcome/products/tools-and-guides/email-gateways-guide.md).

## Set up an AMP email

1. Go to **Marketing → Assets → Email** and open an email, or create a new one.
2. In **Setup**, set **Delivery mode** to **HTML + AMP**. The default is **HTML only**.
3. A new row, **AMP version**, appears under **Mail content**.
4. Build the AMP version:
   * **Edit in Vibe Studio** opens the AMP version in Vibe Studio. The email must be saved first.
   * The arrow next to the button opens **Edit in legacy editor**, a simple code editor (**Simple AMP Editor**). An empty AMP version opens with a ready, valid starter document: a carousel with two slides and a call-to-action button.
5. Click **Save**.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fk2hNhk4RlcbHT1xeiXWy%2Fimage.png?alt=media&amp;token=ec627ca9-5bcb-467f-b939-3b841d49feab" alt=""><figcaption><p>Delivery mode set to HTML + AMP and the AMP version row</p></figcaption></figure>

{% hint style="warning" %}
An email in **HTML + AMP** mode can be set to **Active** only when it has both the HTML version and the AMP version. A **Draft** can be saved without the AMP version.
{% endhint %}

If you switch an email back to **HTML only**, its AMP version is kept but not sent. Switching back to **HTML + AMP** brings it back.

### Build the AMP version in Vibe Studio

When you open the AMP version in Vibe Studio, only the AMP version is edited. The HTML version stays as it is, and the AI uses it as the source.

* **Convert HTML to AMP** (in the top bar) builds the AMP version from your HTML version. Texts, images, links and merge tags are kept. What AMP does not allow is removed or rewritten: scripts, forms, embedded video, Liquid tags, web fonts and CSS that AMP rejects. The current AMP version is replaced. The AI checks the result with the official AMP validator, lists what it changed, and then suggests AMP features that fit your email (for example a carousel or an accordion). Nothing is added unless you pick it.
* Ask for interactive parts in your own words, for example "show the three games as a swipeable carousel" or "put the updates in tabs".
* The preview shows the AMP version live. A badge above the preview shows whether the AMP version is valid (**Valid AMP**).
* **Apply & Save** puts the AMP version into the email and saves it.

The HTML version of a visual (drag-and-drop) email cannot be changed in Vibe Studio, but the AI can read it to build the AMP version.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fbg683HRjHP27xfanmIWf%2FGIF%20for%20AMP%202.gif?alt=media&amp;token=a13e85fe-60fd-4523-b654-68ab06988717" alt=""><figcaption><p>The AMP version in Vibe Studio with the Valid AMP badge and Convert HTML to AMP</p></figcaption></figure>

### AMP check in the email form

The email form checks the AMP version with the official AMP validator about a second after every change. A valid AMP version shows nothing. Otherwise the form shows:

<table data-search="false"><thead><tr><th>Message</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>N errors — Gmail will show the HTML version instead</strong></td><td>The AMP version is invalid. Each error is listed with its line and column, and a <strong>docs</strong> link to the AMP rule. The email can still be saved, but readers will see the HTML version.</td></tr><tr><td>Warning about Liquid</td><td>The AMP version contains <code>{% ... %}</code> tags. Liquid is not processed in the AMP version; these tags are delivered as plain text.</td></tr><tr><td>Warning about <code>&#x3C;style amp-custom></code></td><td>The CSS block is over 50,000 bytes. Keep it smaller; the AMP validator rejects it above 75,000 bytes.</td></tr><tr><td><strong>The HTML version looks like AMP markup</strong></td><td>The HTML version contains AMP code. Keep it plain HTML, because it is what every inbox without AMP shows.</td></tr><tr><td>Gateways that cannot carry AMP</td><td>Lists the gateways of your label that are not Mailgun or SendGrid. Their recipients get the HTML version.</td></tr><tr><td>Data-guard proxy</td><td>Your label sends some or all emails through a data-guard proxy. Those recipients get the HTML version until the proxy supports AMP.</td></tr><tr><td>Variations without an AMP version</td><td>Lists the active content variations that have no AMP version yet. They send the HTML version only.</td></tr></tbody></table>

## Personalization, links and tracking

* **Merge tags** work in the AMP version: `{{state.*}}`, `{{label.*}}`, `{{event.*}}` and the other Smartico tags are filled in for each player, as in the HTML version.
* **Liquid does not work in the AMP version.** AMP uses `{{ }}` for its own placeholders, and Liquid would break them. Keep Liquid logic in the HTML version. A Liquid email can still have an AMP version; only its HTML version is processed with Liquid.
* **Deep links** such as `dp:unsubscribe` are replaced with real links, as in the HTML version. Include an unsubscribe link in the AMP version too.
* **Click tracking:** links in the AMP version are tracked. Links that AMP fills in itself (inside an AMP template, or with `{{` in the address) are left as they are and are not tracked.
* **Open tracking:** Smartico adds an open-tracking pixel to the AMP version.
* **Automated UTMs** are added to the links of the AMP version as well, if they are turned on for your label.

## Content variations

The **Delivery mode** is set on the main email and applies to all its content variations. A variation shows it as read-only text. Each variation has its own AMP version. A variation without an AMP version sends the HTML version only, and the main email lists such variations in its AMP check.

## Size limits

* The AMP version may be up to **100 KB**. A larger AMP version cannot be saved.
* Keep the `<style amp-custom>` block under 50,000 bytes.
* The HTML version keeps its own limits: a warning over 100 KB and no saving over 200 KB. See [Email](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/email.md).

## Testing an AMP email

1. Save the email in **HTML + AMP** mode.
2. Click **Send Test Mail** and choose a Mailgun or SendGrid gateway. The test email carries the AMP version too.
3. Open the email in a Gmail inbox. Gmail shows AMP only from a sender that Google approved, so test with your registered sender address.

If Gmail shows the HTML version, check the AMP check in the email form for errors, and make sure the email is not in Spam and passes SPF, DKIM and DMARC.

## What happens when the AMP version cannot be sent

* **Invalid AMP version:** the email is sent with both versions, and Gmail shows the HTML version.
* **Empty AMP version, or an error while preparing it:** the email is sent with the HTML version only, so the player still gets it. Smartico sends an alert email about the problem to your label's alert address.
* **Gateway without AMP support or data-guard proxy:** the HTML version only.

## Finding AMP emails

In **Marketing → Assets → Email**, emails in **HTML + AMP** mode show a blue lightning icon next to the mail type. To list them, click **Filter → Delivery mode** and choose **HTML + AMP**. Changes to the AMP version are recorded in the email's **History**.

## The earlier AMP setting

Before the **Delivery mode** setting, AMP was turned on with `{"amp-html":true}` in the email's **Extra parameters**, or with the `amp-html` parameter of a Mailgun gateway. These settings copy the HTML version into the AMP part of the email, so the email has no real AMP version, and the gateway parameter applies to every email sent through that gateway.

They still work for emails in **HTML only** mode. For emails in **HTML + AMP** mode they are ignored. We recommend moving to **Delivery mode → HTML + AMP** for the emails that need AMP, and removing the gateway parameter, so that all your other emails are sent as plain HTML.

## Frequently Asked Questions

**Q: Do I need to make every email AMP?**

**A:** No. **Delivery mode** is set per email. Only the emails in **HTML + AMP** mode (and their variations) send an AMP version. All other emails are not affected.

**Q: Which inboxes show the AMP version?**

**A:** Gmail, Yahoo Mail and Mail.ru, for senders registered for AMP with them. All other inboxes, such as Outlook and Apple Mail, show the HTML version.

**Q: I sent an AMP email, but Gmail shows the normal version. Why?**

**A:** Check that the sender address is approved by Google for AMP, that the email passes SPF, DKIM and DMARC, that it is not in Spam, and that the AMP check in the email form shows no errors. Also check that you sent it through a Mailgun or SendGrid gateway.

**Q: Can I use Liquid in the AMP version?**

**A:** No. Use merge tags such as `{{state.user_first_name}}` in the AMP version. Liquid works only in the HTML version.

**Q: Which email gateways support AMP?**

**A:** Mailgun and SendGrid. Other gateways deliver the HTML version only.

**Q: Can I build the AMP version without writing code?**

**A:** Yes. Open the AMP version in Vibe Studio and click **Convert HTML to AMP**, or describe what you want in the chat. The AI writes the AMP code and checks it with the AMP validator.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/crm-automation/communication-channels/amp-email.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
