Prepare one deliberate campaign before automating a series. This guide connects audience reconciliation, content review, authorized dispatch and outcome measurement. Its fictional Fieldnotes example produces a launch brief; completing the brief does not send mail.
Campaign outcome
Fieldnotes invites consenting studio customers to book an autumn workshop. Its local campaign reference is FN-AUTUMN-01. Success means a confirmed booking in the booking system within seven days of sending. Opens and clicks support investigation but do not count as bookings.
Choose a broadcast for this announcement to a stored audience. A receipt triggered by one booking belongs in the application’s transactional flow. A reminder series needs its own trigger, exit condition and eligibility checks; it is an optional later step.
Name the marketer responsible for content, the operator authorized to send, and the person who will review results. Use Email marketing for the product context and Broadcasts for exact draft, schedule and cancellation operations.
Campaign audience
Record the selection rule: customers who requested workshop updates, excluding people who have already booked. Save the source revision, evaluation time and completed audience refresh.
Scroll horizontally to see more columns.
| Fictional contact | Evidence at review | Decision |
|---|---|---|
| Alex | Selected, with permission evidence and no applicable restriction | Include subject to the final dispatch checks. |
| Sam | Selected, with permission evidence and no applicable restriction | Include subject to the final dispatch checks. |
| Jules | Selected, but permission evidence is missing | Hold and resolve the missing evidence. |
| Mira | Selected, but suppressed | Preserve the restriction; exclude the affected sending context. |
A changed contact property does not automatically update static audience membership. Record total members, addressable contacts and the current sendable estimate separately. Members are resolved when sending starts, so the reviewed count is not a frozen recipient list or a delivery guarantee. Recheck audience counts and current preferences and suppressions before dispatch.
Review the content that can be sent
For FN-AUTUMN-01, the team reviews the published studio-invitation template at v3, with the subject “Your studio invitation.” The greeting has a contact-property fallback and the booking link opens the intended workshop. The brief’s version field records what the team inspected; it does not pin the scheduled broadcast to v3.
- Confirm a verified From domain and a monitored Reply-To address.
- Check subject, preheader, HTML, plain text, destination and unsubscribe path. Broadcasts use supported contact properties rather than arbitrary per-send parameters.
- Preview representative contacts and missing values. Preview sends nothing. Follow the template review workflow for languages and variable contracts.
- Record the published version, reviewer and review time. Coordinate subsequent publication: later sends use the current published template, and scheduled campaigns need another check after changes.
- Rehearse with a separate audience containing only sandbox recipients. A mixed audience can reach real people; simulated recipients still consume allowance.
No actual rehearsal or email-client test is claimed by this example. Record your observed results before approving production traffic.
Decide when to dispatch or stop
The authorized operator checks current sender verification, content, audience estimate, allowance and funds. For the fictional brief, the intended window is 19 September 2026 at 10:00 Europe/Madrid, 08:00 UTC. Record the actual chosen time and zone in your own campaign. Autosaving a draft does not send it.
Scroll horizontally to see more columns.
| Observed stage | Team action |
|---|---|
| Draft or scheduled | Review changes and current eligibility; editing remains possible before acceptance for sending. |
| Accepted or sending | Inspect recipients and events. Cancellation can skip remaining recipients but cannot recall mail already dispatched. |
| Failed or uncertain | Read the failure and reconcile recipients before selecting supported recovery. A lost response does not justify a duplicate campaign. |
Suppose the From domain loses verification after review but before the scheduled start. Hold the campaign, inspect its failure, restore verification and repeat the content and audience checks. If an allowance failure occurs partway through, inspect who was reached before retrying. Cancellation does not return consumed broadcast allowance. Follow the broadcast lifecycle for the current recovery procedure.
Measure the agreed outcome
Save the actual broadcast ID beside FN-AUTUMN-01. Review recipient results, bounces and complaints. Treat open and click counts with their documented privacy and scanner limitations.
At the agreed review, join campaign context to distinct confirmed booking IDs within the seven-day window. In an illustrative result, two confirmed bookings remain two bookings even if a person clicks three times. Keep unmatched bookings unassigned. This measures attributed outcomes; causal improvement requires a separately planned comparison such as the research experiment.
If the team later automates the journey, define its trigger, stop it when the booking completes, recheck eligibility at execution and reconcile retries. Contact synchronization and campaign dispatch remain separate operations.
Campaign brief
Campaign reference / content owner / authorized operator:
Intended action / outcome system / attribution window:
Audience ID / selection rule / source revision / completed refresh:
Permission evidence / current preferences and suppressions:
Members / addressable / sendable estimate / checked at:
Verified From / monitored Reply-To / category:
Template ID or slug / reviewed published version:
Subject / preheader / greeting fallback / destination / unsubscribe:
Languages / HTML and text review / actual client test evidence:
Sandbox-only rehearsal result / reviewer / review time:
Allowance and funds / local send time / time zone / UTC:
Stop rule / actual broadcast ID / current stage:
Post-review content or audience changes requiring another check:
Failure or unknown outcome / recipient reconciliation / recovery:
Distinct business outcomes / unmatched records / result review:
Optional automation trigger / exit / eligibility and retry policy:Prepare an Email workspace, then implement the approved brief through Broadcasts and its technical guide.