Follow

Affise <-> Kochava Integration

Time to read: 3 min.

Screenshot_40.png

topic.pngThe article covers the following topics:

To start the integration process with the Kochava, you need to contact a Kochava representative and ask for integration possibility.

By the policy conducted by Apple Inc. in 2021, it is prohibited for attribution platforms (including Kochava) to use click ID value or any other unique values which could help to identify the end-user. As a result the whole tracking process performed in conjunction with attribution platforms has been changing. Kochava isn't an exclusion. 

Tracking process between Affise and Kochava is based on basics of Probabilistic Attribution. We highly recommend reading this article to learn more about this type of integration. 

click__1_.png Find out Kochava Integration documentation here. This document provides all the details about the integration process on the Kochava side. 

Tracking link

Basic Kochava Tracking URL contains Kochava parameters and Affise macros:

http://kochava_tracking_url?2click_id={clickid}&ad_platform={sub1}&att={sub3}

Where:

  • click_id={clickid} - Affise click ID value. A mandatory parameter.
  • &ad_platform={sub1}-{sub8} - this should be populated with in_app for in app traffic and m_web for mobile web traffic.
  • &att={sub1}-{sub8} - this should be populated with 1 for users who’ve consented and 0 for those who haven’t.

Postback link

Below you will find Postback URLs examples, which can be helpful when filling the Kochava integration form. 

Application installation postback example: 

https://offers-rocketcompany.affise.com/postback?clickid={click_id}&action_id={click_id}&offer_id={sub_site_id}&pid={site_id}&timestamp={timestamp}&sub2={creative_id}&country={user_country}&att=0/1&ad_platform={sub1}

Goal (event) postback example:

https://offers-rocketcompany.affise.com/postback?clickid={click_id}&action_id={click_id}&offer_id={sub_site_id}&pid={site_id}&timestamp={timestamp}&sub2={creative_id}&country={user_country}&att=0/1&ad_platform={sub1}&goal={event_name}

The must-be parameters are:

offer_id Offer ID
pid Affiliate ID
att

Possible values: 1 and 0. 1 if authorized, 0 - if not determined, denied or restricted

ad_platform Affise traffic type [mobile, web] parameter

You can use the following parameters in the postback link:

action_id Unique conversion ID in the advertiser's system
goal Goal number or goal value
country Country where the conversion was made. Use Alpha-2 ISO codes (FR, RU, DE, etc.)
timestamp Time that the user consented in Unix format
sub2 Sub2 value, which helps to select a right payout in the offer in case of Probabilistic Attribution
platform OS of the end user, who created the conversion. Use these values: ios/android. 
status

Conversions status:

1 - Approved

2 - Pending

3 - Declined

5 - Hold

sum

Conversion revenue 

comment Comment
custom_field1 - custom_field7 Additional information about conversions

The logic of postbacks receiving

If the conversion came with the click ID and &att=1, it will be attributed to a certain click. It is an ordinary process of conversions tracking - no peculiarities.

If the conversion came with the click ID and &att=0, it will be attributed to a certain click. It is an ordinary process of conversions tracking.

If the conversion came without click ID and with &att=0, it means Probabilistic Attribution works. In this case the conversion also must have other parameters: &offer_id= and &pid=, with the help of which the conversion will be attributed to a certain offer and an affiliate.

article.pngYou may also find the following articles helpful:

 If you have more questions on the Integration with Kochava, feel free to contact the Kochava Support Team via support@kochava.com.

 Updated by Lizaveta Talkachova

 
Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.