Meta Health Restriction Checker

Why health pages get restricted

Since January 2025 Meta limits what health and wellness advertisers can share about visitors. Meta does not only look at the ad. It looks at the data your site sends back: the page address, the page title, the names of your events and the details in them. When those reveal a treatment or a condition, Meta restricts the dataset. Events lose their detail, optimisation for leads and sales gets weaker, and the restriction follows the dataset and the domain into every campaign.

The cause is usually invisible. Clinics and agencies check their funnel builder, find no pixel in the tracking code, and still get restricted. That is because the pixel is often added after the page loads, by another script.

How the check works

1. We open the page like a visitor. A real Chrome browser loads your link, runs every script on it and waits for the page to settle. Reading the page code alone misses pixels that other scripts add later, so we do not rely on it.
2. We record every request. Each call the page makes is logged: Meta's pixel, the Conversions API helpers, Google Ads, TikTok and any other tag. For each Meta pixel we note which script loaded it.
3. We read what Meta already thinks. Every Meta pixel loads a settings file from Meta. We read it to see whether Meta already runs that pixel in a restricted data mode, and which custom event names are set up on it.
4. We check the words. Event names and the page address are compared against a list of treatment and condition words in English and Spanish, such as implant, veneer, botox, weight loss, IVF or therapy.
5. We write the report. The results become a short audit in plain words. It only states what the check saw. It never guesses your exact restriction level, because only your Meta account shows that.

What the report covers

What the report contains

The report follows the same structure as the audits we write for agencies by hand:

• Summary. Likely restricted or not, in two lines.
• What we found. Each check with Pass, Review or Fix, and the evidence: the pixel ID, the script that loaded it, the event names.
• What could happen. Lost event detail, weaker optimisation, and the same event counted twice when the pixel and the server both send it.
• Fix plan. The steps in order, ending with asking Meta to review the dataset once the page is clean.

A typical finding

A dental clinic runs ads to an implant offer page built in a funnel builder. There is no Meta code in the builder's tracking settings. The check shows that a third-party tracking script loads first and then adds Meta's pixel, that a custom event named after veneers fires on the form, and that Meta's own settings file already puts the pixel in a restricted data mode. The fix is to remove that script, rename the event, and send conversions server-side with the health details removed.

For agencies

Paste each client page, or send this link to the client. Every check is saved under your email, so you can come back with the same email, open any report and show the client exactly what was found. Each email gets 5 checks a month.

After the check

Most pages need the same three steps: remove the outside pixel, rename events that name a treatment, and send conversions server-side with health details removed. DataCops health mode does the last step for every event: the page address is cut to your domain, event names become neutral codes, and only the ad click, the value and hashed email and phone are sent. See how health mode works.