Customers are unable to view the event data they have created in Facebook.

[InvocaKnowledge]

Symptoms

For Facebook(Meta) Server-side integration with webhooks, customers set up the offline events, and the pixel and generated the token. Despite receiving successful response codes for all deliveries in the Invoca webhooks, customers are unable to view the event data they have created in Facebook.

Resolution

The integration steps for Facebook (Meta) server-side integration with webhooks are as follows:

1. Customers should determine the specific Facebook pixel they intend to use for the integration.
2. Customers need to generate an authentication token for that particular pixel within the Facebook platform. The generated token, along with the pixel ID, should be shared with Invoca.
3. Invoca will handle the setup of webhooks for each type of data that customers wish to receive, such as calls or signals. In the POST request body sent by Invoca, an event_name parameter will be included. This parameter allows Facebook to automatically create an event with the specified name under the shared pixel.

It's important to note that customers do not need to manually create the events themselves. The events will be automatically generated once the webhook transition is successfully completed.

Cause

Offline events are created separately in Facebook Business Manager, while the Invoca webhooks are responsible for generating events within the Facebook pixel. The data associated with these events will be located within the pixel, identified by the event name specified within the webhook.

Offline event created by customer - no data flowing in. 

A pixel and its event - data flowing in. The event (event A) is created by the Invoca webhook.

Webhook request body - POST request. event name is set - the event will be created with this name under the pixel.