Is Google Analytics HIPAA compliant for a treatment center? A treatment center can use website analytics, but only in ways that do not send protected health information to vendors without a HIPAA permission and, where required, a business associate agreement. Google says it does not offer business associate agreements for Google Analytics and tells HIPAA-regulated customers not to tag HIPAA-covered pages. Ad pixels raise the same questions, often with more risk.
This article is general information from a marketing agency, not legal advice. Tracking rules depend on your specific setup, so review any changes with healthcare privacy counsel.
Last reviewed: October 2026. Guidance in this area has changed several times since 2022; check the linked sources for updates.
Measurement is part of every SEO and website project we run, so this question comes up early. It connects directly to how we approach behavioral health SEO and admissions-first websites, and to the hosting and management work where tags tend to accumulate over time. Privacy-safe measurement is built into our behavioral health marketing work from the start, not added afterward.
What did HHS say about tracking technologies on healthcare websites?
The HHS Office for Civil Rights issued a bulletin on the use of online tracking technologies by HIPAA covered entities and business associates in late 2022 and updated it on March 18, 2024. It says HIPAA rules apply when information collected through tracking tools includes protected health information (PHI), and that regulated entities may not use tracking in ways that result in impermissible disclosures of PHI to vendors.
Key points from the bulletin that matter for treatment centers:
- Tracking technology is broad. HHS lists cookies, web beacons or pixels, session replay scripts and fingerprinting scripts.
- Logged-in pages generally involve PHI. Tracking on patient portals and other authenticated pages generally has access to PHI.
- Forms and tools on public pages can involve PHI. HHS gives the example of tracking that collects an email address or a reason for seeking care typed into an appointment or symptom-checker page.
- Vendors receiving PHI are business associates. A business associate agreement (BAA) is required, and the disclosure must still be permitted by the Privacy Rule.
- A privacy policy or cookie banner is not enough. HHS says disclosures cannot rest solely on a privacy policy notice, and that cookie consent banners do not constitute a valid HIPAA authorization.
- “We’ll strip the PHI” is not enough. HHS says it is insufficient for a vendor to promise to remove or de-identify PHI after receiving it.
- Marketing disclosures need authorization. Disclosing PHI to tracking vendors for marketing without individuals’ HIPAA-compliant authorizations is impermissible.
- Security Rule obligations apply. Tracking should be addressed in your risk analysis and risk management processes.
What changed after the court ruling in AHA v. Becerra?
On June 20, 2024, a federal court in Texas vacated part of the HHS bulletin. HHS’s page now notes that the court vacated the guidance to the extent it said HIPAA obligations are triggered when tracking connects an individual’s IP address with a visit to an unauthenticated public webpage addressing specific health conditions or healthcare providers. HHS filed an appeal but voluntarily dismissed it on August 29, 2024, so the ruling stands. As of October 2026, HHS has not issued replacement guidance, and its page still says it is evaluating next steps.
That ruling narrowed one theory: that simply viewing a public condition page, tied to an IP address, is a PHI disclosure. It did not remove the rest of the bulletin. Tracking on logged-in portals, information typed into forms, appointment requests and disclosures for marketing all remain risk areas. On a treatment center site, the insurance verification form and the admissions contact form are exactly where people type health information.
Why are addiction treatment centers higher risk than other providers?
Substance use disorder treatment carries extra federal confidentiality rules, a federal law aimed at deceptive marketing of addiction treatment (the Opioid Addiction Recovery Fraud Prevention Act, used in the Monument case below), and severe consequences for patients if information leaks. A tracking mistake that might be an embarrassment for a dental practice can be far more serious for a detox.
42 CFR Part 2
Federally assisted SUD programs are covered by the confidentiality rules at 42 CFR Part 2. HHS’s fact sheet on the 2024 Part 2 final rule explains that the rule aligned parts of Part 2 with HIPAA, applied HIPAA breach notification requirements to Part 2 records, and compliance has been required since February 16, 2026. The one exception is the new right to an accounting of disclosures, whose compliance date will be set when HHS revises the matching HIPAA right. The fact sheet also explains why these protections exist: concern that discrimination and fear of prosecution deter people from entering treatment. Your counsel should confirm whether Part 2 applies to your program and how it affects data from your website and intake.
The FTC is active in this space
The FTC enforces against companies, including those not covered by HIPAA, that share health data contrary to their promises. In 2024 it announced action against Monument, an online alcohol addiction treatment service. According to the FTC, Monument used pixels and APIs to send “custom events” with names like “Paid: Weekly Therapy” to advertising platforms along with email addresses and IP addresses, affecting as many as 84,000 users. The proposed order would ban it from disclosing health information for advertising and included a $2.5 million civil penalty under the Opioid Addiction Recovery Fraud Prevention Act, suspended due to inability to pay.
In 2023 the FTC finalized an order against online counseling service BetterHelp requiring it to pay $7.8 million over allegations that it shared health questionnaire information, email and IP addresses with platforms including Facebook and Snapchat for advertising. That same year the FTC and HHS sent a joint letter to roughly 130 hospital systems and telehealth providers warning about tools such as the Meta/Facebook pixel and Google Analytics. Entities outside HIPAA may also fall under the FTC’s Health Breach Notification Rule.
The Monument detail about event names is worth pausing on. It is common for sites to name their conversion events after the service (“Detox Form Submit,” “Alcohol Rehab Call”), and those labels travel to the ad platform.
Is Google Analytics HIPAA compliant for treatment centers?
Only with great care, and only on pages where no PHI could reach Google. Google’s HIPAA and Google Analytics help page says Google makes no representation that Analytics satisfies HIPAA, does not offer BAAs for it, and tells HIPAA-regulated customers to use it only on pages that are not HIPAA-covered.
Google’s page goes further. It says authenticated pages are likely HIPAA-covered and should not have Analytics tags, that unauthenticated pages related to the provision of healthcare services are more likely to be HIPAA-covered, and that customers should work with their legal team to identify which pages do not relate to providing care. Google Analytics policies also prohibit sending data Google could recognize as personally identifiable information.
On a treatment center site, our view is that most of the important pages relate to providing care: program pages, insurance pages, admissions pages and every form. In practice, that leaves very little room for standard Google Analytics without careful configuration and legal review.
Is the Meta pixel HIPAA compliant? What about Google Ads tags and other ad tracking?
Ad pixels are where we see the most risk, because their purpose is to send visitor behavior to an advertising platform. If a pixel fires on a form submission, an insurance page or an admissions page, it may be transmitting exactly the kind of information HHS and the FTC have warned about.
Platform rules also limit what you can do with that data. Google’s personalized advertising policy treats health as a sensitive interest category, so health advertisers cannot use advertiser-curated audiences like remarketing lists, Customer Match or lookalike segments. And Google’s addiction services policy allows ads for addiction treatment only from advertisers Google has approved, and only in certain countries, including the US. For many treatment centers, the retargeting value that justified a pixel in other industries is not available anyway.
What does a safer, HIPAA-aware analytics setup look like?
A safer setup starts with an inventory of every tag on your site, removes third-party tracking from pages and forms where people share health information, and measures admissions outcomes inside systems that are covered by a BAA. HHS itself describes one option: working with a vendor that will sign a BAA to de-identify data before anything reaches vendors who will not.
| Approach | How it works | Tradeoffs |
|---|---|---|
| No third-party tracking on care pages | Remove ad pixels, session replay and standard analytics from program, insurance, admissions and form pages | Least risk; less granular marketing data |
| Analytics vendor that signs a BAA | Use an analytics product whose vendor agrees to act as your business associate | Costs more; still requires permitted uses and minimum necessary |
| BAA-covered data platform that de-identifies | A customer data platform under a BAA strips PHI before passing data on, an option the HHS bulletin describes | Technical setup; must be configured and reviewed carefully |
| Call tracking under a BAA | Use a call tracking provider that will sign a BAA, with recording and transcription settings reviewed | Calls are often the main conversion; vet the vendor’s terms |
| Outcomes measured internally | Admissions logs source, qualified calls, pre-admits and admits in your CRM or EMR, reported in aggregate | Requires discipline from the admissions team; the most reliable data you will have |
None of these is automatically compliant. Each needs to fit your risk analysis and be reviewed by counsel.
The Create Flo Tracking Inventory: a step-by-step audit
This is the audit we run before touching a client’s measurement. You can do the first four steps yourself.
- List every script. Check your tag manager, theme files, plugins, chat widgets, scheduling tools and embedded forms. HHS specifically lists session replay and fingerprinting scripts as tracking technologies.
- Map where each one fires. Note which pages and which actions (page view, form submit, button click) trigger each tag.
- Check what is sent. Look at URLs, page titles, form field values and event names. A URL like “/thank-you?program=opioid-detox&insurance=aetna” sends more than you think.
- Rename revealing events. Event names should never describe a condition, substance or service. Learn from the Monument case.
- Confirm agreements. For every vendor that could receive PHI, confirm whether a BAA is in place and whether the disclosure is permitted. If not, remove the tag from those pages.
- Update your risk analysis. Document the tracking review in your HIPAA risk analysis, as the Security Rule requires and the HHS bulletin calls out.
- Rebuild measurement around outcomes. Move admissions reporting into your CRM or EMR and report in aggregate.
- Repeat quarterly. Plugins and vendors add tags without asking. Our website management clients get this check as part of routine maintenance.
What should you ask your marketing agency about tracking?
Ask exactly which tags they have installed, where each one fires, what data each one sends, which vendors have signed BAAs with you, and how they measure results without sending health information to ad platforms. If the answers are vague, treat that as a finding.
- Which pixels and analytics tags are on our site today, and who installed them?
- Do any tags fire on forms, insurance pages, admissions pages or portals?
- What are our conversion events named, and what parameters do they send?
- Which of our vendors have signed BAAs, and do you need one with us?
- How will you report on admissions without sending PHI to Google, Meta or anyone else?
Frequently asked questions
Is Google Analytics HIPAA compliant?
Google says it makes no representation that Google Analytics satisfies HIPAA requirements and does not offer BAAs for it. HIPAA-regulated entities must avoid exposing PHI to Google and should not tag HIPAA-covered pages.
Did the court ruling make tracking pixels safe again?
No. The June 2024 ruling vacated one part of the HHS guidance about IP addresses and visits to public pages. It did not address forms, portals, appointment requests or marketing disclosures, and FTC enforcement continues separately.
Does a cookie consent banner make tracking HIPAA compliant?
No. HHS says website banners asking users to accept or reject cookies do not constitute a valid HIPAA authorization.
Can we still run Google Ads without a pixel?
You can run search campaigns and measure results through calls and internal admissions records. Google’s health ad policies already restrict remarketing and audience lists, so much of what a pixel would add is limited anyway. Talk to your ads team and counsel about which conversion tracking, if any, fits your setup.
Does 42 CFR Part 2 apply to our website?
Part 2 applies to records of federally assisted SUD programs. Whether information from your website or intake becomes a Part 2 record depends on your program and workflow, which is a question for healthcare counsel.
Need a clear picture of what your site is tracking?
We’ll run the Tracking Inventory on your site, show you every tag and what it sends, and give you a cleanup plan to take to your compliance lead or counsel. Request a free audit, or learn about our website hosting and management and behavioral health SEO services. To see where privacy-safe tracking fits in a full marketing plan, read how to market a rehab center.
