Resources

Google Analytics, Meta Pixel and HIPAA: What a Small Practice Website Can Safely Track

Google offers no BAA for Analytics and Meta bans health data. Where HHS tracking guidance stands after 2024, and a 15-minute script audit for practice sites.

By ClinicSite Editorial Team, Healthcare Practice Web Architecture · Published September 4, 2026

The short answer
No, not on pages that touch patient care. Google's Analytics help page says Google "does not offer Business Associate Agreements in connection with this service" and tells HIPAA-regulated customers not to tag authenticated pages or pages related to health care services. Meta's business terms likewise prohibit sending it health information through its pixel.

General information, not legal advice. Sources were verified in 2026. Ask your compliance officer or attorney before changing how your site handles tracking.

What Google and Meta say about health data, in their own words

Start with the vendors, because their positions are clearer than most blog posts about them.

Google Analytics. Google's help article "HIPAA and Google Analytics" says customers "must refrain from using Google Analytics in any way that may create obligations under HIPAA for Google," and that "Google makes no representations that Google Analytics satisfies HIPAA requirements and does not offer Business Associate Agreements in connection with this service." It then gives page-level instructions:

  • Customers subject to HIPAA "may only use Google Analytics on pages that are not HIPAA-covered."

  • "Authenticated pages are likely to be HIPAA-covered," so no Analytics tags there.

  • Unauthenticated pages "related to the provision of health care services" are "more likely to be HIPAA-covered."

  • Work with your legal team to identify pages that do not relate to the provision of care.

Meta Pixel. Meta's Business Help Center page "About prohibited information" says Meta does "not want or permit advertisers to use the Meta Business Tools" to share prohibited information, which "includes health information." Its examples include medical conditions, mental health, treatments and testing, and "places of treatment and counseling." It also warns against sending data from pages "where visitors may log in and provide potentially sensitive information, such as patient portals," and notes that UTM parameters in URLs "may contain prohibited data." Meta offers a "core setup" mode that strips URL details and custom parameters, but says it is "not a substitute for your own compliance mechanisms."

So neither vendor will sign a BAA for these tools, and both put the burden of keeping health data out on you.

Where HHS's tracking guidance stands after the 2024 court ruling

HHS's Office for Civil Rights publishes a bulletin titled "Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates." The court record refers to the version at issue as the revised bulletin of March 18, 2024. Here is what happened next, from the docket of American Hospital Association v. Becerra, No. 4:23-cv-01110 (N.D. Tex.):

DateEvent
June 20, 2024The court declared unlawful and vacated one part of the bulletin, which it called the "Proscribed Combination," and entered final judgment. It denied an injunction.
August 19, 2024HHS filed a notice of appeal to the Fifth Circuit.
September 4, 2024The Fifth Circuit appeal (No. 24-10775) was dismissed on HHS's own motion.

HHS's bulletin page now opens with a note describing the vacated part: guidance saying HIPAA obligations are triggered when an online technology connects "(1) an individual's IP address with (2) a visit to a[n] [unauthenticated public webpage] addressing specific health conditions or healthcare providers." The note ends: "HHS is evaluating its next steps in light of that order." The page shows it was last reviewed June 26, 2024.

What that leaves standing, in plain terms: the rest of the bulletin is still posted. It says tracking on logged-in pages, such as a patient portal, "generally" has access to PHI. It treats an unauthenticated page where someone books an appointment or enters symptoms as a page where tracking may collect PHI. It says login or registration details typed into a portal page are PHI. It says a privacy-policy disclosure alone does not permit sharing PHI with a tracking vendor, and that a vendor's promise to strip PHI after receiving it is not enough without a BAA.

What got narrower: HHS can no longer rely on the bulletin's position that an IP address plus a visit to a public page about a condition, without more, triggers HIPAA. That is a smaller change than "the tracking rules were struck down," which is how it is sometimes summarized.

Which pages on a small practice site carry the most risk

Roughly in order, for a typical dental, medical or therapy site:

  1. Booking and appointment-request pages, including confirmation and thank-you pages. HHS's own example is an appointment booked on a public page.

  2. Pages with forms that ask for a reason for visit, symptoms or insurance details.

  3. Patient portal login and registration pages, if your site hosts them rather than linking out.

  4. Search results pages, where the search term ("anxiety therapist," "implant cost") can travel in the URL.

  5. Condition and treatment pages. After the 2024 ruling this is the most contested category; Google's own guidance still says pages related to providing care are "more likely" covered.

  6. General pages such as hours, directions, careers and the blog. These are where Google says analytics may be used, subject to your legal team's review.

A 15-minute audit: find every script your site loads

You do not need to be technical for this. You need a desktop browser and a notepad.

  1. List your pages, using the risk order above. Note which ones a patient would visit before or after booking.

  2. Open each page with the browser's developer tools (right-click, then Inspect), go to the Network tab, and reload. Type these into the filter box one at a time: google-analytics, googletagmanager, facebook, fbevents. Any hit means that script loaded on that page.

  3. Check your builder's integration settings. On Squarespace, look at the Meta Pixel & Ads panel, the Google Analytics setting, and Code Injection (site-wide and per page). On Wix, check whether PHI protection is active, since Wix says it hides identifying visitor analytics. On WordPress, list every analytics, marketing and chat plugin.

  4. Open your Google Tag Manager container, if you have one, and list every tag. Tag Manager can load tools that never appear in your site settings.

  5. Look at your URLs after a test booking or form submission. If a name, email, visit type or search term appears after a ?, any tag on that page can read it.

  6. Write down the date and what you found. If your practice ever needs to show what it reviewed and when, this note is the evidence.

Options once you know what loads

  • Remove. Delete pixels and tags from every high-risk page, or from the whole site. A practice can still judge marketing results from booking volume and from what new patients say at intake.

  • Restrict. Keep Google Analytics on pages your legal team has identified as unrelated to care, as Google itself describes. This needs per-page control, which some builders handle poorly, and it needs re-checking whenever pages change.

  • Replace. Use an analytics vendor that will sign a BAA, or the route HHS mentions: a customer data platform vendor that signs a BAA and de-identifies data before anything reaches a tracking vendor. Read the BAA's scope before you rely on it.

Meta's core setup and similar "restricted data" modes reduce what is sent. Meta itself says they do not replace your own compliance controls.

Enforcement in brief, with dates

Two well-documented federal actions on health-data tracking came from the Federal Trade Commission, against digital health companies rather than medical practices:

  • GoodRx, February 1, 2023. The FTC announced its first enforcement action under the Health Breach Notification Rule. Under the proposed order, GoodRx agreed to a $1.5 million civil penalty over undisclosed sharing of health information with Facebook, Google and others. The FTC also said GoodRx displayed a seal falsely suggesting HIPAA compliance.

  • BetterHelp, March 2, 2023. The FTC announced a proposed order requiring the online counseling service to pay $7.8 million to settle charges that it shared consumers' health questionnaire data with Facebook and others for advertising.

The FTC's own guidance says its Health Breach Notification Rule does not apply to HIPAA covered entities or to companies acting solely as HIPAA business associates; those fall under HHS's breach rule. The cases still show how regulators read pixel data: as disclosures of health information.

How ClinicSite sites handle this

Published ClinicSite sites run under a content security policy that blocks third-party scripts and outbound network calls, so they carry no analytics, ad pixels, session recording or tag manager. The one widening is the website assistant on the Elite plan, which, when enabled, allows a single known origin. The trade-off is real: there is no analytics on the published site, which some practices will miss. Details are on the hosting page and in the FAQ, and the website builder overview lists what ClinicSite does not claim, including any HIPAA certification.

If you want to see your current site rebuilt without tracking scripts, start a free preview; it needs no account or card and is deleted after seven days. For the form side of the same problem, read Do website forms need to be HIPAA compliant?, and for the wider checklist, the HIPAA website requirements guide.

Sources

Frequently asked questions

Is Google Analytics 4 HIPAA compliant?
Google does not describe GA4 as HIPAA compliant and does not offer a BAA for it. Its help page says HIPAA-regulated customers may use Analytics only on pages that are not HIPAA-covered, should not tag authenticated pages, and should treat pages related to the provision of care as more likely covered. Configuration settings such as IP handling do not change the absence of a BAA.
Was the HHS tracking guidance struck down?
Partly. On June 20, 2024, a federal court in Texas vacated the part of HHS's bulletin saying that an IP address combined with a visit to a public page about specific conditions or providers triggers HIPAA. HHS appealed, then dismissed its appeal in September 2024. The rest of the bulletin, including the sections on portals and booking pages, remains posted on HHS's site.
Can I use the Meta Pixel on my practice's homepage?
Meta's terms prohibit sending health information, and Meta warns that URLs and parameters can carry it. A homepage with general information is lower risk than a booking or condition page, but the pixel often loads site-wide once installed. Decide page by page with your compliance reviewer, and check that the pixel is not also firing on booking, form or portal pages.
Does "core setup" or restricted data mode make the Meta Pixel safe?
It reduces what is sent by stripping URL details and custom parameters. Meta's own help page says core setup restrictions "are not a substitute for your own compliance mechanisms." The pixel still records page visits, and Meta's terms do not permit health information to be sent at all.
Is server-side tracking a way around HIPAA?
Moving tags to a server changes how data travels, not who receives it. If PHI still reaches Google or Meta, the same problem applies. HHS's bulletin also says a vendor agreeing to remove PHI after receiving it is not sufficient without a BAA. A server-side setup helps only if it removes PHI before anything reaches a vendor without a BAA.
What can a small practice measure without third-party tracking?
Plenty, using data you already own: calls by source if your phone system tracks them, new-patient bookings, the "how did you hear about us" question at intake, directory and Google Business Profile statistics, and Search Console data about which searches show your site. Those answer most small-practice marketing questions without placing a third-party script on patient-facing pages.
Does HIPAA apply to tracking on a cash-only practice's website?
HIPAA applies to covered entities, and a provider is covered only if it transmits health information electronically in a standard transaction such as an insurance claim. A practice outside that definition may not be bound by HIPAA. FTC consumer-protection law and state privacy laws can still apply, so treating health-related tracking with the same caution is the safer default.

See what your clinic site could look like

Paste your current website address. You get a full generated replacement to look at, free, with no account and no card.

Free preview with no card. Previews are deleted after 7 days.