Marketing and Patient Growth

Tracking Pixels on Practice Websites: HIPAA Risks

Where federal tracking guidance and the 2024 court ruling leave Meta pixels, analytics and tags on medical practice websites, with a page-by-page audit.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. What a tracking pixel actually sends
  2. Where the federal guidance stands
  3. Why authenticated pages matter more each year
  4. Enforcement outside HIPAA
  5. A page-by-page risk map
  6. How to audit your site in an afternoon
  7. Chat widgets, forms and session replay
  8. Who owns this inside the practice
  9. Example: a pediatric practice clean-up
  10. Marketing still works without the risky tags
  11. Frequently asked questions
  12. References
Marketing and Patient Growth: Tracking Pixels on Practice Websites: HIPAA RisksArticle coverMARKETING AND PATIENT GROWTHTracking Pixels onPractice Websites:HIPAA RisksAva Medical IntakeInsightsMarketing and Patient Growth: Tracking Pixels on Practice Websites: HIPAA RisksArticle coverMARKETING AND PATIENT GROWTHTracking Pixels onPractice Websites:HIPAA RisksAva Medical Intake

Key takeaways

  • A June 2024 court ruling vacated one part of federal tracking guidance, about IP addresses on public pages; the rest of the bulletin stands[1].
  • Patient portals, appointment forms and bill pay remain the highest-risk places for third-party tags.
  • A vendor that receives protected health information needs a business associate agreement; if your ad platform has not signed one, keep its tags away from patient data[2].
  • Regulators outside HIPAA also act: the FTC fined GoodRx for sharing health data with advertising platforms[3].

What a tracking pixel actually sends

A tracking pixel is a small piece of code, supplied by an advertising or analytics company, that runs when a page loads. Practice websites commonly carry several: an advertising pixel from a social network, a search platform's conversion tag, an analytics script, a chat widget, a heatmap or session-replay tool, and whatever the website builder adds by default. Each one can send the vendor the page address and title, the visitor's IP address, device identifiers, cookies that link visits together, and sometimes the buttons clicked or the text typed into a form.

On a restaurant site that information is harmless. On a medical site, a page address such as a booking confirmation for a named specialty, or a form field containing a reason for visit, can reveal that a specific person is seeking a specific kind of care. That is the core of the HIPAA problem: the practice is disclosing information about a patient to a company that has no agreement to protect it.

Where the federal guidance stands

The HHS Office for Civil Rights revised its bulletin on online tracking technologies on March 18, 2024. On June 20, 2024, in American Hospital Association v. Becerra, the US District Court for the Northern District of Texas vacated the portion of the revised bulletin covering what the court called the proscribed combination: technology that connects an individual's IP address with a visit to an unauthenticated public webpage addressing specific health conditions or providers[1]. The ruling did not affect the remainder of the bulletin, and commentators advised continued monitoring of tracking, especially on patient portals that require a login[1].

In practical terms the decision lowered the risk for general public pages, such as a page describing knee pain services that anyone can read. It did not bless tags inside a portal, on intake and appointment forms, or anywhere a visitor has identified themselves as a patient. Those remain the places where a disclosure of protected health information is most likely.

Why authenticated pages matter more each year

Portals carry a growing share of patient traffic. In 2024, 65% of US individuals were offered and accessed their online medical records or patient portal, up from 25% in 2014[4]. Every logged-in page view is, by definition, a patient interacting with their care. A tag left on a portal template can therefore expose far more people than a tag on a blog post.

US individuals offered and accessing their online records or patient portal
US individuals offered and accessing their online records or patient portalComparison. 2014: 25%; 2024: 65%.25%20142014: 25%65%20242024: 65%US individuals offered and accessing their online records or patient portalComparison. 2014: 25%; 2024: 65%.25%20142014: 25%65%20242024: 65%

Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[4]

Show the data
ItemValue
201425%
202465%

HIPAA lets a covered entity share protected health information with a vendor only when it has satisfactory assurances, in a business associate agreement, that the vendor will safeguard it[2]. If an advertising vendor has not signed one with your practice, the safe assumption is simple: its pixel does not go anywhere protected health information could flow.

Enforcement outside HIPAA

The Federal Trade Commission treats sharing health data with advertisers as a consumer protection issue, including for companies that are not HIPAA covered entities. In February 2023 GoodRx agreed to a $1.5 million civil penalty, the first action under the FTC's Health Breach Notification Rule, over disclosures of users' health information to Facebook, Google and other companies[3]. For practices the lesson is that regulators view pixel data as real data about real people, whichever law applies.

Within HIPAA itself, the inflation-adjusted civil money penalties reach a calendar-year cap of $2,190,294 per identical provision in the highest tier[5]. Even a lower-tier finding brings investigation costs, corrective action plans and notification work that dwarf whatever the pixel was worth for marketing.

A page-by-page risk map

A working classification for practice websites. Confirm with counsel for your own site and state law.
Page typeRisk with third-party ad tagsRecommended action
Home, about, careersLowAnalytics acceptable; review what each tag collects
Location and hours pagesLowAnalytics acceptable; avoid ad pixels that build audiences
Condition and service pagesModerate after the 2024 rulingPrefer analytics without ad audience building
Provider bio pagesModerateTreat like service pages
Appointment request and intake formsHighNo ad pixels; no form contents sent to any analytics tool
Patient portal and anything behind loginHighNo third-party tags unless covered by a business associate agreement
Bill payHighNo ad pixels; payment and account data stay with the processor
Form thank-you pagesModerateUse a generic address and title that reveal no specialty or reason

How to audit your site in an afternoon

  1. List every tag

    Open your tag manager and your website builder's integrations, then load key pages with the browser's developer tools open and note every third-party domain that receives a request.

  2. Map what each tag receives

    For each vendor, record whether it sees page addresses, titles, IP addresses, cookies or form contents. Session-replay and chat tools often capture typed text.

  3. Classify your pages

    Use the risk map above. Pay special attention to templates shared by many pages, such as the form layout or the portal frame.

  4. Remove or reconfigure

    Take ad pixels off high-risk pages, turn off automatic form capture, and rename confirmation pages so their addresses and titles are generic.

  5. Fix the vendor paperwork

    Keep only analytics or chat vendors that will sign a business associate agreement for pages where patient information may flow, or move those pages to tools that do.

  6. Document and repeat

    Write down what you changed and why. HIPAA requires policy and compliance documentation to be kept for six years[6]. Re-run the audit after every site redesign or new plug-in.

Chat widgets, forms and session replay

The riskiest tools on many practice sites are not advertising pixels at all. Chat widgets store full conversations, and patients type exactly what you would expect: symptoms, medication names, dates of birth and insurance details. Session-replay and heatmap tools can record keystrokes and form fields so a marketer can watch a visit back. Form builders often keep a copy of every submission on their own servers and may send notification emails that contain the whole message.

Treat each of these as a vendor that may handle protected health information. Ask whether it will sign a business associate agreement, where submissions are stored, how long they are kept and who at the vendor can read them. If the answers are unclear, remove the tool from any page a patient might use to describe their care, and replace free-text boxes with short structured choices where you can.

Who owns this inside the practice

Website tags fall between roles. Marketing adds them, IT or the web vendor installs them, and compliance rarely hears about them. Name one person, usually the privacy officer or practice administrator, who must approve any new script, plug-in or integration before it goes live, and give your web vendor that rule in writing. Add a line to the agency contract stating that no third-party code may be added without written approval, and that the agency will provide a current tag list on request.

  • Keep a one-page register of every tag, its purpose, the pages it runs on and whether a business associate agreement covers it.
  • Review the register when staff, agencies or website platforms change.
  • Ask the front desk to report any patient comment about seeing ads related to their visit, and investigate each one.

Example: a pediatric practice clean-up

Example (fictional): Maple Grove Pediatrics finds seven third-party domains on its site, including a social advertising pixel loaded on every page by the website theme, a session-replay tool its previous agency installed, and a chat widget that records full conversations. The practice removes the ad pixel from forms, the portal link page and the bill pay page, deletes the session-replay tool, and asks the chat vendor for a business associate agreement. The vendor declines, so the practice replaces the chat with a callback request that routes to staff. Marketing reporting now relies on call tracking and generic confirmation-page conversions, and the practice records the audit in its compliance file.

Marketing still works without the risky tags

Removing pixels from sensitive pages does not end measurement. Count calls by source with tracked numbers, count completed requests on generic confirmation pages, and reconcile both against new patients in your scheduling system each month. Search ads still work on intent and location, and social posts still build familiarity without audiences built from patient behavior. The rules for each channel are covered in Google Ads healthcare policies and social media for medical practices.

A useful test for any tag: if a patient saw exactly what this code sends, and to whom, would they be surprised? If the honest answer is yes, the tag does not belong on that page.

Frequently asked questions

Is the Meta pixel allowed on a medical practice website?

On low-risk public pages it is less of a problem after the 2024 ruling, but it should not run on forms, the patient portal, bill pay or any page where a visitor identifies as a patient[1]. Many practices remove it from the whole site to be safe.

Does Google Analytics violate HIPAA?

It depends on what it collects and where. Analytics on public pages that does not capture form contents is lower risk. On pages where protected health information may flow, the vendor would need a business associate agreement[2].

What did the court decide in American Hospital Association v. Becerra?

It vacated the part of the federal bulletin treating an IP address plus a visit to an unauthenticated public health page as protected information. The remainder of the bulletin was unaffected[1].

How often should we audit website tags?

After every redesign, new plug-in or agency change, and at least once a year. Keep the record with your HIPAA documentation for six years[6].

References

  1. Holland & Knight (2024). American Hospital Assn. v. Becerra: Are Tracking Tools OK Again? Court Dials Back OCR Bulletin (opens in a new tab) ↑

  2. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑

  3. Federal Trade Commission (2023). FTC Enforcement Action to Bar GoodRx from Sharing Consumers' Sensitive Health Info for Advertising (opens in a new tab) ↑

  4. Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024 (Data Brief No. 77) (opens in a new tab) ↑

  5. Legal Information Institute, Cornell Law School (current). 45 CFR § 102.3 - Penalty adjustment and table (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo