What Are Meta's Health and Wellness Restrictions And How Do They Affect Tracking?
Meta applies advertising and data restrictions to health, wellness, and supplement businesses, and these restrictions can limit what you can track and optimize for in Meta Ads Manager. This article explains Meta's health and wellness policies, the restriction tiers Meta may apply, and how PixelFlow's server-side tracking behaves within those restrictions.
Who this affects
Meta classifies brands as health and wellness if they're associated with:
Medical conditions or specific health statuses
Provider/patient relationships (such as patient portals or wellness trackers for medical conditions)
Dietary supplements and weight loss products
Prescription drugs and pharmaceuticals
Health-related services and remedies
If Meta categorizes your business as health and wellness, you'll receive email notifications and alerts in Meta Events Manager. These restrictions can affect your ad targeting and conversion tracking.
Understanding Meta's health restrictions
Why these restrictions exist
Meta implemented these restrictions to protect against promoting false health claims and to prevent sharing sensitive personal health data. Under Meta's advertising policy, customer purchases of health products are considered health data, which could violate HIPAA regulations if tracked and sent back to Meta.
Ad content restrictions
Meta enforces strict content policies for health and wellness advertising.
Weight loss and cosmetic products
Must target people 18 years or older
Cannot imply negative self-perception or promote a "perfect" body type
Cannot show side-by-side before/after comparisons for weight loss products
Cannot feature body-shaming or exploit insecurities
Cannot promote permanent skin whitening or bleaching products
Adult products and reproductive health
Must target audiences 18 years or older
Must focus on medical benefits, not sexual pleasure
Can promote contraceptives, reproductive health apps, and family planning services
Cannot promote adult sexual arousal products or services
Prescription drugs
Require pre-approval and LegitScript certification for telehealth providers, online pharmacies, and pharmaceutical manufacturers
Cannot target individuals under 18
Sale of prescription drugs is prohibited on Meta's platforms
Tracking and data restrictions
Meta applies restrictions to health and wellness advertisers at different levels, depending on how Meta classifies your business and what type of health information you might be collecting.
Meta determines which level applies to your account based on your business type, website content, and the data you're collecting. You'll receive email notifications and see alerts in Meta Events Manager if restrictions are applied to your account.
Tier 1: Core setup restrictions
The most common level for general health and wellness businesses. This tier includes:
Ad delivery: Cannot share custom parameters and URL parts with Meta (e.g., UTM parameters beyond the domain)
Custom audiences: May decrease in size or stop working if they rely on restricted data
Ad content: Adding items to a product catalog via Meta Pixel may no longer work
Reporting: Some information unavailable in Meta Events Manager (sampled activities, test events tool)
Tracking: Automatic advanced matching may not be available
If you're only hit with core setup restrictions, you can still run effective campaigns by focusing on allowed events and removing restricted data from your tracking implementation.
Tier 2: Restriction on certain standard events
This mid-level restriction prevents optimization toward specific conversion events:
Blocked events: Cannot optimize for Purchase, Add to Cart, or other mid- and lower-funnel standard events
Still available: Upper-funnel events like PageView, ViewContent, and Landing Page View remain accessible
Custom events: Meta allows custom events with coded names (for example, EVENT_001 instead of Purchase)
Audience restrictions: Cannot build custom audiences based on blocked conversion events
Tier 2 restrictions typically apply to businesses selling health supplements, weight loss products, or wellness services where purchases directly indicate health-related information about users.
Tier 3: Full restrictions
The most severe level, where Meta may fully restrict all events in specific regions or globally:
No conversion tracking: Meta Business Tools cannot be used for campaign optimization
Limited targeting: Forced to rely on broad demographic targeting only
Minimal reporting: Severely limited data visibility in Events Manager
No algorithmic optimization: Cannot leverage Meta's machine learning for campaign performance
Full restrictions typically apply to patient portals, medical condition-specific services (such as mental health platforms or chronic disease management), prescription drug sellers, and healthcare providers where the business relationship itself reveals protected health information.
How restrictions are applied
Meta's restrictions may vary by region based on local regulations:
Some accounts face restrictions only in specific countries (stricter in EU/US due to GDPR/HIPAA)
Others may be restricted globally depending on the business type
Restrictions can escalate from Tier 1 to Tier 3 if compliance issues aren't addressed
How to tell which restriction level you're at
Meta uses visual indicators in Events Manager to show your restriction status. Check Meta Events Manager > Manage Data Source Categories (next to your domain) and look for these warning symbols:
Yellow triangle warning = Level 1 (partial block on lower-funnel events). Purchases still track accurately when compared to your actual data (for example, Shopify orders). Minimal impact on campaigns.
Red stop sign = Level 2 (lower funnel blocked, top of funnel OK). You'll notice missing Add to Cart, Initiate Checkout, or Purchase events when compared to actual data.
Red stop sign plus missing Page View/View Content = Level 3 (regional or full block). Even basic events like Page View and View Content are missing. This typically applies in EU regions or to highly sensitive health categories.
Verify your level by comparing event counts in Meta Events Manager to your source of truth (Shopify sales, form submissions, and so on). If purchases match, you're Level 1. If purchases are missing but page views work, you're Level 2. If everything is blocked, you're Level 3.
How PixelFlow works with these restrictions
PixelFlow has no health-specific restriction logic. It treats health, wellness, and supplement events exactly like any other supported event: it sends the standard Meta events you configure through the Conversions API, subject to its normal processing rules. Whether Meta accepts, restricts, or optimizes on that data is Meta's platform decision, made after your events are delivered.
What PixelFlow sends and logs
PixelFlow sends the standard Meta events you set up — such as PageView, ViewContent, Lead, Schedule, and the eCommerce events — through the Conversions API. You choose which events to track by tagging elements or assigning URLs, or through the native Calendly integration. See What Events Can PixelFlow Track? for the full list of supported standard events.
PixelFlow's Event Logs and analytics show what PixelFlow captured and processed. Events that are blocked before persistence, rejected because the event name is not a supported standard event, or filtered by bot detection may not appear as ordinary stored events, so the logs are not a guarantee that every action on your site is retained.
How each tier affects PixelFlow
PixelFlow applies no restriction tier of its own and has no health-category filter. The effect on your tracking comes from what Meta does with the events it receives, not from any PixelFlow setting:
Tier 1: PixelFlow continues sending the standard events you configure. Meta may limit custom parameters and URL parts it accepts, and automatic advanced matching may not be available.
Tier 2: PixelFlow sends events normally, but Meta may block optimization on Purchase, Add to Cart, and other lower-funnel events. Upper-funnel events like PageView, ViewContent, and Lead still work.
Tier 3: PixelFlow continues sending the events you configure, but Meta may block or remove all events from ad optimization.
PixelFlow does not support creating custom event names. Meta may allow custom events with coded names, but PixelFlow only accepts standard Meta events, so this workaround is not available through PixelFlow. An event name that does not match a supported standard event is rejected.
Consent and privacy limitations
PixelFlow does not natively delay loading until a visitor consents. The tracking script initializes immediately when the page loads, and PixelFlow has no built-in consent gate or CMP integration. To gate tracking behind consent, load PixelFlow conditionally through an external tag manager or consent tool, such as the workflow in Load PixelFlow in Google Tag Manager.
PixelFlow hashes customer data (email, phone, and names) before sending it to Meta. Hashing is not a consent decision — it does not remove your obligation to comply with consent requirements or Meta's data terms.
What you should do
1. Check your classification and restriction level in Meta Events Manager
Open Meta Events Manager
Go to your dataset
Click Settings
Scroll down to "Manage data source categories" and click the Manage button
Check if you have any limitations displayed
If the classification is incorrect, contact your Meta representative to appeal
If you see restrictions on Purchase/Add to Cart only, you're likely in Tier 2. If all events are restricted, you're in Tier 3. If you only see warnings about URL parameters and custom data, you're in Tier 1 (core setup).
Appeals can take up to 30 days and aren't always successful. Meta has final discretion on classifications. If your appeal is denied, you'll need to adjust your tracking and campaign strategies.
2. Adjust your advertising strategy
If you're affected by these restrictions:
Focus on upper-funnel events: Optimize campaigns for PageView, ViewContent, or Lead events instead of Purchase
Use Landing Page Views: Meta recommends tracking Landing Page Views and Engagement metrics as alternatives
Broaden your targeting: Since detailed targeting options are limited, use broader audience segments
Adapt ad copy: Avoid symptom-related terminology and health claims that trigger Meta's AI review system
Monitor event match quality: Continue improving your Event Match Quality scores for allowed events
3. Review your ad creative compliance
Make sure your ads comply with Meta's content policies:
Target audiences 18+ for all health and wellness products
Avoid before/after comparisons for weight loss and cosmetic procedures
Don't use body-shaming language or exploit insecurities
Focus on medical benefits rather than sexual pleasure for reproductive health products
Avoid banned phrases that trigger automatic AI disapprovals
4. Audit your tracking setup
To prevent restrictions or reduce their severity:
Review pixel placement: Remove Meta Pixel from patient portals, account dashboards, or any pages containing protected health information
Check URL parameters: Ensure URLs don't contain health-related information that could be shared with Meta
Remove duplicate scripts: Remove any standalone native Meta Pixel scripts that duplicate PixelFlow, since overlapping tracking produces duplicate events
Audit page content: Review landing pages and website content to avoid explicitly naming specific health conditions
Never place tracking on patient portals. One of the worst implementations is placing a Meta Pixel on pages where users log in to view personal health records. This directly exposes protected health information to Meta and can result in severe restrictions.
Troubleshooting common issues
Events are firing but not showing in Meta Ads Manager
If you see events in your PixelFlow event logs but they're not appearing in Meta Ads Manager:
Check if your business has been classified as health and wellness in Meta Events Manager
Verify which specific events are restricted for your classification
Confirm you've received notification emails from Meta about restrictions
Contact your Meta representative for clarification on your specific restrictions
For the full diagnostic workflow, see Why are my events not showing in Meta Events Manager? and Common Facebook Events Manager warnings, errors, and suggestions.
Event Match Quality score dropped
If your Event Match Quality score decreases after restrictions are applied:
This is expected when transitioning to upper-funnel events that have less user data
Focus on improving data collection for allowed events
Ensure form submissions collect email, phone, and name when possible
Limitations and known behaviors
Classification is account-wide: If Meta classifies your business as health and wellness, all pixels and data sources under that account are affected
Custom events are not supported: PixelFlow only accepts standard Meta event names; custom event names are rejected
No native consent gate: PixelFlow loads immediately unless you gate it externally through a tag manager or consent tool
Appeals take time: Classification appeals can take weeks or months with no guarantee of approval
Restrictions evolve: Meta continues updating and refining these policies; what's allowed today may change
HIPAA compliance required: Businesses must ensure their data handling practices comply with HIPAA and other health privacy regulations
Getting help
If you need assistance with Meta's health restrictions or PixelFlow tracking:
Check your classification: Review your data source category in Meta Events Manager Settings
Review event logs: Use PixelFlow's Event Logs to see exactly what events are firing from your website
Contact Meta: For classification appeals or policy clarifications, reach out to your Meta representative
Contact PixelFlow: Schedule a free setup call to discuss your specific tracking setup and optimization strategies within these restrictions
When reaching out for support, have this information ready:
Your business type and products/services offered
Screenshot of your classification in Meta Events Manager
Examples of ads that were rejected (if applicable)
PixelFlow event logs showing what's being tracked
Copy of any notification emails from Meta about restrictions