Probabilistic Attribution
With the iOS 14 update, Apple has introduced new privacy features that aim to protect users' personal information, making it increasingly difficult for advertisers to accurately monitor user behavior and attribute conversions.
However, by using probabilistic attribution for a long chain of redirects, we can still accurately measure the effectiveness of our campaigns while maintaining compliance with Apple's policies. To implement this solution, we recommend adding an affiliate privacy postback in Offer18, which will allow us to push conversion data back to you without compromising user privacy.
Implementation for Advertiser
Create an offer using the tracking link provided by the advertiser. Confirm with the advertiser on the parameter for receiving offer ID and affiliate ID. Add {offerid},{aff_id}|{aff_sub7} against the parameter provided by the advertiser.
{offerid}
Macro to pass the Offer ID
{aff_id}
Macro to pass the Affiliate ID
{aff_sub7}
Macro to pass Affiliate data
Example - AppsFlyer tracking link
In above example &af_adset_id is the parameter which is being used to pass offer ID, affiliate ID and affiliate data to advertiser.
Implementation for Affiliate
Recive offer ID and affiliate ID inside &adv_sub7 parameter from the affiliate. Confirm with affiliate on the parameter for reciving offer ID and affilate ID inside postback. Add {adv_sub7} against the parameter provided by the affiliate.
Example - Offer18 Privacy Postback
In above example &adv_sub7 is the parameter which is being used to pass offer ID, affiliate ID to affiliate.
Privacy Postback at Advertiser End
Click Flow in Probabilistic Attribution (Example)
Client | Offer18 tracking link | Example |
Client 4 (Sub source) | https://client3.o18.click/c?o=3&m=0000&a=3&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client3.o18.click/c?o=3&m=0000&a=3&aff_sub7=4,4 |
Client 3 (Sub source) | https://client1.o18.click/c?o=1&m=0000&a=1&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client2.o18.click/c?o=2&m=0000&a=2&aff_sub7=3,3|4,4 |
Client 2 (Affiliate) | https://client2.o18.click/c?o=2&m=0000&a=2&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client1.o18.click/c?o=1&m=0000&a=1&aff_sub7=2,2|3,3|4,4 |
Client 1 (Admin) | http://app.appsflyer.com/{app_id}?af_siteid={aff_id}&af_c_id{offerid}&af_adset_id={offerid},{af_id}|{aff_sub7} | http://app.appsflyer.com/com.appsflyer?af_siteid=1&af_c_id=1&af_adset_id=1,1|2,2|3,3|4,4 |
Conversion Flow in Probabilistic Attribution (Example)
Client | Postback format | Example |
Client 4 (Sub source) | https://client3.o18.click/c?o=3&m=0000&a=3&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client3.o18.click/c?o=3&m=0000&a=3&aff_sub7=4,4 |
Client 3 (Sub source) | https://client2.o18.click/c?o=2&m=0000&a=2&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client2.o18.click/c?o=2&m=0000&a=2&aff_sub7=3,3|4,4 |
Client 2 (Affiliate) | https://client1.o18.click/c?o=1&m=0000&a=1&aff_sub7={offerid},{aff_id}|{aff_sub7} | https://client1.o18.click/c?o=1&m=0000&a=1&aff_sub7=2,2|3,3|4,4 |
Client 1 (Admin) | https://client1.o18.click/p?mid=000&privacy_postback=1&a={Site ID}&oid={Campaign ID}&p_country={Country code}&adv_sub7={Adset ID}&p_timestamp={Click timestamp}&p_package={Bundle ID}&p_postbackid={Postback ID} | https://example.o18.click/p?mid=000&privacy_postback=1&a=1&oid=1&p_country=US&adv_sub7=1,1 |2,2|3,3|4,4&p_timestamp={Click timestamp}&p_package={Bundle ID}&p_postbackid={Postback ID} |
Last updated