Skip to main content
Take an email campaign from an approved marketing campaign to a sent, correctly tracked, correctly segmented send. This process covers all three levels, campaign or flow, segment, and individual send, because the inputs are gathered once for the whole build.

What you’ll end up with

Three things that point at each other:
  • A completed email campaign brief, filed in the campaign library under the Email folder.
  • A sent campaign or a live sequence, named per the three naming conventions, tagged with UTMs that distinguish each send, driving a conversion action defined in the event tracking plan.
  • Links back from the marketing campaign brief to this campaign’s brief and finished copy.
One person, the owner, is accountable for all three. A builder, person or AI agent with platform access, can audit the inputs, draft the brief, build the segment from its written definition, assemble names and UTMs, and run the checks. Two gates stay a person’s whoever builds: the consent attestation, and pressing send.

Before you start

Every input below has to exist, or be deliberately marked as not applicable, before the build starts.
Consent basis and domain authentication are the two rows that stop a send rather than delay it. Neither is fixable in the hour before a scheduled send, so check both first.

The process at a glance

1

Confirm the campaign has a parent

Every email campaign belongs to a marketing campaign brief.
2

Gather the inputs

Work the table above. Pick what exists, brief what doesn’t.
3

Fill in the email campaign brief

Send type, objective, conversion action, audience, content, send settings, deliverability.
4

Build the segment and its suppressions

From the written definition, not from memory at send time.
5

Write the copy and build the email

Copy from the copy brief into the email copy template, then into the platform.
6

Assemble names and UTMs

All three naming levels, with utm_content distinguishing each send.
7

Send test emails and render-check

Real inboxes, real devices, light and dark mode.
8

Run the pre-send checklist

The last pass before it goes out.
9

Send, then link back

Send or activate, then link the finished copy into the marketing campaign brief.
10

File the brief and set a review date

Into the campaign library. Sequences get a recurring review date.

1. Confirm the campaign has a parent

Open the marketing campaign brief this send belongs to and confirm email is listed in its channels table with a reason.

2. Gather the inputs

Work down the table in Before you start. Segment. Write the segment as a definition in the brief before building it in the platform. A written query can be checked by someone else; a segment built at send time usually cannot, and that is where wrong-audience sends come from. Suppressions. List them explicitly, including other campaigns sending in the same window. Overlapping sends are a deliverability problem as much as an experience one. Consent. Confirm every contact in the segment has a recorded basis for receiving marketing email. This is not a step to take on trust, and it is not the builder’s to attest: a named person confirms the basis and the confirmation is recorded in the brief. Destination. Check the landing page library for a page that already serves this offer. The page has to carry the same offer and the same call-to-action wording as the email, or the click is wasted.

3. Fill in the email campaign brief

Copy the email campaign brief and work down it. Every campaign or sequence gets its own. If this is an automated sequence, pay particular attention to the trigger, the timing, and the exit condition. A sequence with no exit condition keeps asking a contact to do something they have already done.

4. Build the segment and its suppressions

Build the segment from the written definition. Then check the count against the estimate in the brief; the comparison is mechanical, and a sharp difference is a finding to raise, never to resolve silently. A count that differs sharply from the estimate means the query does not say what you thought it said. Resolve that before sending rather than after.

5. Write the copy and build the email

Copy comes from the copy brief, drafted into the email copy template, and only then into the platform. Write the subject line and preview text together, since they are read together in the inbox. Design has to meet the email creative specs: body width, image weight, dark mode behavior, and the total HTML size that keeps the message from being clipped.

6. Assemble names and UTMs

Write all three names and the tagged URLs into the brief. Use utm_content to distinguish each send in a sequence. Without it, three touches collapse into one line in reporting and you cannot tell which one did the work.

7. Send test emails and render-check

Send a real test to real inboxes, not just the platform’s preview. A rendering service can stand in for the device wall, and the builder can run the link, token, and clipping checks; the dark-mode read stays a person’s eyes.
  • Check at least one webmail client, one mobile app, and one desktop client, directly or through a rendering service.
  • Check light and dark mode. (human eyes) Dark mode handling varies sharply between clients, and a logo that disappears against an inverted background is the most common failure.
  • Click every link in the test, including the unsubscribe link and any link inside an image.
  • Confirm personalization tokens resolve, and that the fallback is sensible when a field is empty.
  • Confirm the email is not clipped. See the email creative specs for the size threshold.

8. Run the pre-send checklist

Run the email pre-send checklist. A person presses send. A broadcast is irreversible, so sending the broadcast or activating the sequence is the owner’s act, the email counterpart of flipping a campaign live. Then:
  • Paste the finished copy link into the marketing campaign brief and file it in the copy drive.
  • Confirm the first conversions are attributing correctly rather than assuming they will; an automated check that alerts when they don’t is the builder’s way to do it.
  • Record the send date in the brief.

10. File the brief and set a review date

File the completed email campaign brief in the campaign library, under the Email folder, named per the file naming conventions. For an automated sequence, set a recurring review date, and make it a scheduled pass: the pass sweeps live sequences for expired offers, dead links, and lapsed claims, and flags findings to the owner. A sequence keeps sending to new contacts long after the campaign closes, and an unreviewed one is the most common way an expired offer stays in circulation.

Exceptions

  • The send is transactional. Order confirmations and account messages are not marketing sends and do not need a marketing consent basis. They still need correct authentication, working links, and a recorded owner.
  • The send is a small internal or list-hygiene message. It still gets a brief, but sections like creative, experiment, and KPI targets may not apply.
  • The campaign is cancelled before sending. File the brief with a short note on why it stopped. The segment definition and copy usually get reused.
Type: process
Domains: email, campaign, tracking, approval
Provides: process:email
Uses: campaign-brief, checklist-prelaunch:email, copy-brief, copy-template:email, creative-brief, creative-specs:email, customer-profile, email-brief, experiment-brief, library:campaign, library:copy, library:event, library:landing-page, naming-convention, utm-rules
Best for: channel: email
Triggers: “Send an email campaign” · “Launch the nurture sequence” · “Set up and test our newsletter send” · “Build an automated email flow”Asks, in order:
  1. Which approved marketing campaign is this for? Options: campaign-brief. Skip when: in context.
  2. Is this a marketing send, transactional, or an internal/list-hygiene message? Options: send-scenario. Skip when: obvious.
  3. Who will confirm the consent basis and press send? Options: your answer. Skip when: owner recorded.
  4. Is the sending domain authenticated (SPF, DKIM, DMARC)? Options: your answer. Skip when: verified in brief.
Output: Email brief, built segment with count check, copy in template, names and per-send UTMs, render tests, pre-send checklist; send by owner; brief filed; recurring review pass for sequences.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on November 2, 2026