> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/channels/email/interactive-emails.md).

# Interactive Emails

Add interactive elements to your email campaigns to increase engagement.

Interactive emails allow recipients to engage with content directly in their inbox — without needing to visit a separate landing page. Using CSS and HTML techniques, you can add movement, navigation, and input to your emails.

Interactive emails are more complex to build than standard emails and require support from the UbiQuity team. Contact UbiQuity to discuss what is possible for your campaigns.

***

### What you can do with interactive emails

* **Accordions and menus** — group information into collapsible sections
* **CSS animations** — add movement and motion to your template
* **Carousels** — let recipients scroll through a gallery or product range
* **Embedded video** — allow video to be played directly in the email
* **Animated GIFs** — draw attention with motion (*note: GIFs are not supported in Outlook versions prior to 2019*)
* **In-email forms** — capture information entered directly into the email, such as NPS scores or survey responses

***

### Compatibility

Interactive elements are supported on a limited number of email clients. For unsupported clients, a fallback version of the email must be provided so that all recipients have a functional experience.

| Client                           | Supported |
| -------------------------------- | --------- |
| Apple iOS (iPhone/iPad)          | Yes       |
| Samsung (default email client)   | Yes       |
| Apple Mail (desktop)             | Yes       |
| Microsoft Outlook                | No        |
| Microsoft Outlook for Mac        | No        |
| Gmail (desktop and mobile app)   | No        |
| Outlook (desktop and mobile app) | No        |
| Yahoo                            | No        |

Before building an interactive email campaign, check the proportion of your database using supported clients — this will help determine whether interactive elements are worth the additional investment and whether the fallback experience is sufficient for your audience.

***

### Fallback emails

Because some recipients will open your email in a client that does not support interactive elements, a fallback version of the email must be created alongside the interactive version. The fallback is a standard email using similar content and assets.

In some cases this is a simple swap of assets. In others, the layout or content may need to be adjusted for the fallback to make sense on its own.

***

### Tracking

Tracking for interactive emails is currently limited to external URL links and the View Online link. Events within the email — such as scrolling, entering fields, or clicking interactive elements — are not tracked directly. Responses captured in-email (such as survey answers) can be passed to a UbiQuity Survey to record and report on.


---

# 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://docs.ubiquity.co.nz/documentation/channels/email/interactive-emails.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.