Meta Pixel and HIPAA: what the HHS guidance says
What the HHS bulletin on tracking technologies says about the Meta Pixel and Google Analytics on HIPAA-covered sites, and what a 2024 court ruling vacated.
By DATALYR · · 4 min read
Contents
Is the Meta Pixel HIPAA compliant?
No tracking tool is HIPAA compliant on its own; HIPAA governs what covered entities and their business associates do with protected health information. Under guidance from the HHS Office for Civil Rights, a hospital, clinic or health plan that lets the Meta Pixel or another tracking technology send protected health information to a vendor needs a HIPAA permission for that disclosure, and generally a business associate agreement (BAA) or the patient's authorization.
Marketing is the hard case. HHS says disclosing protected health information to tracking vendors for marketing without HIPAA-compliant authorizations would be an impermissible disclosure. This guide summarizes the bulletin and what changed in 2024.
What the 2024 court ruling vacated
On June 20, 2024, the U.S. District Court for the Northern District of Texas declared unlawful and vacated part of the bulletin in American Hospital Association v. Becerra. The vacated part is the guidance that HIPAA obligations are triggered when an online technology connects an individual's IP address with a visit to an unauthenticated public webpage addressing specific health conditions or healthcare providers. HHS notes the order at the top of the bulletin. It appealed, then withdrew the appeal in August 2024, so the ruling stands.
The rest of the bulletin still appears on the HHS site, including the guidance on logged-in pages, appointment and symptom-checker tools, and mobile apps.
Authenticated pages, public pages and apps
The bulletin sorts tracking by where it runs.
- User-authenticated pages, such as a patient portal or telehealth platform, generally give tracking technologies access to protected health information. They must be configured so tracking only uses and discloses it as the Privacy Rule allows.
- Unauthenticated pages often don't involve protected health information, for example a page with visiting hours or job postings. But a public page that lets someone book an appointment or use a symptom checker can collect it, such as an email address or the reason for a visit.
- Login and registration pages are unauthenticated, but credentials or registration details entered there are individually identifiable health information when a tracking tool collects them.
- Mobile apps offered by covered entities generally collect protected health information, including device and advertising IDs.
Business associate agreements and cookie banners
HHS says a tracking vendor that creates, receives, maintains or transmits protected health information on behalf of a covered entity for a covered function, such as health care operations, is a business associate, and a BAA is required. Naming the vendor in a privacy policy is not enough, a cookie banner is not a valid HIPAA authorization, and a vendor's promise to strip or de-identify the data after receiving it is insufficient.
If a vendor won't sign a BAA, the bulletin describes one alternative: a BAA with another vendor, for example a customer data platform, that de-identifies the data before passing only de-identified information to the vendor that won't sign.
Google Analytics, Google Tag Manager and HIPAA
Google says HIPAA-regulated customers must not expose to Google any data that may be protected health information, makes no representation that Google Analytics satisfies HIPAA requirements, and does not offer a BAA for it. Google advises keeping Analytics tags off authenticated pages and off unauthenticated pages that are HIPAA-covered.
A tag manager doesn't change that. Whichever container loads a tag, the tag still sends its data to its vendor, so review each tag by what it sends and where.
Example: sort a clinic site before choosing tags
Imagine a hypothetical clinic site with 10,000 visits a month: 6,000 to general pages such as locations and careers, 3,000 to service pages about specific conditions, and 1,000 to the appointment booking flow. Booking pages, where a visitor enters contact details and a reason for the visit, are in scope under the bulletin: that is 1,000 ÷ 10,000 = 10% of visits.
Service pages are the uncertain group after the 2024 ruling, so decide on them with counsel. General pages are generally out of scope. Placing third-party tags only where they belong starts with this kind of page inventory.
One site, three page groups
1. General pages
6,000 visits
Hours, locations, careers.
2. Condition and service pages
3,000 visits
The area the 2024 ruling affected; review with counsel.
3. Booking flow
1,000 visits (10%)
Contact details and visit reason: in scope under the bulletin.
What DATALYR does and doesn't do
DATALYR does not make a website HIPAA compliant, and no tool does. What it gives you are controls over what ad platforms receive. Page filters can block or mask URLs so selected pages are never stored. Health filtering removes health-related fields from the conversions DATALYR sends and keeps its managed Meta, Google and TikTok browser pixels off. Platform notices you record make DATALYR withhold the events they cover.
Tags installed outside DATALYR aren't affected by these settings and need their own review.
Related articles.
Health and wellness ·
My Health My Data Act and FTC rules for advertisers
What Washington's My Health My Data Act, the FTC Health Breach Notification Rule and FTC health cases mean for ad tracking on health and wellness sites.
Health and wellness ·
Meta Pixel lawsuits and health data enforcement
The Meta Pixel healthcare litigation, related tracking-pixel cases, and state and FTC actions over health data sent to ad platforms, with primary sources.
Use cases ·
Health and wellness ad tracking: measure conversions with careful data handling
Design a wellness measurement workflow that separates collection, filtering, platform restrictions, and attribution without promising a tracking workaround.
