Remove Meta's Health & Wellness Restriction. Here's How

Summary / TL;DR

It is possible to remove Meta's Health & Wellness restriction from your tracking. It requires a structural change to how your data reaches Meta, not a successful appeal.

Meta provides a "request review" button inside Events Manager. It is automated, does not accept supporting evidence, and returns a decision in 3 to 7 days. If rejected, you wait 30 days before resubmitting.

Across 75+ Meta ad accounts we reviewed spanning January 2025 through Q1 2026, and across every major practitioner community (Shopify Merchants, Stape forums, r/FacebookAds, Foxwell Founders), we found no documented case of a brand that genuinely sells health or wellness products successfully having the category removed through this appeal process.

The brands that restored their events did it by changing what Meta receives, not by convincing Meta to reclassify them.

Key Takeaways

• Meta's appeal is a one-click "request review" button inside Events Manager. Automated. No evidence field. 3 to 7 day turnaround. 30-day cooldown after rejection.

• Appeals work when the classification is genuinely wrong: an ergonomic furniture brand flagged as medical equipment, a protein bar company flagged as supplements. If Meta misread your domain, the appeal is the correct path.

• For brands that actually sell health or wellness products (supplements, telehealth, med spas, CBD, weight loss, GLP-1, sexual wellness, mental health), the classification reflects reality. Appealing does not change what is on your domain.

• The only documented partial win from appeal: demotion from Level 3 (full restriction) to Level 2 (standard event restrictions). Not a removal. Purchase events remain blocked.

• Some brands report performance declines after categorization, even when no events appear blocked, and EMQ scores have not changed. The classification may affect Meta's delivery algorithm separately from event suppression.

• The fix is structural: server-side payload cleansing for Level 1-2, or a clean intermediary domain for Level 3. The category stays. Your events flow anyway.

Check Your Classification First

Paste your URL below to see how Meta is classifying your domain, which signals are triggering it, and at what severity.

Or check manually: go to Meta Business Manager > Events Manager > Overview >

You will see either no classification (your domain has not been flagged yet) or a classification under one of the Meta's restricted categories.

From this screen, you can either confirm the category or request a review. The "request a review" button is the appeal.

You also have the option to self-categorize your data source. Meta's documentation states: "You can categorize your datasets and all connected data sources... based on their topics and the products and/or services provided. This is designed to allow you to select if your data sources should fall under a category that comes with restrictions." If you voluntarily categorize your data source, Meta may still override your selection with its own categorization, and you will not be able to modify a Meta-assigned categorization.

What the Health and Wellness Category Is

Meta classifies your domain, not your ad, not your pixel, not your ad account, into a restricted category based on what its automated crawler finds on your website. The classification is driven by landing page content, product descriptions, URL paths, event payloads, and (since the September 2025 enforcement expansion) custom audience names and custom conversion names.

The Health & Wellness category has three sub-classifications:

• Health & Wellness, Other: General wellness products without condition-specific positioning.

• Health & Wellness, Condition: Products or services associated with a specific medical condition (weight loss, diabetes, hormonal imbalance, anxiety, pain).

• Health & Wellness, Provider: Clinical services, telehealth, patient portals, or provider-patient relationships.

Each sub-classification can trigger restrictions at three levels: Core Setup (Level 1), Standard Event Restrictions (Level 2), and Full Domain Restriction (Level 3). The higher the level, the more data Meta blocks from your events.

The part most brands miss: ad approval and domain classification are two completely separate systems. Your ads can be approved, running, and delivering clicks while your domain is simultaneously classified and your purchase events are being silently suppressed. If you have not checked Events Manager for a classification banner, you may already be restricted without knowing it.

What Core Setup Restricts

Core Setup is the most common restriction level. It is also the most misunderstood. Many brands see "Core Setup" in Events Manager and assume it has no real impact because their events are not visibly blocked. That is not accurate.

According to Meta's documentation, Core Setup restricts two specific types of data:

1. Custom parameters. Any parameter that is not on Meta's predefined list of standard parameters is blocked. If you are sending custom parameters with your events (product category, appointment type, condition name, plan tier), those parameters are stripped before Meta processes the event.

2. Everything in the URL after the domain. Meta truncates your URLs at the domain level. The URL https://yourstore.com/products/semaglutide-injection?variant=10mg&category=weight-loss becomes https://yourstore.com/. All path segments, query strings, and parameters are removed.

What this breaks in practice:

• Custom audiences stop working as expected. Any custom audience built on URL rules (e.g., "people who visited /products/weight-loss") or custom parameters can no longer be prefilled and may take longer to populate or stop updating entirely.

• Automatic advanced matching may become unavailable. If Meta cannot use automatic advanced matching, you need to implement manual advanced matching instead.

• Pixel-based catalog updates stop working. If you add items to your catalog via Meta Pixel, this may no longer function. You need to add items manually or via product feed.

• Custom events require manual review. After Core Setup is applied, all custom events are automatically blocked until you review and confirm each one in Events Manager. If you have not reviewed your custom events, they are not firing.

• Events Manager data becomes incomplete. Custom parameters and URL data are no longer visible in Events Manager, including in the test events tool and sampled activities.

The critical point: Core Setup does not block your standard events (Purchase, Lead, AddToCart). Those still fire. But the supporting data that makes those events useful for optimization (the URL context, the custom parameters, the audience rules) is degraded. Your events are technically flowing, but Meta's algorithm has less signal to work with.

This is why brands at Core Setup often see a gradual performance decline without any obvious event blocking.

Ad Rejection vs Event Suppression: Two Different Problems

This is one of the most common misdiagnoses. Brands conflate "my ad got rejected" with "my events are blocked." These are two separate systems solving two separate problems.

Ad rejection (creative policy): Meta's ad review system evaluates your ad creative, copy, landing page content, and targeting against its advertising policies. If your ad makes health claims, uses before-and-after imagery, or references restricted products without required certifications, the ad is rejected. This has nothing to do with your domain classification or your pixel.

Event suppression (data sharing restrictions): Meta's domain classification system evaluates your website content, product descriptions, URL paths, and event payloads. If your domain is classified under Health & Wellness, Meta restricts the event data flowing from your pixel and CAPI. This has nothing to do with whether your ad creative was approved.

These two systems do not communicate. Your ads can be approved, running, and delivering clicks while your domain is simultaneously classified and your purchase events are silently suppressed. If you are troubleshooting a ROAS decline by changing your ad creative when the real problem is event suppression, you are solving the wrong problem.

How to tell which problem you have:

• Ads rejected or disapproved in Ads Manager is a creative policy issue. Fix your ad copy, imagery, or landing page.

• Ads are approved and running, but purchase events are missing in Events Manager, or Events Manager shows "Data Sharing Restrictions Applied" is domain/data source classification issue. Fix your data infrastructure.

• Both happening simultaneously → both systems flagged you independently. Fix both.

What the Appeal Process Is

The appeal is a single "request review" button. No form, no evidence upload, no written argument. You click it, Meta's automated system re-scans your domain, and a decision comes back.

About the process:

Timeline: 3 to 7 days. Some sources report up to 14 days. Meta does not publish an official SLA.

Resubmission: 30-day cooldown after rejection. Appeal takes about 3-7 days. Once an appeal is rejected, you can't resend it for 30 days.

Evidence: The system does not accept supporting documentation. If you have a dedicated Meta representative, ask them to attach context to your review request.

What happens when you click it: Meta's automated system re-scans your domain. If the signals that triggered the classification are still present (health-adjacent product names, condition-specific URLs, wellness-focused landing page content), it reaches the same conclusion. The appeal is rejected.

When the Appeal Works

Appeals work when the classification is genuinely wrong. The Health & Wellness label does not match what you sell.

Documented examples:

• An ergonomic office furniture brand flagged as medical equipment

• A fitness apparel brand classified as a weight loss

• A protein bar/food brand classified as a supplement

• A skincare brand with no condition-adjacent language flagged for acne treatment

• A general wellness lifestyle brand with no products tied to a specific condition

In each case, the brand could credibly argue that Meta's classifier made an error.

If this is you: scrub any language on your domain that could be misread as health-adjacent ("relieves tension," "supports recovery" can trigger classification even on non-health products), then file the review request. If you have a Meta rep, ask them to escalate with context.

When the Appeal Does Not Work

If your domain genuinely sells supplements, telehealth services, CBD, med spa treatments, weight loss programs, GLP-1 products, or anything associated with a medical condition, the classification is correct.

Meta classified your domain because your domain sells health products. The appeal asks Meta to re-scan the same domain with the same products. It reaches the same conclusion.

The legal reason this does not change: when a Purchase event carries a product like "Blood Sugar Support Formula" or a URL reads /products/semaglutide-injection, Meta infers that an identifiable person has a medical condition. Under HIPAA, FTC regulations, and state privacy laws, that inference constitutes Protected Health Information that Meta is not permitted to receive.

This is not hypothetical. In 2023, the FTC entered settlements with BetterHelp and GoodRx over allegations that both companies shared health-related user data with social media platforms without consent. Multiple class action lawsuits have named Meta directly over health data collected through its pixel.

When you appeal a classification that accurately describes your domain, you are asking Meta to reverse a decision that reduces its legal liability. The automated system has no incentive to grant that.

Even if it did, the next crawl would re-classify you based on the same signals.

The appeal cycle (file, wait 30 days, get rejected, file again) produces nothing except lost time.

What If Your Events Are Not Blocked But Performance Still Dropped?

This is the scenario that confuses the most brands.

You check Events Manager. No events appear suppressed. Event Match Quality scores have not changed. CPMs have not spiked. But since the categorization was applied, ROAS has been declining incrementally. Nothing looks broken, but performance is worse.

We hear this consistently from brands at Core Setup (Level 1). The standard diagnostic advice ("check if your events are blocked") returns a clean result. But performance is still degrading.

There are several possible mechanisms:

URL and parameter stripping degrades optimization signal. At Core Setup, Meta truncates your URLs at the domain and strips custom parameters. Your Purchase event still fires, but Meta no longer knows which product page the user was on, which category they browsed, or which variant they selected. The algorithm has less context for optimization. Over time, this degrades targeting quality and delivery efficiency.

Custom audiences go stale. If your custom audiences were built on URL rules or custom parameters, they stop updating under Core Setup. The audience shrinks. Ad sets using those audiences deliver to a smaller, less fresh pool. Performance declines gradually, not suddenly.

Lookalike audiences lose their seed signal. Lookalike audiences built from custom audiences that rely on restricted data stop refreshing. The lookalike model trains on stale data and drifts from the profile of your actual converters.

Meta may adjust delivery for health-categorized domains. Some practitioners hypothesize that categorization affects Meta's auction dynamics or bid modifiers separately from event suppression. This is not confirmed by Meta's documentation, but the pattern is consistent: brands report performance declines after categorization that cannot be fully explained by event blocking or EMQ changes alone.

If this matches your experience, the classification itself is likely the root cause, even if no events appear blocked. The fix is the same: server-side payload cleansing to restore the URL context and custom parameters that Core Setup strips, and neutral custom event architecture to replace audience and conversion rules that rely on restricted data.

The 2026 Enforcement Expansion

Starting September 2, 2025, Meta expanded automated scanning to two additional classification vectors that were not previously enforced:

Custom audience names. An audience called "Diabetes Interest Lookalike," "Weight Loss Purchasers," or "GLP-1 Leads" is now flagged. Meta scans audience metadata, not just the audience rules or the underlying data.

Custom conversion names. A custom conversion called "Anxiety Product Purchase," "Semaglutide Consultation Booked," or "CBD Checkout Complete" is now flagged.

This catches brands that had compliant event payloads and clean URLs but non-compliant labeling. The fix is straightforward: rename every custom audience and custom conversion to use neutral labels ("High Intent Segment Q2," "Conv Signal A," "Program Interest Audience"). But if you do not know this is now enforced, you can be re-flagged after fixing everything else.

Go to Audiences and Events Manager > Custom Conversions and review every name. If any name contains a drug name, condition term, or treatment reference, rename it now.

The "Request More Time" Extension Is Gone

During the January 2025 enforcement rollout, Meta offered a one-time "Request more time" button in Events Manager. Per Matchnode, it appeared for seven days starting January 6, 2025, and added 30 days before enforcement began on that specific data source. Each data source needed its own request. Meta sales reps were unable to submit it on your behalf.

It did not affect classification. It only delayed when restrictions took effect. It has since lapsed.

If someone is advising you to "request more time," that option no longer exists.

What You Have Probably Already Tried

If you have been classified for more than a few weeks, you have likely tried one or more of these. We documented why each one fails in detail in our Myths vs Reality analysis across 75+ accounts. The short version:

Renaming events does not work. Meta evaluates the full payload content (product names, content IDs, URL paths), not the event name string.

Switching to CAPI alone does not work. Meta's data sharing restrictions apply at the domain level, not the delivery method. Events sent server-side from a restricted domain are filtered on receipt.

Moving to a subdomain does not work. Restrictions apply at the root domain level. shop.yourbrand.com inherits the classification of yourbrand.com.

Waiting it out does not work. The 35-state attorney general coalition letter to Meta (December 2025), FDA enforcement actions (2026), and expanding state privacy laws all point toward stricter enforcement, not a rollback.

What Non-Compliant vs Compliant Data Looks Like

The structural fix is about transforming your event data before it reaches Meta. Here is what that transformation looks like in practice.

URL transformation

Meta's Core Setup strips everything after the domain automatically. But if you are sending events via CAPI from a non-restricted domain (including an intermediary domain), the URL you include in the payload matters.

Non-compliant URL in event payload:

https://yourstore.com/products/semaglutide-injection-kit?variant=10mg&category=weight-loss&plan=monthly

Compliant URL in event payload:

https://yourstore.com/products/item-2847

Or stripped entirely to the domain:

https://yourstore.com/

The product path, query parameters, and category labels are all signals Meta's classifier reads. Stripping or neutralizing them removes the health inference from the event.

Event payload transformation

Non-compliant event payload:

{
  "event_name": "Purchase",
  "event_source_url": "https://yourstore.com/products/testosterone-booster-90-caps",
  "custom_data": {
    "content_name": "Testosterone Booster 90 Caps",
    "content_category": "mens-health-supplements",
    "content_ids": ["SKU-TEST-BOOST-90"],
    "value": 49.99,
    "currency": "USD"
  }
}

Compliant event payload after server-side cleansing:

{
  "event_name": "Purchase",
  "event_source_url": "https://yourstore.com/",
  "custom_data": {
    "content_name": "Wellness Product",
    "content_category": "general",
    "content_ids": ["SKU-WP-001"],
    "value": 49.99,
    "currency": "USD"
  }
}

The product name, category, content ID, and URL are all neutralized. The value and currency (standard parameters) remain intact. Meta still receives a valid Purchase event with revenue data. It no longer receives the health-adjacent context.

This transformation must happen server-side, between your store and Meta. The browser pixel sends data directly from the user's browser to Meta with no interception layer. Server-side CAPI gives you control over what reaches Meta.

Neutral event name reference

If you are using custom events instead of standard events (recommended for Level 2+ restrictions), use genuinely neutral names:

Register custom events in Events Manager and map them to your campaign objectives before switching. Custom events require a training period for Meta's algorithm to accumulate conversion data.

What Actually Restores Your Events

You do not need the category removed. You need your conversion events to flow cleanly to Meta, regardless of the category.

Level 1 (Core Setup): Server-side payload cleansing on your existing domain. Your server intercepts every event before it reaches Meta and strips health-adjacent signals: product names, condition terms, sensitive URL paths. Meta receives a clean payload. Your domain stays classified, but the data no longer carries the signals that Core Setup restricts. This also restores the URL context and custom parameters that Core Setup strips, because your server sends the event via CAPI with a clean (but functional) URL rather than letting Meta truncate it.

Level 2 (Standard Event Restrictions): Same-domain payload cleansing restores events in most cases. If cleansing alone does not restore purchase events, escalate to a clean intermediary domain.

Level 3 (Full Domain Restriction) or disabled accounts: A clean intermediary domain is required. Separate root domain, no restriction history, no health-adjacent content, no connection to your flagged domain in Meta's pixel or CAPI history. Your ads point here. Your server captures session data, passes the user to your real store, stitches the session across both domains, and sends a single cleansed event to Meta from the clean domain.

The domain-name exception: If your root domain itself contains health or drug terms (getslim.com, glp1clinic.com, semaglutidedirect.com), same-domain payload cleansing cannot help. The restricted signal is embedded in the domain string, which appears in every event URL you send to Meta. In this case, an intermediary domain is required regardless of the restriction level.

In the accounts we have worked with that implemented this architecture correctly, Event Match Quality recovered from approximately 5/10 to 8.5-9/10 after the correct fix was applied.

The category does not need to change. The data architecture does.

If You Are Not Yet Categorized

If your domain sells health or wellness products and has not been classified yet, it is likely a matter of time. Meta re-crawls domains periodically. Proactive setup now prevents the performance disruption later.

Step 1: Voluntarily enable Core Setup restrictions. Meta's documentation confirms you can self-categorize your data source and enable core setup restrictions proactively. This prevents your pixel from sending sensitive URL paths and custom parameters to Meta before Meta flags you. Go to Events Manager > Data Sources > Settings > Manage Data Source Categories. This is a necessary step, but not sufficient on its own.

Step 2: Implement server-side payload cleansing. Move event delivery from browser pixel to server-side CAPI with payload transformation. Strip product names, condition terms, and health-adjacent URL paths from every event before it reaches Meta. This is the structural fix that prevents the classification from affecting your performance.

Step 3: Audit your custom audiences and custom conversions. Rename anything containing drug names, condition terms, or treatment references. The September 2025 enforcement expansion scans audience and conversion metadata independently from your domain classification.

Step 4: Audit your domain content. Run the free audit to see what signals Meta's classifier is likely reading on your domain. Product names, URL slugs, collection names, blog content, customer reviews, and form labels all contribute to classification.

Brands that implement the infrastructure before categorization experience no performance disruption. Brands that wait and react after categorization typically lose 4 to 8 weeks of optimization signal while the fix is built and Meta's algorithm retrains.

What to Do Right Now

Step 1: Check your classification. Go to Events Manager and see if you have been categorized under any categories.

Step 2: If you are genuinely miscategorized, clean any ambiguous language from your domain and file the appeal. If you have a Meta rep, ask them to escalate with context.

Step 3: If you genuinely sell health or wellness products or other restricted categories, then start building the structural fix. Do not wait for the appeal outcome.
Unrestrict by Zappush helps Health and Wellness, CBD & Hemp, Sexual Wellness, and other restricted category brands become platform compliant.

Step 4: If your domain is categorized but your events are not visibly blocked, and performance is still declining, the category itself is likely affecting your delivery. Data degradation from Core Setup & data source categorization could be the reason.

Step 5: If you are not yet categorized and sell products from the restricted category, set up the infrastructure now. Voluntarily enable core setup, implement server-side CAPI with payload cleansing, and audit your audience and conversion names. Prevention is faster and cheaper than recovery.