Is Pixel Relay right for you?
Who gets the most from Pixel Relay, what it replaces, and when you may not need it.
Pixel Relay suits you if you advertise on Meta and any of these is true.
Your page addresses say too much
Addresses like /ivf-consultation, /therapy/anxiety or /book?treatment=implants tell Meta what a visitor is interested in. Meta's own pixel sends them as they are. Pixel Relay drops query strings and replaces sensitive words before Meta sees an event. See What the relay removes.
Meta has restricted your ads or your data
Meta limits businesses it files under health and wellness. Pixel Relay's domain masking and clean addresses keep sensitive details out of the events you send.
You lose conversions to ad blockers and browsers
The Conversions API runs server to server, so browser tracking limits and most blockers do not stop conversions reaching Meta.
You manage several sites or clients
Each website has its own pixel, token, domains, mappings, blocked terms and analytics, and each client gets a login that only shows their sites, with the permissions you choose.
When you may not need it
- Your site has nothing sensitive in its addresses or events, and Meta's own Conversions API integration in your platform (for example a Shopify app) already does what you need.
- You do not advertise on Meta. Pixel Relay only sends to Meta.
Getting started
Send a request from Request access. Once your account is set up, the setup checklist takes about fifteen minutes per site.
Related articles
Still stuck?
Tell us what you are trying to do and we will help you set it up.