> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-in-email/dynamic-email.md).
# Dynamic Email
Dynamic Email addresses some of the inherent limitations of email technology, and enables a far richer survey (and overall email) experience. However, because it is a new standard, not all ESPs or email clients support it.
### Key differences between HTML email and “Dynamic Email Surveys
Dynamic email surveys provide a rich, personalized, web-like experience in email.
| HTML Email Surveys | Dynamic Email Surveys |
| ----------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Survey/campaign is hardcoded in the email as links. | Survey/campaign is dynamically displayed within the email. A code somewhat parallel to a website tag is placed in the email to enable it. |
| Clicking any answer (or any link in the email) opens up a web browser window. | Clicking an answer does not open up a web browser/new tab. Answer is captured within the email and without the need to pop open a new window. |
| You can only show one single-choice question in the email. Any followup questions need to be shown and completed on the web landing page. | You can have multiple questions inside the email itself |
| Question branching is not supported (only one question is supported) | You can have dynamic question branching, like on web. |
| Can only ask a single choice question in-email. | Multiple question types are supported, including free text. For now, the first question needs to be a single choice question. |
| User responses are tracked via custom links the client will embed in their email. | User responses are tracked via a code snippet from Console, without leaving the email. |
## Getting your Dynamic Email code snippet
You can find your code snippet in Console under Settings > Get Code Snippet > Dynamic Email.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-in-email/dynamic-email.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
