If Events Manager shows your dataset in the health and wellness category, or Meta has notified you that it is limiting the events your site or app can share, you are dealing with Meta's data-sharing restrictions, not ad review. Meta assigns categories to websites, apps and datasets, and a restricted category can carry one or more of three restriction types: core setup, which stops custom parameters and anything in a URL after the domain from being shared; restrictions on specific mid- and lower-funnel standard events, the part of the funnel where Purchase and Lead sit; and full restrictions on all events in some or all regions. This guide explains how classification works, how to check your dataset and which compliant campaign and measurement options remain. It is not a workaround guide.
What changed for health and wellness advertisers
Meta's Business Tools Terms already bar advertisers from sharing health information through the Meta Pixel, the Conversions API and the SDKs. What changed is enforcement at the source: Meta now categorizes websites, apps and datasets, limits or fully restricts the event data that sources in a restricted category can share, and notifies the advertiser by email and in Events Manager. Typical symptoms are a conversion event that can no longer be used for optimization, thinner reporting, and flagged custom audiences or custom conversions.
Meta health compliance now has two halves: what your ads say and what your site sends. Meta's Health and Wellness and Personal Attributes policies govern the first, from prohibited claims and body-image depictions to 18+ targeting for dietary, health and weight-loss products, and our health and wellness playbook covers it. The data restrictions govern the second, so a fully compliant ad can still lose its conversion signal. Online pharmacies and telehealth providers that promote prescription drugs face a third layer: LegitScript certification, Meta authorization, and targeting limited to people 18 and over in the US, Canada or New Zealand, covered in our LegitScript guide.
Region matters. Meta says each restriction can apply to specific countries or regions, or globally, and its help pages do not list which markets are affected. The notices on your own dataset are the only authoritative answer for your account.
How Meta classifies a business or dataset as health and wellness
Meta assigns categories to data sources, meaning the websites, apps and offline sources that send events through its Business Tools, based on the source's topics and the products or services provided. Its health and wellness definition covers sources associated with medical conditions or specific health statuses, provider and patient relationships, services for accessing personal health information, or health-related products and services. Meta's examples are a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace and condition-specific support group.
A data source lands in a category in one of two ways: Meta assigns it, or you self-categorize the dataset or an individual data source in Events Manager. Picking a category that carries restrictions can switch core setup on by default. If Meta assigns a different or more restrictive category, it applies on top of your choice and the most restrictive category wins. Separately, if you repeatedly receive notices that event parameters were blocked, Meta may place the dataset in core setup for at least 90 days.
The test is what the site is about and what the business sells, not your ad copy, so a clean ad does not change a category driven by the site. You can edit or remove categories you assigned yourself but not one Meta assigned; the only route there is a review request, and Meta emails its decision.
Restriction levels and core setup
Meta's Business Help Center names three restriction types. A category can carry one or more, and they can differ by country or region. Labels you may see elsewhere, such as tier 1, 2 and 3 or partial restrictions, are not Meta's, so go by the wording in your own Events Manager notice before acting on anyone's summary, including this one.
Core setup is the least disruptive of the three. A URL with a path and query string is cut back to the bare domain, and any parameter outside Meta's standard list is dropped. Standard events and standard parameters such as value, currency and content IDs still flow, and Meta says most campaigns should continue to run as expected. The side effects: audiences built on URL rules or custom parameters may populate slowly or not at all, Events Manager shows less detail (Sampled Activities and the test events tool included), automatic advanced matching may be unavailable, adding catalog items through the pixel may stop working, and custom events must be reviewed and confirmed before they can be used.
If you or a colleague switched core setup on, you can switch it off under Data restrictions in the dataset settings, and if it came from a category you assigned, removing that category may switch it off. If Meta applied it, you cannot. Some teams turn it on voluntarily as a safety net while they audit their integration, an option Meta's documentation suggests considering, but Meta is explicit that core setup is not a substitute for your own compliance checks.
- Core setup: custom parameters and anything in a URL after the domain are not shared
- Restriction on certain standard events: specific mid- and lower-funnel events are not shared
- Full restrictions: no events are shared, and Business Tools cannot be used for ads, in the affected regions
What is restricted: events, URL parameters, optimization goals
The Purchase event is where most of the pain sits. Under core setup alone, Purchase is a standard event, so it keeps flowing with its value and currency, and purchase optimization can continue on a thinner signal. Under a restriction on certain standard events, Meta stops accepting specific mid- and lower-funnel events. Its help pages describe that bracket without listing the events, but it is where AddToCart, InitiateCheckout, Purchase, Lead and CompleteRegistration sit, so treat your main conversion event as at risk until the notice on your dataset says otherwise.
When an event is restricted, everything built on it goes with it: optimizing for that event, value-based bidding on purchase value, custom conversions that filter it, audiences based on it and its results column in Ads Manager. Meta cannot optimize toward or report on data it no longer receives, so confirm every live ad set still optimizes for an available event instead of waiting for results to tell you.
Restrictions reach the rest of the setup too. On a dataset with data restrictions, custom events are blocked until someone reviews and confirms them, and Meta can block custom events and parameters it detects as carrying prohibited information. Custom audiences and custom conversions that reference a specific health condition (Meta's example is arthritis) are flagged and cannot be used in new campaigns. A published campaign cannot switch to a different custom conversion, so Meta suggests duplicating it with a clean one, and you can request a review if something was flagged in error. Names count: Meta's terms say the names and criteria for events, conversions and custom audiences must not reflect, imply or be based on health information.
That is why renaming is not a fix. Re-sending a restricted Purchase as a neutrally named custom event, or moving the same events to a fresh pixel or domain, is the same data under a new label. Meta tells advertisers not to attempt to resend data it has detected and removed, and warns that non-compliance can lead to further data restrictions or suspension of Business Tools access. Removing a condition name from a URL or parameter is compliance; relabelling restricted data so Meta accepts it is circumvention.
How to check your dataset status in Events Manager
To manage categories you need full control of the business portfolio or an admin role on the ad account that owns the dataset; reviewing custom events and blocked parameters needs full control of the dataset itself. Open Events Manager, click Datasets, select the dataset and open the Settings tab, then work through the sections below. The data source categories section may not appear if none of your sources is in a category, and labels move occasionally, so look for the nearest equivalent.
Then audit what you are actually sending. Open an event, click View details, and use the URL breakdown and Sampled Activities to review recent pages, parameters and URLs from the pixel and the Conversions API. Look for condition names in page paths, quiz answers in parameters, medication names in content fields and health terms in custom event names. With core setup on, some of this detail is hidden, so check your tag manager and server payloads directly too.
If a Meta-assigned category is genuinely wrong, for example a general fitness apparel store tagged as health and wellness, request a review from the Manage data source categories screen via View details. Meta emails its decision, its help pages give no timeline, and approval is not automatic. Custom events blocked by Meta get a single review: if it is not approved, the event stays blocked and you cannot request another.
- Data restrictions: whether core setup is on, and whether you can turn it off
- Dataset categories: the categories applied to the dataset, or None if you have not assigned one
- Manage data source categories: each site or app, its category and its status
- Data controls, Manage event blocking: custom events under Action required, Blocked and Confirmed
- Diagnostics tab: Event parameters blocked messages and the pages involved
Campaign objectives and events that remain available
Under core setup only, keep optimizing for standard events and fix the side effects. Rebuild audiences on standard events instead of URL rules, set up advanced matching manually if the automatic version is unavailable, and add catalog items by feed or manual upload if pixel updates stop. Clean the standard fields you still send too: core setup only restricts custom parameters and URLs, so a condition name in a standard field such as a product name still reaches Meta and is still your problem.
With restrictions on certain standard events, Meta suggests evaluating which events are restricted and leaning on upper-funnel events that remain available for optimization and audience targeting. Expect the system to find people who browse rather than people who buy, so creative, offer and landing page have to do more of the qualifying. Consolidate ad sets so each can still reach the roughly 50 optimization events a week that Meta associates with exiting the learning phase.
Under full restrictions, Business Tools data cannot be used for ads in the affected regions. Meta points to objectives that do not rely on it: Awareness (reach, impressions), Engagement (likes, comments, shares) and Traffic (link clicks). Some teams also test on-platform lead forms, but form questions still fall under Meta's rule that ads must not ask for personal attributes, including medical conditions, and lead outcomes you send back from your CRM go through a dataset that can be categorized and restricted like any other.
Measuring performance without lower-funnel events
Once purchases stop reaching Meta, Ads Manager stops being the source of truth for revenue. Move the scoreboard to your own systems: blended MER (total revenue divided by total ad spend), new-customer revenue and CAC from your backend, read weekly against Meta spend. Our ROAS vs MER guide covers the mechanics; the short version is that MER cannot be broken by a missing pixel event.
Keep UTM parameters on ad links so your own analytics can attribute sessions and orders by campaign and ad; core setup limits what the pixel shares with Meta, not what your site reads from its own URLs. Keep condition names out of UTM values, and make sure your analytics and CRM setup meets your own health privacy obligations, which for covered providers can include HIPAA. Meta itself tells advertisers to work with their own legal counsel on a data-sharing compliance plan.
For incrementality, use tests that need nothing from restricted events: geographic holdouts measured in backend sales, planned spend step-ups and pull-backs read against MER, and post-purchase surveys. Meta still recommends the Conversions API, and for a health brand its real value is control: your server decides exactly which events and parameters leave your systems. It bypasses nothing, because the restrictions apply to data shared through any Meta Business Tool, the Conversions API included.
Why switching ad accounts doesn't change the classification
The category sits on the data source and its dataset, and it is based on what the site is about and what the business sells. Running the same dataset through a new ad account, a second business portfolio or an agency ad account changes none of those inputs. Meta restricts the data being shared, not the account spending against it, so the restrictions travel with your data wherever it is used.
A fresh pixel or new domain built to escape the category is an attempt to circumvent a restriction, and it puts the assets you need for scale at risk under Meta's terms. Meta keeps categorizing data sources over time, and the only legitimate route out of a wrong category is a review request.
What agency ad accounts do change for a health brand is capacity and resilience: more accounts to spread spend across, billing that does not depend on your own cards, and replacements when an account has a problem. With Power Ads, accounts are created in our business portfolio and shared into yours through partner access. Your dataset, its category and its restrictions stay as they are, and every ad still goes through Meta's review under its Advertising Standards. One caveat for prescription drug advertisers: Meta authorizes prescription drug ads per ad account, and its flow for sharing an existing authorization covers other ad accounts within the same business portfolio. Agency accounts sit in the provider's portfolio, so confirm how authorization would cover an account before planning prescription drug spend on it.
Pre-scale checklist for health brands
Run this before you push budget on a health, supplement or telehealth offer. It is a working session with whoever owns your tracking, and it prevents the costliest mistake in this vertical: scaling ad sets whose optimization event Meta has already stopped accepting.
Then plan the account side. At $100k or more a month, spreading spend across several accounts limits the damage when one has a problem. Power Ads supplies agency ad accounts only and does not run campaigns, so your team keeps full ownership of the data setup and compliance work in this guide.
- Check every dataset's Settings for categories, core setup status and blocked events
- Audit URLs, parameters and custom event names for conditions, medications and treatments
- Rebuild audiences and custom conversions whose names or rules reference health conditions
- Confirm each live ad set optimizes for an event that is still available
- Stand up MER and backend reporting before trusting Ads Manager results
- Clear content rules: claims, 18+ targeting, LegitScript and Meta authorization where required
- Request a review only if the category is wrong, and never resend blocked data
Key takeaways
- Meta's health and wellness restrictions attach to data sources and datasets, not to ad accounts or ad copy.
- Meta names three restriction types (core setup, restriction on certain standard events and full restrictions), and they can vary by country or region.
- Core setup strips custom parameters and everything in a URL after the domain, but standard events such as Purchase keep flowing.
- Events Manager Settings and Diagnostics show your categories, core setup status, blocked custom events and blocked parameters.
- Renaming or re-routing restricted events is circumvention; fix prohibited data instead and request a review only if the category is wrong.
- Measure on MER and backend data, and treat agency accounts as capacity and redundancy, not a way out of the category.
FAQ
What is the Meta health and wellness category?
It is one of Meta's data source categories for websites, apps and datasets. Meta applies it to sources associated with medical conditions or health statuses, provider and patient relationships, access to personal health information, or health-related products and services, such as patient portals, wellness trackers, telemedicine platforms and pharmacies. The category can bring data-sharing restrictions that limit which events and parameters Meta accepts.
What is core setup in Meta Events Manager?
Core setup is a set of data-sharing restrictions on a pixel or dataset. It stops custom parameters and anything in a URL after the domain from being shared with Meta, while standard events and standard parameters such as value and currency still flow. Meta can apply it, a category that carries restrictions can switch it on, repeated blocked-parameter notices can put a dataset in it for at least 90 days, and you can turn it on yourself.
Can health and wellness advertisers still optimize for purchases on Meta?
It depends on the restriction. With core setup only, Purchase is still a standard event and can generally be used for optimization. If your dataset has restrictions on certain standard events, Purchase and other mid- and lower-funnel events may be restricted, and Meta suggests leaning on upper-funnel events instead. You cannot lift a Meta-applied restriction yourself; if the category is wrong, request a review in Events Manager.
Will a new ad account or agency ad account remove the health and wellness restriction?
No. Meta assigns the category to the data source, meaning your website, app or offline source, and the dataset connected to it, based on its topics and what the business sells. A new ad account, a second business portfolio or an agency ad account still carries the same site's data, which is what the restriction is attached to. Agency accounts add spend capacity and redundancy, not a different classification.
How do I check if my Meta pixel is restricted for health and wellness?
In Events Manager, open Datasets, select the dataset and go to Settings. Check Data restrictions for core setup, Dataset categories and Manage data source categories for assigned categories, and Manage event blocking under Data controls for blocked custom events. The Diagnostics tab shows blocked parameters. Meta also notifies affected advertisers by email and in Events Manager.
Can I rename blocked events or send them as custom events instead?
You shouldn't. Re-sending a restricted event under a neutral name, or through a new pixel or domain, is the same data under a different label and amounts to circumventing the restriction. Meta's terms say the names and criteria of events, conversions and audiences must not reflect, imply or be based on health information, Meta tells advertisers not to resend data it has removed, and non-compliance can bring further data restrictions or suspension of Business Tools access.
Sources
- facebook.com/business/help/511197658391698
- facebook.com/business/help/1402913027039332
- facebook.com/business/help/124742407297678
- facebook.com/business/help/467621355878794
- facebook.com/business/help/1666235380728268
- facebook.com/business/help/423150200627651
- facebook.com/business/help/361948878201809
- facebook.com/business/help/414614186228298
- facebook.com/business/help/3720004518245751
- facebook.com/business/help/344247017987537
- facebook.com/business/help/642275438032995
- facebook.com/business/help/815029860145251
- facebook.com/business/help/1055828013359808
- facebook.com/business/help/2455915321411996
- facebook.com/business/help/910877842876429
- facebook.com/business/help/263390265553560
- facebook.com/legal/technology_terms
- transparency.meta.com/policies/ad-standards/restricted-goods-services/health-wellness
- transparency.meta.com/policies/ad-standards/restricted-goods-services/drugs-pharmaceuticals
- transparency.meta.com/policies/ad-standards/objectionable-content/privacy-violations-personal-attributes
