Skip to content
Pixel Relay

Keeping health details out of Meta

How a health business can keep measuring Meta ads while sending Meta less sensitive information.

1 min read Updated 8 Oct 2026

A tracking pixel sends Meta the address of every page a visitor opens, plus whatever the site attaches. On a health site, the address alone can say what someone is being treated for. Pixel Relay sits between your site and Meta so you decide what leaves.

What changes with Pixel Relay

With Meta's pixel alone With Pixel Relay
The browser sends events straight to Meta Your site sends events to the relay; the relay sends a cleaned copy to Meta
Full addresses, including query strings Query strings always dropped, sensitive words replaced with page
Your domain in every event Your domain, or the relay's when masking is on
Visitor IP always seen by Meta Visitor IP sent only if you switch it on
Event names as your site sends them Mapped to standard events; anything unmapped becomes a meaningless code
Form fields only as safe as the site's code Only listed fields kept; emails, phones and names hashed

Good practice that goes with it

  • Name pages neutrally where you can. /services/consultation is better than /ivf-consultation, even with blocked terms.
  • Send conversions, not content. A booking is a Schedule event with a value. What was booked does not belong in the event.
  • Review your blocked terms against your own page addresses, and check the Pages tab in analytics to see what Meta received.
  • Remove other trackers that send the same information, including any Meta Pixel installed separately.
  • Decide on IP forwarding with your risk analysis. Turning it off sends Meta less and can lower match rates.

Not legal advice

Pixel Relay reduces what Meta receives. Whether that meets your obligations, such as HIPAA in the US or UK GDPR, depends on your business. Check with your compliance team.