Event Postbacks to Facebook

If you acquire users from app-install campaigns on Facebook, you can designate specific in-app conversion events to post back to Facebook.When a user you acquired from Facebook completes one of the in-app events you designate, Localytics uses an API call to send the information back to Facebook. Use this data to work with your Facebook account manager to measure and improve the performance of your Facebook campaigns or to create audiences in the Facebook Ads Manager.

Event postbacks to Facebook are available for iOS and Android apps.

For Android apps, Localytics passes GAID to Facebook as a device identifier. If your Android app is not sending GAIDs to Localytics, Facebook will accept event postbacks but may not always correctly attribute your postbacks to the appropriate end user.

Please select only important conversion events for your app to postback to Facebook. Do not postback all in-app events to Facebook, as doing so will dilute the significance of event postbacks as indicators of end user value. Consider designating events for postback that indicate

monetization, such as user completed an in-app purchase
end user engagement, such as end user completed completed my app's tutorial
end user community contribution, such as end user rated an item in my app

Per Facebook's specifications, each in-app event that you choose to post back to Facebook must be categorized into one of fourteen Facebook event names. The descriptions of each event in the table below are based on our experience and industry best practices, and are intended to help you determine which Facebook event name to select.

Facebook maintains more detailed documentation on their event names. If you're not sure which Facebook event name to choose for your postback, contact your Facebook account manager.

You can map multiple in-app events to the same Facebook event name. For example, two in-app events named PurchaseOneMonthSubscription and PurchaseOneYearSubscription could both be mapped to the fb_mobile_purchase event name. However, keep in mind that Facebook doesn't actually receive your app’s event names, so completion of either of these events would appear identical in the Facebook Ad Manager.

Facebook event name	Description
fb_mobile_level_achieved	End user completed a level in your app.
fb_mobile_activate_app	Not available. Used by Localytics to indicate that an end user has installed and run your app. This event name cannot be manually configured in the Localytics Dashboard.
fb_mobile_add_payment_info	End user added their payment information in your app.
fb_mobile_add_to_cart	End user added an item to their shopping cart in your app.
fb_mobile_add_to_wishlist	End user added an item to their wishlist in your app.
fb_mobile_complete_registration	End user completed user registration in your app.
fb_mobile_tutorial_completion	End user completed your app’s tutorial feature.
fb_mobile_initiated_checkout	End user started the checkout process in your app.
fb_mobile_purchase	End user completed a purchase in your app.
fb_mobile_rate	End user rated an item in your app.
fb_mobile_search	End user performed a search in your app.
fb_mobile_spent_credits	End user spent in-app credits in your app.
fb_mobile_achievement_unlocked	End user unlocked an achievement in your app.
fb_mobile_content_view	End user viewed content or an item in your app.

Navigate to Attribution Settings.
Click Add postback event to add a postback event.
Select your app event.
BoughtSomeShoes
Select the Facebook event name that best corresponds to your event.

fb_mobile_purchase

The information is automatically saved.