In this article, we are going to explain how the attribution link template and the postback URLs should look like for Appsflyer.

To initiate this integration you need to send the following:

Appsflyer attribution link contains the minimum information to record the click and redirect the user to download the app. Additional parameters must be added to the link after the “?” character, to record extra information and get back the information via the postback link. This is how the base attribution link looks like,

http://app.appsflyer.com/{app_id}?pid={media_source}&c={Campaign Name}

The base attribution link includes the {app_id}, which is the Application ID for Apple iTunes/App Store app, or the package name for Google Play, as well as the “pid” (media source). This is the minimum requirement for an attribution link. “C” aka the campaign name is either decided by the advertiser or you can put the offer name/Id macro “{offer.name}”

See below what the complete attribution link should look like after you have added additional Swaarm macros:

https://app.appsflyer.com/com.testapp?pid=Media_int&af_enc_data={offer.weGet}&af_ip={user.ip}&af_lang={user.language}&af_ua={user.encoded_ua}&af_siteid={publisher.id}&af_sub_siteid={publisher.subId}&c={offer.name}&af_c_id={offerId}&af_ad={publisher.creative}&af_adset={pea.chain}&clickid={id}&advertising_id={device.ids.gaid}&idfa={device.ids.idfa}

Or you can also use the capture below as a template to set the Attribution link on the AppsFlyer platform.

For the full list of Macros supported by Swaarm, click here

You can find the additional Attribution link parameters supported by Appsflyer,

here.

Appsflyer has the ability to fire the install through the global postback and any other post-install events through an additional event postback.

This is how the Default postback should look like after adding the Appsfyler-supported macros,

Install postback for iOS & Android:

https://track.yournetwork.swaarm-clients.com/postback?publisher_id={Site ID}&rejection_reason={Blocked reason}&rejected_reason_value={Blocked reason value}&country={Country code}&os_name={Platform}&publisher_sub_id={Sub site ID}&click_id={Click ID}

In-App event postback for both OS:

https://track.yournetwork.swaarm-clients.com/postback?publisher_id={Site ID}&rejection_reason={Blocked reason}&rejected_reason_value={Blocked reason value}&country={Country code}&os_name={Platform}&publisher_sub_id={Sub site ID}&click_id={Click ID}&event_id={Event name}&sale_amount={Event revenue USD}

Alternatively, you can also use the capture below as a template to set the Default postback on the AppsFlyer platform

To track the In-App event in the Swaarm system you need to insert the AppsFlyer Event in the Adv. EventType ID in the events section on the offer details page.

Do note: Adv. EventType ID should be an exact match with the AppsFlyer Event

These are suggested templates that you can use, but you can add or delete some parameters that are macros based on your company's requirements.

Once you are done with template creation, you can either configure it yourself or share them with the Appsflyer team, they will do the necessary changes based on the data collection requirements meaning the data you are asking for, needs to confirm whether Appsflyer will pull the data from user click or from SDK.

For the full list of Postback parameters supported by Swaarm, click here

You can find the additional Postback link macros supported by Appsflyer, here