By the numbers
- $744.37average order value from birthday messages, more than 4x the average, across brands sending with Omnisend in 2025Omnisend 2026 Ecommerce Marketing Report
- 43.3%open rate for automated birthday emails, with a 14.3% click-to-conversion rateOmnisend email marketing statistics 2026
- 19xhigher conversion rates for automated messages than for campaign sendsOmnisend 2026 Ecommerce Marketing Report
- 1.5%conversion for four-field signup popups, against 2.1% for a single fieldOmnisend email popup statistics
Vendor figures are averages across many stores, not controlled tests. Use them to decide what to test first.
Why a birthday is worth asking for
A birthday gives you one message a year that is about the customer rather than your calendar. Omnisend’s data from 2025, covering 27 billion emails from 150,000 brands, put the average order from a birthday message at $744.37, more than four times the average. Its 2026 statistics report automated birthday emails opening at 43.3%, with 14.3% of clicks becoming orders. Those are averages across many stores and the order value will be skewed by some large ones, so treat them as a reason to test rather than a forecast. The cost of asking is small if you ask at the right moment.
Ask beside the email, or just after it
Every extra field asks for more effort. In Omnisend’s 1.24 billion popup displays, single-field popups converted at 2.1% and four-field popups at 1.5%. Other data is less clear-cut: Wisepops found multi-step popups at 5.17% against 4.62% for single-step, which suggests asking in stages can help. Two patterns work. The birthday can be its own step after the email, so the first screen stays one field. Or it can sit on the email’s screen, which suits a store with a legal age that has to ask anyway. In Veya, a date question can share the email’s screen, and in a multi-step email and SMS form the email is kept even if the visitor stops before the texts step.
Store it in a format Klaviyo can use
Klaviyo starts a birthday flow from a date property, and the value has to be in one of its accepted formats, such as YYYY-MM-DD or MM/DD/YYYY. A value saved as plain text will not appear as a flow trigger. A free-text field where people type “April 12th” or “12/04” causes exactly that problem. Veya’s date question collects month, day and year in three boxes, checks that the date is real, and sends it to Klaviyo as YYYY-MM-DD in the profile property you name; birthday is the name to use. Klaviyo and webhooks get it as they get any answer.
Month, day and year, and why the year
A birthday email only needs the month and day, so some stores skip the year. Veya’s date question asks for all three, which lets it check the date is real (no 31 June), not in the future and at most 120 years back, and lets it apply a minimum age. Naming the question or property “birthday” lets the browser offer its birthday autofill. The boxes are always in month, day, year order. You can change their placeholder words for another language, but a shopper used to day, month, year may still need a clear label. If you only want month and day, Veya’s date question does not offer that today.
Make it optional unless you need it
Most stores should let people skip the birthday. A required date on a general signup form turns a quick email capture into a form some people will abandon or fill with a made-up date. In Veya, a date question can be marked optional; a half-filled date is not treated as blank, so the visitor finishes it or clears it rather than sending a partial date. Say why you are asking, next to the field: “for a birthday treat” is clearer than a bare label. Make it required only when you have a reason, such as a store with a legal minimum age.
Set a minimum age when your products need one
A wine, spirits or vape store has a legal age, and a birthday on the signup form can enforce it for the list. In Veya, a date question can carry a minimum age from 16 to 25. Under it, the browser shows “You must be 21 or older to sign up” (or your own wording), and the API refuses the signup too, so nothing of it is kept. That catches a visitor who tapped Yes at an age gate and then entered a 19-year-old’s birthday. The browser checks against the visitor’s own date; the server allows for the latest date anywhere in the world. Your legal minimum is a question for your lawyer.
Children and COPPA
In the US, the Children’s Online Privacy Protection Act covers personal information collected from children under 13. The FTC says general audience sites are not required to ask visitors’ ages, but an operator who learns it has collected a child’s information is treated as having actual knowledge, and the rule’s notice and consent requirements follow. A birthday field can give you that knowledge. The FTC’s guidance on age screens asks for neutral questions that let people enter their age accurately, and allows a general audience site to block children. Setting a minimum age on the date question refuses those signups outright. If children may use your store, get legal review before collecting birthdays.
Keep birthdays where they are needed
A birthday is personal data, and with a year it can help identify someone. The GDPR’s data minimization principle, Article 5(1)(c), asks that data be limited to what is necessary for its purpose. In Veya, birthdays stay out of the places they are not needed: the responses report counts who answered without listing dates, a report cannot be split by them, and the agent tools’ signup lists leave them out. They are in the merchant’s CSV export and in data requests, and they go to Klaviyo and webhooks with the other answers. Review who can see them in Klaviyo too.
Build the flow in Klaviyo
In Klaviyo, a date property trigger enters each profile into the flow every year on the same month and day. Klaviyo lets you start on the date or a chosen number of days, weeks or months before it, and its flow library includes ready-made birthday flows. A week before suits a gift-shopping message; the day itself suits a simple greeting with a treat. Give a code enough time to be used, say a week or the rest of the month. Check what new subscribers receive if their birthday is days away when they sign up.
Test with a real date
Sign up in a private window with an address you control and a birthday a few days from today. In Klaviyo, open the profile and confirm the property shows as a date, then check the profile is scheduled in the birthday flow. Submit a half-filled date and confirm the form asks you to finish it. If the form has a minimum age, enter a date just under it and confirm the signup is refused, then one exactly on the boundary. On a multi-step form, leave at the texts step and confirm the email still reaches the list. Finish with the rest of the launch checklist.
Brief Veya
Send your storefront URL, the Klaviyo list for signups and the name of the birthday property your Klaviyo flows use (birthday if you are starting fresh). Say where the birthday should go: on the email’s screen or as its own step, whether it is optional, and the minimum age if your products have one. Include the words you want next to the field, the treat you will send and how long it lasts, and whether the form also collects SMS with your approved consent wording. If you sell age-restricted products, say whether the store also needs an age gate.
Questions
How do I collect customer birthdays on Shopify?
Add a date field to your signup form and send it to your email platform as a date property. The usual place is the welcome popup, either beside the email field or as a second step after it. Make it optional on a general store and explain what the visitor gets, such as a birthday treat. Then build a birthday flow in Klaviyo that starts from that date property.
What date format does Klaviyo need for a birthday flow?
Klaviyo’s help center says a date property must use an accepted format, such as YYYY-MM-DD or MM/DD/YYYY, to trigger a flow. A value stored as text will not appear as a trigger option. That is why a free-text birthday field causes trouble. Veya’s date question sends the birthday as YYYY-MM-DD in the profile property you choose, so it can be used as a flow trigger.
Should a birthday signup form ask for the year?
Only if you need it. A birthday email works with month and day, and asking for less is better for privacy. The year matters when you sell age-restricted products and want to refuse under-age signups, or want to keep children’s data out of your list. Veya’s date question always asks for the year, which is what lets it apply a minimum age from 16 to 25.
Is it legal to ask customers for their birthday?
Generally yes, with care. In the US, COPPA applies to personal information from children under 13, and learning a subscriber is under 13 triggers its requirements. Under the GDPR, data should be limited to what the purpose needs. Tell people why you are asking, make the field optional where you can, and get legal review for your markets. This is not legal advice.
Can my age gate collect birthdays for birthday emails?
Not in Veya. The age gate checks a date of birth in the visitor’s browser and never stores or sends it, because its job is to check an age, not to build a list. To send birthday emails, ask for the birthday in the signup form, where the subscriber chooses to give it with their consent. That date question can carry its own minimum age.
Sources
- Omnisend, 2026 Ecommerce Marketing Report (150,000 brands; 27 billion emails sent in 2025; birthday AOV $744.37)
- Omnisend, email marketing statistics 2026 (automated birthday emails: 43.3% open rate, 14.3% click-to-conversion)
- Omnisend, email popup statistics (1.24 billion displays in 2025)
- Wisepops, 20+ popup statistics 2026 (email signup popups, about 1 billion displays)
- Klaviyo Help Center, create a date property-triggered flow (accepted formats; yearly recurrence; on or before the date)
- FTC, Complying with COPPA: frequently asked questions
- GDPR Article 5, principles relating to processing of personal data (data minimization)
Figures checked November 6, 2026.