Facebook Ads in-app event mapping

At a glance: Send your app's rich in-app events from AppsFlyer to Facebook Ads.

Facebook IAE mapping

Advertisers map their in-app events, SDK or Servers-to-servers, to Facebook predefined events. Advertisers can also send Facebook postbacks about each app launch or any known app uninstall.

This enables advertisers to utilize Facebook's advanced optimization capabilities, as well as build Custom and Lookalike Audience segments.

Predefined event mapping

Facebook offers a wide range of events that are already predefined and can be mapped.

Find here the list of rich in-app events that can be sent to Facebook with additional parameters providing extra information about the quality of events.

Learn more about mapping events on Facebook

In-app_event_postbacks_en-us.png

Note that there's no predefined event for sending uninstalls to Facebook Ads. To send uninstalls, use a custom event.

Below is the list of other predefined Facebook events that don't have additional parameters:

Facebook event identifier

Description

Recommended AppsFlyer SDK name

Donate

The donation of funds to your organization or cause.

af_donate

Schedule

The booking of an appointment to visit one of your locations.

af_schedule

SubmitApplication

The submission of an application for a product, service or program you offer, such as a credit card, educational program, or job.

af_submit_application

FindLocation

When a person finds one of your locations via web or app, with an intention to visit. For example, searching for a product and finding it at one of your local stores.

af_find_location 

Contact

A telephone or SMS, email, chat or other type of contact between a customer and your business.

af_contact

CustomizeProduct

The customization of products through a configuration tool or other application your business owns.

af_customize_product

Custom in-app events mapping

AppsFlyer allows you to map any custom in-app event to send to Facebook, by using the CUSTOM Facebook Event Identifier option.

The event name and the event value (including the event parameters) configured in the SDK are forwarded to Facebook, as is, and displayed under its original AppsFlyer SDK event name - not as "custom".

Note that you are able to use these events to optimize your campaigns.

Automatic parameter mapping with the custom event

Through the AppsFlyer deep integration with Facebook, many of the AppsFlyer standard SDK event parameters are automatically mapped to Facebook's predefined parameters. For example, the af_revenue parameter is converted to the _valueToSum parameter in Facebook, which allows you to send a revenue per event that can be measured and optimized in Facebbok.

 Note

Automatic parameter mapping can differ between CUSTOM and predefined events.

For predefined events, af_price is mapped to _valueToSum in some cases (for example, fb_mobile_add_to_cart). In other cases, af_revenue is mapped to _valueToSum (for example, in fb_mobile_purchase).

For events mapped to CUSTOM, af_price is always mapped to fb_price, and af_revenue to _valueToSum.

The following table details all the AppsFlyer event parameters, which when mapped through the CUSTOM event to Facebook, are automatically mapped to Facebook parameters.

AppsFlyer Parameter Facebook Parameter
af_city fb_city
af_class fb_travel_class
af_content_id fb_content_id
af_content_list fb_content_id
af_content_type fb_content_type
af_country fb_country
af_currency fb_currency
af_date_a fb_checkin_date
af_date_b fb_checkout_date
af_departing_arrival_date fb_departing_arrival_date
af_departing_departure_date fb_departing_departure_date
af_description fb_description
af_destination_a fb_origin_airport
af_destination_b fb_destination_airport
af_destination_list fb_destination_ids
af_hotel_score fb_hotel_score
af_level fb_level
af_max_rating_value fb_max_rating_value
af_num_adults fb_num_adults
af_num_children fb_num_children
af_num_infants fb_num_infants
af_order_id fb_order_id
af_payment_info_available fb_payment_info_available
af_preferred_neighborhoods fb_preferred_neighborhoods
af_preferred_num_stops fb_preferred_num_stops
af_preferred_price_range fb_preferred_price_range
af_preferred_star_ratings fb_preferred_star_ratings
af_price fb_price
af_quantity fb_num_items
af_region fb_region
af_registration_method fb_registration_method
af_returning_arrival_date fb_returning_arrival_date
af_returning_departure_date fb_returning_departure_date
af_revenue _valueToSum
af_search_string fb_search_string
af_success fb_success
af_suggested_destinations fb_suggested_destinations
af_suggested_hotels fb_suggested_hotels
af_travel_end fb_travel_end
af_travel_start fb_travel_start
af_user_score fb_user_score

Event and parameter limitations

The following limits apply to events you send to Facebook Ads:

  • The following characters are not allowed:
    • Colon (:)
    • Period (.)
    • Non-Latin (English) character sets: As of January 12, 2020, Facebook rejects Chinese characters. AppsFlyer has not tested other character sets and you should use these only after verifying with Facebook if they support these character sets in postbacks. 
  • Event names are case-sensitive. To avoid discrepancies, make sure you use the correct case in the event names for all media sources and app versions.
  • Maximum number of parameters: 25.
  • Length of event names and parameters: 2–40.
  • Maximum parameter length: 100 characters.
  • Characters permitted: Alphanumeric characters, underscores, hyphens, or spaces. Don't use non-Latin (English) characters. Using non-Latin letters results in inconsistent results.

Considerations regarding in-app event naming:

  • Event names on AppsFlyer can be named the same as Facebook event names (for example, fb_price), however, these should not be sent as CUSTOM events to Facebook.
    To keep on the safe side, refrain from naming events the same as Facebook event names.
  • To perform in-app events postback mapping with Facebook, get events data from all sources, including organic.

 Important!

With the exception of the above parameters, AppsFlyer sends the CUSTOM events data as is to Facebook. It is the responsibility of the app owner to verify the events data is on par with Facebook's requirements.

If the event value contains parameters that are not mapped to valid Facebook parameters (see the table above), these parameters are not sent to Facebook.

Was this article helpful?