Tracking appointment bookings without sending health data to ad platforms
Healthcare tracking has a constraint no other vertical has: the page URL itself can be health information. A booking confirmation at /book/dermatology-consultation tells Meta something about the patient that neither you nor they should be transmitting, and both Meta and Google prohibit it in their own terms. The approach that works is to strip identifying context at the container before anything leaves — send that an appointment was booked, its value, and nothing that identifies the condition or the person.
Free30 minutesNo obligation
Healthcare appointments · what breaks
The situation, as it usually presents — Healthcare appointments
- 01
Appointment bookings tracked with condition in the URL
The most common and most serious error.
- 02
Marketing and compliance unable to agree
So nothing gets measured at all.
- 03
Form fields captured by session recording
Including free-text symptom boxes.
Healthcare appointments · the fix
What changes — Healthcare appointments
Bookings measured without health context
One generic conversion, real value.
Sensitive parameters stripped at the container
Before anything leaves your infrastructure.
A documented data-handling position
That compliance can actually review.
Healthcare appointments · architecture
Why this pattern keeps recurring — Healthcare appointments
The exposure in healthcare tracking is rarely a deliberate choice; it's what tags send by default.
- 1
The URL travels with every tag
You didn't choose to send the condition. The page path did it for you, on every event.
- 2
Referrers leak the previous page
A booking confirmation reached from a condition-specific landing page carries that page in the referrer.
- 3
Session recording captures form fields
Including free-text boxes where patients describe symptoms. This is usually the largest unnoticed exposure.
- 4
Browser-side stripping isn't a boundary
Client-side filtering runs after the data is already in a third party's script. Only a server container is an actual control point.
Healthcare appointments · diagnose
How the root cause gets found — Healthcare appointments
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Capture every outbound parameter on the booking page
Read them individually.
- 02
Check the URL and page title for condition names
The usual finding.
- 03
Check the referrer chain
It carries the previous page.
- 04
Audit session recording and heatmap scope
Form fields especially.
- 05
Establish who signs off on data handling
Before changing anything.
Healthcare appointments · prove
How the work is proven — Healthcare appointments
Against the client's own records, not a dashboard turning green.
Source of truth
Appointment records in the practice management system
- Every outbound parameter reviewed and documented.
- No condition or identifying context present in any dispatched event.
- Stripping verified by capture, not by configuration.
- Booking counts reconciled against the practice system.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Healthcare appointments · free audit
What we check in the free audit
- Capture every outbound parameter on the booking page
- Check the URL and page title for condition names
- Check the referrer chain
- Audit session recording and heatmap scope
- Establish who signs off on data handling
Checked against
Appointment records in the practice management system
Free30 minutesNo obligation
Healthcare appointments · when not to buy
Why there are no client numbers on this page — Healthcare appointments
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Healthcare appointments · what we deliver
What the work involves — Healthcare appointments
Every outbound parameter inventoried
URL, referrer, form fields, page title.
Sensitive values stripped server-side
Where you control the boundary.
Conversion generalized
Appointment booked, not which appointment.
Session recording and heatmaps audited
Usually the biggest unnoticed exposure.
Written guarantee
95%+ tracking accuracy
Measured against Appointment records in the practice management system. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, for advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Healthcare appointments questions, answered
Yes, with the health context removed. Both platforms' terms prohibit receiving health information, so stripping it protects the account as well as the patient.
No. This is a technical control that supports a compliance position your counsel defines. We reduce what leaves; we don't certify anything.
It can't be recalled. Fixing the flow stops it continuing, which is the part still under your control.
Inside your own analytics and practice system, yes. What we don't do is send that segmentation to an ad platform.
Free · 30 min
Measure bookings without exposing patient data
WhatsAppFree30 minutesNo obligation
