Costs
Part of A practical guide to email campaign planning, start to finish
Case studies in email campaign planning, compared side by side
Email campaign planning case studies examine two documented public-sector campaigns, preserving audience, method, reported results, attribution limits, and lessons.
What to take away
- Side by side, the six cases share a planning sequence but not a measurement standard.
- The reported signals run from a few referrals and weekly view counts to delivery receipts, subscription totals, and registration numbers. The CDC case reports no campaign figure.
- These are documented public-sector examples, not commercial benchmarks, endorsements, causal proof, forecasts, or promises of equivalent performance.
- The Growth Hubs example shows the difference between broad awareness activity and a targeted campaign that produced a few reported referrals.
- The pension example connects a plain-language content theme with email and web activity while leaving employer forwarding and causal limits visible.
- Four further campaigns, run by Transport for London, the UK Government Digital Service, the US CDC, and the UK Electoral Commission, add named audiences, send volumes, and reported results to the comparison.
Email campaign planning case studies are useful only when their purpose, audience, intervention, period, measures, context, and limitations remain attached. The six examples below concern public-sector communication in the U.K. and U.S. They do not establish what a commercial campaign will achieve.
Case 1: two targeted Growth Hubs campaigns
A U.K. government Growth Hubs pilot evaluation describes two rounds of targeted email with HMRC. A 2015 general-awareness send went to 22,000 businesses, but the report says impact could not be determined. A later international-trade campaign produced a few referrals, according to the participating Growth Hub.
The narrow planning lesson is to distinguish a broad distribution count from an observable business outcome. Define the target and referral path before launch, and retain the report's weak-attribution language.
Case 2: Pension Awareness Week
Wiltshire Pension Fund's 2023 annual report describes a 2022 campaign designed to remove pension jargon through short fact sheets distributed to active and deferred members and to employers for onward sharing. It reports about 60,000 email views and 3,440 website views during the week, compared with 1,375 in the previous week.
Employer forwarding complicates the denominator; an email view is not proven comprehension; the week-over-week website comparison may reflect other differences.
The transferable lesson: define the audience, simplify the message, coordinate the destination, and publish the comparison honestly. A documented email campaign planning checklist keeps audience, message, and destination decisions from drifting apart.
Case 3: Transport for London travel alerts
Transport for London runs a service-status email program covering Tube, bus, and rail lines. Subscribers choose lines and receive disruption alerts, planned-closure notices, and weekly travel summaries. Sign-up is free through the TfL website and the same account manages Oyster and contactless settings.
TfL's status feed covers 11 London Underground lines plus bus, Overground, DLR, and tram services. The alerts draw on the TfL Unified API, the same public feed behind the online status board.
The planning pattern is event-triggered sending: the message fires from a live service feed rather than a calendar. TfL publishes subscription counts and alert volumes, not open or behavior data.
Case 4: GOV.UK Notify for public bodies
The UK Government Digital Service operates GOV.UK Notify, a shared email and SMS platform used by central and local public bodies. Teams load templates, send through an API or dashboard, and see delivery receipts per message. Pricing is published per message, with email priced below text messages, and central government departments draw on an agreed volume allowance.
GDS publishes the rates on the GOV.UK Notify pricing page, and the platform logs every send against the template that produced it.
The planning lesson is template governance: one approved wording per transaction, versioned and reusable.
Case 5: CDC immunization reminders
The US Centers for Disease Control and Prevention publishes immunization schedules and reminder materials that clinics and health departments adapt for patient email. The CDC provides the clinical content and plain-language templates; the sending organization owns the list and the follow-up.
The lesson is source separation: the content authority and the sender are different bodies, so the sender must confirm the schedule version and the local eligibility rules before each send. The CDC does not report campaign-level open or completion rates for these local sends.
Case 6: Electoral Commission voter registration prompts
The UK Electoral Commission runs registration reminder email around election deadlines, pointing recipients to the GOV.UK register-to-vote service. The Commission's published guidance sets the registration deadline at 12 working days before polling day. The Commission publishes deadline dates and registration totals after each poll, but not per-email conversion.
The lesson is deadline anchoring: the send is tied to a fixed public date, and the destination is a single government form.
What the cases share
- A specific audience and communication job existed before the reported activity.
- The message was tied to a destination, referral, or information resource outside the inbox.
- Distribution and platform activity did not by themselves prove understanding, value, or causation, and a delivery receipt is not evidence that the recipient acted.
- The limitations materially change how the reported numbers should be used in a new plan.
A business adapting any of these patterns should define permission, customer benefit, claims, accessibility, destination capacity, privacy, service response, economics, measurement, and stop rules for its own market. Preserve neutral and unfavorable evidence. A case study should improve the next decision, not become an unsupported sales claim.
Case-study comparison
Growth Hubs
- Primary job
- Awareness and referrals
- Reported signal
- Distribution and referrals
- Useful lesson
- Target and outcome path
- Critical limit
- Impact largely uncertain
Pension Awareness Week
- Primary job
- Plain-language education
- Reported signal
- Email and web views
- Useful lesson
- Message and destination
- Critical limit
- No causal design
TfL alerts
- Primary job
- Service disruption alerts
- Reported signal
- Subscriptions and alert volumes
- Useful lesson
- Event-triggered sending
- Critical limit
- No behavior data
GOV.UK Notify
- Primary job
- Transactional delivery
- Reported signal
- Delivery receipts
- Useful lesson
- Template governance
- Critical limit
- Delivery is not action
CDC reminders
- Primary job
- Immunization reminders
- Reported signal
- Schedule uptake guidance
- Useful lesson
- Source separation
- Critical limit
- No campaign rates
Electoral Commission
- Primary job
- Registration prompts
- Reported signal
- Registration totals
- Useful lesson
- Deadline anchoring
- Critical limit
- No per-email conversion
Audit the published evidence
Check six things before you reuse a case study:
- Purposewhat the campaign set out to do, in the author's words.
- Audiencewho received the email, and how they joined the list.
- Periodthe dates the reported numbers cover.
- Measures and denominatorswhat was counted, and out of what total.
- Attributionwhat the author says the figure does and does not prove.
- Sourcewho published it, and whether the link still resolves.
The FTC advertising substantiation policy requires a reasonable basis before objective advertising claims are disseminated. Hold each figure above to that standard.
The FTC guidance for marketers using reviews warns about fake feedback, selective requests, conditioned incentives, hidden relationships, and paid rankings. Apply those U.S. integrity checks when email campaign planning case studies name providers.
For email campaign planning case studies, keep the evidence record beside the decision so a reviewer can reproduce the reasoning without relying on memory.
Common questions
Are these commercial email benchmarks?
No. They are context-specific public-sector examples with different missions, audiences, methods, periods, systems, and limitations.
Can the reported figures be used in a forecast?
Not without preserving the original definitions, denominators, channels, attribution limits, uncertainty, and the new program's material differences.
What is the safest lesson to transfer?
Define the audience and decision, connect the message to a useful destination, measure a downstream outcome, and keep limitations beside every reported result.
