AppsFlyer Integration

by Ralitsa Petkova

Last updated: 02-Jul-2026

MyAffiliates supports integration with AppsFlyer for clients tracking app downloads.

Traffic Flow Overview

When a visitor clicks a MyAffiliates tracking link, they are redirected to the operator’s landing page along with a unique tracking token. This token is typically stored in the visitor’s browser as a cookie and is used later to attribute any registration back to the originating affiliate.

When the visitor downloads the app, the browser-based tracking token is no longer available, meaning tracking may be lost at this stage.

To maintain attribution, several clients use AppsFlyer. The tracking token can be passed through to AppsFlyer by embedding it in the AppsFlyer link using a designated format.

Example:

https://app.appsflyer.com/id11111111111?pid=myaffiliates&af_click_lookback=7d&c=ieQz0IK_kMKuDMXTvJVWGWNd7ZgqdRLk

In this setup:
The pid=myaffiliates parameter identifies MyAffiliates as the traffic source
The c parameter carries the MyAffiliates tracking token
The app ID (id11111111111) must be replaced with the client’s actual AppsFlyer application ID

The AppsFlyer (OneLink) URL must be configured as a landing page within the MyAffiliates Back Office.

The tracking flow becomes:

Affiliate Tracking Link > AppsFlyer URL > App Store / Google Play

All refer conversions recorded in AppsFlyer containing, pid=myaffiliates and c=tracking_token must be extracted by the operator’s technical team and sent to MyAffiliates using the standard customer registration data import process.

This integration ensures affiliate attribution can be maintained across mobile app installations where traditional browser-based cookies are not available.