Meta rejected my data source review the same day. What now?
Short answer
The review is automated, so it re-scans the same data. Stop pressing, clean what your site and events say, build about four weeks of clean data, check it, then ask once with a plan for no.
It happened to a store we work with, so here is what we learned, in order.
The timeline: Meta warned on 1 September, blocked standard events on 2 October, and when a review was requested on 6 October it came back rejected the same day, with a block for visitors in Europe added on top. A review that was meant to help made things tighter.
Why so fast? Because nothing had changed. Every event was still going out with product names and page links. The site still had the same titles, claims and alt text. Vendor reports describe the review as automated: one button, no way to attach evidence, a decision within days. If it is a re-scan, then a re-scan of the same data finds the same thing.
So, what now. First, do not press the button again. Vendors report a 30 day wait after a rejection, and even if you can press it, pressing it again on the same data gets the same answer.
Second, use the wait. Turn off any channel that sends product detail, such as Shopify's Meta data sharing. Remove gender and date of birth from advanced matching. Make a list of every place your site carries condition words, claims or treatment names, including image alt text and the names of your custom audiences and conversions, and change them. Send everything through one place that cleans it before it reaches Meta.
Third, build up clean data before you ask again. We aim for about four weeks. Check that what actually left your site is clean, event by event, before you press anything.
Fourth, decide now what you will do if the next answer is also no. If you leave that decision until the rejection arrives, you will make it in a panic. Options include running ads without a conversion signal, putting more into channels Meta cannot block, and, as a last resort with real risks, a separate clean store on another domain.
One vendor that looked at more than 125 accounts reports it found no genuine health seller that had its category removed through review. Take that as one sample, not a rule, but it is a good reason not to bet the business on the second attempt either.
Has anyone had a second review succeed after a clean-up? What did you change?
For reference, the DataCops delivery log marks every cleaned send, so before a second review you can check exactly what has been leaving your site.
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.
Not legal advice. The decision is Meta's, and it does not explain or negotiate it.