If you haven't found the tracker you are using on the list, this article provides some additional available options.
You won't see these trackers on the PropellerAds dashboard, but you can still use them to set server-to-server tracking.
In this manual, you can check how to set tracking for the following tracking tools:
AppsFlyer
AppsFlyer is a Mobile Measurement Partner Tracker that is used mostly for App Promotion.
In AppsFlyer, there are two main flows to follow:
Direct advertiser
Agency or external media buyers
If you are a direct advertiser promoting your own app, please follow these steps:
1. Add PropellerAds as a Partner
Log in to your AppsFlyer account.
From the left-side menu, choose the Configuration option, then Partner Marketplace.
In the list of available partners, search for PropellerAds and select it.
2. Activate the Integration
On the PropellerAds setup page, go to the Integration tab.
Turn on the Activate Partner toggle.
Click on Save Integration.
3. Configure Additional Tabs
On the PropellerAds setup page, you’ll see several tabs (Attribution Link, Cost, Ad Revenue, Permissions). Configure them according to your offer's needs.
4. Manage the App Settings
In AppsFlyer, select an app from those listed in the table.
If you are running campaigns for an iOS app, go to the app settings in AppsFlyer. Under the Integration Tab, disable the Advanced Privacy feature.
If the toggle cannot be disabled here, open App Settings and switch off Aggregated Advanced Privacy.
5. To grant the permissions:
Go to the Permissions tab.
Enable both (integration and configure in-app event postbacks)
Click on the Save Permissions tab.
Important: Under In-App Event Postback, set Including to No Values & No Revenue. If both options are enabled, AppsFlyer may send duplicate events, which can cause problems with optimization later.
Example:
If you’re an agency representative, PropellerAds requires pre-approval and a handshake (security feature) before tracking can work for such account types.
To get this pre-approval, share your Agency ID (af_prt) with your PropellerAds account manager or support team. They will set up the handshake for you.
After the handshake is approved, the integration process is the same as for direct advertisers.
Handling Multiple Conversion Events with AppsFlyer
With AppsFlyer, you can track more than one event (e.g., install, trial, subscription).
By default, all events are sent via token goal=1.
To track different events separately, map events to goals in AppsFlyer.
Recommended setup:
goal=1 → Install (or another primary event)
goal=2 → Important secondary event (e.g., registration)
goal=3 → High-value event (e.g., purchase, subscription)
Note: Install events will always fire as goal=1 unless &af_installpostback=false is added to the tracking URL.
Adjust
Adjust is a Mobile Measurement Partner Tracker that is used for App Promotion.
The flow for setting tracking for the applications is the following:
Enter Callback - Advertiser Postback
With Adjust, you can set up postbacks to receive advertising IDs, attribution details, app data, and more directly to your servers in real time as raw data if the relevant consent requirements are met.
To set up a callback(advertiser postback URL), you must specify:
The server endpoint URL where you want to receive data. (You can get it from the PropellerAds dashboard on the tracking section)
Callback parameters and Adjust placeholders for the data points you want to track.
Whether you want to set up a single activity postback or multiple postbacks for the same activity.
You can create server callbacks using the guided setup or classic setup.
Adjust recommends using the guided setup to create callback URLs.
The flow for creating the postback is below:
Access the server callback setup from your app card or from the Data management tab of your app setup.
- To set up a server callback from the app card, under AppView, select All apps. Find your app and select Server callbacks.
- To set up a server callback from the Data management tab of your app setup, select All apps under AppView, select your app, and then select the Data management tab.Under Server callbacks, select Add callback > Guided setup.
In the Callback trigger list, select the activity or event that would trigger the callback. Adjust supports the following events: click, impression, install, reattribution, conversion, session, in-app event (as defined by the client), rejected install (Identified as fraudulent), rejected reattribution (Identified as fraudulent).
In the Server endpoint field, enter an endpoint URL where you can receive your data.
(Optional) Select Add a condition to add a condition in combination with placeholders and values. The callback would be triggered only if the condition is satisfied.
Select Add a placeholder to dynamically include user or engagement data in your callback. You can add multiple placeholders at this point.
Select Create callback URL to generate the encoded callback URL. For more information about the encoded callback, check the Adjust documentation.
The process of Еncoding the callback is described below:
1. Go to the Adjust Encoding tool.2. Enter Target URL(from the Adjust dashboard)
Make sure to replace “clickid” with “label,” as this is Adjust’s universal parameter. If no “clickid” parameter is added, include “label=${SUBID}” instead.
Your updated link should look like this:
Without Pre-lander: https://app.adjust.com/1eay5f52?label=${SUBID}
3. Enter Install Callback - Advertiser Postback. You can get it from the PropellerAds dashboard.
4. Final Link Ready for Tracking can be found under the third section of the encoding tool:
You can use the final Target URL while creating the campaigns in PropellerAds.
Appmetrica
PropellerAds is directly integrated with Appmetrica; you can find PropellerAds in Appmetrica under the Tracking section, then choose Media Sources.
If necessary, you can add a media source yourself: Go to Tracking → Media Sources and click + Add Media source.
In the window that opens, fill in the information and click Create.
The new media source will be available in the list. You can find media sources you have added by sorting them with the "Your" button or using the search bar.
Example of the Postback Setup in Appmetrica:
Install postback should look like this: http://ad.propellerads.com/conversion.php?aid=12345&pid=&tid=123465&visitor_id={click_id}
Install postback should look like this:
Example of Target URL from Appmetrica
List of Trackable Events: https://appmetrica.yandex.com/docs/en/mobile-tracking/postback-specification
Affise
Setting up the PropellerAds network postback in Affise is the follows:
Сreate an offer on the Affise portal
Set up Target URL
Set up Postback
Set up Tracking URL
1. Get the Affise tracking link in Offers > Choose a certain offer > Tracking link.
2. If you want to pass additional information, update the link with your macros.
3. You can use sub1 for ${SUBID} and sub2 for {zoneid}
4. The link updates automatically.
Set-up Postback
1. Update your postback URL with your parameters and the selected Affise macros.
2. Set up a postback URL for a particular offer in Offers > a certain offer > Your Postbacks.
3. Click on "Add postback".
4. Insert the postback URL.
5. Select the status of the conversions you want to get postbacks for.
6. Select the goal of the conversions you want to get postbacks for.
Google Tag Manager (GTM)
To set S2S tracking through Google Tag Manager, mind the following:
All actions need to be performed on the same website.
You need to have the (correct) GTM tag installed on the website.
You need to have trigger points configured in GTM, for example, REG and FTD.
Add a script that triggers on all pages - that stores a cookie with the Propeller Visitor ID.
You need to add 2 more scripts that fire back the Propeller Visitor ID at each individual trigger point.
Explanation:
The target URL should be structured as follows: https://domain.name/?utm_prid=${SUBID}.
The parameter "utm_prid" is connected to ${SUBID}, which represents the visitor_id. The script will store the visitor ID in a cookie and fire it back when trigger points are reached.
It's crucial that the script has sufficient time to activate and store the Propeller Visitor ID in the user's cookie. In cases where the website has unusual redirect logic, it may prevent the visitor ID from being stored, resulting in no conversions being fired.
Below is a guide to set up Google Tag Manager:
Create a GTM Account:
Go to the Google Tag Manager website.
Click on “Start for free” and sign in with your Google account.
Create a new account by entering your account name and setting up a container (which can be your website or app).
Install GTM on Your Website:
Once your container is created, GTM will provide you with two snippets of code.
Copy and paste the first code snippet as high in the <head> of the page as possible.
Paste the second code snippet immediately after the opening <body> tag.
Save your changes and publish your container.}
Verify Installation:
Use the GTM preview mode to ensure the code is working correctly.
In GTM, click on “Preview,” enter your website URL, and then click “Connect.”
Your website will open in a new tab with a debug panel at the bottom showing which tags are firing.
Some custom HTML tags written for PropellerAds users can be found in the article:
https://propellerads.com/blog/adv-gtm-google-tag-manager/
Testing:
Once the script implementation is done, perform a test conversion using a URL in the following format: https://domain.name/?utm_prid=${SUBID}.
You should see it in your Google account like this:
Telegram Tracking
The Telegram tracking is performed via API and used with Telegram Mini Apps traffic.
Generally, it is performed this way:
You Track Telegram Group Events → Capture click ID in Telegram bot → Detect user interaction → Send postback on target event..
To set up tracking, you should perform the following steps inside Telegram:
Create Telegram Bot
Use @BotFather to create a bot and get the Bot Token.
Set Up Backend Server (Public server with SSL (HTTPS), PHP/Node.js, and a domain)
Configure Telegram Webhook
Set Webhook URL to your server endpoint.
Set PropellerAds Target URL: https://t.me/your_bot?start=${SUBID}_{campaignid}_{zoneid}_prop
Bot Logic (PHP) On: /start, extract ${SUBID}.