Health systems, telehealth startups and private practices all want to know which pages and campaigns drive appointments. The trouble is that standard analytics and ad pixels can collect information that counts as protected health information. HIPAA conversion tracking in the US needs a careful setup, and this guide explains the basics.
This is general information, not legal advice. Have your privacy officer or counsel review your configuration.
Why tracking is a risk on health sites
The Department of Health and Human Services has issued guidance on the use of online tracking technologies by HIPAA-covered entities and their business associates. In short, tracking tools on pages that relate to a person's health, such as appointment booking or symptom pages, can lead to impermissible disclosures if they send identifiable data to third parties.
The FTC has also taken action against health companies for sharing sensitive data with advertising platforms, and its Health Breach Notification Rule can apply to health apps that fall outside HIPAA. Some states add their own rules, including Washington's My Health My Data Act.
Guidance is updated and has been challenged in court, so check the current position with counsel.
Audit what is on your site
Start by listing every script, pixel and tag. Many sites carry tags nobody remembers adding.
- Run a scan to list tags and cookies on key pages.
- Check patient portals, booking pages, forms and symptom checkers first.
- Look for session recording, chat widgets and heatmap tools, which can capture typed text.
- Confirm whether each vendor will sign a business associate agreement where one is needed.
Design tracking that respects the rules
You can still measure conversions without sending sensitive details. The aim is to record that an action happened, not who took it or why.
Safer patterns
- Use server-side or first-party event collection that you control, with data stripped of identifiers before it leaves.
- Send generic events such as "booking_completed" without service names that reveal a condition.
- Avoid URL paths or parameters that contain conditions, provider names or appointment details.
- Do not install advertising pixels on authenticated or booking pages without legal review.
Mask or block form fields in any session recording tool, or switch recording off on sensitive pages.
Measure with what you can use
Many practices can learn a lot from aggregate data. Combine privacy-conscious web analytics with your scheduling system, call tracking and front-desk intake questions.
For example, compare booked appointments per month against traffic sources, and ask new patients how they found you. That gives you channel-level answers without individual-level tracking on sensitive pages.
Run CRO tests that stay safe
Testing tools often add scripts and cookies. Run tests mainly on public marketing pages, such as service overviews and location pages, and keep them off authenticated areas.
Focus on changes that do not need personal data: page layout, copy clarity, button placement, form length and mobile speed. Evaluate results using aggregate counts of bookings.
Also follow marketing and consent rules
If your forms feed email or text programs, CAN-SPAM and the Telephone Consumer Protection Act apply. Record consent properly and offer easy opt-outs.
State privacy laws such as CCPA and CPRA may also apply to some data. Keep your privacy notice accurate and easy to find.
| Area | Lower risk | Higher risk |
|---|---|---|
| Public blog pages | Aggregate analytics | Retargeting pixels tied to conditions |
| Booking pages | First-party event counts | Third-party pixels, session replay |
| Patient portal | No third-party tags | Any advertising tag |
Build a review habit
Add tag governance to your release process. Any new script should be approved by someone responsible for privacy, and you should re-scan quarterly.
If you need a partner who can plan measurement and testing around these limits, see our services.
Practical steps for the first 30 days
- Inventory every tag, pixel, plugin and embedded form on your site.
- Ask your privacy officer to classify pages as public, booking or authenticated.
- Remove or restrict third-party tags on booking and portal pages.
- Check vendor agreements and ask which vendors will sign a business associate agreement.
- Set up first-party event counts for core conversions such as booking started and booking completed.
What good reporting looks like
A monthly dashboard can show visits to service pages, booking starts, completed bookings, phone calls by tracking number and self-reported source from intake. None of those require identifying a person in an ad platform.
Use that view to decide which pages to improve. If a service page gets strong traffic but few booking starts, rewrite the page and simplify the path. That is classic conversion work, done without risky data flows.
Document your decisions
Keep a short record of what you track, why, which vendors receive data and who approved it. If regulators or patients ask questions later, that record shows you took a considered approach.
Frequently asked questions
Can we use Google Analytics on a HIPAA-covered site?
It depends on where and how it is configured. Avoid it on pages where identifiable health information may be collected, and get legal advice on your setup.
Are Meta and Google ad pixels allowed on patient pages?
Treat them as high risk on any page connected to appointments or conditions. Seek legal review before using them.
How can we measure ad performance without pixels?
Use aggregate data, unique phone numbers by campaign and patient intake questions, and consider privacy-preserving server-side methods reviewed by counsel.
Want help with this? See our Conversion rate optimisation service, or how we work in healthcare branding.
Explore Conversion rate optimisationHealthcare branding