Research

Why your pixel data gets stripped on Meta's health and wellness category

Male author wearing black jacket

Josh Richards

 Image featuring the phrase "How to Build AI Automation Workflows That Actually Scale."

If you run paid social in regulated health and wellness, you've watched it happen. Your pixel reports conversions cleanly. Events Manager shows green. But the algorithm doesn't seem to be learning, your CPMs creep up, and lookalikes underperform compared to identical setups in any other vertical.

The reason is that since January 2025, Meta strips conversion signals from health and wellness accounts by default. Your pixel is firing. Meta is filtering what it does with the data.

What Meta strips in the health and wellness category

The January 2025 healthcare reclassification put every operator in compounded GLP-1, telehealth, online pharmacy, hormone therapy, and adjacent verticals into a sensitive-category zone. Inside that zone:

  • Purchase, Add to Cart, and Subscribe events are blocked or stripped at ingestion

  • Identifying parameters are removed so Meta can't tie the conversion to a specific user

  • Audience signals from health-related behavior can't be seeded into lookalike modeling

  • PHI detection flags event names, URLs, and parameter values that look health-related, regardless of whether they actually are

Your dashboard shows the event firing. Meta records that it fired. But the data fed into the auction optimizer is stripped of the signals Meta would use in any other category.

That's why operators in this vertical see flat ROAS, slow Learning, lookalikes that don't work, and CPMs that climb for no creative reason. The algorithm isn't getting the data it would have on a non-restricted account.

Why the standard workarounds don't last

Most agencies in this category have a playbook: server-side tracking through Conversions API, renaming Purchase events to non-descriptive labels, custom event configurations that strip variables likely to trip PHI detection.

All of them work briefly. Then Meta updates its detection. The CAPI setup that cleared in Q1 starts getting flagged in Q2. The event renaming that worked in March triggers filters by June. Operators in this category spend more on consultants chasing workarounds than they would spend on infrastructure that doesn't need them.

What changes when the account is credentialed

When the underlying account is LegitScript-whitelisted at the entity level and sits at Platinum HiVA tier, the sensitive-category restriction layer behaves differently. Clean events feed the algorithm the way they would in a non-restricted vertical. Learning phases complete. Lookalikes seed. Optimization runs on full data.

This isn't a workaround. It's a different auction context. PHI detection still applies. Category rules still apply. But the same pixel firing through a credentialed account produces a different outcome than the same pixel firing through a standard health and wellness account.

How Scoreify does it

Scoreify operates Meta ad accounts that ship pre-credentialed at the level that lets pixel data flow. Pre-launch event review keeps your setup outside Meta's current PHI detection patterns as they update. Conversions API, custom events, and domain verification all run on credentialed infrastructure.

You don't have to rotate workarounds every quarter to keep your pixel feeding Meta. We do that for you.

Book your free consultation →

If you run paid social in regulated health and wellness, you've watched it happen. Your pixel reports conversions cleanly. Events Manager shows green. But the algorithm doesn't seem to be learning, your CPMs creep up, and lookalikes underperform compared to identical setups in any other vertical.

The reason is that since January 2025, Meta strips conversion signals from health and wellness accounts by default. Your pixel is firing. Meta is filtering what it does with the data.

What Meta strips in the health and wellness category

The January 2025 healthcare reclassification put every operator in compounded GLP-1, telehealth, online pharmacy, hormone therapy, and adjacent verticals into a sensitive-category zone. Inside that zone:

  • Purchase, Add to Cart, and Subscribe events are blocked or stripped at ingestion

  • Identifying parameters are removed so Meta can't tie the conversion to a specific user

  • Audience signals from health-related behavior can't be seeded into lookalike modeling

  • PHI detection flags event names, URLs, and parameter values that look health-related, regardless of whether they actually are

Your dashboard shows the event firing. Meta records that it fired. But the data fed into the auction optimizer is stripped of the signals Meta would use in any other category.

That's why operators in this vertical see flat ROAS, slow Learning, lookalikes that don't work, and CPMs that climb for no creative reason. The algorithm isn't getting the data it would have on a non-restricted account.

Why the standard workarounds don't last

Most agencies in this category have a playbook: server-side tracking through Conversions API, renaming Purchase events to non-descriptive labels, custom event configurations that strip variables likely to trip PHI detection.

All of them work briefly. Then Meta updates its detection. The CAPI setup that cleared in Q1 starts getting flagged in Q2. The event renaming that worked in March triggers filters by June. Operators in this category spend more on consultants chasing workarounds than they would spend on infrastructure that doesn't need them.

What changes when the account is credentialed

When the underlying account is LegitScript-whitelisted at the entity level and sits at Platinum HiVA tier, the sensitive-category restriction layer behaves differently. Clean events feed the algorithm the way they would in a non-restricted vertical. Learning phases complete. Lookalikes seed. Optimization runs on full data.

This isn't a workaround. It's a different auction context. PHI detection still applies. Category rules still apply. But the same pixel firing through a credentialed account produces a different outcome than the same pixel firing through a standard health and wellness account.

How Scoreify does it

Scoreify operates Meta ad accounts that ship pre-credentialed at the level that lets pixel data flow. Pre-launch event review keeps your setup outside Meta's current PHI detection patterns as they update. Conversions API, custom events, and domain verification all run on credentialed infrastructure.

You don't have to rotate workarounds every quarter to keep your pixel feeding Meta. We do that for you.

Book your free consultation →

Ready to work with Scoreify?

High-trust Meta ad accounts for regulated health & wellness

A green screen displayed against a solid black background, emphasizing the vibrant color contrast.