Meta health and wellness restrictions: what's blocked
What Meta's health and wellness data restrictions block, how Core setup and restricted events work, and what to do when you can't optimize for purchase.
By DATALYR · · 6 min read
Contents
What Meta's health and wellness restrictions are
Meta's health and wellness restrictions limit the event data a health-related website or app can share through the Meta Pixel, the Conversions API and other Meta Business Tools. Depending on the restriction, Meta strips URLs and custom parameters (Core setup), blocks specific mid- and lower-funnel events such as purchases (restricted events), or stops event sharing altogether (full restriction).
They are data-sharing restrictions, not ad-approval rules. Your ads can still run. What changes is which conversion events Meta receives, and therefore which events your campaigns can optimize for and report on.
Meta assigns a category to a data source based on its topics and the products or services it provides. Its help center describes the health and wellness category as sources associated with medical conditions or health statuses, provider and patient relationships, access to personal health information, or health-related products and services. Its examples include a patient portal, a wellness tracker, a telemedicine platform, a pharmacy, a health insurance marketplace and a condition-specific support group.
This guide covers the data side: categories, Core setup, restricted events and what to do next. For the broader measurement workflow, read the health and wellness ad tracking guide linked below.
The three levels: Core setup, restricted events, full restriction
Meta lists three types of restriction for a category with additional data-sharing limits. They can apply to specific countries or regions, or globally, and Meta notifies you by email and in Events Manager when it applies one.
If a data source has restrictions, Meta also blocks custom events automatically until you review and confirm them. Under a full restriction they may not be available at all.
- Core setup: restricts the sharing of custom parameters and anything in a URL after the domain.
- Restriction on certain standard events: restricts the sharing of specific mid- and lower-funnel events.
- Full restriction: blocks the sharing of all events in specific regions or all regions; Meta Business Tools cannot be used for ads purposes where it applies.
What each level removes from your event data
1. Core setup
Domain only, standard parameters only
https://example.com/weight-loss/plan?step=2 is shortened to https://example.com/.
2. Restricted events
Named events withheld
Mid- and lower-funnel events such as a purchase stop reaching Meta.
3. Full restriction
No events in the region
Optimize for objectives that don't rely on shared event data.
What Meta Core setup is and what it changes
Core setup is a set of data-sharing restrictions that Meta can apply to a Pixel or dataset, or that you can turn on yourself in Events Manager. It restricts custom parameters (any parameter not on Meta's standard list) and every part of a URL after the domain. Meta's own example shortens a product URL with a path and query string to the bare domain.
Meta says most campaigns should keep running as expected under Core setup, with limits in certain advertiser experiences. Its help page lists these effects:
- Custom audiences that rely on custom parameters or URL rules may not prefill, may take longer to populate or may be unavailable.
- Ad sets can be affected when such an audience shrinks or stops updating.
- Events Manager may no longer show custom parameters or URL paths, including in sampled activity and the test events tool.
- Automatic advanced matching may be unavailable; you can set up advanced matching manually.
- Adding catalog items through the Pixel may stop working.
- Custom web, app and offline events need review before you can use them.
Why you can't optimize for purchase
If your data source is restricted for certain standard events, Meta stops accepting those events. When the restricted list includes Purchase, Meta does not receive purchases from that source, so a sales campaign has no purchase signal to optimize toward. The same applies to any other restricted mid- or lower-funnel event.
Custom conversions are a separate check. Meta says a custom conversion must not suggest information its terms prohibit, such as a specific health condition. Flagged custom conversions can't be used in new campaigns, and Meta recommends duplicating an affected campaign with an unflagged conversion. Renaming a restricted event to slip it through is not a fix: Meta's prohibited-information page says event names and criteria must not reflect or imply prohibited information.
Meta's own guidance for restricted events is to evaluate which events are restricted and consider alternatives, for example events further up the funnel, while making sure you are not sharing prohibited information. Under a full restriction, Meta suggests objectives that don't rely on shared event data, such as Awareness, Engagement and Traffic.
Example: a restricted purchase still has a measurable return
Consider a hypothetical wellness subscription that spends $3,000 on Meta in a month. Its own records show 50 first payments of $120, or $6,000 in revenue. Meta has restricted Purchase for the data source, so Meta receives none of those 50 events.
Inside Meta, the campaign optimizes for a permitted upper-funnel event and shows no purchase value. In first-party measurement tied to the payment records, the same month shows $6,000 of revenue against $3,000 of spend: a 2.0× return. The payments did not disappear. Only the signal Meta is allowed to receive changed.
That separation is the practical answer to a restriction: send Meta only what it permits, and judge campaigns on revenue measured in your own records.
One month, two views
Sent to Meta
0 purchases
Purchase is a restricted event for this data source.
Measured first-party
$6,000 ÷ $3,000 = 2.0×
50 payments × $120, attributed to the campaign by your own records.
What to do after a restriction notice
Start in Events Manager. Check the category assigned to each dataset and data source, and which restriction applies. Meta lets you request a review if you think a Meta-assigned category is wrong; you can change categories you assigned yourself, but not one Meta assigned.
Then work through the data, the campaigns and the measurement in that order.
- Read the notice and note its scope: which data source, which events and which regions.
- Remove health details from URLs, page titles, product names, form fields and custom parameters at the source.
- Review custom events and confirm only those that follow Meta's terms.
- Move campaigns to permitted events or objectives, as Meta's guidance suggests.
- Keep measuring revenue from your payment records so budget decisions don't depend on the restricted signal.
- Don't rename events, move them to another sender or use a server path to get around the restriction.
Special ad categories and the personal attributes policy
Health is not one of Meta's special ad categories. Those cover housing, employment, financial products and services, and social issues, elections or politics, and they limit audience options for the first three. Health advertisers deal instead with the data restrictions above and the ad content policies below.
Meta's personal attributes policy bans ad copy that asserts or implies a person's physical or mental health, including medical conditions. Meta's examples allow “Depression counseling” and “New diabetes treatment available”, and reject “Do you have diabetes?”. Separate policies cover health and wellness products (18+ targeting for weight loss, supplements and cosmetic procedures) and prescription drugs.
How DATALYR handles Meta restrictions
DATALYR filters health-related fields from the conversions it sends once you turn on health filtering, and its managed Meta, Google and TikTok browser pixels stay off while filtering is on. When you receive a notice, you record it in Settings and DATALYR withholds what it requires: under Core setup it filters supported data and URLs and withholds app events and the managed Pixel; under restricted events it withholds the exact Meta events you enter; under a full restriction it withholds all Meta server events.
You can also pause sharing with a platform while you review. First-party collection continues the whole time, so revenue reporting by campaign keeps working. Filtering does not make a restricted event permitted and does not guarantee platform approval.
Related articles.
Health and wellness ·
Healthcare Facebook ads: rules, copy and tracking
How healthcare, mental health, med spa and men's health brands run Facebook ads within Meta's policies, and measure paid patients when data is restricted.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
Use cases ·
Health and wellness ad tracking: measure conversions with careful data handling
Design a wellness measurement workflow that separates collection, filtering, platform restrictions, and attribution without promising a tracking workaround.
