HIPAA-compliant analytics means measuring website results without sending protected health information (PHI) to analytics or advertising tools that have not signed a Business Associate Agreement. For most practices, that means tracking that a call or booking happened, not what the patient asked about. This guide explains what Google, HHS and the FTC have said, and how to set up safe tracking.
This guide explains how we approach tracking. It is not legal advice. Check your practice’s duties with a healthcare privacy professional.
Why analytics became a HIPAA question
Analytics and ad tools collect details such as page addresses, IP addresses and button clicks. On a medical website, these details can reveal health information. A visit to a page called “/book-hiv-testing/” from a known IP address, for example, can link a person to a health service.
In December 2022, the US Department of Health and Human Services issued guidance on the use of online tracking technologies by HIPAA-covered entities. HHS updated it in March 2024. In June 2024, a federal court in Texas ruled that part of the guidance, about tracking on public pages, went beyond HHS’s authority. The rules around tracking on public pages are still unsettled, so many practices follow a careful approach on every page.
Is Google Analytics HIPAA compliant?
No, not on its own. Google states that it does not offer Business Associate Agreements for Google Analytics and makes no claim that Google Analytics meets HIPAA requirements.
Google also says customers must not use Google Analytics in a way that creates HIPAA obligations for Google. In practice, Google advises HIPAA-regulated entities to:
- Not send Google any data that may be PHI.
- Not place Google Analytics tags on authenticated pages, such as patient portals.
- Not place tags on public pages that HHS would treat as related to providing health care services.
A practice can still use Google Analytics with care, on pages and events that carry no health information.
What the FTC has done
The Federal Trade Commission enforces health privacy for companies outside HIPAA, such as many health apps and online services.
- In February 2023, the FTC announced a $1.5 million civil penalty against GoodRx for sharing health data with advertising platforms.
- In 2023, the FTC ordered the online counseling company BetterHelp to pay $7.8 million over the sharing of consumers’ health data for advertising.
These cases show that regulators look closely at tracking pixels on health websites.
5 rules for safe medical website tracking
These 5 rules keep most practice websites on the safe side.
1. Track events, not conditions
Track “form sent”, “call clicked” and “booking completed”. Do not send the service, condition, appointment type or form answers to analytics or ad tools.
2. Keep tags off sensitive pages
Do not place analytics or ad tags on patient portals, bill pay pages, symptom checkers or booking steps that reveal a condition.
3. Remove advertising pixels from health pages
Ad platform pixels, such as Meta Pixel, send detailed page data to advertisers. Remove them from pages about specific conditions and treatments, or use a server-side setup that strips health details first.
4. Choose vendors that sign a BAA
For call tracking, form tools, chat and analytics that may touch PHI, choose vendors that sign a BAA. Several analytics tools built for healthcare offer one.
5. Audit tags every quarter
Old tags from past agencies and plugins often keep sending data. Review Google Tag Manager, plugins and page code every 3 months and remove what is not needed.
Safe analytics setups for practices
Practices usually choose one of 3 setups:
- Google Analytics with limits. Tags only on safe pages, no health details in events and no advertising features. Low cost, but it needs careful setup and review.
- A HIPAA-ready analytics tool. A tool that signs a BAA and is built for healthcare. Higher cost, but it can handle more pages.
- Server-side tracking. A server between your website and analytics tools that removes health details and IP addresses before data leaves your control. More setup, more control.
What to measure without health data
A practice can measure almost everything it needs without PHI: calls by source, form submissions by source, bookings by source, rankings, Google Business Profile actions and traffic to page groups. Results by service line can come from your scheduling system, where patient data already lives under your own HIPAA controls.
HIPAA-compliant analytics FAQ
Can a medical practice use Google Analytics 4?
Yes, with care. Google does not sign a BAA for Analytics, so do not send it PHI, do not tag patient portals and keep health details out of events.
Does Google sign a BAA for Google Analytics?
No. Google states that it does not offer Business Associate Agreements for Google Analytics and makes no claim that the service meets HIPAA requirements.
Is the Meta Pixel safe on a medical website?
No, not on pages about conditions, treatments or booking. The Meta Pixel sends detailed page data to Meta. Remove it from health pages or use a server-side setup.
Do I need a BAA with my call tracking vendor?
Yes, when calls are recorded or transcribed. Recordings can contain patient health details, so choose a call tracking vendor that signs a BAA.