At a glance: Send your app's rich in-app events from AppsFlyer to Meta ads.
Meta in-app events mapping
This enables advertisers to utilize Meta's advanced optimization capabilities, as well as build Custom and Lookalike Audience segments.
Predefined event mapping
Meta ads 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 Meta with additional parameters providing extra information about the quality of events.
Learn more about mapping events on Meta.
Note that there's no predefined event for sending uninstalls to Meta ads. To send uninstalls, use a custom event.
Below is the list of other predefined Meta events that don't have additional parameters:
|Meta event identifier||
Recommended AppsFlyer SDK name
The donation of funds to your organization or cause.
The booking of an appointment to visit one of your locations.
The submission of an application for a product, service or program you offer, such as a credit card, educational program, or job.
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.
A telephone or SMS, email, chat or other type of contact between a customer and your business.
The customization of products through a configuration tool or other application your business owns.
Custom in-app events mapping
AppsFlyer allows you to map any custom in-app event to send to Meta, by using the CUSTOM Meta Event Identifier option.
The event name and the event value (including the event parameters) configured in the SDK are forwarded to Meta, 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 Meta, many of the AppsFlyer standard SDK event parameters are automatically mapped to Meta's predefined parameters. For example, the af_revenue parameter is converted to the _valueToSum parameter in Meta, which allows you to send a revenue per event that can be measured and optimized in Meta.
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
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 Meta, are automatically mapped to Meta parameters.
|AppsFlyer Parameter||Meta Parameter|
Event and parameter limitations
The following limits apply to events you send to Meta ads:
- The following characters are not allowed:
- Colon (:)
- Period (.)
- Non-Latin (English) character sets: As of January 12, 2020, Meta rejects Chinese characters. AppsFlyer has not tested other character sets and you should use these only after verifying with Meta 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 Meta event names (for example, fb_price), however, these should not be sent as CUSTOM events to Meta.
To keep on the safe side, refrain from naming events the same as Meta event names.
- To perform in-app events postback mapping with Meta, get events data from all sources, including organic.
With the exception of the above parameters, AppsFlyer sends the CUSTOM events data as is to Meta. It is the responsibility of the app owner to verify the event data is according to Meta requirements, using valid Meta parameters (see the table above). Otherwise, these parameters aren't sent to Meta.