Skip to content

Healthcare, dental and clinics

Track the leads. Never the patient.

Healthcare clients still need Google Ads and Meta to learn which campaigns bring bookings. We set up conversion tracking that sends no health information and no personal details to ad platforms, and we document every field so the client's compliance team can review it.

WHO IT'S FOR

  • Dental practices, med spas, physiotherapy and private clinics
  • Multi-location healthcare groups running Google Ads and Meta
  • Telehealth and wellness brands with sign-up or booking flows

Why it's different

The rules that change the setup.

  • 01

    Ad platforms aren't built for health data

    Google's and Meta's terms don't allow sensitive health information to be sent through their tags, and neither treats its ad tools as a place to process patient data.

  • 02

    Regulators have looked at tracking pixels

    The US health regulator (HHS) warned in 2022 that tracking on health websites can disclose patient information. A federal court set part of that guidance aside in 2024, but tags on patient portals and logged-in pages remain a clear risk.

  • 03

    Hashing doesn't make data anonymous

    A hashed email is built to be matched back to a person. For healthcare we don't send emails or phone numbers to ad platforms at all, hashed or not.

  • 04

    Meta limits some health events

    Meta has started restricting certain conversion events for health-related advertisers. We check what the client's account is allowed to use before planning the setup.

The data map

What goes out, and what never does.

What ad platforms receive

  • A generic conversion: lead, booking_request or call
  • The ad click ID (gclid, fbclid) so the conversion matches the ad
  • A page location with the path and query string removed or generalized
  • A fixed conversion value agreed with the client, if any

What never leaves the site

  • Names, emails, phone numbers, hashed or not
  • Treatment, condition or service names in event names or URLs
  • Form answers, symptoms, insurance details or appointment notes
  • Anything from patient portals or logged-in pages

How we set it up

Step by step, in the client's own accounts.

Pricing

Part of Server-side & Privacy, from $1,490 per client account. Scoped after the free tracking check, with a fixed quote before any work starts.

See full pricing
  1. 01Map every tagWe list every tag on the site and record exactly what each one sends today: URLs, page titles, parameters and form fields.
  2. 02Remove tags from sensitive areasNo ad tags on patient portals, logged-in pages, intake forms after submission, or appointment details.
  3. 03Generalize events and URLsEvent names like lead instead of ivf_consultation. Page paths and titles that reveal a condition are stripped or replaced before they leave the site.
  4. 04Turn off personal matchingEnhanced conversions and Meta advanced matching stay off. Conversions match by click ID, not by the patient's details.
  5. 05Filter on the serverServer-side GTM sits between the site and the ad platforms, removes anything not on the approved list and truncates IP addresses where possible.
  6. 06Consent firstConsent Mode v2 and the client's banner are configured so ad tags wait for consent where the client's rules require it.
  7. 07Write the data specOne document listing every event, every field and every destination, for the client's compliance or legal team to approve before go-live.

Outcomes

Outcomes without patient data

Bidding still needs to know which leads became real appointments. We send those outcomes back using only the click ID and a generic event name.

  1. Stage 1

    Booking request

    The form or call that started it, counted once.

  2. Stage 2

    Appointment booked

    Marked in the practice system or CRM, sent back by click ID only.

  3. Stage 3

    Attended

    Optional, and only if the client's compliance team approves it.

Platforms covered

Works with the client's existing stack.

  • Google Ads
  • GA4
  • Meta
  • Server-side GTM
  • Consent Mode v2
  • CallRail
  • HubSpot
  • GoHighLevel
  • Booking widgets

Something else? Tell us which tools the client uses and we'll confirm before you pay.

What we do and don't claim

We don't claim HIPAA compliance or any certification, and this page isn't legal advice. We build privacy-safe tracking that sends no personal or health information to ad platforms, and the client's legal or compliance team decides what is acceptable.

Healthcare tracking: questions

5 questions

No setup can promise that, and we don't claim certifications. We make sure no personal or health information reaches ad platforms and document exactly what is sent, so the client's compliance team can decide.

Some matching is lost, yes. That's the trade-off for not sending patient details. Click IDs, server-side tracking and offline outcomes recover a good part of the signal without personal data.

Usually, with care. Meta restricts some events for health-related advertisers, so we check what the account can use and keep event names generic.

Our setup is designed so that we and the ad platforms don't handle patient information. If a client's legal team requires a BAA for any part of the stack, they choose vendors that offer one.

No. The same approach works for UK, EU and other clients. Consent rules differ by country, so we configure consent for where the client's patients are.

Got a healthcare client whose numbers don't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.