Meta Conversions API, done properly
When the pixel misses a sale, Meta optimises blind. FunnelTrace sends the events from the server too, so Meta sees the buyers you actually got.
How it works
Your pixel and FunnelTrace send the same events with the same IDs, and Meta keeps one of each.
Deduplicated
Browser and server share one event ID per purchase, so a sale is never counted twice.
In line with consent
With marketing consent, Meta gets the click ID. Without it, only hashed contact details go.
Offline sales reach Meta
A bank transfer or UPI payment you record is sent as a Purchase, with the right product and value.
A status for every payment
Each payment shows whether it went to Meta, and if not, the reason or Meta's own error.
Common questions
Do I still need the Meta pixel?
Yes, keep it. The browser and the server send the same event with the same ID, and Meta keeps one. The server copy fills the gaps when a browser blocks the pixel.
What does Meta receive about a buyer?
Hashed contact details, plus the click ID when the person agreed to marketing cookies. Without that consent, only the hashed contact goes.
Can I see why an event wasn't sent?
Yes. Each payment shows its Meta status: sent, skipped with the reason, or failed with Meta's message.
Goes well with
Attribution
First and last touch on every lead, so each sale is credited to the ad that started it.
Read about AttributionPayments
Razorpay checkout, UPI, bank transfer, payment links and offline sales.
Read about PaymentsIntegrations
Signed webhooks, n8n, Zapier, Google Sheets, and WhatsApp and email tools.
Read about Integrations
Let Meta see your real buyers
The pilot is by invitation, with early-bird pricing for the first coaches. Tell us about your brand and we'll set up a call.