HIPAA guide
HIPAA compliant analytics: what it takes.
No analytics tool is HIPAA compliant by itself. On any page where a visit could reveal patient information, the analytics vendor must sign a business associate agreement (BAA) and be set up to keep PHI out of reports. Google says it does not offer a BAA for Google Analytics, so it is limited to pages that are not HIPAA-covered.
Checked November 10, 2026. Not legal advice.
What has to be true before patient data goes in.
Decide which pages can reveal PHI
HHS says tracking on user-authenticated pages, patient portals, mobile apps and unauthenticated pages for scheduling appointments or using a symptom checker may have access to PHI in certain circumstances.
Get a BAA from any vendor that receives PHI
HHS says tracking technology vendors are business associates if they create, receive, maintain or transmit PHI for a regulated entity, and that regulated entities must have a BAA with them.
Do not send PHI to vendors that will not sign
Google says it offers no BAA for Google Analytics, and Meta's terms bar sending health information through its business tools. Keep both off pages where PHI could be collected.
Keep PHI out of URLs and events
Health details in page URLs, titles, event names and parameters travel to the vendor. Strip them before any tag fires.
Re-check tags when the site changes
The Security Rule asks regulated entities to assess the need for a new evaluation when their environment changes, for example when they adopt new technology.
Your options, and what each needs.
| Piwik PRO Healthcare Enterprise | Piwik PRO's Healthcare Enterprise plan includes a BAA and is listed from $30,000 per year; Piwik PRO says the setup requires an appropriate BAA and compliant configuration and does not guarantee HIPAA compliance. |
|---|---|
| Freshpaint | Freshpaint describes a BAA- or DPA-covered tracking layer that controls what each analytics and ad platform receives; check its pricing page or talk to sales for the price. |
| CallRail Healthcare Plan | BAA included with every Healthcare Plan for call tracking; the plan price is not published. |
| Google Analytics on non-health pages only | Google offers no BAA and says to use it only on pages that are not HIPAA-covered. |
| Meta Pixel off patient pages | Meta's terms bar sending health information and mention no BAA, so keep the pixel off portals, logged-in pages and appointment pages. |
Where this usually goes wrong
- Installing GA4, the Meta Pixel or other ad tags on portals, booking pages or symptom checkers
- Assuming the June 2024 court decision removed the risk, when HHS's page still lists logged-in pages, portals, apps and some appointment pages
- Passing health details in URLs, form field names or event parameters
- Letting an agency add tags without a vendor and BAA review
This page reports what the vendor publishes and is not legal advice. Vendors change their terms, so check the sources below before you rely on it.
HIPAA compliant analytics: common questions.
Is Google Analytics HIPAA compliant?
Google says it does not offer a BAA for Google Analytics, that HIPAA-regulated organizations must refrain from exposing PHI to Google through it, and that it may be used only on pages that are not HIPAA-covered.
What did the 2024 court ruling change?
On June 20, 2024 a federal court vacated the part of HHS's tracking bulletin about an IP address plus a visit to an unauthenticated public page about health conditions or providers. HHS's page still lists tracking on logged-in pages, portals, apps and some appointment-booking or symptom-checker pages.
Questions people search
Which analytics tools can a healthcare website use?
That depends on the page. Where a visit could reveal patient information, the vendor must sign a BAA and be set up to keep PHI out of reports. CallRail signs one with every Healthcare Plan for call tracking. Google Analytics and the Meta Pixel offer none, so they stay off pages where patient information could be collected.
Which pages on a clinic website can reveal patient information?
HHS says tracking on logged-in pages, patient portals, mobile apps and unauthenticated pages for scheduling appointments or using a symptom checker may have access to PHI in certain circumstances. Treat those as the pages to protect first, and keep health details out of their URLs, titles and event names.
What should I do about ad pixels like the Meta Pixel on a clinic site?
Keep them off portals, logged-in pages and appointment pages. Meta's Business Tools Terms bar sending health information and mention no BAA. Ad tags on a page where patients type health details can pass that information to the vendor, and HHS says tracking vendors that receive PHI must sign a BAA.
How often should I re-check the tags on my website?
Whenever the site changes, including a new form, chat widget, booking tool or tag. The Security Rule asks regulated entities to assess the need for a new evaluation when their environment changes, for example when they adopt new technology. Letting an agency add tags without a vendor and BAA review is a common pitfall.
- HHS: Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates
- HHS: Business Associates FAQs
- HHS: Summary of the HIPAA Security Rule
- American Hospital Association: Judge rules in favor of AHA, vacating HHS online tracking bulletin
- Google Analytics Help: HIPAA and Google Analytics
- Meta: Business Tools Terms
- Piwik PRO: Pricing
- Freshpaint: Protect Privacy and Compliance
- CallRail: Call Tracking for Healthcare
More HIPAA guides
Find out what AI says about you.
A free 20-minute call. We ask the assistants your customers' questions and show you where you come up today.
No pitch unless you ask for one.