DATALYR

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.

By DATALYR · · 4 min read

Contents

What the Meta Pixel lawsuits are about

The Meta Pixel lawsuits are mainly class actions alleging that the Pixel, installed on hospital and health system websites and patient portals, sent patients' health information to Meta. The lead federal case is In re Meta Pixel Healthcare Litigation in the Northern District of California, filed in June 2022 against Meta.

Alongside the private suits, regulators have acted against companies over tracking that sent health data to ad platforms. This page lists cases from court records and government releases only. Outcomes in the private cases depend on the facts and are still developing.

In re Meta Pixel Healthcare Litigation

The case (No. 3:22-cv-03580-WHO, N.D. Cal.) is before Judge William H. Orrick and was filed on June 17, 2022. In his December 22, 2022 order, the judge described the case as about Meta's alleged use of its code to obtain healthcare-related information of Facebook users. The named plaintiffs alleged that their providers installed the Pixel on their patient portals and that logging in sent information to Meta.

That order denied the plaintiffs' request for a preliminary injunction. The court called the allegations troubling and said the plaintiffs raised potentially strong claims, but found they had not met the high standard for a mandatory injunction at that early stage. Meta's core defense, as the order describes it, is that it has systems to address receipt of such information.

Other tracking cases in court

Similar suits target other trackers and individual providers. Doe I v. Google LLC (No. 23-cv-02431, N.D. Cal., filed May 17, 2023) is a class action whose complaint alleges that Google Analytics, Google Ads and Google display code on health care provider websites collects patients' health information. Other suits name hospitals and health systems directly over the pixels on their own sites.

These are allegations unless a court has ruled on them. Check the docket for the current status of any case before citing it.

Government actions over pixels and health data

Regulators have also acted. These summaries come from the agencies' own releases.

  • New York Attorney General, NewYork-Presbyterian Hospital (December 2023): the AG said the hospital used third-party tracking tools on its website from June 2016 to June 2022, that in some cases the companies received information about users' health, and that the hospital reported the incident affected over 54,000 people. The hospital agreed to pay $300,000 and adopt policies on third-party tools.
  • FTC, GoodRx (February 2023): the first action under the Health Breach Notification Rule, over health information shared with Facebook, Google and others; a $1.5 million civil penalty under a proposed order.
  • FTC, BetterHelp (final order July 2023): health questionnaire information, email and IP addresses shared with Facebook, Snapchat, Criteo and Pinterest; $7.8 million for consumer refunds.
  • FTC, Cerebral (April 2024): tracking tools on its website and apps allegedly sent sensitive information about nearly 3.2 million consumers to third parties including LinkedIn, Snapchat and TikTok.

The pattern behind the cases

The facts repeat. A tag sends a URL, a search term, a form answer or a contact detail to an ad platform from a page that reveals something about the visitor's health. The NewYork-Presbyterian release gives an example: a search for “spine surgery” could appear in the URL that the tracking tools received.

HHS guidance, the FTC rule and Washington's My Health My Data Act each address that flow from a different angle. Our guides to each are linked below.

Example: audit tags by what they can see

A practical audit starts with which tags load on which pages. In a hypothetical audit, a health site loads 12 third-party tags. Nine load only on general pages. Three also load on the booking flow, where the URL contains the service name and the form asks for a reason for the visit.

Those 3 of 12 tags, a quarter of the total, are the ones to review first: what they send, under which agreement and with which consent. Removing a tag from the booking flow or masking its URLs reduces what it can see without touching the other nine.

Prioritise by exposure

General pages only

9 tags

Lower exposure; still review what they collect.

Also on booking flow

3 tags (25%)

Review first: URLs and form fields can carry health details.

Illustrative audit.

Reducing what tags can reach

DATALYR's controls address the same flow. Page filters block or mask URLs before events are 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, and you can pause all sharing with a platform while you review.

None of this is a legal shield, and tags installed outside DATALYR need their own review.

Related articles.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started