Platform

Health and wellness ad restrictions

If your account sells anything health, medical, or wellness adjacent, Meta and other platforms limit what your conversion data can be used for. Most of the advice on how to get around this does not work. Here is what actually happens, and what actually helps.

What it is

Since 2025, Meta classifies advertisers as health and wellness when the account is associated with medical conditions, treatment, or a provider and patient relationship. Once flagged, Meta stops using your bottom-funnel conversion events, like a booked appointment or a completed purchase, for optimization or audience building. Your campaigns keep running. They just stop learning from your best signal.

The restriction, plainly

A dental clinic, med spa, mental health practice, weight-loss brand, or supplement seller can all be classified this way, whether or not the business is a clinical provider. The classification sits on the domain and the ad account, not on any single campaign. Once it applies:

  • Standard conversion events like Purchase, Lead, and CompleteRegistration stop being usable for optimization.
  • Custom audiences built from those events stop updating.
  • Upper-funnel events like PageView keep working, so the drop can look like a mystery performance decline rather than a policy change.

This is separate from HIPAA, and separate from any advertiser's own ad copy review. It is a data-restriction system, not a content-review system, and the two run independently of each other.

What actually triggers it

Classification looks at the domain's content and the events sent to it, not just what you declare when you set up the ad account. It reads the full event, not only the event name: the URL path, the parameters, and any product or content names in the payload. A page at /root-canal-consult or a custom parameter like appointment_type: dental_implant is enough on its own, independent of what the event itself is called.

Why the common fixes fail

Two workarounds get repeated constantly. Neither holds up:

  • Renaming the event. Calling a purchase event event_01 instead of Purchase does nothing if the payload still carries a content name, a category, or a URL that reveals the same thing. The classifier reads the whole event, not the label on it.
  • Moving to a subdomain. A subdomain inherits its root domain's classification. Pointing your pixel at shop.yourclinic.com instead of yourclinic.com changes nothing if the root is already flagged.

Both of these are attempts to disguise the event rather than remove what makes it sensitive. That distinction is the whole ballgame, and it's the next section.

How DataCops handles it

The rule is strip, never disguise. DataCops has a per-site switch called health mode. When it is on, every conversion is cleaned before it reaches any ad platform. The cleaning is an allow list, not a block list: only a short, fixed set of fields may pass, and everything else is dropped. That matters because form answers arrive under any name a form builder picks. A block list would miss them. An allow list cannot.

The page link is cut down to your domain. https://yourclinic.com/ivf/book?x=1 becomes https://yourclinic.com/. Product names, categories, page titles, referrers and every custom or form field are removed. What is left is what a platform needs to count the conversion and match it to an ad: a hashed email or phone, the ad click id, the value, the currency, and the time. Nothing is hidden inside a renamed field. It is gone.

The cleaning follows fixed rules, the same way for every event. It also runs after any field mapping you set in the Event Manager, so a mapped field can never add the details back in.

How health mode turns on

You do not have to find the switch yourself. Here is what happens:

  1. You connect an ad platform

    When you connect any of the 8 ad platforms, DataCops reads your homepage once.

  2. Our AI checks the page

    It decides whether the site is a health business: medical, dental, mental health, med spa, fertility, weight loss, pharmacy, telehealth and similar. It must quote the words on your page that show it. Reasons it cannot find on the page are thrown away.

  3. Sure means on, unsure means suggest

    If the AI is sure, health mode turns on and you see a notice. If it is unsure, DataCops suggests it and leaves the choice to you.

  4. Your choice wins

    You can turn health mode on or off in the site's settings at any time. Once you choose, detection never changes it. Detection also never turns health mode off by itself.

The AI only decides whether to suggest or switch on health mode. It never touches the events themselves. You can also press Check again to re-read your homepage after you change it.

The same check looks for Meta's own browser pixel and for Google Tag Manager on your homepage. If the pixel is there, DataCops warns you: the pixel sends full page links straight from the browser, and health mode can only clean what DataCops sends.

What is sent, field by field

With health mode on, this is what your ad platforms receive:

DetailSent to ad platforms
Page linkYour domain only, for example https://yourclinic.com/
Path, query string, referrer, page titleNever sent
Email and phoneHashed by each platform sender
Ad click ids (fbclid, gclid, ttclid and others)Sent
Value, currency, order id, event timeSent
IP address and browserSent, for matching
Consent and region signalsSent
Product names, categories, form answers, treatmentsNever sent

Your own CRM and email tools still get the full details. They are your systems, not ad platforms, so health mode leaves them alone. Every cleaned send is marked Cleaned in the delivery report, so you can check it worked.

Neutral event names on Meta

Renaming alone does not work, as shown above. But once the content is gone, a standard name like Purchase or Schedule is the last hint left. So with health mode on, DataCops also sends Meta a neutral name:

Your eventWhat Meta sees
LeadL_1
ScheduleS_1
PurchaseP_1
CompleteRegistrationR_1
ContactC_1
SubmitApplicationA_1
Any other eventE_1

The name change is for Meta only. The strip is what removes the sensitive detail; the name is the last step, not the fix.

Finish setup in Meta

  1. In Meta Events Manager, create a custom conversion on L_1 or S_1 and use it as your campaign goal.
  2. Remove Meta's own pixel from your site. DataCops only cleans what DataCops sends.
  3. Send a test lead and check the delivery report shows it as Cleaned.

Every ad platform, not just Meta

This is not a Meta-only problem, and DataCops does not treat it as one. The same strip applies to all 8 ad platforms DataCops sends to: Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X. Each gets exactly what it needs to count the conversion and nothing that says why. One rule, applied everywhere your conversions go.

Health mode works with every other part of the platform. Offline conversions from your CRM, such as a booked or attended appointment, are cleaned the same way. Real people only and the consent gate still apply as usual.

Good to know before you start

  • Health mode is a technical cleaning step. It is not a HIPAA compliance service; if you need a covered vendor relationship, talk to a compliance provider.
  • Meta decides how it classifies your account. Health mode makes sure what DataCops sends carries no health detail.
  • Optimise Meta campaigns on the neutral custom conversion, since standard events stay restricted for flagged accounts.
  • Remove browser pixels that send page links. Health mode cleans DataCops sends only.
Was this page helpful?