Meta Conversions API relay
Conversions that reach Meta. Details that don't.
Pixel Relay sends your site's events to the Meta Conversions API from the server. Before anything leaves, it drops query strings, replaces health terms, hashes personal details and holds back the visitor IP. Your ads get the signal, Meta gets less of your visitors' data.
The problem
The browser pixel misses events, and leaks the ones it catches
Events go missing
Ad blockers, browser tracking protection and cookie limits stop a share of pixel events from ever firing. Meta optimises your campaigns on the conversions it can see.
URLs say too much
A page path like /ivf-consult or a query string with an email address goes to Meta with every event the browser pixel sends.
Every client is a separate setup
Agencies end up with a pixel, a token and a different tag configuration for every client site, and no single place to see what's being sent.
How it works
Your site, then Pixel Relay, then Meta
-
Received from your site
clinic.example/ivf-consult?email=jane@…
ip 81.2.69.160
-
Sanitised by Pixel Relay
clinic.example/page-consult
em: 3f1c…a9e2 (SHA-256)
-
Delivered to Meta Conversions API
Lead event accepted
-
01
Add the script
Each site gets its own embed code. Paste it into the site once and events start flowing to Pixel Relay.
-
02
Map your events
Choose which site events become which Meta events, per site, without touching the site again.
-
03
Clean every event
Query strings go, health terms and your own blocked words are replaced, personal fields are hashed, the IP stays back unless you allow it.
-
04
Deliver and check
Events are sent to the Meta Conversions API from the server. Use Meta test event codes to confirm delivery, then watch the numbers in analytics.
Features
What's in the box
Server-side delivery
Events go from our server to the Meta Conversions API, so browser blockers can't drop them.
URL and content sanitising
Query strings removed, health terms replaced in page paths and content fields, plus your own blocked terms per site.
Hashed personal data
Email, phone, first and last name and external IDs are SHA-256 hashed in the format Meta expects.
IP and domain controls
Visitor IPs are only forwarded when you enable it, and the source domain can be masked behind the relay.
Event mappings
Turn your site's own event names into Meta standard events, per site.
Multi-client dashboard
Clients, sites, Pixel IDs and access tokens in one place, with tokens encrypted at rest.
Analytics per site
Daily event counts per client and per domain, so you can see what was sent and when.
Safety rails
Allowed domains and a per-site rate limit, so only your sites can send events.
Short links
Trackable short URLs with click counts, for campaigns and bios.
For agencies
Every client's Meta tracking in one dashboard
Set up each client once with their Pixel ID and token, give each site its script, and manage mappings, blocked terms and analytics without logging into ten different tag managers. Staff accounts have roles and two-factor sign-in.
For privacy-sensitive sites
Run Meta ads without sending page-level detail
Clinics, health services and anyone whose URLs can reveal something personal. Health terms and query strings are stripped before Meta sees the event. It reduces what's shared; your compliance decisions are still your own.
FAQ
Common questions
What does Pixel Relay actually do? +
Your site loads a small tracking script that sends events (page views, leads, purchases) to Pixel Relay instead of straight to Meta. Pixel Relay cleans each event, hashes any personal details the way Meta requires, and delivers it to the Meta Conversions API from the server.
Do I still need the Meta Pixel? +
No. Pixel Relay sends events server to server through the Conversions API, so the browser never talks to Meta directly. That also means ad blockers and browser tracking limits don't stop the events reaching Meta.
What gets removed before Meta sees an event? +
Query strings are dropped from URLs, health related words in page paths and content fields are replaced with a neutral word, and you can add your own blocked terms per site. Email, phone and name fields are SHA-256 hashed before sending. The visitor IP is only forwarded if you switch that on for a site, and the source domain can be masked.
Is it built for healthcare sites? +
It was built for sites where page URLs can reveal sensitive information, such as clinics and health services. The sanitising reduces what Meta receives; it isn't legal advice, so check your own obligations with your compliance team.
Can I manage several clients? +
Yes. Pixel Relay is multi-client: each client has its own sites, Meta Pixel ID and access token, event mappings, blocked terms and analytics. Staff accounts have roles and two-factor authentication.
How do I get access? +
Accounts are set up by our team rather than self sign-up. Send us a request from the Request access page and we'll get you connected.
Send Meta the conversions, keep the details
Accounts are set up by our team. Tell us about your sites and we'll get you connected.