Most ophthalmology practices running Facebook ads are using some version of the Meta Pixel to measure conversions — and many are doing it in a way that creates real HIPAA exposure without realizing it. The risk isn’t the existence of the pixel itself. It’s what gets sent to it.

A standard pixel implementation fires events based on page visits and form submissions. On a typical ophthalmology site, those events can end up associated with pages like “cataract-surgery-consultation” or “glaucoma-treatment-request” — which, combined with the visitor’s identity, starts to look a lot like protected health information being transmitted to a third-party ad platform without a signed Business Associate Agreement in place. That’s the core of the compliance problem, and it’s more common than most practices realize.

This isn’t a reason to stop tracking conversions — it’s a reason to track them differently. Server-side conversion tracking, rather than browser-based pixel events, gives you a layer of control over exactly what data gets passed along, and lets you strip out anything that could be tied to a specific health condition before it ever reaches the ad platform. Building retargeting audiences off general visit behavior — rather than off which specific procedure page someone viewed — accomplishes a similar goal from a different angle.

The practical fix usually involves three things: moving to server-side tracking through a properly configured conversions API, auditing exactly what data each tracked event includes before it fires, and working with whoever manages your ad account to confirm there’s no condition-specific data leaking into audience names, event labels, or custom conversions.

None of this requires giving up the ability to measure what’s working. It requires being deliberate about the difference between tracking that a conversion happened and tracking which medical condition prompted it — and most practices, once they look closely, find they’ve been doing more of the second than they intended.