Data Infrastructure

Healthcare marketing tracking without sending patient data to ad platforms

Healthcare teams can still learn which campaigns book consultations without passing clinical details, identifiers, or condition-specific page data into ad platforms and analytics tools.

Founder of MetricMaven. Previously managed Google Tag Manager and Google Analytics across 800+ sites at HCA Healthcare, and built attribution and eCommerce reporting at RYZE Superfoods and Mars.

Healthcare marketing measurement needs clear boundaries around what is collected and where it goes. A booking outcome may be useful to a campaign report, but clinical details and identifiers can make the same data flow inappropriate. Review the payload and destination, not just the event name.

Why this is a measurement design problem

Legal questions belong with counsel. HHS’s Office for Civil Rights has published guidance on online tracking technologies for HIPAA covered entities and business associates. The guidance discusses tracking data that includes protected health information (PHI), disclosures to vendors, and user-authenticated pages, public pages, and mobile apps. Have counsel assess the data and circumstances in your own implementation.

On June 20, 2024, the U.S. District Court for the Northern District of Texas, in American Hospital Association v. Becerra, vacated the portion stating that HIPAA obligations are triggered when tracking connects an IP address with a visit to an unauthenticated public page about specific health conditions or providers. HHS’s current bulletin describes this partial vacatur and retains other guidance.

Many visits to unauthenticated public pages do not involve PHI; some can, depending on the information collected or disclosed. The bulletin also discusses authenticated pages and mobile apps.

Treat it as a starting point and ask counsel how the FTC Act, the FTC’s Health Breach Notification Rule, and applicable state laws affect your setup.

Keep clinical detail out of the payloads

Keep clinical context out of URLs, page titles, event names, and parameters sent to ad platforms and analytics tools. A path or title can reveal what a person was viewing even without a name attached. Google says it does not offer a business associate agreement for Google Analytics and that HIPAA-regulated entities must not expose PHI to it. Check its current guidance and PII policy before changing the implementation.

Clinical records are separated from aggregate campaign reporting.
Data elementOK in ad or analytics platforms?Safer alternative
Condition-specific page URL or titleGenerally no. A path or title that names a condition can reveal health information.Generalize the path to a service category, use a neutral page identifier, and review with counsel.
Appointment reason or service line tied to a personNoKeep it in the EHR or CRM only, and report a generic booked-consultation event instead.
Ad click ID, such as gclidTypically used for matching, so review with counsel before it leaves the form flow.Store it on the intake record at submit, and send it only where counsel has approved.
Hashed email sent for conversion matchingRequires counsel review and an authorization analysis before any use.Send a generic conversion event with no contact data unless counsel approves matching.
UTM campaign, source, and medium valuesLower risk as campaign labels, but on booking and intake pages the same request can carry PHI, so review those flows with counsel.Restrict them to campaign labels, with no free-text fields.
Generic conversion event, such as “qualified consultation”Only with counsel sign-off. A cookie banner choice is not a HIPAA authorization.Send no diagnosis, service detail, or patient identifier with it.
A measurement view, not legal advice. Each row needs sign-off from counsel for your organization.

Measure campaign to booked consultation without the clinical record

The business still needs to know which campaigns produce booked consultations and patients. The pattern that works is to split the job. The intake system or CRM holds the clinical and identity context under its own controls, while the reporting warehouse holds campaign and outcome counts. Ad platforms and analytics tools receive the minimum signal they need, if any.

  1. Capture UTMs and click IDs on the form page, before any navigation that could drop them.
  2. Write them onto the intake record at submit, next to the consultation request, rather than into a page URL.
  3. Keep appointment reasons and clinical notes in the EHR or CRM, under its access controls.
  4. Join campaign to booked and attended outcomes in your warehouse, using a stable record ID rather than names.
  5. Decide with counsel which conversion events, if any, go back to ad platforms, and send only generic ones.

Patient portals and authenticated areas

Review patient portals and other authenticated areas as a distinct measurement surface. What a tag collects or discloses matters; ask counsel to assess whether PHI reaches a vendor and what permissions or agreements apply. A conservative design can keep third-party ad pixels out of portals and use tools reviewed by the compliance team.

Public pages also need review. HHS gives the example of an appointment request that sends appointment details and a visitor’s IP address to a tracking vendor. Inspect booking and intake pages, as well as other public page paths and titles, for information that could identify a person’s health context.

Document what each consent choice enables, then verify that tags follow it when the page loads. HHS states that a banner asking visitors to accept or reject tracking is not a HIPAA authorization. For each vendor, review current terms and ask counsel whether an agreement or other permission is needed for the data flow. Financial institutions face a parallel problem with account data; see bank and credit union marketing tracking.

Before a release, use the tracking QA checklist before launch and add checks for page titles, URL paths, form fields, and portal tags. A server-side layer may let your team remove or generalize fields before sending data onward; review its actual configuration and destinations.

See the server-side tagging guide for implementation context. Want it done for you? MetricMaven can inventory the public marketing pages, form fields, and tags in scope. That audit is not a compliance review.

Frequently asked questions

Does a tracking pixel on a healthcare site violate HIPAA?

It depends on what the tag collects, where it runs, and who receives the data. HHS OCR guidance says HIPAA applies when tracking technologies collect or disclose PHI to tracking vendors, and that disclosing PHI to a vendor for marketing without a HIPAA-compliant authorization is impermissible. Pixels on patient portals and other authenticated areas deserve the closest review. Ask privacy counsel to look at your specific setup.

Can a healthcare site send data to Google Analytics?

Google says it makes no representation that Google Analytics satisfies HIPAA, does not offer a business associate agreement for it, and that HIPAA-regulated entities must not expose PHI to Google through it. Check its current help page for the exact language, since it can change. Design the setup so that page paths, page titles, and events carry no clinical or identifying detail.

How do you measure healthcare ad conversions without sending patient data?

Capture campaign parameters and ad click IDs at form submit, store them with the intake record, and report campaign to booked to attended in your own warehouse. Send ad platforms only conversion signals that counsel has approved, with no diagnosis, service detail, or patient identifier attached. A cookie banner is not a HIPAA authorization, so banner consent alone does not clear a disclosure.

Can Maven help with healthcare tracking without patient data?

It helps on the tag side. Maven’s tracking audit finds broken, degraded and stalled pixels and events and tags with no trigger in each client’s Google Tag Manager, and every container change is staged with the exact diff and QA evidence and goes live only after you approve it. It is not a compliance review. Decisions about legal requirements stay with your counsel and compliance team.

Sources and references

Jamie Isabel

Founder of MetricMaven. Previously managed Google Tag Manager and Google Analytics across 800+ sites at HCA Healthcare, and built attribution and eCommerce reporting at RYZE Superfoods and Mars.

Updated October 16, 2026

Start your 14-day trial

Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.

  • Free for 14 days, no credit card
  • Your first client workspace and portal
  • Every report template, ready to clone
Start a 14-day trial

Nothing is charged unless you subscribe.

Prefer a walkthrough? Book a demo on one of your own clients.