Appsflyer Integration : Helpdesk

Appsflyer Integration


This article is intended for Networks who are would either like to implement for the first time or migrate to their AppsFlyer advertiser's to Everflow. 

AppsFlyer is able to send attribution data to Everflow for both installs and in-app events.

Click here to read about troubleshooting.

Initiating the Integration

For new clients to AppsFlyer, complete the Partner Registration Information Form.

Once you have submitted the above registration form, you will need to send the following information to

1.  Your company name and transparent logo

2.  The recommended Everflow tracking link template, replaced with your desired partner id (pid) value and any additional values you wish to add:

Tracking URL Template{transaction_id}&af_siteid={affiliate_id}

3.  Your Everflow Network ID (nid) and postback domain for install and in-app event postbacks configurations:


If you currently have an intergration with AppsFlyer, contact including your new Everflow postback and tracking link template.

Creating your Tracking Link In AppsFlyer

The tracking link consists of the below AppsFlyer base tracking link and additional macros added by the ad-network.

See below AppsFlyer’s base tracking link with a detailed explanation per macro:

AppsFlyer Base URLDescription
AppsFlyer end point
Application unique ID – dynamic value changed per app promoted
Media source name concatenated with  _int to identify integrated networks
Campaign name

Set out below is an example of a complete tracking link once you have added the additional Everflow macros:{transaction_id}&af_siteid={affiliate_id}


  • For campaign cost models other than “CPI”, please update the &af_cost_model=parameter to the appropriate model (e.g. CPA/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 tracking links.

For AppsFlyer’s complete list of parameters click here

For Everflow’s complete list of macros 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 “” in the below postbacks

Global Install Postback[everflow_network_placeholder]&transaction_

NID is the Network ID provided by Everflow.

Global In-App Event Postback$$sdk(mapped-iae)&nid=


The unique in-app event ID generated by Everflow for each offer event.

event_id= Set as Event Tag in the AppsFlyer dashboard for each app by the advertiser

This is the actual in-app event name from the application.

For details of Dynamic Event Mapping for In-App Events, click here

Extra useful things to add to Appsflyer tracking links

&af_additionalpostback=1This allows you the ability to place more than one postback url in Appsflyer and fire them at the same time for every click ID
&af_installpostback=falseThis allows you to only postback conversions for the event and not postback conversions for the install to Everflow at all

Extra useful things to add to your Everflow postback urls placed on Appsflyer

&fraud_flag={Rejected_Value}This will indicate if Appsflyer considers the conversion fraud, and will set it to rejected. We will reject if the fraud flag value is not 0
&fraud_reason={Rejected_Reason}   This will display the reason that Appsflyer rejected the conversion. 

In order to setup events in Everflow, please see this article here

"mapped-iae" is the global event macro on Appsflyer

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.