# How emails work

> What an email is in Releva, what the editor asks for, how product blocks and merge tags personalise it, how campaigns and workflows send it, and which events feed its results.

An **email** in Releva is a saved design with a sender, a subject and a body. Saving it sends nothing. A campaign or a workflow picks the email and sends it to the profiles of a segment; every send, delivery, open and click is recorded as an event on the profile, and those events are what the **Emails** list and the **Statistics** page count.

Emails live under **Marketing Channels › Emails**. The list, search and results are in [Find an email and check its results](https://releva.ai/documentation/guides/emails/find-an-email-and-check-its-results/); the per-email charts in [Check how an email performs](https://releva.ai/documentation/guides/emails/check-how-an-email-performs/).

## Building an email

**New email › Create Blank** opens an empty design in the visual editor (Stripo); **Browse Email Templates Gallery** starts from a ready-made template. Emails built this way carry the badge **VISUAL - STRIPO** on their card. The editor has two tabs:

**Content**

| Field                | What it does                                                                                                                                                                                                    |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sender Name**      | The name shown in the inbox. A new email starts with the shop’s default sender name from **Settings › Messaging**. Unicode is supported.                                                                        |
| **Name**             | The internal name you search for on the list. Must be unique within the shop; saving a duplicate fails with `Email name must be unique!`. A new email starts as `New email <date>`; a copy as `Copy of <name>`. |
| **Subject**          | The subject line. Required.                                                                                                                                                                                     |
| **Preview Text**     | Appears in the inbox just after the subject line. It does not show in the email body.                                                                                                                           |
| Editor canvas        | The body. Drag structures and blocks from the panel on the right; the editor’s own help covers styling.                                                                                                         |
| **Template Gallery** | Replaces the body with a template.                                                                                                                                                                              |
| **Test Email**       | Sends the email to an address you type, optionally rendered for one profile. Disabled until sender verification is complete (see below), unless the shop sends through Klaviyo.                                 |

**Advanced settings**

| Field                                | What it does                                                                                                                                                                   |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Sender Email**                     | The local part of the from-address; the shop’s sender domain is fixed after the `@`. Leave it empty to send from the shop’s default address. It cannot contain `@` or a space. |
| **Reply-to Email**                   | Where replies go. Leave it empty to use the shop’s default reply-to address.                                                                                                   |
| **If max emails per day is reached** | **Reschedule** (default), **Send anyway** or **Skip sending**. See [The daily limit](https://releva.ai/documentation/learn/emails/how-emails-work/#the-daily-limit).                                                                        |
| **Max Reschedules**                  | Shown only with **Reschedule**: how many days in a row Releva retries, 1 to 10, default 3.                                                                                     |

**Save** stays disabled while **Name** or **Subject** is empty, while the editor is still loading, or while **Sender Email** is invalid. Subject, preview text and sender name may contain merge tags; a broken tag also blocks **Save**. When the HTML has errors the form shows a red notice and asks you to confirm **I understand and want to save the email.** before saving.

The footer also has **Delete** (asks **Are you sure?** and reminds you to check that the email is not part of any workflows or campaigns; this cannot be undone), **Make a copy** and **Send**. **Send** does not send anything: it opens a dialog, **How would you like to send your email?**, that leads to a campaign or a workflow.

## Personalisation

* **Merge tags.** The text toolbar’s **Releva** category inserts profile fields, custom fields, coupons and survey values as `{{...}}` tags. They are rendered per recipient at send time.
* **Special links.** The link dialog offers **Unsubscribe link**, **Subscribe link**, **Subscription Management Link**, **View in browser link**, a loyalty programme link and one **Survey link** per survey. Every marketing email needs an unsubscribe link; profiles without one are skipped by campaigns when the shop runs external subscription management. See [How consent works in Releva](https://releva.ai/documentation/learn/consent/how-consent-works-in-releva/).
* **Product block.** A placeholder that is filled with products for each recipient when the email is sent. It takes a **product feed** (one with the Marketing Channels scope; see [How product feeds work](https://releva.ai/documentation/learn/product-feeds/how-product-feeds-work/)), a **template** that decides how each product is rendered, and the number of products to show. The card on the list shows a badge for each feed the email uses. Saving an email whose product block has no valid feed or template opens **Invalid Product Blocks Detected**. Gmail clips messages above about 102 KB, so keep the block to a dozen or so products.
* **What is stripped on save.** AMP elements are refused (**AMP elements are not supported**); `<iframe>` and `<script>` tags are removed with a notice (**Removed embedded content**).

## Sending

Emails are sent only by **Campaigns** (one-off and continuous) and **Workflows** (one-off, continuous and triggered). When a run reaches a profile, Releva renders the email for that profile, wraps every link through the click-tracking host, and hands it to the mailer. The mailer’s answer is recorded as a delivery or a bounce. Opens are recorded by a tracking pixel, clicks by the wrapped links.

Before any of that works, the sender domain needs two DNS records. Until they exist, the list and the editor show red alerts: **Campaign sending is disabled until the click-tracking DNS record is in place for your sender domain** and **Email sending is disabled until the DKIM DNS record is in place for your sender domain**. Both link to **Shop Settings** (**Settings › Messaging**), where the values to add are shown and checked.

### The daily limit

**Max Emails Per Day** in **Settings › Messaging** caps how many marketing emails one profile receives per day (default 3, 1 to 10). The email’s **If max emails per day is reached** setting decides what happens to a profile that is already at the cap when a continuous campaign or a workflow wants to send:

| Setting          | What happens                                                                                                          | Event recorded    |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- | ----------------- |
| **Reschedule**   | The message is moved to the next allowed slot at least 24 hours later, up to **Max Reschedules** times, then dropped. | `emailReschedule` |
| **Send anyway**  | The cap is ignored for this email.                                                                                    | `emailSend`       |
| **Skip sending** | The profile is left out of this run.                                                                                  | `emailSkip`       |

The limit applies to one-off and continuous campaigns and workflows. Triggered workflows ignore it.

## What gets counted

Each step of a send writes one event on the profile with the email’s id attached. The **Statistics** chart counts **unique profiles** per event, not raw events: a profile that opens five times is one open.

| Event                                   | Written when                                   | Shown as                                             |
| --------------------------------------- | ---------------------------------------------- | ---------------------------------------------------- |
| `emailSend`                             | The email is handed to the mailer              | **Sent**                                             |
| `emailDelivery`                         | The mailer accepts it                          | **Delivered**                                        |
| `emailBounce`                           | The mailer rejects it (permanent or transient) | **Bounces**                                          |
| `emailOpen`                             | The tracking pixel loads                       | **Opened**                                           |
| `emailClick`                            | A wrapped link is followed                     | **Clicks**, and the click map on **Click Analytics** |
| purchase events attributed to the email | An order follows a click                       | **Purchases**, **Revenue**                           |
| `emailComplaint`                        | The recipient marks it as spam                 | **Complaints**                                       |
| `unsubscribe`                           | The recipient uses the unsubscribe link        | **Unsubscribes**                                     |

On the list, **Delivered** and **Opened** are shown as a share of **Sent**, **Clicks** as a share of **Opened**, and **Purchases** as a share of **Clicks**. The people icon next to a number creates a segment of those profiles, so you can target “opened but did not buy” with the next campaign. See [How segments work](https://releva.ai/documentation/learn/segments/how-segments-work/).

To read email results outside the admin, ask an AI assistant connected to Releva’s MCP server. Its `get_campaign_report` tool returns the email results of your campaigns per day, week or month, grouped by campaign, brand or subject line. It counts unique profiles for opens and clicks and events for the other numbers, so its totals can differ from the **Statistics** page.

## Next steps

* [Find an email and check its results](https://releva.ai/documentation/guides/emails/find-an-email-and-check-its-results/): Search your emails and read sent, opened, clicks and revenue.
* [Check how an email performs](https://releva.ai/documentation/guides/emails/check-how-an-email-performs/): See the funnel, daily chart and products bought from an email.
* [How product feeds work](https://releva.ai/documentation/learn/product-feeds/how-product-feeds-work/): Learn how a feed picks the products your email shows.
* [How consent works in Releva](https://releva.ai/documentation/learn/consent/how-consent-works-in-releva/): Learn which customers can receive marketing email.