Birthday and anniversary emails: the easy wins most programs don't run

Open one of these emails next to your last promo and the difference is obvious before you read a word. The subject line says "Happy birthday, Sarah" — addressed to one human being, on a date that matters to her. The promo says "25% off this weekend only" — addressed to a list. One of those is a message; the other is an announcement that happens to land in an inbox.

That's the whole mechanism. Birthday and anniversary emails are the rare lifecycle send — meaning a triggered, state-driven message rather than a calendar broadcast — that's explicitly about the recipient, not about the brand. The reader opens because the message names them, not because the merchandising team needed to move stock.

The numbers track the mechanism. 45–60% open rate. 8–15% click-through. Two to five times the conversion of a standard promotional send. Numbers that would look fabricated coming from any other program, and turn out to be structural once you understand why the email works.

Four decisions make or break it: when it fires, what the subject line says, what the body says, and what the gift actually is. None of them are difficult. Most programs get one of them wrong and wonder why the email underperforms.

When it fires. Trigger on a date match against the user's birthday field — meaning the user's stored day-and-month. Send 3–7 days before the birthday so the offer is usable on or around the day itself. On-the-day sending lands late: most users have committed their birthday plans by that morning, and a gift that arrives after the candles are out isn't a gift, it's a coupon with bad timing.

What the subject line says. "Happy birthday, [first name]" or a clean variant. Keep it simple. The personal addressing is doing all the work — adding cleverness on top dilutes the only thing you have going for you.

What the body says. A genuine greeting (not breathlessly enthusiastic), a gift that reads as a gift (not the same 10% off everyone gets every Tuesday), an expiry 2–4 weeks out, and a clear redemption path. Calmer voice, one emoji max. Over-the-top "SO excited to wish you a HAPPY BIRTHDAY" reads as performative — and performative celebration from a brand that barely knows the user is the uncanny valley of lifecycle. See the brand voice guide.

What the gift actually is. The single decision that determines whether this works. The gift has to feel like a gift. Options that work: a free item at a low-cost threshold, a more-generous-than-usual discount (20–25% against the program's standard 10%), free shipping, or — best of the lot — a free small-value product with purchase. The cheap option, a 10% discount that matches every other email you send, underperforms because it reads as formulaic. Users aren't stupid. They know what a gift looks like and what a template looks like. If the birthday gift matches the standard promo, skip the email rather than send a weak one.

An anniversary email fires on the date a user signed up, or the date they made their first purchase. It works for the same reason the birthday email works — it's addressed to one person on a date that's about them — but it carries a different feeling. A birthday is about the user's life. An anniversary is about the user's relationship with the brand. Less universal, but earns attention precisely because it's less expected.

Trigger: the user's first-purchase anniversary or signup anniversary. Send on the date or the day before.

Subject: "One year with [brand] — thank you" or similar.

Content: acknowledge the tenure, summarise what they've done with the brand (orders, favourite category, points earned — whatever the data supports), and optionally a thank-you gift. The summary is what separates a strong anniversary email from a weak one. "In the past year you've ordered 12 times from us" lands. Generic "thanks for being a customer" performs like a standard promo and tells the user you can't be bothered to look at their record. Same template, different fill-in logic, completely different numbers.

For programs without budget for a birthday gift, the anniversary version does most of the work — a thank-you for being a customer doesn't require a discount, just personalisation. The "here's what you've done with us this year" message carries genuine warmth without costing a margin point.

Multiple anniversaries (year 1, year 2, year 3+)? Yes, with distinct treatments. Year 1: substantial thank-you with a gift. Year 2: simpler acknowledgment with a usage summary. Year 3+: lighter touch, occasional milestone recognition (5-year, 10-year). Annual repetition of the identical email gets old fast; varying the treatment keeps it feeling specific across long tenures.

Open the user table on most programs and 30–60% of records have a birthday on file. The rest either weren't asked or skipped the field at signup. That's a real gap, and it's also a solvable one. Three options that work, in rough order of return on effort:

1. Progressive profiling. A fancy term for "ask for one bit of data at a time, in context, after the user knows you." Wait until the user has been active for 30 days, then ask: "Let us know your birthday and we'll send you something on the day." Higher response rate than asking at signup, and the request has an obvious payoff. See the progressive profiling guide for the mechanics.

2. Signup anniversary as substitute. For users without birthdays, fire an anniversary on their signup date instead. Weaker emotional trigger than a birthday, but the date is definite and you already have it.

3. First-purchase anniversary. Particularly strong for commerce. The first-purchase date is both a natural milestone and a useful re-engagement moment — a year since the user first committed money, which is worth marking.

Four ways these programs go wrong. None of them are subtle, and all of them are common.

Weak gift. A 10% off code on someone's birthday feels cheap when it's the same 10% the user got in Tuesday's newsletter. Users notice. Make it gift-like or skip the email — a thoughtful greeting with no offer beats a thoughtful greeting wrapped around a generic discount.

Bad birthday data. A birthday email on the wrong day is worse than no email. It tells the user the program is broken and undermines every other send you do. If the birthday data is legacy or low-quality, clean it (or re-collect) before firing the program.

No expiry on the gift. Discounts that never expire train users to stockpile offers and never redeem any of them. A 2–4 week expiry preserves urgency and matches the "around your birthday" framing the subject line set up.

Tone mismatch. Breathless enthusiasm from a brand the user interacts with five times a year reads as disproportionate. Calmer voice, restrained visuals. The email is a small moment, not a fireworks display.

Worth building? Yes. High open and click rates, low build cost (one template, one date trigger), and once the data collection is in place, the email is essentially free to run forever. Most programs get to it eventually. Being earlier than eventually is worth a couple of weeks of work.

Where to slot it: not first. The three core flows — welcome, cart, win-back — come ahead of birthday in any sensibly sequenced roadmap, because they touch users every day rather than once a year. Once those are stable and measured, birthday and anniversary are the next thing to ship.

treats birthday and anniversary as "easy wins" — not the priority for an early-stage program, but high-value once the core is stable. They pay off every year forever for a day of template work.