Skip to main content
Offline events in Facebook are created separately from the events Invoca’s webhooks generate in the Facebook pixel — the two aren’t the same event.
Applies to: Facebook Conversions API (CAPI), Facebook pixel, offline events

​
Symptoms

For a Facebook (Meta) server-side integration using webhooks, you’ve set up offline events, a pixel, and generated a token. Despite receiving successful response codes for all deliveries in the Invoca webhooks, you’re unable to view the event data you created in Facebook.

​
Cause

Offline events are created separately in Facebook Business Manager, while Invoca’s webhooks generate events within the Facebook pixel itself. Data associated with those webhook-generated events lives in the pixel, identified by the event name specified in the webhook — not in the manually created offline event.

​
Resolution

  1. Determine which Facebook pixel to use for the integration.
  2. Generate an authentication token for that pixel in Facebook, and share the token along with the pixel ID with Invoca.
  3. Invoca sets up a webhook for each data type you want to send (calls or Signals). Each webhook’s POST request includes an event_name parameter, which tells Facebook to automatically create an event with that name under the shared pixel.
You don’t need to manually create the events yourself — they’re generated automatically once the webhook integration is complete.

​
Where to go next

Last modified on September 24, 2026