Skip to main content

Tracker integration guide

Tracker integration guide

J
Written by Jorge Rubia

When an Advertiser uses a third-party tracker to manage their campaigns, Aftrad needs to communicate with that tracker in both directions: sending clicks to it and receiving conversion notifications back from it.

This requires two URL configurations in Aftrad:

  • Offer Tracking URL — the URL configured in the Aftrad Offer that routes clicks to the Advertiser's tracker. It uses the tracker's own parameter names, with Aftrad macros as values so the tracker receives the correct data on each click.

  • Advertiser Postback URL — the URL you share with the Advertiser so their tracker can notify Aftrad when a conversion occurs. It uses the tracker's own macros so the data is passed back automatically, without the Advertiser needing to replace any values manually.

This guide provides ready-to-use URL templates for the most common trackers. For each tracker you will find both URLs pre-configured and ready to use.


Parameters reference

Before looking up your tracker, here is a quick reference of the Aftrad macros used in the Tracking URL:

Aftrad macro

Description

{click_id}

Unique Aftrad click ID. Used to attribute conversions back to the correct click.

{aggregated_id}

Alternative aggregated ID. Used when the click ID cannot be passed individually.

{source}

Traffic source identifier sent by the Affiliate.

{sub_source}

Traffic sub-source identifier sent by the Affiliate.


Tracker list

Affise

Offer Tracking URL

https://advertiser.com/offer.html?clickid={click_id}&transactionid={aggregated_id}&sub1={source}&sub2={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id={sub1}&aggregated_id={transactionid}&event_parameter={goal}&payout={sum}

💡 Affise uses {clickid} (no underscore) for the click ID in the Tracking URL, and {sub1}{sub8} for custom values. Use {sub1} to pass the Aftrad click_id back in the postback.


Swaarm

Offer Tracking URL

https://advertiser.com/offer.html?pub_click_id={click_id}&unique1={aggregated_id}&pub_sub_id={source}&pub_sub_id2={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id=#{click.publisher.clickId}&aggregated_id=#{click.publisher.unique1}&event_parameter=#{eventType.name}&payout=#{payout.theyGetInDollars}

💡 Swaarm uses the #{ } syntax for macros. #{click.publisher.clickId} is the standard macro to pass back the click ID on conversion.


Trackier

Offer Tracking URL

https://advertiser.com/offer.html?click_id={click_id}&txn_id={aggregated_id}&p1={source}&p2={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id={click_id}&aggregated_id={txn_id}&event_parameter={goal_value}&payout={payout}

💡 Trackier uses {click_id} as the primary click identifier, {txn_id} as the transaction ID, and {goal_value} to pass the event or goal name in the postback. {p1} and {p2} are Trackier's custom sub-parameters for source and sub-source.


Offer18

Offer Tracking URL

https://advertiser.com/offer.html?aff_click_id={click_id}&transaction_id={aggregated_id}&source={source}&sub1={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id={aff_click_id}&aggregated_id={transaction_id}&event_parameter={event_name}&payout={payout}

💡 Offer18 uses {aff_click_id} to pass the affiliate click ID and {transaction_id} for the transaction identifier.


Tune / HasOffers

Offer Tracking URL

https://advertiser.com/offer.html?aff_click_id={click_id}&aff_unique1={aggregated_id}&aff_sub={source}&aff_sub2={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id={aff_click_id}&aggregated_id={transaction_id}&event_parameter={goal}&payout={amount}

💡 Tune uses aff_click_id to store unique click IDs from publishers, aff_sub and aff_sub2 for source and sub-source values. {transaction_id} is Tune's internal transaction identifier.


CAKE

Offer Tracking URL

https://advertiser.com/offer.html?reqid={click_id}&s2={aggregated_id}&s1={source}&s3={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id=#reqid#&aggregated_id=#s2#&event_parameter=#s4#&payout=#price#

⚠️ CAKE uses #token# syntax (with hash symbols) for postback tokens. The s1 parameter is reserved for Sub-Affiliate IDs — do not use it to pass click IDs. Use s2 through s5 for unique values like click IDs.


Impact

Offer Tracking URL

https://advertiser.com/offer.html?SubId1={click_id}&SharedId={aggregated_id}&SubId2={source}&SubId3={sub_source}

Advertiser Postback URL

https://chameleon.aftrad-event.com/api/v1/events?click_id={SubId1}&aggregated_id={SharedId}&event_parameter={ActionTrackerName}&payout={Payout}

💡 Impact uses SubId1SubId3 for custom publisher values, and SharedId for values visible to both the partner and the brand. {ActionTrackerName} identifies the conversion event type in Impact.


Don't see your tracker?

The pattern is always the same regardless of the tracker:

  1. In the Offer Tracking URL — use the tracker's parameter names with Aftrad macros as values.

  2. In the Advertiser Postback URL — use the tracker's own macros so the data is returned to Aftrad automatically.

If you need help configuring a tracker not listed here, contact your Aftrad account manager.


Related articles

Did this answer your question?