A year-in-review email should help a customer recognize something worth remembering. It does not need to reveal every purchase, calculate a flattering score, or pretend that an incomplete record tells a complete story.
Start with Migma to build a clear, branded recap from approved facts. Then have the owner of your customer data verify what the final email can truthfully say. A good-looking milestone card cannot repair a missing date range or a loyalty balance that means something different from its label.
This guide is published by Migma. It focuses on producing and reviewing the message; your sending platform still owns its audience rules and populated customer values.
Choose the recap your records can support
There are three useful approaches: a brand recap, a customer milestone recap, and a mixed message. Choose based on the evidence available, rather than the amount of personalization your template can display.
A brand recap shares a small number of company achievements that your team can substantiate. A customer milestone recap celebrates a verified relationship or action. A mixed message opens with a shared story and adds one reliable personal detail.
Klaviyo’s New Year campaign guide includes personalized recaps among its seasonal ideas. Treat that as a starting question: what would this particular customer enjoy seeing? Browsing and purchase histories can expose information the recipient would rather keep private. More detailed is not automatically more thoughtful.
For a small homeware shop, a mixed message might mention a newly launched repair service and thank a long-standing customer for another year together. It need not list everything that person bought.
Write the fact record before the creative brief
For every proposed personal detail, record its meaning, reporting period, owner, and fallback. Keep sample records free of unnecessary personal information while preparing the design.
| Proposed line | Question the data owner must answer | Safer fallback |
|---|---|---|
| You joined us this year | Is this the first account, first order, or subscription date? | Thank you for being here |
| You earned 400 points | Points earned during the period, or current available balance? | Explore your rewards account |
| Three years together | Which start date and cutoff establish the anniversary? | We appreciate being part of your routine |
| Your favorite collection | Does the evidence establish a preference, or only one purchase? | Explore the collection |
The numbers in this table are illustrative, not customer results. Their purpose is to show how a short phrase can hide several possible definitions.
Decide whether refunded orders, merged profiles, imported history, or incomplete periods make a personal detail unsuitable. The answer may be to omit that detail. Do not ask a writing model to guess the missing value or turn uncertainty into confident copy.
Build two complete versions in Migma
Prepare a personal version and a general version that each read naturally on their own. A general version should not feel like a broken personalized template with an empty card removed.
Migma’s brand setup uses website information, brand settings, and saved references to guide appearance and writing. Review that context first. Give the draft an approved story, exact facts, desired action, and explicit restrictions on what it may infer.
A useful brief might say: “Create a warm year-end thank-you for a homeware shop. Mention our repair service using the approved description below. Include one optional relationship milestone. Do not infer favorite products, environmental impact, money saved, or rewards balances.”
Example: a verified relationship milestone
Subject: Another year of making home yours
Preview: A small thank-you, and something useful for the year ahead.
Opening: Thank you for being part of our community since 2023. This year, we introduced a repair service to help customers keep using the pieces they love.
Action: Explore the repair service.
Use that year only when the underlying record establishes it. The repair-service statement is an example of approved brand copy, not a claim about Migma or an actual retailer.
Example: incomplete personal history
Subject: Thank you for being here
Preview: A look back at one useful change, and what comes next.
Opening: As the year closes, we want to share a service we are glad to have introduced: repairs for eligible pieces. Whether you have just found us or have been here for years, thank you for following along.
Action: See how repairs work.
This version makes no assumption about tenure. It still offers a reason to read and a useful next step.
Review the populated message, not just the design
Run Email Preflight in Migma to review inbox previews, links, writing, and common delivery risks. Fix the relevant warnings and check again. Preflight cannot establish whether a customer’s milestone is accurate or guarantee inbox placement.
After handoff, inspect the actual destination template. Migma’s export guidance explains that platforms can add wrappers or change variables. Customer values must be checked where they are populated.
Use a small acceptance set: a complete record, a missing value, a newly joined customer, and a record with corrected history. Confirm that each receives coherent wording, a working action, and the intended reporting period. Keep audience eligibility separate from creative approval: a suitable design does not establish permission to contact someone.
Finally, review the subject and preview beside the body. “Your year in numbers” is a poor promise when the general version contains no personal numbers. If you cannot reliably separate those versions, choose a subject that suits both.
Keep the next action modest
A recap can end with thanks, a useful guide, or an invitation to explore a relevant service. It does not need to become a crowded sale email.
Start your draft in Migma, using only the facts your team is ready to stand behind. The finished message should feel personal because it is considerate and accurate, even when the safest version contains very little personal data.
Frequently Asked Questions
What should a year-in-review email include?
Choose a useful shared story and, where the records support it, a verified customer milestone. State the reporting period clearly. A short thank-you and one relevant action can work without purchase totals or detailed browsing history.
What if some customers have no reliable recap data?
Prepare a complete general version with a subject and preview that suit its content. Omit unsupported personal claims rather than substituting guessed values. Check the populated destination message for missing fields and awkward gaps.
Can Migma verify loyalty points or purchase history?
The workflow here uses Migma to prepare and review the creative. The owner of the customer and loyalty data must verify the meaning, period, and accuracy of values before the final sending platform populates them.
Does a successful Preflight check mean the recap is ready to send?
It is one part of review. You still need accurate customer facts, audience eligibility, final-platform variable checks, and appropriate sender settings. Preflight reduces avoidable problems but cannot guarantee inbox placement.