Time to read: 4 min
The article covers the following topics:
Parameters for Tracking URL
The integration process starts with Affise Tracking URL that can be taken from the offer page. To set the Affise <-> Tune Integration as Affiliate, you need to add the Tune's {transaction_id} macro to the offer Tracking URL. You may pass the Tune's {transaction_id} macro using one of the free sub-account parameters: &sub1 - &sub8.
Tracking URL example:
http://track.offer.com/click?pid={pid}&offer_id={offer_id}&sub1={transaction_id}
Put the updated Tracking URL into your Tune system.
The full list of the Affise parameters for the Tracking URL:
| sub1-sub8 | Subaccount 1 - Subaccount 8 |
| ref_id | Additional parameter for Tracking URL |
| ext1-ext3 | Additional parameters for Tracking URL |
| os_id | Additional parameter for Tracking URL |
| imp_id | Impression ID |
Macros for Postback URL
Next, you need it to share your Tune Postback URL to get information about conversions. You can set your postback via Affiliate panel on the offer page or in the Profile settings as a Global Postback URL. Your Postback URL should contain &transaction_id parameter with {sub1}-{sub8} macro which you use to pass {transaction_id} value in the Tracking URL:
Tune Postback URL example:
http://rocketcompany.go2cloud.org/aff_lsr?transaction_id={sub1}
The full list of the Affise macros for the Postback URL:
| {uagent} | UserAgent of user browser |
| {ip} | User IP-address |
| {sub1}-{sub8} | Subaccount 1 - Subaccount 8 |
| {ref_id} | Additional macro for postback URL |
| {os_id} | Additional macro for postback URL |
| {user_id} | Additional macro for postback URL |
| {ext1} - {ext3} | Additional macro for postback URL |
| {transactionid} | Conversion identificator of the advertiser |
| {date} | Date and time of conversion committing in format Y-m-d H:i:s |
| {offerid} | Offer identificator in the System |
| {offer_name} | Offer title in the System |
| {status} |
Conversion status, available values: 1 – action "Allowed" (will be paid later by the advertiser) |
| {sum} | Conversion payout |
| {city} | City |
| {geo} | Country |
| {goal} | Goal |
| {currency} | Currency |
| {comment} | Comment |
| {time} | Time of conversion committing in format H:i:s |
| {date_only} | Date of conversion committing in format Y-m-d |
| {rand} | Unique number (UUID format, eg: 9cdf32d5-124e-4e06-b25b-4c92d3cec9dc) |
| {referrer} | Click referrer |
|
{custom_field1} - {custom_field8} or {custom_field_1} - {custom_field_8} |
Custom field 1 - Custom field 8 |
| {os} | OS Family |
| {timestamp} | unix timestamp of conversion creation |
When the links are updated with the correct parameters & macros, you can request your Manager to proceed with Integration tests.
You may also find the following articles helpful:
If you have more questions on the Affise <-> Tune Integration, feel free to contact your Affiliate manager via the Tickets in the Support section or Tune Support team via the help center.
Written by Anastasia Deryugina
0 Comments