Facebook App Events Destination Documentation Facebook Events collects required info from one among Segment’s cellular SDKs (iOS or Android) and sends it from Segment’s servers to Facebook App Events servers. This server-to-server connection is not going to work with our server-aspect libraries. The Facebook App Events Destination is open-source. You possibly can browse the code on GitHub for iOS. This doc was final up to date on October 04, 2018. In the event you discover any gaps, outdated data or just need to leave some feedback to assist us enhance our documentation, please let us know! Use Cases Improve mobile app retention with Facebook Ads Getting Started The first step is to make sure Facebook App Events helps the supply type and connection mode you’ve chosen to implement. You can learn extra about what dictates the connection modes we help here.
From your Segment UI’s Destinations page click on “Add Destination”. Seek for “Facebook App Events” within the Destinations Catalog and affirm the Source you’d prefer to connect to. Drop in your Facebook App ID which might be retrieved out of your Facebook Apps dashboard. Once you activate the Facebook App Events integration in your app’s Segment venture, we’ll begin sending monitor knowledge to Facebook’s App Events endpoints. Screen When you haven’t had an opportunity to review our spec, please have a look to grasp what the Screen method does. An instance name would appear like: Our integration additionally supports using Segment display screen occasions as monitor events. For instance, for those who had a display event named Confirmation you could possibly map the invocation of this to a Facebook app event as you'll with Segment monitor events. To use this functionality you could choose into it via the integration setting named Use Screen Events as Track Events. Once enabled, you should start seeing display occasions populate in Facebook App Events. The display identify you provide might be bookended with the words