integration recipe · Make → Meta
Send Make scenario conversions to Meta, server-side.
A Make scenario conversion happens off your page, where no pixel fires. Point Make at a TracerKit webhook and it reaches Meta's Conversions API with the visitor's click ids and hashed email — no code, and verified end to end.
Free sweep — see your server-side readiness before you connect anything. Or start free →
Raw email and phone are hashed before anything is stored. IP and user agent ride only the delivery, never the event log.
set it up
Three steps. No deploy.
Create the webhook in TracerKit
On your site's page in the dashboard, add a conversion webhook with the Generic JSON preset. You get a URL once — it's the only credential, and only its hash is stored.
Paste it into Make
Add an HTTP → Make a request module at the end of your scenario. Set the method to POST, the URL to your TracerKit webhook, and the body to JSON with email, value, currency, eventName and eventId mapped from the trigger module.
Connect Meta with server-side forwarding on
Add Meta as a destination with a Conversions API access token from Events Manager, plus your ad account and pixel ids, and turn on server-side forwarding. From the next conversion onward, every conversion is enqueued to Meta's Conversions API.
join the visitor
If the trigger app carries the visitor's TracerKit id (from a hidden form field or a CRM property), map it to anonymousId to join the visitor's click ids directly; otherwise TracerKit matches by hashed email.
Sites that enforce per-field consent skip this join: the conversion then carries only what Make sent, with no click ids from the visit.
sign the webhook
Add any shared secret of 16+ characters to the hook and send an X-TracerKit-Signature header of t=<unix seconds>,v1=<hex HMAC-SHA256 of "<t>.<raw body>">. Make's built-in sha256() function returns an HMAC when you pass the secret as its key. Until a secret is set, the unguessable URL is the only credential.
why server-side
Meta can only optimise on what it receives.
It arrives even when the pixel didn't fire.
The conversion comes from Make's servers, so blockers, ITP and a visitor who closed the tab before the thank-you page loaded don't lose it.
It matches to a real visit.
Meta scores each event on match quality: hashed email and phone plus the fbc click id and fbp browser id from the landing hit lift it from anonymous to attributable.
It's counted once.
The server event carries the same event id as the browser pixel fire, so Meta counts one conversion, not two.
You can prove it happened.
Most tools stop at "sent". TracerKit records each delivery's outcome and reconciles what it observed against what Meta reports, so a silent break shows up as drift, not as a bad quarter.
questions
Asked and answered.
Do I need a developer?+
No. Creating the webhook and pasting the URL into Make is the whole install. Threading the visitor id through is one optional line if you want direct click-id matching instead of email matching.
What does the Make webhook send?+
Email, phone, value and currency mapped in your scenario (PII hashed before it's stored); an eventId of your choosing as the idempotency key; an anonymousId if the scenario has the visitor's TracerKit id. TracerKit adds the click ids it captured when the visitor landed before forwarding to Meta.
How does Meta match the conversion to an ad click?+
Meta scores each event on match quality: hashed email and phone plus the fbc click id and fbp browser id from the landing hit lift it from anonymous to attributable.
Will this double count against my Meta pixel?+
The server event carries the same event id as the browser pixel fire, so Meta counts one conversion, not two.
What if the visitor blocked the pixel?+
That's the point of server-side. The Make conversion arrives from Make's servers, not the visitor's browser, so ad blockers and ITP never see it. TracerKit matches it back to the visitor's landing visit by the hashed email or the visitor id you threaded through.
How do I know it's working?+
Each webhook shows when it last received a delivery, every forwarded event shows its delivery status per destination, and reconciliation compares what TracerKit observed against what Meta reports — so drift is a number you see, not a hunch.
What does it cost?+
Server-side forwarding is on the Server-side tier at a flat monthly price per site. There is no per-conversion metering, so a busy checkout day never becomes a surprise bill.
Related recipes
Make to other platforms
other tools to Meta
Every Make scenario conversion, in the light.
Tag management is free forever. Server-side forwarding starts with a 14-day trial — no card, no per-conversion metering.