Public pages use no advertising trackers. The secure portal uses an essential session cookie and the service providers described in our privacy policy.

Skip to main content

· Court ruling

In re Meta Pixel Healthcare Litigation

U.S. District Court for the Northern District of California, No. 3:22-cv-03580-WHO, ECF No. 1425

For plaintiffsClass certification granted under Rule 23(b)(3) and (b)(2), with a narrowed section 631 class and a redefined CDAFA class; motions to exclude experts largely denied

Primary source: Order on class certification (ECF No. 1425). Checked on November 10, 2026.

A federal court certified classes of Facebook users suing Meta over health information allegedly obtained from provider websites and apps, holding that consent, intent and whether the data is contents are common questions.

What happened

The plaintiffs are Facebook users suing Meta Platforms, Inc., which supplies the Meta Pixel and its other Business Tools. The only defendant the order addresses is Meta; healthcare providers appear in it as the websites and apps from which data was sent. The plaintiffs asked the court to certify four classes for a class period running from June 17, 2018, to the present (ECF No. 1425 at 1, 3).

The four proposed classes cover Facebook users who had at least one patient portal, medical appointment, bill payment or diagnostic assessment button click obtained by Meta from listed providers; users with at least one communication or fact identifying a doctor, condition or treatment acquired by Meta from those providers, other than those button clicks; users whose communications with a prescription drug website for a drug they were prescribed were obtained by Meta; and users on whose devices Meta placed an _fbp cookie or used computing resources while they were on a healthcare provider's property. The listed providers are entities the plaintiffs identified as covered by HIPAA, and whether each one is covered was left for summary judgment or trial (ECF No. 1425 at 3 & n.1, 4).

All four classes sought certification of claims for breach of contract, breach of the implied covenant, intrusion upon seclusion and violation of California's Comprehensive Computer Data Access and Fraud Act (CDAFA). The first three classes also sought certification of claims under the federal Wiretap Act, which the order calls the ECPA, and the California Invasion of Privacy Act (CIPA) (ECF No. 1425 at 3-4).

The plaintiffs and their experts contended that for most of the class period Meta's default Business Tools settings let it acquire the data at issue and that Meta never told healthcare entities to change those defaults or how to do so. Meta disputed this, pointed to its filters and to providers that set up the tools differently, and argued that under its retention policies its oldest classwide data dates from March 2022. The court made no finding on these disputes and described the evidence on them as common, to be tested at summary judgment or trial (ECF No. 1425 at 5-7).

What the court held

  1. Rule 23(a) was met. Meta did not dispute numerosity, adequacy, typicality or the existence of common questions, and it contested only predominance and superiority. (ECF No. 1425 at 4)

  2. Meta's arguments about which provider sites sent data, the configurability of the Pixel, its data retention, its blocking efforts and differences among users raise complex questions that are not truly individualized, and they can be managed by narrowing class periods or provider lists, by subclasses or, if needed, by decertification. (ECF No. 1425 at 4-10)

    Plaintiffs will have to make choices on how to try this case and manage some of the complex but not truly individualized questions.

    ECF No. 1425 at 7
  3. The classes reach only patients whose specifically identified information, protected by HIPAA or by California's Confidentiality of Medical Information Act (CMIA), Meta acquired. The court said that structure distinguishes Smith v. Facebook, Inc., where the data was URL headers with general health information available to the public, and that general research a person did before becoming a patient or prescription user would not be actionable. (ECF No. 1425 at 7-9)

    any general research she engaged in prior to becoming a patient or user of a specific prescription drug would not be actionable

    ECF No. 1425 at 9
  4. Meta's standing objections did not defeat certification. The court found its reliance on Popa v. Microsoft Corp. unpersuasive, relied on the Ninth Circuit's decision in Black v. IEC Group, Inc. and on the plaintiffs' contract claim, and said Meta may move to decertify if it shows that more than a de minimis part of the class lacks standing. (ECF No. 1425 at 9-11 & n.7)

    Plaintiffs’ breach of contract claim, based on promises Meta made to plaintiffs, provides a firm footing for the breach of contract claim and also informs the statutory and common law privacy claims.

    ECF No. 1425 at 10
  5. Consent under the Wiretap Act and CIPA is an affirmative defense and must be actual. Following the Ninth Circuit's Calhoun v. Google, LLC, the question is what a reasonable user would understand the disclosures to mean, a common question the court said will likely be resolved classwide at summary judgment. It distinguished cases in which defendants had disclosed the very practice at issue. (ECF No. 1425 at 11-15)

    Under the ECPA and CIPA, consent is an affirmative defense.

    ECF No. 1425 at 11
  6. On the Wiretap Act's one-party consent rule, evidence of what Meta told website and app operators, and of what each provider knew or told its users, is common to that provider's patients, and any provider-by-provider review would not outweigh the common evidence. (ECF No. 1425 at 12-13 & n.9)

    That evidence will be largely, if not fully, common.

    ECF No. 1425 at 12
  7. The court did not decide whether the crime-tort exception applies. It said that analysis would be needed only if Meta showed actual consent on behalf of identified providers. (ECF No. 1425 at 13 n.11)

    I do not need to determine the applicability of the crime-tort exception at this juncture

    ECF No. 1425 at 13 n.11
  8. What Meta knew about receiving healthcare data, when it knew, what it did to prevent it and how well that worked are subject to common proof, as is the evidence about how Meta promoted and delivered its tools to healthcare entities. (ECF No. 1425 at 15)

  9. Because CIPA section 631 and CDAFA require a California connection, the court agreed to certify the section 631 claim for narrowed subclasses of patients who communicated from California or with a California-based healthcare provider, and it found a plausible showing of the required connection for that claim and for the CDAFA claim. (ECF No. 1425 at 16-17)

  10. Whether the class categories of information are contents under the Wiretap Act or CIPA section 631 is a common question. The court noted that Meta may be able to prove that prescription drug site URLs it acquired, or its later efforts to hash URLs, meant protected contents were not disclosed for some or all of the class period. (ECF No. 1425 at 17)

    Whether these categories of information are considered contents under the ECPA or CIPA section 631 are common questions.

    ECF No. 1425 at 17
  11. Damages issues did not defeat predominance. Statutory or punitive damages, even if discretionary, will be determined on a classwide basis, and the court distinguished Campbell v. Facebook Inc., where the Wiretap Act's discretionary statutory damages precluded certifying a class that was not limited to a type of information. (ECF No. 1425 at 18 & n.17)

    As an initial matter, differences in damages rarely defeat class certification.

    ECF No. 1425 at 18
  12. A class action is superior given the case's complexity and cost, and certification is also appropriate under Rule 23(b)(2) for the injunctive relief the plaintiffs identified, though injunctive relief would no longer be at issue if the evidence overwhelmingly shows Meta no longer acquires the data and has structures to prevent it. (ECF No. 1425 at 19-20)

  13. The court denied Meta's motions to exclude the plaintiffs' experts on identifying provider data, valuing the data, Meta's profits, medical ethics and consumer expectations, treating most criticisms as matters for cross-examination, and it denied the plaintiffs' motions to exclude Meta's experts. It granted Meta's motion to strike attorney commentary in one reply exhibit. (ECF No. 1425 at 21-34)

  14. General descriptions of how Meta acquired data from the listed providers, matched it to its users and used it should be disclosed, while source code, certain table and field names, employee contact information and the plaintiffs' health information may stay under seal for now. (ECF No. 1425 at 34-36)

  15. The motion was granted except for the limited section 631 class and the redefined CDAFA class; the plaintiffs had agreed to amend the device class to drop Conversions API and customer list uploads, which Meta said do not affect devices. The plaintiffs were given ten days to file a revised class definition and thirty days to submit a notice plan. (ECF No. 1425 at 17 n.16, 37)

    For the reasons discussed, plaintiffs’ motion to certify the classes is GRANTED, except for the limited Section 631 and redefined CDAFA class.

    ECF No. 1425 at 37

What it did not decide

  • Whether Meta is liable on any claim. The court applied the rule that merits questions are considered only to the extent they bear on the Rule 23 requirements (ECF No. 1425 at 2-3).
  • Whether patient-status button clicks, communications identifying a doctor, condition or treatment, or prescription drug site URLs are contents under the Wiretap Act or CIPA section 631 (ECF No. 1425 at 17).
  • Whether the crime-tort exception applies (ECF No. 1425 at 13 n.11).
  • Whether Meta's disclosures, or any provider's disclosures, gave users actual consent (ECF No. 1425 at 11-15).
  • Whether each listed provider is a HIPAA or CMIA covered entity, which the court expected to be briefed at summary judgment (ECF No. 1425 at 4-5).
  • Any claim against a healthcare provider; the order addresses claims against Meta only.

The tracking involved

Tools

  • Meta Pixel
  • Meta Business Tools in provider websites and apps
  • _fbp cookie

Data

  • patient portal, appointment, bill payment and diagnostic assessment button clicks
  • communications identifying a doctor, condition or treatment
  • communications with prescription drug websites, including their page addresses
  • device storage and computing resources (device class)

How it bears on website tracking claims

Supports: strengthens a website tracking claim on this issue. Limits: narrows or defeats a website tracking claim on this issue. Context: bears on the issue without deciding it either way.

  • Supports: Class certification

    Whether claims can go forward on behalf of a whole class of website or app users.

    The order lets health-data privacy claims against the platform that received the data proceed as a class, holding that disputes over default settings, filters, data retention and user behavior do not defeat predominance and can be handled by narrowing the classes or by decertification. It treats each website's setup and disclosures as evidence common to all of that site's users rather than as visitor-by-visitor questions. It is a certification ruling against Meta, not a merits ruling, and it binds no other court.

    All tracker entries on this issue

  • Supports: Consent

    Whether visitors agreed to the tracking through banners, privacy policies or terms.

    Applying Calhoun v. Google, LLC, the court held that consent under the Wiretap Act and CIPA must be actual and is judged by what a reasonable user would understand, not by what any one user read or knew. That treats a site's privacy disclosures as objective evidence judged the same way for every visitor. The court distinguished cases where the defendant had disclosed the very practice at issue, so what the disclosures actually say still matters.

    All tracker entries on this issue

  • Context: Party exception

    Whether the website, as a party to the visit, could consent to the tracking under 18 U.S.C. § 2511(2)(d).

    The court treated a provider's possible consent to Meta's receipt of its patients' data as evidence common to that provider's patients, and it tied the crime-tort exception to the case where Meta proves such consent. This order does not address how the party exception applies when the website operator itself is the defendant.

    All tracker entries on this issue

  • Context: Crime-tort exception

    Whether a communication was intercepted for the purpose of a criminal or tortious act, which removes the party exception.

    The court expressly left the crime-tort exception undecided. It noted the plaintiffs' argument that the exception would apply because of Meta's further use of the data in matching it to specific Facebook users, and said that analysis would be needed only if Meta showed actual consent by identified providers.

    All tracker entries on this issue

  • Context: Contents

    Whether what was sent, such as page addresses, searches and clicks, counts as the contents of a communication.

    The court did not decide whether the class categories, including button clicks that reveal patient status and the URLs of prescription drug sites, are contents. It held only that the answer will rest on common evidence, and it flagged Meta's possible proof that URLs it acquired or later hashed did not disclose protected contents for some or all of the class period.

    All tracker entries on this issue

  • Supports: Standing and injury

    Whether the people suing were harmed in a way that lets a federal court hear the claim.

    Meta's standing objections did not defeat certification. The court distinguished two September 2026 rulings from the same district that found no standing, one because the browsing was not shown to be sensitive enough and one because the Pixel sent no substantive information about the transactions, pointing to the nature of the information here and to expert evidence of acquisition and matching. Part of the court's footing was a contract claim based on Meta's own promises to its users.

    All tracker entries on this issue

  • Context: Health information

    What counts as individually identifiable health information when it is sent through tracking tools.

    The classes are confined to patients and to button clicks that reveal patient status, communications identifying a doctor, condition or treatment, and prescription drug communications by people who hold the prescription. The court said general research done before someone became a patient would not be actionable, and it distinguished a case about URL headers carrying general health information available to the public. That line favors claims about patient-specific activity and cuts against claims resting on general browsing of health content.

    All tracker entries on this issue

  • Context: HIPAA

    How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.

    There is no HIPAA claim, but the court said HIPAA is relevant to reasonable consumer expectations and possibly to how a reasonable consumer would understand Meta's promise that its partners have lawful rights to the data they send. The first two classes are tied to providers the plaintiffs identify as HIPAA covered entities, a status still to be proven.

    All tracker entries on this issue

  • Limits: State wiretap laws

    State interception statutes, such as California Penal Code § 631 and the Washington Privacy Act.

    CIPA section 631 requires a California connection, and the court did not certify a section 631 class of all users. It agreed instead to subclasses of patients who communicated from California or with a California-based provider. The order recounts that in Frasco v. Flo Health, Inc. a section 631 class was not certified for lack of a California connection.

    All tracker entries on this issue

  • Supports: Damages

    What must be shown to recover money, including statutory damages and proof of actual loss.

    The court held that statutory or punitive damages will be determined on a classwide basis, and it distinguished a ruling that found the Wiretap Act's discretionary statutory damages precluded certifying a class not limited to protected healthcare information. It also described $5,000 in statutory damages, if available under CIPA or otherwise, as by no means insignificant but far smaller than Meta's legal bills, which it treated as favoring a class action.

    All tracker entries on this issue

Arguments it addresses

Consent has to be decided visitor by visitor
The court held that consent under the Wiretap Act and CIPA must be actual and is judged by what a reasonable user would understand, a common question, and it distinguished cases where the defendant had disclosed the very practice at issue (ECF No. 1425 at 11-15).
The website operator consented, so the one-party rule applies
The court treated each provider's consent as evidence common to that provider's patients and said the crime-tort exception would need analysis only if Meta proved actual consent by identified providers (ECF No. 1425 at 12-13 & n.11).
Clicks and page addresses are not contents
The court did not decide that question and held only that whether the class categories are contents is a common question (ECF No. 1425 at 17).
The data was hashed or filtered
The court said Meta may be able to prove that its later hashing of URLs meant contents were not disclosed for some or all of the class period, and it treated the evidence on Meta's filtering and blocking as disputed and common (ECF No. 1425 at 7, 17).
No concrete injury
The court rejected Meta's standing objections at this stage, distinguished rulings about less sensitive browsing, and left Meta free to move to decertify if it shows that more than a de minimis part of the class lacks standing (ECF No. 1425 at 9-11 & n.7).
General health browsing is not protected health information
The court agreed that general research done before a person became a patient or prescription user would not be actionable, and the classes are limited to patients' protected communications (ECF No. 1425 at 7-9).
Statutory damages cannot be set for a whole class
The court held that statutory or punitive damages, even if discretionary, will be determined on a classwide basis (ECF No. 1425 at 18 & n.17).

For a company that received a letter

  • This order concerns claims by Facebook users against Meta, not claims against any website operator, and it decides only that the claims may proceed as a class.
  • The court treated what each healthcare provider told its patients, and how each provider set up Meta's tools, as evidence common to all of that provider's patients.
  • The court described the plaintiffs' expert evidence about Meta's default settings and filters as disputed and made no finding about what any particular provider's site sent.
  • The court said the classes can be narrowed or decertified as the evidence develops, so this order does not fix their final scope.

What to check on your own site

  • Check whether clicks on patient portal, appointment, bill payment or assessment buttons send an event, including the button's text, to an advertising platform.
  • Check whether pages that name a doctor, condition, treatment or prescription drug send their page address or title to a third party.
  • Check which data collection settings are on by default in your advertising platform accounts, since the order describes disputed evidence about default Business Tools settings.

Later history

As of November 10, 2026, the district court docket listed a stipulation and proposed order filed November 9, 2026 (ECF No. 1426), the day the order's ten-day deadline for a revised class definition fell, and an order on that stipulation entered November 10, 2026.

September 7, 2023 · Court rulingDoe v. Meta Platforms (N.D. Cal. 2023)Mixed rulingPatients' Wiretap Act and CIPA claims against Meta over its pixel on health care providers' patient portals survived dismissal, with the scope of covered content, Meta's intent and the providers' consent left to evidence.August 1, 2025 · Court rulingFrasco v. Flo Health (N.D. Cal. 2025)For plaintiffsA federal jury found Meta violated California Penal Code section 632 by eavesdropping on or recording Flo app users' menstrual and ovulation answers through its software development kit, and the court denied post-trial motions.October 17, 2025 · Court rulingDoe v. Eating Recovery Center (N.D. Cal. 2025)For defendantsA federal court held Meta Pixel data from an eating disorder provider's site were contents of communications but rejected the California wiretap claim because Meta did not read or try to learn them in transit.November 14, 2024 · Court rulingCastillo v. Costco Wholesale (W.D. Wash. 2024)Mixed rulingRuling on the pleadings, a Seattle federal court held pharmacy customers' prescription searches sent to Meta were contents and a financial motive does not defeat the crime-tort exception, but dismissed the Washington Privacy Act claim.October 23, 2026 · Court rulingRand v. Eyemart Express (5th Cir. 2026)For plaintiffsThe Fifth Circuit held that the alleged unauthorized disclosure of website users' health information to Meta through its Pixel is a concrete injury, and that such information need not reveal a diagnosis.August 19, 2026 · Court rulingMagliocca v. United Healthcare Services (E.D. Cal. 2026)For defendantsData from one visit to a health insurer's general plan pages, with only a ZIP code entered, showed no concrete injury, a federal court held, dismissing the tracking suit with prejudice for lack of standing.

Published by Privacy Resolve from public records. It does not cover our own matters.

General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.