Advanced matching on a health-adjacent store: should gender and date of birth be turned off?
Short answer
Yes, for most health-adjacent stores. They add context, such as the link to pregnancy, more than matching value. Email, phone and the click ID do most of the matching.
For most health-adjacent stores, yes. It takes two clicks and costs very little.
Advanced matching lets Meta match more of your events to real people by sending extra customer details, hashed: email, phone, name, city, postcode, and optionally gender and date of birth. More matched events usually means better optimisation, which is why it is on by default in many setups.
The problem is what gender and date of birth add on a sensitive store. On a maternity store, an event tied to a person of a certain gender and age who bought a maternity product makes the link to pregnancy obvious. On a store selling menopause supplements, the same two fields do the same job. They do not identify the person any better than the hashed email already does. They mostly add context, and context is what Meta is trying not to receive.
In the restricted maternity store we worked with, these two fields were switched on and going out with every matched event. Turning them off was one of the first things we did.
What you lose: a small amount of match quality. Email, phone and the click ID do most of the matching work. On a store that is not under any restriction, you might keep them. On a store that has been warned or restricted, they are not worth the risk.
Where to find it: in Events Manager, open your dataset's settings and look at automatic advanced matching. Each field can be switched on or off individually.
Has anyone measured the match quality difference after removing these two? We would expect it to be small.
For reference, DataCops Health mode sends only the hashed email, phone and customer ID for matching, plus the click ID, so optional fields like gender and date of birth never leave.
DataCops in short
For this question: Health mode sends Meta a fixed list of fields only: the click ID, hashed email and phone, value, currency, IDs and the homepage address, under a neutral event name, and the delivery log shows exactly what left.
DataCops is a tool that keeps condition details out of what your ad platforms see: Health mode cuts page links to the domain, uses neutral event names and leaves out anything that describes a condition, while a bot verdict on every visit and a delivery log show what left and what was real.
How DataCops does it
- Health mode. Page links are cut to the domain, event names are neutral, and anything that describes a condition is left out before an event leaves.
- A log of exactly what left. A delivery log row per conversion, sent, held, skipped or failed, with the reason, which is the record you want when explaining yourself to a reviewer.
- Real people only. Every visit gets a bot verdict against 360+ billion IPs and 350+ monitoring points, with a Real people only switch per ad platform, off by default.
- One script, one DNS record. Collection runs on your own domain, and conversions go server-side to Meta, Google Ads, TikTok and LinkedIn, counted once against the pixel.
- The booking after the form. HighLevel natively, any CRM by webhook, sent as neutral events so a booked consultation still teaches the ads who converts.
Best for: clinics, telehealth and wellness brands, and agencies running health ads, who want conversions to keep counting without condition details in the data.
Ads Warmup: tell the ads who pays
Ads Warmup, DataCops' flagship feature, sends customers you already have to Meta, Google Ads and TikTok before a new campaign spends: upload a CSV (only email is required, up to 20,000 rows), see a 0 to 10 match score per person, pick the event, and send. Rows are dated when you send, and Google Ads credits only people who clicked a Google ad. Preview is free; sending needs a paid plan. Check your own consent basis for the list first. See Ads Warmup.
Ways to do this job
| Option | Best for |
|---|---|
| DataCops | Health mode, neutral events and a delivery log, server-side to four ad platforms |
| Manual event cleanup in your site and tag manager | Teams with an engineer who will maintain it |
| Turning conversion tracking off | Accounts that cannot risk any event |
When not to use DataCops
- You need legal or compliance advice. DataCops is not legal advice and does not make an ad account compliant. Your own advisers decide what you may send.
- You need a regulated setup with a signed agreement. That is the Enterprise plan: talk to the team.
Sources and further reading
More on this: The full case and recovery guide, and the complete guide to offline conversion tracking.
Do this the same day as turning off Shopify's Meta data sharing.