
Birthday campaigns consistently produce the highest open and redemption rates of any automated restaurant message, for the obvious reason that the recipient is the subject. They are also close to free to run once set up, and most pizza shops either do not run one or run one that gives away a single pizza to a single person.
A birthday is a gathering. An offer built for one person, a free personal pizza, captures a fraction of the available occasion. An offer built for a group brings four people through the door and produces a ticket several times larger.
The structure that works: something genuinely free for the birthday person, conditional on a group-sized order. Everyone feels looked after, the ticket is healthy, and you have introduced your food to several people who may not be customers.
| Send | Timing | Content |
|---|---|---|
| Advance notice | 7 days before | "Your birthday is coming: here is what we have for you." Enables planning. |
| On the day | Morning of | Short, warm, no hard sell. |
| Reminder | 3 days before expiry | The value they hold and the deadline. |
| Window | 14–21 days from the birthday | Birthdays are rarely celebrated on the exact day. |
Asking for a full date of birth at signup depresses completion and raises privacy concerns. Ask for the day and month only, which is all the campaign needs, and ask for it after the customer has already joined rather than as part of the initial form.
A post-signup message, "tell us your birthday and we will do something about it", collects the date from a meaningful share of members without adding a field to the form that costs you enrolments.
The anniversary of a customer’s first order is a genuinely under-used trigger. It reaches people whose birthday you never captured, it works for every customer without any additional data collection, and the message writes itself: a year ago today you ordered from us for the first time.
It performs particularly well as a retention touch for customers whose frequency has softened, because it arrives as recognition rather than as a promotion.
You already know the date of every customer's first order. That is a free birthday for everyone who never gave you a real one.
A free item with a group-sized minimum spend. A free dessert or a free pizza conditional on a family-sized order produces a much better ticket than an unconditional free personal pizza and feels equally generous.
Not worth it at pizza-shop scale. A small amount of gaming is cheaper than the friction of verification and the goodwill cost of accusing a real customer of lying. Cap it to once per twelve months per customer and move on.
They produce a strong response, and the honest question is incrementality: some of those customers would have ordered anyway. Hold out a portion of eligible birthdays and measure the difference. In most files the lift is real, driven by the larger group ticket rather than the individual visit.
Keep reading
The seven automated journeys every pizza location should have running (welcome, second order, habit, drift, win-back, birthday and post-catering) and the order to build them in.
Loyalty & retentionPoints, punch cards, tiers and surprise rewards, which structure suits which shop, and how to avoid paying regulars for behaviour they were already giving you.
Audience & dataPractical ways to turn anonymous tickets into identified customers (online ordering, loyalty, QR on the box, the till, and wifi) without annoying anyone.
MeasurementBuilding holdout groups into every campaign, reading the difference honestly, and accepting that most reported marketing revenue was going to happen anyway.
marketing.pizza runs all of it, every night, across every store you have.