FMP Integration

 

Install Postbacks

Upon conversion, AppsFlyer can return the following parameters:

Parameter Name Parameter Name Convention

Facebook Campaign Name

{campaign_name}

Facebook Campaign ID

{campaign_id}

Facebook Ad Set Name

{adset_name}

Facebook Ad Set ID

{adset_id}

Facebook Ad Group Name

{adgroup_name}

Facebook 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}

Facebook channel (Instagram, Facebook Audience Network, Facebook Ads, Messenger)

{af_channel}

Geo

{user_country}

 Example

http://FMP_postbackURL.........&FMP_ADGroup_name ={adgroup_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 FMP 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.32pm and 42 seconds, we can pass 5pm 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 Facebook. Same random ID can be passed downstream for In-app events postbacks.

 Note

 Based on Facebook terms sending post backs is available only for companies who obtain the following badges: Ad Technology

 Example

Click HERE to see the full list 

Was this article helpful?
0 out of 0 found this helpful