Aarki conversion tracking with voluum (2)

Ben is in the morning shift. I’m Paul, one of the Ad Ops here at Aarki. Thanks for reaching out to us about integrating with your tracking platform. I’ll be happy to help you here.

First thing, we do require that the installs you register be matched against the clicks we generate using device identifiers such as the IDfA on iOS and the Android ID and/or IMEI/MEID on Android. We do not consider “Fingerprinting” or other methods that rely on the device’s IP address to be sufficiently reliable for our publishers’ needs.

With that in mind, can you please tell me what data points you usually capture from users’ devices upon installation of a new app for use in install attribution matching? Our most commonly used model is to capture these identifiers on-click and send them to you in the tracking URLs provided by your advertiser clients, so that you can match against identifiers captured on-install.

On iOS, we can send you the IDfA values using our “{advertising_id}” macro.
On Android, we can pass the Android ID as “{device_id}” and the user’s IMEI or MEID value as “{phone_id}”

For both platforms, we also need to send an “{app_id}” value, which references the specific campaign as entered in our portal. Additionally, each click is assigned its own unique value, which we will send to you as “{click_id}”.

Please send me an example of your tracking URLs with these identifier macros inserted into the appropriate parameters or locations so that I can create generate templates for your format.

To confirm a valid transaction, you will only need to send us the relevant {app_id} and {click_id} values through our standard Postback URL. You do not need to return the device identifiers to us. Our postback URL is: http://postback.aarki.net/pbn/instal...try=&language=
Please let me know if you have any questions about this method and I’ll be happy to help.

Best,
Paul

Paul Edward Casem
Advertising Operations
www.aarki.com