Conversions API

Meta Conversions API
Server-side, in 15 minutes.

Recover 30-40% of Facebook and Instagram ad events lost to iOS 14.5, ad-blockers, and Safari ITP.

QbiTrack sends purchases, leads, and custom conversions directly from your server to Meta — dedup'd against the Pixel via event_id, hashed PII (em, ph, fbc, fbp), and Advanced Matching auto-applied. No Cloud Run, no Python scripts.

Why server-side for Meta Conversions API

Deduplication out of the box

event_id + event_name pair stops Meta counting Pixel + CAPI events twice.

Event Match Quality 8.5+

Automatic fbc / fbp / IP / UA / hashed PII attached — no manual mapping.

Offline events

Upload CRM-closed deals via API — CAC attribution even when purchase happens off-site.

Events tracked out of the box

Standard Meta Conversions API events mapped automatically. Custom events supported via the same endpoint.

PurchaseInitiateCheckoutAddToCartLeadCompleteRegistrationViewContentSearchSubscribe

Setup — 4 steps

Average time to live: under 15 minutes.

1
Paste your Meta Pixel ID + CAPI access token
Grab both from Events Manager > Data Sources. QbiTrack encrypts the token with AES-256.
2
Install the Meta Pixel GTM template
Fires client-side Pixel + mirrors event to QbiTrack container with matching event_id.
3
Turn on Advanced Matching
QbiTrack hashes em, ph, fn, ln, zp, ct, st, country before sending — SHA-256 as Meta requires.
4
Verify in Events Manager
Diagnostics tab shows 'Server' source with EMQ score. Our average: 8.5/10.

Send a Purchase from your backend

javascript

fetch("https://track.yourdomain.com/capi/meta", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    event_name: "Purchase",
    event_id: orderId,
    event_time: Math.floor(Date.now() / 1000),
    user_data: { em: hashedEmail, ph: hashedPhone, fbc, fbp },
    custom_data: { currency: "USD", value: 129.99, content_ids: [sku] },
  }),
});