Facebook Events
Type: SDK · Status: Available · Category: Events and tracking
Required credentials
Section titled “Required credentials”| Field | Required | Where to get it |
|---|---|---|
Clave facebook | Yes | developers.facebook.com/apps, in the app, Settings → Basic. It is the App ID, the identifier of the application on Meta. |
Facebook Client Token | Yes | developers.facebook.com/apps, in the app, Settings → Advanced, Security section, Client Token field. |
Facebook App Name | Yes | developers.facebook.com/apps, in the app, Settings → Basic, Display name field. It is the name of the app as registered on Meta. |
Facebook Events Pixel ID | Yes | business.facebook.com/events_manager, in the Web (pixel) data source associated with the app. It is different from the App ID. |
The step-by-step to find them is in the guide Get the Meta credentials. The Client Token is not the App Secret. They are two different values and only the Client Token needs to be provided.
What it adds
Section titled “What it adds”Facebook Events provides the attribution of installs and conversions to the campaigns that originated them.
Prerequisites
Section titled “Prerequisites”An app registered in Meta for Developers, with access to its management panel, and the credentials in the table above.
Who does what
Section titled “Who does what”Reskyt provides the customer with the information needed to configure the Facebook app. With it, the customer sets up their app in Meta and returns their own data to Reskyt, that is, the key, the app name, the Client Token and the Pixel ID, which Reskyt uses to configure the module.
Impact on the app
Section titled “Impact on the app”Enabling Facebook Events requires rebuilding the app and resubmitting it to the App Store and Google Play.
System permissions
Section titled “System permissions”It requires no system permissions on iOS or Android.
Data and privacy
Section titled “Data and privacy”The privacy data is the same the customer already uses on their website with Meta, so the module does not add a policy different from the one already published.
Timeline and process
Section titled “Timeline and process”The usual timeline is 3 to 5 working days, covering the handover of information between both parties and the review in the stores.
The steps, in order, are:
- Reskyt provides the customer with the information to configure the Facebook app.
- The customer configures their app in Meta and obtains the key, the app name, the Client Token and the Pixel ID.
- The customer provides that data to Reskyt.
- Reskyt configures the module.
- The app is rebuilt and the new version is published in the stores, where it goes through their review.
- It is validated that events reach Meta Analytics.
Validation
Section titled “Validation”Once the new version of the app is published, check that events reach Meta Analytics correctly.