Does WhatsApp Show Birthdays? What Stores Need to Know

No — and the answer is the same for personal and for business accounts.

What WhatsApp shows you about a contact is short: the profile photo, the display name, the About line and the phone number. Everything else you see next to a customer's name comes from your own address book or from your own shop data. There is no birthday field in the platform, so no tool can read one out of it — including ours.

On the business side the field list is documented. A business profile carries a name, an address, up to three categories, a description, an email address, a website and business hours (WhatsApp Help Center, retrieved August 2026). Meta's developer reference for the same object lists the same set (Meta for Developers, retrieved August 2026). Neither includes a date of birth, and neither exposes one for the people you message.

That is worth saying plainly, because the results for this question are full of apps promising automatic birthday wishes. What those apps read is your phone's address book, or a list you uploaded yourself. Not WhatsApp.

From you. If you know a customer's birthday, it is because you asked.

There are three realistic places it enters a Shopify store: a field in your newsletter sign-up, a question in an account or loyalty step, or a post-purchase survey. Each is a deliberate moment where the customer hands over a date and you record why you hold it. None of them happens by itself, and none of them fills in retrospectively for the customers you already have.

Once the date is in your data it behaves like any other attribute you keep on a contact. You tag the contact — how labels work covers why one contact can carry several — and you turn the tag into a condition in the Segment Builder. What you get is a saved segment that updates itself, not a list you export in December and export again in January.

Ask for the month rather than the full date if you only want it for marketing. It is less personal data to hold, it is easier to justify, and the month is the unit you will actually send to.

Partly — and it matters which mechanic you reach for, because one of the two people usually imagine does not exist.

A Keaz Flow starts from one of five triggers across four sources: Contact purchase and Abandoned checkout, both Shopify events; Smart Activation, where Keaz picks the moment; Webhook, where another system calls us; and Chat-in, where the customer writes first. A calendar date is not among them. A Flow will not watch a date field and fire on the morning of someone's birthday.

Two routes do work:

1. Segment plus send. Build a segment of contacts whose birthday month is the current one, then send a newsletter to it. Twelve sends a year, and you can see exactly who received each one.
2. Webhook trigger. If the date lives in another system — a loyalty app, your own backend — that system can call Keaz and start a Flow for a single contact. The date logic stays where the date is, which is usually where it belongs.

Most shops should take the first route. It costs one recurring calendar entry and it uses the mechanic you already have for every other campaign; setting up a WhatsApp newsletter covers the send itself.

Do the arithmetic before you build anything, because this segment is smaller than it feels.

Take the number of contacts you can reach on WhatsApp and for whom you actually hold a birth date, then divide by twelve. That is your monthly send. A shop with 1,000 reachable contacts that has collected the date from a quarter of them is writing to about 21 people a month. A shop with 6,000 reachable contacts and the date on half of them is writing to 250.

Which is why coverage comes first. Most shops start with 35–55% of their last-twelve-months customers reachable on WhatsApp at all, and a birthday segment is a slice of a slice of that. At the bottom of that band the honest next move is the revenue forecast on your own Shopify data, or how we work out what a reachable customer is worth — not a birthday campaign.

The verticals where a date-based message pays are the ones with a gift or self-treat motive and a short repurchase cycle. What we see per industry is the faster way to check whether yours is one of them.

And if what you want is a reason to message someone that you reliably have, behaviour beats the calendar. RFM segmentation works off what people did, which you always know, rather than a date you mostly do not.

Five patterns, in the order we see them:

1. Waiting for WhatsApp to supply the date. It will not. There is no field, so there is nothing to sync and no integration to go looking for.
2. Designing a date-triggered Flow. The five triggers do not include a calendar date. If a plan begins with "the Flow checks the date every morning", the plan needs changing rather than configuring.
3. Collecting the full date when the month would do. More personal data than the campaign needs, held for longer than you can comfortably justify.
4. Treating the date as permission. A birth date tells you when to send. Whether you may send is a separate, explicit opt-in, and the two are independent of each other.
5. Sending the usual discount code and calling it a gift. If it is the code that goes out in every campaign, the birthday message is a discount with a date on it. Early access, a sample or a plain thank-you reads differently.

This is a summary rather than legal advice — have your own counsel review how you collect, document and store birth dates.

Does WhatsApp notify me about a contact's birthday?

No. There is no birthday field and no birthday notification. Anything you have seen along those lines came from another app reading your phone's address book.

Is "WhatsApp birthday" about the app itself?

Sometimes, yes — the phrase carries two different questions. WhatsApp was founded in 2009, and searches for "when is WhatsApp birthday" are often about the app rather than about contacts.

How do I keep birth dates in Keaz?

The Segment Builder filters on labels and on purchase behaviour, so the workable route is a birthday-month label on the contact and a segment built on that label.

What if I only have birth dates for a handful of customers?

Then skip it for now. A segment of nine people is a nice gesture, not a channel. Spend the same hour on coverage — the share of your customers you can reach at all — and come back when the monthly segment runs into the hundreds.