AppsFlyer Integration For Partners

UNDERSTANDING THE BASICS

AppsFlyer Integration For Partners

This guide will walk you through the step-by-step process for setting up your mobile tracking with AppsFlyer as a partner account.

Overview

This article is intended for Everflow clients that want to:

Work with AppsFlyer for the first time

Migrate an advertiser to AppsFlyer

AppsFlyer is a Mobile Measurement Partner (MMP). Apps use an MMP for their internal attribution data around installs and in-app events, which can then be passed to Everflow through Postbacks.

Integrating with AppsFlyer

To initiate a new integration:

Your Advertiser must follow the steps outlined in AppsFlyer's Helpdesk and invite you to integrate with AppsFlyer.

To update an existing integration:

If you need to make an update to an existing integration, then send an email request to integrations@appsflyer.com. Most requests are completed within 2 business days.

Creating Your Offer's Default Landing Page Using an AppsFlyer Attribution Link

You will need the AppID, your AppsFlyer PID, and the cost model (CPI / CPA / etc.) from the AppsFlyer attribution link. You can then modify the URL below with those parameters, replacing the [ ] sections, and you'll properly pass all of the required AppsFlyer parameters.

AppsFlyer App ID:
- Example (Android): com.greatapp
- Example (iOS): id1297
AppsFlyer Publisher ID
- Example: chartboost_int
For campaign cost models other than CPI, please update value paired with the &af_cost_model= parameter to the appropriate model.
- Example: CPA or CPC‍
If you are an existing AppsFlyer partner and currently migrating to Everflow from a different platform, make sure to add &af_additional_postback=1 to your attribution links.

For the complete list of AppsFlyer parameters, click here.

Integrating your Install and In-App Event Postbacks

See below for an explanation of how to format install and in-app event postbacks for the Everflow platform.

You must send AppsFlyer your custom Everflow domain in place of YOUR_DOMAIN in the below URL

NID is the Network ID provided by Everflow

Global Install Postback

https://www.YOUR_DOMAIN.com/?nid=[EVERFLOW_NETWORK_ID]&transaction_id=$$click(clickid)

Setting up Events with AppsFlyer

If you're trying to troubleshoot an issue with receiving AppsFlyer events - [Click Here]

Global In-App Event Postback

https://www.YOUR_DOMAIN.com/?adv_event_id=$$sdk(mapped-iae)&nid=[EVERFLOW_NETWORK_ID]&transaction_id=$$click(clickid)

adv_event_id: The unique ID generated by Everflow for each Advertiser Event.

In the Event Postback above, it will automatically return the Event Tag from the AppsFlyer dashboard under adv_event_id. The AppsFlyer events are the actual in-app event names from the app.

Advanced additions for AppsFlyer attribution links

&af_additionalpostback=1 Used when you want to place more than than one Postback URL in AppsFlyer and have all of them fired on every Transaction ID

&af_installpostback=false Used when you only want to receive Postbacks for the AppsFlyer Events, and not receive Postback from the install action

Useful things to add to your Everflow postback URLS placed on AppsFlyer

&fraud_flag={Rejected_Value} Whenever AppsFlyer considers a conversion fraudulent it will reject the conversion, and return &fraud_flag=1 or higher numbers. Everflow will automatically reject any received conversions with a fraud_flag of 1 or higher. Fraud_flag=0 means that the conversion wasn't rejected as fraudulent.

&fraud_reason={Rejected_Reason} This will display the reason that AppsFlyer rejected the conversion.

mapped-iae is the global event macro on AppsFlyer.

AppsFlyer Event Troubleshooting

There are four parts to confirming whether an AppsFlyer integration is setup correctly.

Event Creation - Events can be created at the offer level within the Payout & Revenue tab or at the advertiser level within the Events tab of an Advertiser.
Offer-level events are used in this example:

Default Landing Page- Below is a breakdown of the most commonly used parameters within AppsFlyer links and their corresponding Everflow macros. The goalid parameters are required in order to track events.

https://app.appsflyer.com/id1297?af_siteid={affiliate_id}&af_sub_siteid={sub2}&pid=everflow_int&clickid={transaction_id}

AppsFlyer Parameter

Everflow Macro/Variable

Definition

af_site_id

{affiliate_id}

ID of an affiliate on the network

af_sub_siteid

{sub2}

Sub ID 2 in the affiliate tracking URL

pid

Partner ID from AppsFlyer

clickid

{transaction_id}

Unique ID associated with the transaction

af_c_id

{offer_id}

ID of specific Offer from Everflow

AppsFlyer's In-App Event Postback - If you do not have access to this screen, please confirm via screenshot how it's set up from your client. The Partner Event Identifier will correspond with the adv_event_id that is tied to the event inside Everflow.

Everflow's Postback - This is how you can setup a global postback within AppsFlyer. You will have to choose between always using advertiser level or offer level events, or have two global postbacks placed.

Advertiser Level Events

https://www.everflowtest.com/?nid=215&transaction_id=$$click(clickid)&adv_event_id=$$sdk(mapped-iae)

Everflow Parameter

AppsFlyer Macro

Definition

nid

Network ID provided by Everflow

transaction_id

$$click(clickid)

Unique ID associated with the transaction

adv_event_id

$$sdk(mapped-iae)

Advertiser Event ID (from Everflow) associated with the conversion

oid

$$sdk(af_c_id)

Offer ID (from Everflow) associated with the conversion

affid

$$sdk(af_siteid)

Affiliate ID (from Everflow) associated with the conversion

If you are using Offer level events instead of Advertiser Events replace adv_event_id with event_id.

Advanced Privacy

The Advanced Privacy postback mechanism described here works when all of the following are true:

The user device is running iOS 14.5+ (General Availability)
Apple has begun enforcing ATT (App Tracking Transparancy)
The advanced Privacy setting is turned on in AppsFlyer

In Everflow the following must be confirmed in order to track the Advance Privacy Postback:

"Enable Click To Conversion Time" is Disabled on the Attribution card of the Offer. ‍
The Advance Privacy Postback is clickless, which means it relies on "affid" and "oid" to attribute the conversion correctly. These values must be in the Base Destination URL as well as the Advertiser Postback.

Using AppsFlyer's self serve Postback Management feature: