> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snowdoughnut.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Email campaign brief
> A fill-in workbook for a single email campaign or automated flow: objective, conversion action, segment and suppression, content, send settings, deliverability, and the briefs it runs on.
*This page is a workbook. Fill it in top to bottom before anything is built in your email platform. Each section has a "Concept review" dropdown explaining what the section is for. The dropdowns explain the thinking; the decision is yours.*
This brief sits between the [marketing campaign brief](/marketing-campaign-brief), which covers strategy across every channel, and your email platform, where the send is built.
Grayed `E.g.` text is a placeholder. Delete it and replace it with your own. Examples use **Doughnut Labs**, a SaaS company that sells disruptive Doughnut Technology.
Email maps onto the same three levels as the ad platforms: the campaign or flow is the campaign, the segment is the ad set, and the individual send is the ad. The [naming conventions](/naming-conventions-overview) apply at all three, using the list and segment type values in the [ad set / ad group / variant conventions](/ad-set-group-naming-conventions).
## Setup
| Field | Fill in |
| :--------------------------------------------------------------- | :------------------------------------------------------------------- |
| [Owner](/glossary#owner) | *E.g. Aisha Bello* |
| Builder | *E.g. Aisha Bello* |
| [Marketing campaign brief](/marketing-campaign-brief) | *E.g. [Doughnut Labs "Fresh Batch" spring trial push](https://link)* |
| Email platform | *E.g. \[your ESP]* |
| Brief name ([file naming conventions](/file-naming-conventions)) | *E.g.* `DOC_email-fresh-batch-nurture_2026-08-07_v01` |
| Send or flight dates | *E.g. Three-touch sequence, 22 Apr to 6 May 2026* |
## Send type
| Field | Fill in |
| :-------------------- | :--------------------------------------------- |
| Type | *E.g. Automated sequence* |
| Number of sends | *E.g. Three* |
| Trigger, if automated | *E.g. Contact enters "trial eligible" segment* |
| Timing between sends | *E.g. Day 0, day 4, day 10* |
| Exit condition | *E.g. Contact starts a trial* |
| Type | What it is |
| :----------------- | :---------------------------------------------------------------- |
| Broadcast | A one-off send to a segment at a chosen time |
| Automated sequence | A fixed series of sends triggered by entry into a segment |
| Triggered | A single send fired by one behavior, such as an abandoned signup |
| Transactional | An account or order message, sent regardless of marketing consent |
An exit condition is not optional on an automated sequence. Without one, a contact who converts on send one still receives sends two and three, asking them to do something they have already done.
The type decides how long the brief stays live. A broadcast is finished the day it sends. An automated sequence keeps running against new contacts for months, which means its copy, its links, and its offer all keep being seen long after the campaign that produced it has closed.
That difference is why the exit condition and the review date matter more on a sequence than on a broadcast. An unreviewed sequence is the most common way an expired offer keeps going out to new contacts.
## Objective and conversion action
| Field | Fill in |
| :---------------------------------------------------------------------- | :--------------------------------------------------------- |
| Objective | *E.g. Convert trial-eligible contacts into started trials* |
| Reader action | *E.g. Clicks through and completes the trial signup form* |
| Conversion action, from the [event tracking plan](/event-tracking-plan) | *E.g.* `Trial Started` |
| How the conversion is attributed to the email | *E.g. UTMs plus platform click tracking* |
Open rate and click rate describe what happened inside the inbox. Neither says whether the email did its job, and open rate in particular has been unreliable since mail privacy features began pre-fetching images.
Naming a conversion action from the [event tracking plan](/event-tracking-plan) is what connects the send to the outcome it was meant to produce. It also makes email comparable to the paid channels in the same campaign, which is not possible when one channel reports conversions and the other reports opens.
## Audience
| Field | Fill in |
| :----------------------------------------------------- | :------------------------------------------------------------------------------------ |
| [Customer profile](/customer-profile-library-overview) | *E.g. [Mid-market RevOps lead](https://link)* |
| Segment definition | *E.g. Signed up, no trial started, active in last 90 days* |
| Estimated size | *E.g. 4,200 contacts* |
| Suppressions | *E.g. Current customers, unsubscribed, hard bounced, contacts in the onboarding flow* |
| Consent basis | *E.g. Opted in at signup, consent date stored* |
List suppressions explicitly, including other campaigns sending in the same window. A contact receiving three unrelated emails from you in one day is a deliverability problem as much as an experience one.
A segment is a query, and a query written into a brief can be checked by someone else before it sends. A segment built directly in the platform at send time usually cannot, and that is where the wrong-audience sends come from.
Consent basis belongs here because it governs whether the send is allowed at all, separately from whether it is a good idea. Recording where consent came from and when means a later question about a contact's inclusion has an answer that does not depend on anyone's memory.
## Content
| Field | Fill in |
| :----------------------------------------------------------- | :-------------------------------------------------------------- |
| [Copy brief](/ad-copy-standards) | *E.g. [COPY\_fresh-batch-email\_2026-04-02\_v01](https://link)* |
| Copy template | *E.g.* [Email copy template](/email-copy-template) |
| Subject line | *E.g. Your doughnut stack is one afternoon away* |
| Preview text | *E.g. No card. No sales call. Cancel any time.* |
| Primary call to action | *E.g. Start free trial* |
| [Creative brief](/creative-brief), if the email needs design | *E.g. [Fresh Batch email header brief](https://link)* |
| Template | *E.g. Standard single-column promotional template* |
Design has to meet the [email creative specs](/email-creative-specs).
Subject line and preview text are read together in the inbox and should be written together. Preview text left unset falls back to whatever the first line of the email happens to be, which is often an image alt tag or a "view in browser" link.
Keeping the copy in the [copy brief](/ad-copy-standards) and the [email copy template](/email-copy-template) rather than typing it into the platform means it gets reviewed against the campaign's message before it goes out, and stays findable in the [copy drive](/copy-drive) afterward.
## Send settings
| Field | Fill in |
| :--------------------- | :-------------------------------------------------------------------------------- |
| From name | *E.g. Priya at Doughnut Labs* |
| From address | *E.g. [priya@mail.doughnutlabs.example](mailto:priya@mail.doughnutlabs.example)* |
| Reply-to address | *E.g. [hello@doughnutlabs.example](mailto:hello@doughnutlabs.example), monitored* |
| Send time and timezone | *E.g. 09:00 in the recipient's local time* |
| Sending domain | *E.g. mail.doughnutlabs.example* |
The reply-to address is the field most often set to something nobody reads. A campaign that invites a reply and then discards it costs more than the replies were worth, and on some providers reply behavior feeds into how your mail is treated.
From name and sending domain are recognition signals as much as technical settings. Changing either mid-campaign resets the familiarity a list has built with you, so both belong in a brief rather than in whatever the platform defaulted to.
## Deliverability
| Check | Fill in |
| :---------------------------------------------- | :------------------------------------------------ |
| SPF, DKIM, and DMARC pass on the sending domain | *E.g. Yes, verified 4 Apr* |
| List-Unsubscribe header present | *E.g. Yes, one-click* |
| Unsubscribe link in the body | *E.g. Yes, in the footer* |
| Physical address in the footer | *E.g. Yes* |
| Send volume against normal | *E.g. 4,200, within normal range for this domain* |
| Seed or inbox placement test run | *E.g. Yes, 3 Apr* |
Authentication is a hard requirement rather than a best practice. Major mailbox providers reject or filter bulk mail that fails SPF, DKIM, or DMARC, and a large send from a domain with no sending history can be throttled regardless of authentication. Warm a new domain before a large campaign rather than during one.
Deliverability problems present as performance problems. A send with a weak subject line and a send that landed in spam both show a low open rate, and only one of those is fixed by rewriting copy.
Checking authentication and running a placement test before the send separates the two questions in advance. It is a short check that prevents a long argument about creative that was never the cause.
## Landing page and destination
| Field | Fill in |
| :------------------------------------------------------ | :----------------------------------------------------------- |
| Destination | *E.g. [doughnutlabs.com/lp/fresh-batch-trial](https://link)* |
| From the [landing page library](/landing-page-library)? | *E.g. Yes, existing page* |
| Does the page match the email's offer and CTA? | *E.g. Yes, same offer and wording* |
## Naming and tracking
| Level | Name | Convention |
| :--------------- | :--------------------------------------------------------------------------------------------- | :-------------------------------------------------------------- |
| Campaign or flow | *E.g.* `Email-Nurture-Trial-TOFU` | [Campaign naming conventions](/campaign-naming-conventions) |
| Segment | *E.g.* `20260401-ABTRIAL-ESUB` | [Ad set / ad group / variant](/ad-set-group-naming-conventions) |
| Send | *E.g.* `FreshBatch-EMAIL-FREETRIAL-TRY-LP-01` | [Ad naming conventions](/ad-name-conventions) |
| UTMs | *E.g.* `?utm_source=email&utm_medium=email&utm_campaign=fresh-batch-trial&utm_content=send-01` | [UTM standards](/utm-standards) |
Use `utm_content` to tell the sends in a sequence apart. Without it, three touches collapse into one line in reporting.
## Experiment
Optional: fill this in only if the send carries a controlled test with a planned sample.
| Field | Fill in |
| :------------------------------------ | :--------------------------------------------- |
| [Experiment ID](/experiment-ids) | *E.g.* `TEST04` |
| [Experiment brief](/experiment-brief) | *E.g. [Subject line test brief](https://link)* |
| What varies | *E.g. Subject line only. Body identical* |
| Split and sample | *E.g. 50/50, full list, 4,200 contacts* |
A platform's built-in subject line test that picks a winner after a few hours is not the same as a controlled experiment. It stops early by design, which is the [peeking](/glossary#peeking) problem. If the result is going into the learning library, run it through [creating an experiment](/creating-an-experiment) instead.
## Measurement
| KPI | Target | Actual |
| :------------------------ | :------------ | :----------------- |
| *E.g. Click-through rate* | *E.g. ≥ 3%* | (blank until send) |
| *E.g. Trial signups* | *E.g. 120* | (blank until send) |
| *E.g. Unsubscribe rate* | *E.g. ≤ 0.3%* | (blank until send) |
| \[add KPI] | | |
**Where this campaign is reported:** *E.g. [Lifecycle dashboard](https://link), rolled into the weekly report*
## Post-send
| Item | Link or date |
| :---------------------------------------------------------- | :-------------------------- |
| Pre-send checklist run | *E.g. 21 Apr, Aisha Bello* |
| Send date | *E.g. 22 Apr* |
| Review date, for sequences | *E.g. 22 Jul, quarterly* |
| Filed in the [campaign library](/campaign-library-overview) | *E.g. Email folder, 22 Apr* |
Set a review date for every automated sequence. A sequence with no review date keeps sending an offer that may have expired, to contacts who joined the list long after the campaign closed.
## Related resources
* [**Launching an email campaign**](/email-campaign-process) The process this brief runs on.
* [**Email pre-send checklist**](/email-pre-send-checklist) The pass to run before hitting send.
* [**Email copy template**](/email-copy-template) and the [**email creative specs**](/email-creative-specs)
* [**Marketing campaign brief**](/marketing-campaign-brief) The parent brief this one sits under.
* [**Campaign library**](/campaign-library-overview) Where this brief is filed.