Shopify store flagged as health on Meta: should I turn off the Facebook and Instagram channel data sharing?
Short answer
Yes, while you clean up. The channel sends product names, page links and customer details on every event, which is what Meta reads as health. Replace it with a cleaned server event so Meta keeps learning.
Short version: if Meta has warned you or already restricted you, yes, turn it off while you clean up. It is not obvious why, because the channel is doing exactly what it was built to do.
Shopify's Facebook and Instagram channel is designed to give Meta as much as it can. Every view, add to cart and purchase goes with the product name, the link to the product page and whatever customer details the store has: email, phone, name. At the Maximum data sharing setting it sends that through the Conversions API as well. For a shoe store that is great. Meta learns faster and matches better.
For a store anywhere near health, it is the worst possible default. We worked with a maternity store this autumn whose events all carried the name of a pregnancy-related product and the link to its page. Not some events. Every one of them, all day, including the weeks Meta was deciding whether the store was a health business. By the time the owner asked for a review, Meta had a month of evidence.
The usual pushback is that the data is hashed. The email and phone are hashed, yes. The product name is not, and it does not need to be personal to be sensitive. An event that says a known person bought a pregnancy support band tells Meta something about that person's body. Hashing hides who they are on the way. It does not hide what they bought.
What switching it off costs you: Meta stops getting events from the channel. If that is your only tracking, your campaigns lose their signal, so do not switch it off and walk away. Replace it with something that sends a cleaned event: the order with value and currency, a hashed email and phone, the click ID, and nothing about the product or the page. That keeps Meta learning wherever your level still allows it.
What it does not do: it will not remove a restriction that is already in place. It stops you adding to it. Think of it as closing the tap before you mop the floor. The mop is the rest of the clean-up: product titles, the meta description, claims, image alt text, and the names you gave your audiences and conversions.
While you are in Events Manager, check advanced matching too. Gender and date of birth are optional fields there, and on some stores they are the last piece that turns a hint into a certainty.
Has anyone kept the channel on in a restricted category and still passed a review? We have not seen it, and we would like to know if it happens.
For reference, the DataCops Shopify app sends paid orders from Shopify's server, and with Health mode on each order reaches Meta as P_1 with value, currency, hashed contact details and the click ID, and no product name or page link.
DataCops in short
For this question: The DataCops Shopify app sends the paid order from Shopify's server, and Health mode strips the product name and page link before anything reaches Meta.
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.
If you only do one thing today, do this one. Then read the rest of the store the way Meta would.