At a glance: Learn what data types Meta campaign management partners can receive from AppsFlyer.
Install postbacks
Upon conversion, AppsFlyer can return the following parameters:
| Parameter Name | Parameter Name Convention |
|---|---|
|
Campaign Name |
{campaign_name} |
|
Campaign ID |
{campaign_id} |
|
Ad Set Name |
{adset_name} |
|
Ad Set ID |
{adset_id} |
|
Ad Group Name |
{adgroup_name} |
|
Ad Group ID |
{adgroup_id} |
|
Event time – Rounded up |
{timestamp} |
|
Unique AppsFlyer User ID |
{sha1-appsflyer-device-id} |
|
Device ID Hashed MD5 |
{md5IDFA\md4GAID} |
|
If the attribution was from a view |
{is-impression} |
| Channel (Instagram, Meta Audience Network, Facebook, Messenger) |
{af_channel} |
| Geo |
{user_country} |
Example
http://mcmp_postbackURL.........&mcmp_ADset_name ={adset_name}
In-app event postbacks
Upon In-app events, AppsFlyer can return the following parameters (in addition to the above):
| Parameter Name | Parameter Name Convention |
|---|---|
|
Event Name* |
{event_name} |
|
Event Value |
{event_value} |
Example
http://FMP_postbackURL.........&eventname={event_name}
* The Meta campaign management partner can choose to receive the in-app event name as the advertiser configured it in AppsFlyer's SDK or to have the advertiser fill in a free text field per event.
User-level data policy
- AppsFlyer cannot pass IDFA or Android/Advertising ID.
- AppsFlyer passes rounded-up installs/events timestamps to the closest hour.
For example: If an install happened at 4.32 pm and 42 seconds, we can pass 5 pm as the timestamp
- AppsFlyer can use a Random ID of its own creation to attach to events that ID shouldn’t be derived from the IDFA/Android ID and should be unique to Meta ads. The same random ID can be passed downstream for In-app event postbacks.
Note
Based on Meta terms sending postbacks is available only for companies obtaining the following badges: Ad Technology
