Lesson 2 of 9
Retention strategy
Use retention strategy to make one better email decision: who gets the message, why now, what they should do next, and how you will measure it.
- Do not report a number until you know what decision it supports.
- Decide what you will do differently if the number goes up, down, or stays flat.
What you need to get right
Metrics are not the work. They are signals that help you decide what to change.
When you review retention strategy, separate attention metrics from business metrics. Opens can show interest. Clicks show action. Conversion and revenue show whether the email helped the business.
A useful report ends with a decision: keep, change, test, pause, or investigate.
Do this before you send
- 01
Name the audience and lifecycle moment before writing.
- 02
Write the business goal and the reader goal in plain English.
- 03
Choose the message angle, proof, offer, or help that fits the moment.
- 04
Draft the email structure: subject, preview text, opening, body, CTA, and follow-up logic.
- 05
Review relevance, consent, mobile readability, tracking, and exclusions before sending.
See it in a real email moment
If you are working on retention strategy, use a narrow scenario. A new lead from a guide needs a helpful next step. A returning customer needs context based on what they bought. A dormant subscriber needs a reason to stay or a clean way out.
Your quick todo list
- Choose one primary metric before looking at results.
- Compare the email to the right baseline, not a random send.
- Write one decision the data supports.
Check this before moving on
- The audience is specific.
- The email has one primary job.
- The CTA matches the reader's stage.
- The copy is readable on mobile.
- Tracking is in place before launch.
Mistakes that quietly hurt results
- Writing for the whole list when the message only fits one segment.
- Adding more CTAs because the main ask is not clear enough.
- Polishing copy before the audience, offer, and timing make sense.
- Judging success from one metric without checking the downstream action.