Meta classifies your domain automatically. Your ads stay approved. Your conversion events get silently blocked.
Weight loss implies obesity. Obesity is a disease.
If you’re selling weight loss products like meal replacements, fat burners, GLP-1 supplements, or coaching programs, anyone buying your product implies they have obesity. To Meta, that’s a medical condition.
When a Purchase or Lead event fires with your customer’s first-party data attached, you’re effectively telling Meta that this person has a health condition. That’s Protected Health Information (PHI), and sending it violates Meta’s data sharing policy.
So Meta places data sharing restrictions on your domain under the Health & Wellness category. Your ads keep running. Your pixel keeps firing. But your conversion data is blocked or degraded, and Meta’s optimization algorithm loses signal. Your campaigns go blind.
Weight loss implies obesity. Obesity is a disease.
If you’re selling weight loss products like meal replacements, fat burners, GLP-1 supplements, or coaching programs, anyone buying your product implies they have obesity. To Meta, that’s a medical condition.
When a Purchase or Lead event fires with your customer’s first-party data attached, you’re effectively telling Meta that this person has a health condition. That’s Protected Health Information (PHI), and sending it violates Meta’s data sharing policy.
So Meta places data sharing restrictions on your domain under the Health & Wellness category. Your ads keep running. Your pixel keeps firing. But your conversion data is blocked or degraded, and Meta’s optimization algorithm loses signal. Your campaigns go blind.
Meta restricts data sharing in tiers. Each level restricts a different slice of your conversion signal, and each one needs a different fix.
Meta strips custom parameters and metadata from your events. Standard events still fire, just stripped down.
Product names, content IDs, URL paths, and custom data are filtered out before they reach Meta. Your campaigns keep optimizing, but on a thinner signal. Most brands miss this stage entirely because nothing visibly breaks.
Purchase, AddToCart, and Lead are restricted at the source. Your campaigns can no longer optimize for the conversions that matter.
Meta still receives PageView and ViewContent, but the conversion events your bidding depends on never make it through. CPM rises because the algorithm has no way to identify high-intent buyers. Most brands discover this only after ROAS has already collapsed.
Even PageView stops firing. Your domain is fully flagged. CAPI, custom events, and event renaming do not bypass it.
Every event sent from this domain is suppressed before Meta's optimization layer sees it. The restriction follows the domain, not the pixel. Switching pixels or ad accounts does not move you out of Level 3 unless the new pixel is paired with a clean intermediary domain.
When the pixel is restricted, the campaign is too. Purchase, AddToCart, and Lead never reach Meta. So the algorithm can't see who bought, can't model lookalikes, and can't double down on what's working. No data. No optimization. No scaling.
Audit your websiteEvery restricted brand we've audited tried at least two of these before they found us. Each one is plausible, widely recommended, and quietly leaves the underlying domain classification untouched.
Meta evaluates the full payload, not the event name. An event called "event_01" carrying a product like "Diabetes Management Kit" gets blocked just the same. Renaming is part of the work, not the work.
Event Payload
RenamedPayload evaluated, not event name
Everything keeps working. Nothing about your store changes. We handle what Meta sees.
We scan your landing pages for policy risk before Meta does. Fix issues upfront and prevent restrictions.
Users shop on your main site, but Meta only sees the compliant landing page. Events stay clean and optimisation stabilises.
Users browse your store normally. Events flow back securely to Meta via your landing page.
User clicks ad
Ad runs on Meta as usual
Lands on landing page
Redirected to brand domain
Browses and buys as normal
Events captured
From brand domain
Events processed
Your server
Clean
Remove noise & unwanted data
Hash
Hash PII for privacy
Validate
Ensure quality & standards
Sent to Meta
Via Conversions API
Events delivered reliably & securely
Meta receives clean, privacy-safe events.
Higher data quality
Better targeting & attribution
Privacy-first
Hashed & validated
More reliable
Server-side delivery
Book a free 30-minute call with our team. We’ll review your current Meta advertising setup and show you exactly how Unrestrict would work for your store.
Custom pricing based on your store. 30-day money-back guarantee.