Skip to main content

FB CAPI

CAPI (Conversions API) is server-side sending of events back to the ad platform. When a registration or deposit happens on your side, Qubix sends that event to Facebook's server so that its algorithms optimize ad delivery more accurately. Unlike the browser pixel, server-side sending is more reliable: events are not lost because of blockers and browser restrictions.

Why this is needed

  • The platform receives data about real conversions even when the browser pixel didn't fire.
  • Campaign optimization is driven by actual registrations and deposits — the advertising learns from the right events.
  • Less discrepancy between platform data and the tracker — see Δ Reconcile.

This is not a separate screen

Server-side sending has no page of its own in the admin — it works in the background. You only notice it if something goes wrong.

note

If an event fails to send to the platform, an alert arrives in Telegram — the Conversion send failures role (events: regs and deps that failed to be delivered to Facebook).

Where to see errors

  • Telegram — alerts arrive to subscribers of the Conversion send failures role.
  • Notifications — subscription to this role is enabled in Settings → Notifications.
  • Reminder frequency — to avoid receiving many identical messages during a stream of errors, the «how often to repeat the alert» window is configured in Connections → Telegram: the first message arrives immediately, then a single summary once per the chosen period.

What's next