Privacy-Safe Tracking · Health-Data-Safe Tracking
For telehealth, DTC Rx, women's health and supplement brands, we scope pixels and events so ad platforms get the signals they need to optimize, and none of the condition-level detail they shouldn't have.
Why health is different
A standard ad pixel sends the page URL, page title, button text and an identifier tied to the visitor. On most stores that's routine. On a health store, the same request can say that a specific person viewed an erectile dysfunction treatment, started a fertility quiz or booked a weight-loss consult. That's the kind of disclosure regulators have focused on.
The fix isn't to stop measuring. It's to decide, page by page and event by event, what each vendor may receive, and make the tracking enforce it.
Practical basics
| Rule | Who it usually concerns | What it means for tracking |
|---|---|---|
| HIPAA | Covered entities (such as providers and health plans) and their business associates; many telehealth models involve one | Protected health information can't go to vendors without a business associate agreement (BAA), and most ad and analytics pixels won't sign one |
| FTC Health Breach Notification Rule | Health apps and sites not covered by HIPAA that hold consumers' health records | Sharing health data with advertisers without authorization can count as a breach that requires notification |
| FTC Act | Any business making privacy promises | What your pixels do must match what your policy and banner say |
| State health and privacy laws | Businesses handling health data of residents in states such as Washington, and states treating health data as sensitive | Some require opt-in consent before collecting or sharing health data, not just an opt-out |
This is a technical summary, not legal advice. Confirm with counsel which rules apply to you and how. HHS guidance on online tracking technologies was partly vacated by a federal court in 2024, which is one more reason to get current advice.
Where health stores leak
Product, collection and blog URLs that name a condition, sent with every pixel event.
Answers pushed into events, URLs or the data layer, then forwarded to ad platforms.
Automatic click tracking that captures labels like "Start your ED consult".
Prescription product names and categories in purchase events sent to Meta or Google.
Hashed email sent with condition-level events through Conversions API or enhanced conversions.
ESP or CRM segments based on conditions synced to ad platforms as custom audiences.
Our approach
General pages, condition-specific pages, and intake, account and checkout pages, each with the data it can expose.
Which vendors may load where, and what each may receive. We bring the technical options; counsel decides.
No advertising pixels on intake, consult, account or other authenticated pages. Generic event names and values on sensitive products.
A server-side container removes URLs, product names, search terms and identifiers before anything reaches a vendor.
Where you need analytics on sensitive pages, we help evaluate vendors that offer a BAA, alongside your counsel.
New apps and quiz tools are the most common way a clean setup leaks again.
Measurement that still works
Ad platforms need to know that a valuable conversion happened. They rarely need to know what it was. We design signals around that difference.
Industries
Related services
Start with a Tracking Privacy Review to see what your pixels send today. Consent for sensitive data is configured in your CMP, and Google tags follow it through Consent Mode v2. Health brands win on refills and reorders, so model the upside with the retention rate calculator. Part of Privacy-Safe Tracking.
FAQ
Possibly, on some pages, with limits your counsel approves. The main risk is the pixel sending condition-level information, such as URLs, product names or intake details, tied to an identifiable visitor. A common approach keeps ad pixels off intake, consult and account pages, sends only generic conversion events and filters data server-side. If you're a HIPAA covered entity, get specific advice first.
Google's own guidance says businesses subject to HIPAA shouldn't use Google Analytics in a way that gives Google access to protected health information. That means keeping GA4 off pages and events that could carry PHI, or choosing an analytics vendor that will sign a business associate agreement for those pages. Your counsel should confirm the approach.
No. Server-side tagging gives you a place to remove sensitive fields before data reaches a vendor, which is useful. But if protected health information still reaches a vendor without a business associate agreement, the setup doesn't solve the problem. It's a tool for enforcing rules your counsel sets, not a compliance shortcut.
It's an FTC rule that requires certain health apps and websites not covered by HIPAA to notify consumers and the FTC after a breach of identifiable health information. The FTC has made clear that sharing health data with advertisers without authorization can count as a breach. For tracking, that means treating health data on your site as off-limits for ad pixels unless counsel approves.
Possibly in part. Supplement brands are usually not HIPAA covered entities, but product pages and quizzes can still reveal health conditions, and some state laws define consumer health data broadly. A Tracking Privacy Review shows what your pixels send, so you and your counsel can decide what to change.
Start with the free audit to see your tracking and consent health from the outside, or book a call to talk through your pixels and pages.