All answers

The Prevailing
Answers for
Business model:
Business model, pick up to two

Can a health or wellness business use the Meta pixel and Conversions API without breaking privacy law?

The PrevailingPublished Nov 17, 2026

Our answer

Yes, but only if no health details reach Meta. Keep the pixel and the Conversions API off patient portals, intake forms and booking flows, and strip conditions from URLs and event names. If HIPAA covers you, get counsel's sign-off first.

Confidence
Medium
Strongest proof
8 Meta rules
1 dataset, 3 practitioners, 2 opinions or claims
Sources
9 sources
14 statements

New here? Take the 1-minute tour

Why this is the answer

4 reasons and our judgment

Meta's own terms forbid sending health data. Its Business Tools Terms bar data that includes or is based on health information, and event, conversion and audience names can't imply it (Meta). Meta also says to keep the pixel off pages such as patient portals.

The Conversions API is no way around this. The FTC alleges Hims & Hers sent emails and treatment details through both tools about 8 million times (FTC). Stape, a server tracking host, says Meta's health data limits cover both tools.

Health businesses make up most tracking privacy settlements. Healthcare firms were 64% of defendants in 116 such settlements, and Meta's tracker appeared in most of them (Privado AI, reported by PPC Land). Most defendants had a consent tool, its chief executive says.

You can be at risk without HIPAA. State health data laws and the FTC can treat a visitor's treatment browsing as sensitive (Benesch, a law firm). Under HIPAA, a tracking vendor that receives patient data needs a business associate agreement (HHS).

Our judgment

A health or wellness business can keep the pixel and the Conversions API on general pages if no health details reach Meta, and should keep both off pages where visitors log in, book, fill intake forms or describe a condition. Code names for treatments don't make an event safe, since the FTC alleges Meta understood Hims & Hers' code words, and Meta's terms bar names that imply health information.

Our judgment, built from Meta, US Department of Health and Human Services, US Federal Trade Commission and Benesch: our reading of these sources, not a finding from any one of them.

What the sources say

14 statements from 9 sources
  • MetaUndatedSupports

    Meta says advertisers must not send health, financial or other sensitive data through its tools, including URLs and custom events, and that its filters do not replace their own compliance.

    “Meta’s systems are not a substitute for your own compliance mechanisms.”

    Read it on facebook.com

  • MetaUndatedSupports

    Meta says the pixel uses first and third-party cookies by default. Turning off first-party cookies makes it less effective at reaching customers and less accurate in measurement.

    “This is the default option and is most likely your current Meta Pixel setting.”

    Read it on facebook.com

  • MetaUndatedSupports

    Meta recommends running the Conversions API alongside the pixel and sending the same events through both; only matched events count for attribution and optimization.

    “Use the Conversions API in addition to the Meta Pixel, and share the same events using both tools.”

    Read it on developers.facebook.com

  • US Federal Trade CommissionNov 10, 2026Supports

    The FTC and states allege Hims & Hers shared consumers' health data with Meta about 8 million times through the pixel and Conversions API. These are allegations in a pending case, not findings.

    “Hims shared these two Events with Meta via these tools approximately 8 million times.”

    Read it on ftc.gov

  • Phil KielNov 10, 2026Supports

    Phil Kiel reports Meta is asking some advertisers to confirm their website's category in Events Manager within 60 days; if they do not, Meta picks one, which can limit targeting and optimization.

    “if you don't pick, Meta picks for you, along with whatever data restrictions come with that category.”

    Read it on x.com

  • PPC LandNov 5, 2026Supports

    Privado AI's report, reported by PPC Land, counts 2,350 US website and app privacy lawsuits from January to August 2026 and says most sued companies already had a consent tool, often loading after pixels fired.

    “Most of the companies facing litigation had a consent management platform in place”

    Read it on ppc.land

  • Captain ComplianceOct 18, 2026Supports

    Captain Compliance, which sells consent tools, says there is no universal answer on opting out of Meta's feature. Its default is privacy-first: for sensitive sectors, opt out until Meta documents consent handling.

    “Opt out until Meta documents consent handling in writing”

    Read it on captaincompliance.com

  • BeneschAug 31, 2026Supports

    Benesch, a law firm, warns that health-related site visits can count as sensitive health data even for non-HIPAA businesses, and advises auditing every pixel and tag that sends it to ad platforms.

    “Check every pixel, tag, cookie, SDK and API on your website and apps.”

    Read it on beneschlaw.com

  • StapeAug 28, 2026Supports

    In a Stape webinar co-presented with Meta, the advice is to send both browser and server events to Meta with deduplication rather than replace the pixel, though Stape sells server-side tracking.

    “A combined browser + server event stream is the recommended approach for Meta.”

    Read it on stape.io

  • US Federal Trade CommissionJul 29, 2026Supports

    The FTC and states sued Hims & Hers, alleging it shared customers' health information with ad platforms through customer lists and tracking events despite privacy promises. Allegations only.

    “Hims shared its consumers’ health information with advertising platforms by sharing lists of certain customers with those companies.”

    Read it on ftc.gov

  • StapeMar 3, 2026Supports

    Stape, a server-side tracking vendor, says Meta restricts data from health and wellness sites at three levels, and that the Conversions API does not bypass these rules.

    “These checks apply to both Meta Pixel and Conversions API, and Conversions API does not bypass the data sharing rules.”

    Read it on stape.io

  • Paubox2026-02Supports

    Paubox, a seller of HIPAA-compliant email, says Meta Pixel is not HIPAA compliant because Meta does not sign a business associate agreement.

    “Meta Pixel does not sign a BAA and is therefore not HIPAA compliant.”

    Read it on paubox.com

  • MetaNov 3, 2025Supports

    Meta's Business Tools Terms forbid sending health, financial or other sensitive data through the pixel or Conversions API, including in event names, and require verifiable cookie consent where law demands it.

    Read it on facebook.com

  • HHS says tracking on patient login pages generally accesses health data, so HIPAA-covered providers need a business associate agreement with tracking vendors. A 2024 court ruling struck part of this guidance.

    Read it on hhs.gov

In the full answer

For readers who sign in
  • What to do this week3 steps
  • The numbers behind it2 figures from cited sources
  • The strongest disagreementThe best case against the answer, from a cited source
  • How sure we areWhat its confidence rests on, and what would change the answer

Read next

More in International and regulation