Why analytics went dark
Healthcare removed its analytics — and went blind
The tracking stack that every other industry takes for granted became a legal liability for covered entities. Three facts explain the gap this beta exists to close.
The pixel lawsuits reached $47.5M
Kaiser Permanente’s settlement over website tracking pixels reached $47.5M — one of a wave of wiretapping-law class actions against health systems.
Google won’t sign the contract healthcare needs
Hospitals and clinics strip Google Analytics and ad pixels because Google won’t sign the HIPAA contract (BAA) that covered entities legally require.
Budgets are reallocated blind
With tracking gone, nothing connects a paid click to a booked patient — budgets are reallocated blind.
BAA = Business Associate Agreement, the HIPAA contract where a vendor takes legal responsibility for patient data.
Who sees identifiers
The difference is whose servers see the raw identifiers
Both approaches observe the same visit. What separates them is where each identifier is allowed to travel.
The ad platform still learns “click X converted” — enough to optimize campaigns. It never learns who the person is or what care they sought.
First-party by construction
First-party by construction
Five steps from ad click to measured booking — with the allowlist, not an after-the-fact filter, deciding what leaves.
- 01
Ad click lands
Google, Meta, and LinkedIn append their click ID to the landing URL — the one identifier the ad platform already owns.
- 02
Pixel on your domain
A ~3KB script reports to an endpoint on the clinic’s own domain. No third-party beacons.
- 03
Server-side allowlist
The default is send nothing: IP discarded, URL path redacted, PHI blocked.
- 04
Your warehouse
Clean events land next to your ad-spend data. You stay the data owner; we stay a processor.
- 05
Click ID only
Optionally, the bare click ID returns to the ad platform so bidding keeps learning.
- ✓ We sign a BAA and operate as your Business Associate
- ✓ Consent banner built in — tracking starts only after explicit visitor consent
- ✓ US-only data residency, encryption in transit and at rest, full audit log
What you see
What you see
Compliance evidence
Compliance you can show your legal team
Five beta questions
Early beta — five questions, thirty minutes
The product is early on purpose. Your answers to five questions decide what gets built next.
- 1
Is this problem real for you and your clients today — how painful is the loss of web analytics?
- 2
How do you measure paid campaigns right now without GA — and what does that cost you?
- 3
Would you pilot the beta on one property or sub-client site?
- 4
Looking at this UI — what is missing for your day-to-day work?
- 5
What would your compliance and legal team need to see to approve a pilot?