This guide is for an agency asked to audit the Meta Pixel on a clinic, practice, telehealth or health information website. It covers what Meta's own documentation says the pixel collects, how events and advanced matching add to it, and what Meta's terms say about health information. It describes configurations and quotes Meta's pages; it does not grade the product. To take the pixel off patient pages and keep campaign reporting, see Removing the Meta Pixel from Patient Pages.
What does the Meta Pixel send from every page it loads on?
Each time it loads, the pixel sends a PageView event, and Meta's documentation says the pixel collects HTTP header information, including the page location and referrer, along with the Pixel ID and the Facebook cookie.
Meta's documentation says "[e]ach time the Pixel loads, it automatically calls fbq('track', 'PageView') to track a PageView standard event." It describes HTTP header information as data that "may include data like IP addresses, information about the web browser, page location, document, referrer and person using the website," and pixel-specific data as including the "Pixel ID and the Facebook Cookie."
On a health site the page location is often the sensitive part. An address that names a service, a condition or a doctor goes to Meta with every page view, together with a cookie value that lets Meta connect the visit to a browser it has seen before.
What do button clicks and form fields add?
Meta's documentation says the pixel can collect button click data, including button labels and the pages visited as a result, and the names of form fields, though not the values typed unless the site sends them.
Meta describes button click data as including "any buttons clicked by site visitors, the labels of those buttons and any pages visited as a result of the button clicks." It describes form field names as "website field names like email, address, quantity, etc.," and says: "We don't capture field values unless you include them as part of Advanced Matching or optional values."
On a health site, a label can be the health fact. A button that reads "Schedule a mammogram" or "Start your weight loss consultation" tells Meta what the visitor chose.
What does advanced matching add?
Customer details such as email address, phone number, name, date of birth, city, state and ZIP code, which the pixel hashes with SHA-256 before sending when the site uses Meta's base code.
Meta's developer page says that with the base code, "[v]alues will be hashed automatically by the pixel using SHA-256." It explains manual setup in the base code and adds that "[t]o automatically implement advanced matching use the Events Manager," so check the Events Manager settings as well as the site's code.
Hashing hides a value from anyone reading the request, but the same details hashed the same way produce the same value, which is what makes matching possible. Advanced matching on a booking or intake form ties a health-related event to a person's contact details.
What do event names and custom data reveal?
They can state the health fact outright, and Meta's terms say event names and audience criteria "must not reflect, imply or be based on" health information or the other sensitive categories the terms list.
The full sentence in section 1.h of Meta's Business Tools Terms reads: "The names you choose and criteria you establish for your events, conversions, and any custom audiences you create must not reflect, imply or be based on any category of information described in this Section 1.h."
Three places to look:
- Standard events. A Lead, Schedule or SubmitApplication event fired from an intake or booking form tells Meta that a person took a step toward care.
- Custom events and custom data. Meta says "[d]evelopers and marketers can optionally choose to send additional information about the visit through Custom Data events." A custom event or parameter named for a service line, condition or provider carries that word to Meta.
- Search. Meta's Search event takes a search string parameter, which Meta describes as the "String entered by the user for the search." See Site Search and Form Events.
What do Meta's own terms say about health information?
Meta's Business Tools Terms have the advertiser represent that it will not share data that "includes or is based on, directly or otherwise, health information," among other sensitive categories.
The passage in section 1.h reads, in part: "You represent and warrant that you will not share Business Tool Data with us that ... (iv) includes or is based on, directly or otherwise, health information, financial information, consumer report information, or other categories of sensitive information." The parenthetical that follows in the terms adds "any information defined as sensitive under applicable laws, regulations and applicable industry guidelines." The page shows an effective date of November 3, 2025.
An agency that sets up the pixel for a health client is configuring what that client sends under those terms. The configuration decides what goes to Meta.
Where else can the pixel be installed besides the tag manager?
In the site's theme or header code, through platform plugins and integrations, inside scheduling, form and chat widgets, on campaign landing pages, and through a server connection that sends the same events from the site's server.
Each needs its own check. Removing the Meta Pixel from Patient Pages lists where to look, and Meta Conversions API and Server-Side Tagging explains why a server-side copy reaches Meta too. To trace a request in a record back to the tag that sent it, see Checking a Case File Against Your Tag Manager.
Which laws make a pixel on a patient-facing page a legal question?
Two federal provisions come up first: HIPAA's criminal provision, 42 U.S.C. § 1320d-6, and the crime-tort clause of the Wiretap Act's consent exception, 18 U.S.C. § 2511(2)(d), with state privacy laws alongside.
Section 1320d-6(a)(3) reaches a person who knowingly, and in violation of HIPAA's rules, discloses individually identifiable health information to another person. Section 2511(2)(d) takes an interception outside the consent exception when it is made "for the purpose of committing any criminal or tortious act." A federal court in New York denied a motion to dismiss a Wiretap Act claim over advertising tracking code on a health system's website and patient portal, holding the crime-tort exception plausibly alleged because disclosing individually identifiable health information for commercial advantage would violate § 1320d-6. Cooper v. Mount Sinai Health System, Inc., 742 F. Supp. 3d 369, 379 (S.D.N.Y. 2024).
For addiction treatment programs, 42 C.F.R. Part 2 adds a stricter regime; see Website Tracking at Addiction Treatment Programs. For HHS's guidance, see HIPAA, Pixels and AHA v. Becerra. Other courts have dismissed similar claims, and The Wiretap Act's Crime-Tort Exception sets out the decisions on both sides.
What should an agency change, and how should it confirm the change?
Take the pixel off condition, provider, booking, intake, portal and search pages, turn off automatic advanced matching for what remains, keep health terms out of event names and custom data, and confirm each change in the Network panel.
- Pages. Fire the pixel only on an allowlist of pages that say nothing about anyone's health.
- Advanced matching. Turn off automatic advanced matching in Events Manager, and remove manual advanced matching from any form that remains.
- Events and custom data. Rename or remove events and parameters that name a service, condition or provider, and do not fire lead or scheduling events from health forms.
- Server copies. Keep the same events off any server route as well. If an event should not reach Meta from the browser, it should not reach Meta from the server.
- Confirm. Open each page type in a private window with the Network panel open and filter for
facebook.com/trandconnect.facebook.net. In each request,evis the event anddlthe page address. Then run the five-minute Reject button test. - Record. Write down the date, the pages changed, the tag manager version and who reviewed the change, and keep the old versions.
What sources does this guide rely on?
This guide relies on Meta's documentation and terms, the statutes and the decision listed here, quoted from the pages linked. Checked on November 10, 2026.
- Meta Pixel developer documentation
- Meta: Conversion Tracking
- Meta: Advanced matching
- Meta Business Tools Terms
- 42 U.S.C. § 1320d-6 (Legal Information Institute)
- 18 U.S.C. § 2511 (Legal Information Institute)
- Cooper v. Mount Sinai Health System, Inc., 742 F. Supp. 3d 369 (S.D.N.Y. 2024)