If you sell supplements, run a med spa, operate a telehealth brand, or sell anything adjacent to health - there is a specific type of Meta ad problem you may be experiencing right now without realising it. Your campaigns are running. Your ads are approved. Your spend is being consumed. And your conversion data is silently disappearing.
This is not a pixel misconfiguration or a CAPI setup issue. It is a domain-level classification problem, and it behaves differently from every other tracking failure you have encountered.
How Meta's Restriction System Actually Works
Meta maintains a data sharing restriction framework that classifies domains into health and wellness categories. The classification happens automatically, based on domain crawling, event payload analysis, and business category signals. It runs independently of ad review - a fact that catches most advertisers off guard.
Your ad creative goes through one automated review process. Your domain goes through a completely separate classification process. The two have nothing to do with each other.
This means Meta can approve your ads, deliver them to your audience, and charge you for every click - while simultaneously suppressing the conversion events your account depends on to optimise. The ads keep running. The data layer breaks. Your ROAS drops weeks later and you have no obvious cause.
The Three Restriction Tiers
Core Setup restrictions (Level 1) strip out sensitive parameters from your events. Events still arrive at Meta, but the payload is scrubbed - personal health information, condition-adjacent product names, and PHI are removed before they reach the algorithm. Your data becomes less precise, not absent.
Standard Event restrictions (Level 2) block the events that matter most: Purchase, Lead, AddToCart, and other high-intent conversion events. They stop arriving at Meta entirely. Your campaigns shift into blind optimisation - spending against impressions with no conversion signal to guide targeting.
Full Domain restrictions (Level 3) shut down all conversion event sharing. No events of any type leave your domain to Meta. Your account retains the ability to run ads, but it does so completely without data.
The critical operational point: at Level 2 and above, your CPM rises because Meta's algorithm can no longer identify high-intent buyers efficiently. It overpays for the same impressions, or delivers them to lower-value users, or both. The spend continues. The performance collapses.
Why Most Brands Discover the Problem Too Late
Meta applies classification silently. Notification emails go to the Business Manager email address - not the ad account, not your agency dashboard. Ads continue running. Events degrade over days or weeks. Most advertisers only investigate when a significant ROAS drop triggers a review, at which point the restriction has typically been active for several weeks.
When they open Events Manager, they find suppressed events, degraded Event Match Quality, and a restriction notice they may have missed entirely.
The compounding problem: once you are restricted, the fixes most people try do not work.
The Four Fixes That Do Not Fix Anything
Renaming events
Renaming Purchase to event_01 or CONV_A is not a fix. Meta evaluates the full semantic content of the event payload - product names, item categories, content IDs, URL path segments, and parameter values - not just the event name string. An event called event_01 that carries content_name: "testosterone booster 90 caps" in its payload will be blocked. The event name is the least important variable.
Switching to CAPI alone
This is the most common agency recommendation and the most misunderstood. The Conversions API routes events server-side, which bypasses ad blockers - but it does not bypass domain-level data sharing rules. Meta's own documentation confirms that server-side events are suppressed upon receipt when the originating data source is restricted. We have seen this directly: switching to CAPI on a restricted domain produces exactly the same suppressed event errors as the browser pixel. The delivery method is irrelevant when the domain itself is classified.
Filing an appeal
The appeal process is fully automated. It does not accept supporting evidence or documentation. It typically rejects within 24 to 48 hours and cannot be resubmitted for 30 days after rejection. Across accounts we have worked with and community data spanning r/FacebookAds, Stape forums, and Foxwell Founders, there is no documented case of a genuine health or wellness brand successfully reversing its classification through the appeal process.
There is one partial exception: some brands have appealed their way from Level 3 down to Level 2 - a reduction in restriction severity, not a removal. The domain remains classified. Purchase events remain blocked.
If the classification is genuinely wrong - an ergonomic furniture brand flagged as medical equipment, a fitness apparel brand classified as weight loss - an appeal has a reasonable chance. File it. But if your domain legitimately sells health products, the appeal reflects a classification that is accurate. The system is not misreading you.
Moving to top-of-funnel campaigns
Meta support and many agencies recommend switching to Traffic or Landing Page View objectives when Purchase events are blocked. This is a performance replacement, not a workaround. Meta's algorithm optimises for whatever signal you give it. When you optimise for clicks, you get people who click. You do not get people who buy. A documented conversion rate drop from 7% to under 1% after switching objectives is not an outlier - it is what the algorithm delivers when you ask it to find clickers instead of buyers.
What Determines Whether Your Domain Gets Classified
Meta's classifier does not look for clinical language alone. It uses behavioural inference: if buying your product implies the buyer has a health condition, the classifier may flag your domain regardless of the language you use.
Brands that sell supplements with condition-adjacent positioning - blood sugar support, hormone balance, sleep, cognitive function - are classified. Telehealth and provider services are classified. Cosmetic procedures and body contouring are classified. CBD and regulated substances are classified. Sexual wellness products are classified.
Brands that may not expect to be classified but often are: skincare brands with acne or redness messaging, mental wellness apps, fitness equipment with pain or recovery language, functional food brands with health-outcome claims.
Classification is expanding, not contracting. Q1 2026 saw a material increase in enforcement - retroactive auditing of previously approved ads, a multimodal creative review system, and a significant rise in health-related ad rejections relative to Q4 2025. Brands that have not yet been classified should be treating compliant infrastructure as a present-day priority, not a contingency.
What Actually Restores Purchase Events
The only documented path to restoring conversion data at Level 2 and above involves rebuilding the data infrastructure, not patching around a domain classification.
Three components have to work together.
Server-side payload cleansing is the foundation. The browser-side Meta pixel comes off your domain entirely. All events route through a server-side intermediary - either a server-side GTM container or a first-party data platform - where every sensitive parameter is stripped before any event reaches Meta. Product names like "Diabetes Management Kit," appointment categories like "Oncology Consultation," and URL paths containing condition-specific terms are replaced with neutral equivalents. What Meta receives is a clean payload with no classification triggers.
A clean intermediary domain is required for Level 2-3 resolution. This is a separate root domain with no restriction history and no health-adjacent content on its landing pages. When Meta's crawler evaluates this domain, it finds nothing to classify. Events originating from it enter Meta's systems without restriction. The customer journey stays intact - users pass through the clean domain to your store - but the event data that Meta receives is anchored to an unclassified surface.
Persistent session identity ties the two together. When a user moves from the clean domain to your store, their session data - click IDs, UTMs, fbp, fbc, and any identity parameters - has to travel with them under a persistent identifier your server controls. Without this, you lose attribution the moment the user crosses the domain boundary, and the EMQ score on your conversion events degrades immediately.
In accounts where all three components are implemented correctly, Event Match Quality recovers from the suppressed 5/10 range to 8.5–9/10 consistently. Full conversion-optimised campaigns become viable again.
Custom Events: When They Work and When They Don't
Custom events with neutral coded names are part of the correct fix for Level 1 and Level 2 accounts. Three conditions have to be met simultaneously: the event name must be genuinely neutral (not a descriptive variant of "lead" or "purchase"), the entire payload must be scrubbed of sensitive signals, and the event must be registered and approved in Events Manager before it is used.
The failure mode people miss: custom events require a training period. Meta's algorithm does not inherently understand what a generic event name means. It needs to accumulate training data before it can optimise against that event. Brands that set up custom events only after restrictions force the switch face a second optimisation gap on top of the first. Set them up while standard events are still functioning.
Custom events do not work for Level 3 full domain restrictions. At Level 3, all event sharing is blocked regardless of event name. Clean domain architecture is required first.
Where LeadSignal Fits
LeadSignal's server-side infrastructure handles the technical components of a compliant tracking setup without requiring you to build and maintain the underlying architecture yourself. Events route through LeadSignal's servers, where payload cleansing and neutral event mapping are applied before anything reaches Meta. The fbclid click ID and fbp browser ID are captured at session start and persisted server-side, so they survive domain transitions without degrading.
When combined with a clean intermediary domain, this removes the classification trigger from the data Meta evaluates - not by arguing with the existing classification, but by ensuring new event flow enters Meta's systems through an unclassified surface.
Where to Start
If you are in a restricted account: file the appeal as a formality and start building the structural fix immediately. Do not wait three appeal cycles for an outcome that will not arrive.
If you are not yet restricted: check your Events Manager classification now. The absence of a restriction today is not a guarantee of tomorrow, and Q1 2026 enforcement data indicates the direction is toward broader classification, not narrower. Building compliant infrastructure before you are flagged is meaningfully easier than rebuilding it under performance pressure after the fact.
The restriction system is not going to relax. It is driven by legal liability, class action exposure, FTC enforcement, state privacy laws, and HIPAA - not by a policy preference that could be reversed. The brands recovering performance now are the ones that rebuilt their data layer instead of cycling through workarounds. The brands still struggling are the ones waiting on appeals that will not reverse.