What Happens When Meta Restricts a Health Site's Conversions?

What this means for you

• Meta may assign a data source to a category. Health and wellness covers sites tied to medical conditions, provider and patient relationships or health products, and Meta names telemedicine platforms and pharmacies as examples.
• A restricted source can lose custom parameters and URL paths, certain mid and lower funnel events, or every event.
• Custom conversions and audiences that reference a health condition are flagged. A flagged custom conversion can't be used in a new campaign, and a published campaign can't swap it out.
• You can't edit a category Meta assigned, but you can ask Meta to review it.
• What still works: neutral standard events that say nothing about a condition, sent server-side, with no personal data.

MedScale Health, a paid acquisition agency for telehealth brands and clinics, regularly finds these restrictions when it audits health accounts. This page explains what each restriction does, using Meta's Business Help Center, and what to track instead. It names no tracking tools; the approach works with any server-side setup that meets the rules below. This page is marketing guidance, not medical or legal advice. Platform policies change, so check the sources listed at the end before acting on a specific rule.

How Meta categorises a health site

Meta says data sources that share data through its Business Tools, such as websites and apps, may be assigned a category based on their topics and the products or services they provide. Health and wellness is one of the categories that may carry extra data sharing restrictions. Meta describes it as a source associated with medical conditions or specific health statuses, provider and patient relationships, services for accessing personal health information, or health-related products and services. Its examples include a patient portal, a telemedicine platform and a pharmacy.

You can categorise your own datasets, and Meta may categorise them too. You can change a category you set, but not one Meta assigned. If you think Meta's category is wrong, you can ask for a review in Events Manager, and Meta replies by email. Meta also says it notifies advertisers by email and in Events Manager when it limits or restricts a source, and that restrictions can apply to specific countries or globally.

The three levels of restriction

• Core setup. Custom parameters and anything in a URL after the domain are stripped, so a visit to a treatment page arrives as the bare domain. Audiences built on URLs or custom parameters may not populate, and automatic advanced matching may be unavailable.
• Restriction on certain standard events. Specific mid and lower funnel events can't be shared. Meta says restrictions vary by category and region, so check which events are affected in Events Manager.
• Full restriction. No events are shared in the affected regions, and the Business Tools can't be used for ads purposes there.

Meta adds that when a tool has data restrictions, custom events are blocked automatically until you review and confirm them. For restricted standard events, it suggests considering upper funnel events. For a full restriction, it suggests objectives that don't rely on shared data, such as awareness, engagement and traffic.

Flagged custom conversions and audiences

Separately from the category, Meta checks what custom conversions and audiences say. Its help page is direct: custom conversions must not suggest information its terms prohibit, and references to specific health conditions aren't allowed. A flagged custom conversion can't be used when you create a new campaign. For a running campaign, Meta suggests duplicating it with a custom conversion that isn't flagged, because once a campaign is published its custom conversion can't be changed. Custom and lookalike audiences that reference a condition are flagged the same way, and a lookalike built on a flagged seed audience stays flagged until the seed is fixed. Either can be sent for review if you believe the flag is a mistake.

The rule underneath is Meta's prohibited information policy. It lists information about physical or mental health, including conditions, prescription medications, procedures and treatments. It says the names and criteria of events, conversions and custom audiences must not reflect, imply or be based on that information, and that it must not appear in URL parameters, custom event names or custom data. Meta warns that breaking these terms can lead to performance issues, data restrictions, or suspension of the Business Tools.

What to track instead

• Neutral standard events. Lead, Schedule, CompleteRegistration and Purchase say what happened, not why. Never put a condition or a drug in an event name, a custom conversion rule or a URL parameter.
• Use what the category still allows. Optimise on the deepest event your dataset can still send that happens often enough for Meta to learn from.
• Server-side delivery. Sending events from a server rather than a browser pixel lets you decide exactly what leaves: the event name, the time and a value, with nothing from the page address.
• A BAA where HIPAA applies. Under 45 CFR 164.502(e), a covered entity may let a business associate receive protected health information only with satisfactory assurances documented in a written agreement. Any vendor that handles your event data on the way to an ad platform should sign one.
• No personal data to ad platforms. No names, emails, phone numbers, IP addresses or browser IDs, hashed or not.

This trades some match quality for a clean signal. A smaller set of neutral events keeps the account able to optimise, while a richer feed that reveals health information is the kind of data Meta says can lead to restrictions.

What MedScale does

MedScale Health checks each account's dataset category and restrictions in Events Manager before choosing an optimisation event, renames condition-named events and custom conversions, and rebuilds flagged campaigns on clean ones. MedScale tracks server-side under a BAA with neutral event names, and no names, emails, phone numbers, IP addresses or browser IDs go to any ad platform. Where a category looks wrong, we ask Meta for a review with the evidence. We never open a new dataset, Page or account to route around a restriction, and no reversal is promised. Book the free growth audit at medscale.health/audit, or see Ad Account Rescue at medscale.health/rescue if the account itself is restricted.