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

Birthday and anniversary emails work because they're explicitly about the user, not about the brand. The subject line ("Happy birthday, [name]") is immediately personal. The user opens because the message is addressed to them as an individual, not broadcast to a list.

The typical metrics bear it out: 45–60% open rate, 8–15% click-through, 2–5× the conversion rate of a standard promotional send. Numbers that would be suspicious from any other program and turn out to be structural once you understand why the email works in the first place.

Trigger: date match on the user's birthday field. Send 3–7 days before the birthday so the offer is usable on or around the day. On-the-day sending often lands late — most users have committed their birthday plans by that morning, and a gift that arrives after the window closes isn't really a gift.

Subject: "Happy birthday, [first name]" or a variant. Keep it simple. The personal addressing is the entire draw.

Content: a genuine greeting (not breathlessly enthusiastic), a gift or offer that reads as a gift (not "happy birthday, here's the same 10% off everyone gets"), an expiry date 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.

The gift: has to feel like a gift to work. Options: a free item at a low-cost threshold, a more-generous-than-usual discount (20–25% against the program's usual 10%), a free shipping voucher, or — best option — a free small-value product with purchase. The cheapest option, a 10% discount that matches every Tuesday newsletter, 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 promotional offer, skip the birthday email rather than send a weak one.

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. Less conventional than birthday, which helps it earn attention.

Content: acknowledge the tenure, a summary of what they've done with the brand (orders, favourite category, points earned — whatever the data supports), and optionally a thank-you gift or exclusive. Makes the relationship visible.

The personalised summary ("in the past year you've ordered 12 times from us") is what separates a strong anniversary email from a weak one. Generic "thanks for being a customer" anniversaries perform like standard promotional emails. Specific summaries perform like birthday emails. Same template, different fill-in logic, completely different numbers. For programs without budget for birthday gifts, 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 line item.

Multiple anniversaries (year 1, year 2, year 3+)? Yes, with distinct treatments. Year 1: substantial thank-you with gift. Year 2: simpler acknowledgment with 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.

Most programs have birthday data for 30–60% of users. The rest either didn't provide it at signup or haven't been asked. Three options that work:

1. Progressive profiling. Ask for birthday in a low-friction context once the user has been active for 30 days. "Let us know your birthday and we'll send you something on the day." See the progressive profiling guide for the mechanics.

2. Signup anniversary as substitute. For users without birthdays, use the signup anniversary as the personalisation moment. Weaker 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 anniversary is both a natural milestone and a good re-engagement moment — it's a year since the user first committed, which is worth something.

Weak gift. A 10% off code on birthday feels cheap when it's the same 10% the user got in Tuesday's newsletter. If the gift matches the standard promotional offer, users notice. Make it feel gift-like or skip the email.

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 everything else you're doing. If the birthday data is legacy or low-quality, clean it (or re-collect) before firing the program.

No expiry on the gift. Birthday 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 established.

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

Are birthday emails worth building? Yes. Very high open and click rates, low build cost (a single template with a date trigger). Once the birthday collection is in place, the email is essentially free to maintain. Most programs get to it eventually. Being earlier than eventually is worth a few weeks of effort.

treats birthday and anniversary as "easy wins" — not prioritised for most early-stage programs (the three core flows come first), but highly worth shipping once the core program is stable. They pay off every year forever for a day of template work.