Advertiser integration

Advertiser Tracking

Taptica work as mediation layer between the advertisers and the publisher. We need to be prompt by the advertiser whenever conversion take place and notified the publisher that conversion was close. this section refer to the post back Taptica need to get from the advertiser in order to close conversion.

Mainly Taptica support two type of post backs:

Conversion Post back

   • LSR   - Use for tracking conversion with third party tracking system like Mobile App Tracking, Adx, Appsflyer, Kochava MdotM...

   • Aff_U - Use for tracking conversion without  third party tracking system. the user is redirect directly to the market ( Google Play or  Appstore)

Event Post Back

   • Aff_goal - Use for the notify Taptica  when the user made certain action in the application as  finished tutorial, Faceebook connect purchase ...

______________________________________________________________________________________________________________________________________________

Tracking With Third Party System

As mention above there are many tracking solution in the market as AD-X, Mobile App Tracking, Appsflyer, Kochava and many more. Each one of them implement the tracking logic a bit different but at the end in all cases Taptica expect to get S2S post back upon conversion.

The basic conversion link is:

For iOS:

http://tracking.taptica.com/aff_lsr?tt_cid={tt_cid}&tt_adv_id=XYZ&tt_adv_sub={tt_adv_sub}&tt_time={tt_time}&tt_idfa={user_idfa}&tt_appid={store_appid}

For Android:

http://tracking.taptica.com/aff_lsr?tt_cid={tt_cid}&tt_adv_id=XYZ&tt_adv_sub={tt_adv_sub}&tt_time={tt_time}&tt_imei={user_imei}&tt_advertising_id={user_advertising_id}&tt_android_id={user_android_id}&tt_appid={store_appid}

On top of it there are unique device parameters that collect by the tracking system and need to be send back to us upon conversion:

Taptica Keys

Parameter	Name In Request	Description	Example	Daynamic?
Click ID	tt_cid	Taptica Internal unique click ID which was sent on the click URL	tt_cid=2ab818fe8e574f41838780cb2f6230da	Yes
Advertiser ID	tt_adv_id	Taptica internal unique advertiser id. will be provided to the advertiser in the integration process.	tt_adv_id=123456	No
Advertiser Click ID	tt_adv_sub	The advertiser unique conversion ID	tt_adv_sub=dc1816eac806878e8d1d5a8ee9406a3f71407895	Yes
Conversion Time	tt_time	The conversion time, format "yyyy-MM-dd HH:mm:ss.fff" encoded as UTF-8	tt_time=2013-03-27 23:30:35.356	Yes
IMEI	tt_imei	Use for send Taptica Plain IMEI or when you don’t know what is the format of IMEI you have.	tt_imei=86453214567892	Yes
IMEI SHA1	tt_imei_sha1	Use for send Taptica IMEI in SHA1 format	tt_imei_sha1=35eb6d1fc48b502e239b6449e9df534e415cad95	Yes
IMEI MD5	tt_imei_md5	Use for send Taptica IMEI in MD5 format	tt_imei_md5=946cc1baf8bcaec827bb1828cc6d9a94	Yes
Android ID	tt_android_id	Use for send Taptica Plain Android ID or when you don’t know what is the format of Android ID you have.	tt_android_id=3ee0149b4ccef71b	Yes
Android ID SHA1	tt_android_id_sha1	Use for send Taptica Android ID in SHA1 format	tt_android_id_sha1=4f2e52e8157fcb729d799d1ca69160df2edf0cd4	Yes
Android ID MD5	tt_android_id_md5	Use for send Taptica Android ID in MD5 format	tt_android_id_md5=155551c45efa667f9b470629ae9c0365	Yes
Android Advertising ID	tt_advertising_id	Use for send Taptica Android advertising plain ID	tt_advertising_id=3ee0149b4ccef71bs85d24derg	Yes
Android Advertising ID SHA1	tt_advertising_id_sha1	Use for send Taptica Android advertising ID in SHA1 format	tt_advertising_id=32f2e52e8157fcb729d799d1ca69160df2edf8974	Yes
Android Advertising ID MD5	tt_advertising_id_md5	Use for send Taptica Android advertising ID in MD5 format	tt_advertising_id=2315w52e8157fcb729d799d1ca691608speofd2	Yes
Mac Address	tt_mac	Use for send Taptica Plain Mac Address or when you don’t know what is the format of the Mac Address you have. (upper case with colon)	tt_mac=44:2A:60:G5:GE:G5	Yes
Mac Address SHA1	tt_imei_sha1	Use for send Taptica Mac Address in SHA1 format (upper case with colon)	tt_mac_sha1=fa6bb084ae52461328eb9f06039be222ef287246	Yes
Mac Address MD5	tt_mac_md5	Use for send Taptica Mac Address in MD5 format (upper case with colon)	tt_mac_md5=80efe2256d548c85ca2f2d18de241a80	Yes
IDFA	tt_idfa	Use for send Taptica Plain IDFA or when you don’t know what is the format of IDFA you have.	tt_idfa=4A9B0CAB-FFA5-4190-8CC0-D974D98FC7D7	Yes
IDFA SHA1	tt_idfa_sha1	Use for send Taptica IDFA in SHA1 format	tt_idfa_sha1=4a3b645d5f44565d7e913c612ddb7fee32a03d6d	Yes
IDFA MD5	tt_idfa_md5	Use for send Taptica IDFA in MD5 format	tt_idfa_md5=DEF179E9B89E822C3F838F3F18EB9F43	Yes
UDID	tt_udid	Use for send Taptica Plain UDID or when you don’t know what is the format of UDID you have.	tt_udid=dc1816eac806878e8d1d5a8ee9406a3f71452c80	Yes
UDID SHA1	tt_udid_sha1	Use for send Taptica UDID in SHA1 format	tt_udid_sha1=1ddfad5e4377b8694b5fea2a4c4556e2add9605b	Yes
UDID MD5	tt_udid_md5	Use for send Taptica IMEI in MD5 format	tt_udid_md5=20fbe500c99939adabb4d06600eb4ee7	No

For example This post back link contain plain IDFA and Mac Address in md5.

http://tracking.taptica.com/aff_lsr?tt_cid=2ab818fe8e574f41838780cb2f6230da&tt_adv_id=123456&tt_adv_sub=dc1816eac806878e8d1d5a8ee9406a3f71407895&tt_time=2013-03-27 23:30:35.356&tt_idfa=771468523E3346ABAA04E207BBAF094B&tt_mac_md5=80efe2256d548c85ca2f2d18de241a80

Tracking Without Third Party System

Some of the advertisers are not using third party Tracking system and they are redirect the user directly to the store. Once the user download and open the application they notify to publisher (Taptica) that conversion toke place. The basic post back link is:

http://tracking.taptica.com/aff_u?tt_appid={store_application_id}&tt_adv_id=xyz&tt_adv_sub={tt_adv_sub}&tt_time={tt_time}&tt_idfa={user_idfa}&tt_advertising_id={user_advertising_id}&tt_android_id={user_android_id}

In addition to the basic post back link the advertiser send the device unique parameters so Taptica will match the conversion to the traffic source:

Taptica Keys

Parameter	Name In Request	Description	Example	Daynamic?
Click ID	tt_cid	Taptica Internal unique click ID which was sent on the click URL	tt_cid=2ab818fe8e574f41838780cb2f6230da	Yes
Application ID	tt_appid	the application id as it appears in Google play or App store	tt_appid=440045374 (for iOS)/ tt_appid=com.king.candycrushsaga (for Android)	Yes
Advertiser ID	tt_adv_id	Taptica internal unique advertiser id.	tt_adv_id=123456	No
Advertiser Click ID	tt_adv_sub	The advertiser unique conversion ID	tt_adv_sub=dc1816eac806878e8d1d5a8ee9406a3f71407895	Yes
Conversion Time	tt_time	The conversion time, format "yyyy-MM-dd HH:mm:ss.fff" encoded as UTF-8	tt_time=2013-03-27 23:30:35.356	Yes
IMEI	tt_imei	Use for send Taptica Plain IMEI or when you don’t know what is the format of IMEI you have.	tt_imei=86453214567892	Yes
IMEI SHA1	tt_imei_sha1	Use for send Taptica IMEI in SHA1 format	tt_imei_sha1=35eb6d1fc48b502e239b6449e9df534e415cad95	Yes
IMEI MD5	tt_imei_md5	Use for send Taptica IMEI in MD5 format	tt_imei_md5=946cc1baf8bcaec827bb1828cc6d9a94	Yes
Android ID	tt_android_id	Use for send Taptica Plain Android ID or when you don’t know what is the format of Android ID you have.	tt_android_id=3ee0149b4ccef71b	Yes
Android ID SHA1	tt_android_id_sha1	Use for send Taptica Android ID in SHA1 format	tt_android_id_sha1=4f2e52e8157fcb729d799d1ca69160df2edf0cd4	Yes
Android ID MD5	tt_android_id_md5	Use for send Taptica Android ID in MD5 format	tt_android_id_md5=155551c45efa667f9b470629ae9c0365	Yes
Android Advertising ID	tt_advertising_id	Use for send Taptica Android advertising plain ID	tt_advertising_id=3ee0149b4ccef71bs85d24derg	Yes
Android Advertising ID SHA1	tt_advertising_id_sha1	Use for send Taptica Android advertising ID in SHA1 format	tt_advertising_id=32f2e52e8157fcb729d799d1ca69160df2edf8974	Yes
Android Advertising ID MD5	tt_advertising_id_md5	Use for send Taptica Android advertising ID in MD5 format	tt_advertising_id=2315w52e8157fcb729d799d1ca691608speofd2	Yes
Mac Address	tt_mac	Use for send Taptica Plain Mac Address or when you don’t know what is the format of the Mac Address you have. (upper case with colon)	tt_mac=44:2A:60:G5:GE:G5	Yes
Mac Address SHA1	tt_imei_sha1	Use for send Taptica Mac Address in SHA1 format (upper case with colon)	tt_mac_sha1=fa6bb084ae52461328eb9f06039be222ef287246	Yes
Mac Address MD5	tt_mac_md5	Use for send Taptica Mac Address in MD5 format (upper case with colon)	tt_mac_md5=80efe2256d548c85ca2f2d18de241a80	Yes
IDFA	tt_idfa	Use for send Taptica Plain IDFA or when you don’t know what is the format of IDFA you have.	tt_idfa=771468523E3346ABAA04E207BBAF094B	Yes
IDFA SHA1	tt_idfa_sha1	Use for send Taptica IDFA in SHA1 format	tt_idfa_sha1=ee5c19f8cf370b5978f4b9f33343a5e79c58df9a	Yes
IDFA MD5	tt_idfa_md5	Use for send Taptica IDFA in MD5 format	tt_idfa_md5=bb1e0285fbb97ba83fdb4e72514d62f5	Yes
UDID	tt_udid	Use for send Taptica Plain UDID or when you don’t know what is the format of UDID you have.	tt_udid=dc1816eac806878e8d1d5a8ee9406a3f71452c80	Yes
UDID SHA1	tt_udid_sha1	Use for send Taptica UDID in SHA1 format	tt_udid_sha1=1ddfad5e4377b8694b5fea2a4c4556e2add9605b	Yes
UDID MD5	tt_udid_md5	Use for send Taptica IMEI in MD5 format	tt_udid_md5=20fbe500c99939adabb4d06600eb4ee7	No

For example

This post back link contain plain IDFA and Mac Address in md5.

http://tracking.taptica.com/aff_u?tt_cid=2ab818fe8e574f41838780cb2f6230da&tt_appid=440045374&tt_adv_id=123456&tt_adv_sub=dc1816eac806878e8d1d5a8ee9406a3f71407895&tt_time=2013-03-27 23:30:35.356&tt_idfa=771468523E3346ABAA04E207BBAF094B&tt_mac_md5=80efe2256d548c85ca2f2d18de241a80

Event Post back

In addition to the conversion tracking Taptica support events notifications as Facebook connect and Purchase. Those events should be fired form the advertiser / third party tracking system upon user action. The events assist Taptica to improve traffic sources and provide the advertisers beneficial users.

Taptica Keys

Parameter	Name In Request	Description	Example	Daynamic?
Click ID	tt_cid	Taptica Internal unique click ID which was sent on the click URL	tt_cid=2ab818fe8e574f41838780cb2f6230da	Yes
Advertiser ID	tt_adv_id	Taptica internal unique advertiser id.	tt_adv_id=123456	No
Advertiser Click ID	tt_adv_sub	The advertiser unique conversion ID	tt_adv_sub=dc1816eac806878e8d1d5a8ee9406a3f71407895	Yes
Event ID (Goal id)	tt_goal	Taptica unique identifier will be provided by Taptica in the integration process.	tt_goal=7895	NO
Event Time	tt_time	Event Time "yyyy-MM-dd HH:mm:ss.fff" encoded as UTF-8	tt_time=2012-08-24 16:26:13.000	Yes

For Example

http://tracking.taptica.com/aff_goal?tt_cid={tt_cid}&tt_adv_id=xyz&tt_goal=x&tt_adv_sub={tt_adv_sub}&tt_time={tt_time}&amount={amount}&tt_idfa={user_idfa}&tt_advertising_id={user_advertising_id}&tt_android_id={user_android_id}&tt_imei={user_imei}

Additional parameters

Taptica encourage advertiser to give here feedback on the traffic quality she provide. by adding to the tracking link few parameters

Additional Keys

Parameter	Name In Request	Description	Example	Daynamic?
Affiliate ID	aff_id	Taptica Internal unique affiliate ID	aff_id=3123432	Yes
Sub affiliate ID	tt_sub_aff	indicate the sub affiliate id as it at the affiliate system.	tt_sub_aff=1876287ans	Yes

For example This tracking link show simple third party integration with affiliate ID and sub affiliate parameters.

http://hastrk1.com/serve?action=click&publisher_id=123456&site_id=303030&offer_id=404040&ref_id={tt_cid}&aff_id={aff_id}&tt_sub_aff={tt_sub_aff}