Meta Restricted Your Health Dataset: How Do You Keep Campaigns Optimizing?

What this means for you

• Open Events Manager and find the restriction level. Meta uses three: core setup, restrictions on certain standard events, and full restrictions.
• Core setup strips custom parameters and everything in a URL after the domain. Meta says most campaigns should keep running, with limits on some features.
• For restricted standard events, Meta says only that it restricts specific mid and lower funnel events. Check your own dataset, then optimise on the deepest event still allowed.
• Under full restrictions, Meta suggests objectives that don't rely on shared data: Awareness, Engagement and Traffic.
• If Meta turned core setup on, you can't turn it off, and repeated blocked-parameter notices can keep a tool in core setup for at least 90 days.
• Meta categorises data sources such as the website itself, so the category follows the site. A wrong category is fixed by Meta's review, not by a new dataset.

MedScale Health, a paid acquisition agency for telehealth brands and clinics, rebuilds Meta tracking and campaigns for health brands whose datasets Meta has restricted. This page is the performance side: what to optimise on and how to measure once a restriction is in place. Meta's wording is quoted below as read on October 8, 2026. 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.

Step one: confirm which restriction applies

Meta's help page on data sharing restrictions says data sources such as websites and apps may be assigned to a data source category, and a category may carry one or more of three restrictions. In Meta's words: "Core Setup: Restricts the sharing of custom parameters and parts of URLs following the domain." "Restriction on certain standard events: Restricts the sharing of specific mid and lower funnel events." "Full restrictions: Fully restrict the sharing of all events in specific regions or all regions." Meta says it tells you by email and in Events Manager, and that a restriction can apply to certain countries or regions or globally.

Health and wellness is on Meta's list of categories that may carry restrictions. Meta describes it as associated with medical conditions, provider and patient relationships, or health-related products and services, and names a telemedicine platform and a pharmacy among its examples. Meta does not publish which standard events each level blocks, so check your own dataset's settings and diagnostics.

Step two: choose the event you can still optimise on

For restricted standard events, Meta's advice is to evaluate which events are restricted and explore alternative events, and it says you may want to consider leveraging more upper-funnel events to maintain effective audience targeting and campaign optimisation. In practice that means walking up the funnel from the order to the first event the dataset still accepts, such as a started intake or a viewed program page, and checking that it happens often enough to optimise on.

Custom events need a decision too. Meta says that when a tool has data restrictions, custom events are blocked until you review and confirm them, and that you should only confirm an event if its data follows the Meta Business Tools Terms. Custom conversions that reference a specific health condition are flagged, and Meta says flagged custom conversions can't be used when creating new campaigns.

Step three: change the objective under full restrictions

When every event is restricted, Meta suggests optimising for objectives that do not rely on data shared through the Meta Business Tools, and names Awareness (reach, impressions), Engagements (likes, comments, shares) and Traffic (link clicks). They optimise for the view or the click, so the landing page and intake flow carry more of the work.

Core setup: what changes and for how long

Core setup removes custom parameters and shortens every URL to the domain, so a path such as example.com/weight/checkout arrives as example.com. Meta lists the effects: custom audiences built on URLs or custom parameters may not populate, and automatic advanced matching may be unavailable. Meta's on-and-off page says that if Meta has turned on data restrictions for your core setup, you won't be able to turn it off. Its blocked parameters page says repeated notices may place a tool into core setup for at least 90 days.

Step four: rebuild the events with neutral names

MedScale moves conversion events server-side so every field is controlled, uses standard event names such as Lead and Purchase rather than a condition or a drug, sends no custom parameters that describe health, and keeps condition words out of URLs. This is not a way around a restriction. Meta's Business Tools Terms list the Conversions API alongside the Meta Pixel as Business Tools, and the restrictions apply to data shared through those tools, so changing how events are sent does not lift a category Meta has applied. It does keep the account to what Meta's terms allow.

Step five: count the real outcome off-platform

A restricted dataset reports less, so Ads Manager stops being the scoreboard. MedScale reports from the intake system and the order record, counting new patients and first orders by campaign from the UTM tags on the landing page, and compares cost per patient each week against the agreed target.

If the category is wrong

Meta says that if you think a category it assigned is not appropriate, you can ask it to review the category, and it emails the decision. The request is made in Events Manager under Datasets, then Settings, Manage data source categories, View details and Request review. Meta says this needs full control of the business portfolio or an admin role on the ad account that owns the dataset, and that you can't modify a Meta-assigned category yourself. Meta's own examples include telemedicine platforms and pharmacies, so for those businesses the category is usually right and the work is optimisation within it.

What MedScale changes in the first week

• Day 1: read the category, restriction level and diagnostics for every dataset, and list blocked parameters and flagged custom conversions.
• Days 2 and 3: rename events to standard names, send them server-side with no personal data, and clear health words from URLs and parameters.
• Days 4 and 5: choose each campaign's event from what the dataset still accepts, or move to Awareness, Engagement or Traffic, rebuild flagged campaigns, and switch reporting to patients counted off-platform.

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. MedScale never opens a replacement account, Page or business portfolio to get around a platform's decision, and no approval or reinstatement is promised. Book the free growth audit at medscale.health/audit for a written read of your datasets, or see Ad Account Rescue at medscale.health/rescue if the ad account is restricted too.