Help:Contents

From wiki.taptica.com
(Difference between revisions)
Jump to: navigation, search
(Tracking With Third Party System)
(Tracking With Third Party System)
Line 60: Line 60:
 
|-
 
|-
  
|Plain IMEI
+
|IMEI
 
|tt_imei
 
|tt_imei
|Use for send Taptica Plain  IMEI or when you don’t know what is the format of IMEI you have.
+
|Use for send Taptica '''Plain''' IMEI or when you don’t know what is the format of IMEI you have.
 
|tt_imei=86453214567892
 
|tt_imei=86453214567892
 
|Yes
 
|Yes
 
|-
 
|-
  
|Mac Address
+
|IMEI SHA1
|tt_deviceid4
+
|tt_imei_sha1
|The Android/iOS device mac address
+
|Use for send Taptica IMEI in SHA1 format
|tt_deviceid4=44:2A:60:G5:GE:G5
+
|tt_imei_sha1=
 
|Yes
 
|Yes
 
|-
 
|-
  
|IP Address
+
|IMEI MD5
|i
+
|tt_imei_md5
|Client IP Address
+
|Use for send Taptica IMEI in MD5 format
|i=84.103.57.1
+
|tt_imei_md5=
 
|Yes
 
|Yes
 
|-
 
|-
  
|Localization
+
|Android ID
|loc
+
|tt_android_id
|The localization (Language & Country) that is currently chosen for the device ,following the standards of ISO 639-1,ISO 3166-1.
+
|Use for send Taptica Plain  Android ID or when you don’t know what is the format of Android ID you have.
|loc=en_GB
+
|tt_android_id=
|No
+
|Yes
 
|-
 
|-
  
|Network type
+
|Android ID SHA1
|nt
+
|tt_android_id_sha1
|The type of network the device is currently connected to ("wifi" or "carrier")
+
|Use for send Taptica Android ID  in SHA1 format
|nt=carrier
+
|tt_android_id_sha1=
|No,
+
|Yes
 
|-
 
|-
  
|Marital status
+
|Android ID MD5
|marital
+
|tt_android_id_md5
|Marital status of the user. options are: "single", "divorced", "engaged", "relationship", or "swinger"
+
|Use for send Taptica Android ID  in MD5 format
|marital=single
+
|tt_android_id_md5=
|No
+
|Yes
 
|-
 
|-
  
|Income
+
|Mac Address
|income
+
|tt_mac
|Annual income (in USD) , e.g. 10000.
+
|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)
|income=10000
+
|tt_mac=44:2A:60:G5:GE:G5
|No
+
|Yes
 
|-
 
|-
  
|Interests
+
|IMEI SHA1
|interests
+
|tt_mac_sha1
|a comma separated list of keywords denoting user's area of interests.
+
|Use for send Taptica Mac Address in SHA1 format (upper case with colon)
|interests=cars,sports,F1,stocks
+
|tt_mac_sha1=fa6bb084ae52461328eb9f06039be222ef287246
|No
+
|Yes
 
|-
 
|-
  
|Education
+
|Mac Address SHA1
|edu
+
|tt_imei_sha1
|Education level of the user ("UG" or "PG")
+
|Use for send Taptica IMEI in SHA1 format
|edu=UG
+
|tt_deviceid4=44:2A:60:G5:GE:G5
|No
+
|Yes
 
|-
 
|-
  
|Resolution
+
|Mac Address MD5
|r
+
|tt_mac_md5
|Resolution of the ad request
+
|Use for send Taptica Mac Address in MD5 format (upper case with colon)
|r=320x50
+
|tt_mac_md5=80efe2256d548c85ca2f2d18de241a80
 
|Yes
 
|Yes
 
|-
 
|-
  
|Ad Type
+
|IDFA
|t
+
|tt_idfa
|Ad type - Text (1), Banner (2), Html (3), All (0), Video (5)
+
|Use for send Taptica Plain  IDFA or when you don’t know what is the format of IDFA you have.
|t=2
+
|tt_idfa=77146852-3E33-46AB-AA04-E207BBAF094B
 
|Yes
 
|Yes
 
|-
 
|-
  
|Gender
+
|IDFA SHA1
|gender
+
|tt_idfa_sha1
|Gender, Male, Female, All
+
|Use for send Taptica IDFA in SHA1 format
|gender=male
+
|tt_idfa_sha1=ee5c19f8cf370b5978f4b9f33343a5e79c58df9a
|No
+
|Yes
 
|-
 
|-
  
|Age
+
|IDFA MD5
|age
+
|tt_idfa_md5
|Age of the user
+
|Use for send Taptica IDFA in MD5 format
|age=27
+
|tt_idfa_md5=bb1e0285fbb97ba83fdb4e72514d62f5
|No
+
|Yes
 
|-
 
|-
  
|Date Of Birth
+
|UDID
|dob
+
|tt_udid
|User's Date of birth(Format: yyyyMMdd)
+
|Use for send Taptica Plain  UDID or when you don’t know what is the format of UDID you have.
|dob=19820211
+
|tt_udid=dc1816eac806878e8d1d5a8ee9406a3f71452c80
|No
+
|Yes
 
|-
 
|-
  
|Latitude
+
|UDID SHA1
|lat
+
|tt_udid_sha1
|Location by latitudes lines
+
|Use for send Taptica UDID in SHA1 format
|lat=40.714353
+
|tt_udid_sha1=1ddfad5e4377b8694b5fea2a4c4556e2add9605b
|No
+
|Yes
 
|-
 
|-
  
|Longitude
+
|UDID MD5
|lon
+
|tt_udid_md5
|Location by longitude lines
+
|Use for send Taptica IMEI in MD5 format
|lon=-74.005973
+
|tt_udid_md5=20fbe500c99939adabb4d06600eb4ee7
 
|No
 
|No
 
|-
 
|-
  
|Response Type
 
|rt
 
|JSON=0, XML=1, XHTML=2, types of response
 
|rt=0
 
|No
 
|-
 
 
|Category Name
 
|cat
 
|Specified the offer category (spaces should be replace with %20)
 
|cat=Games,Travel%20and%20Local,
 
|No
 
|-
 
 
|}
 
|}

Revision as of 09:57, 25 June 2013

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:

• 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 Paly or Appstore)

______________________________________________________________________________________________________________________________________________

Tracking With Third Party System

As mention above there are many teaking sulotion in the market and each one of them have diffent device parameters per application. The basic tracking link is:

http://tracking.taptica.com/aff_lsr?tt_cid={tt_cid}&tt_adv_id=xyz&tt_adv_sub={tt_adv_sub}&tt_time={tt_time}

on tope of it there are unique device parameters that send to the traking system upon click and need to be send back to us upon convertion:

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
Conversion Time tt_time The converstion 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= Yes
IMEI MD5 tt_imei_md5 Use for send Taptica IMEI in MD5 format tt_imei_md5= 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= Yes
Android ID SHA1 tt_android_id_sha1 Use for send Taptica Android ID in SHA1 format tt_android_id_sha1= Yes
Android ID MD5 tt_android_id_md5 Use for send Taptica Android ID in MD5 format tt_android_id_md5= 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
IMEI SHA1 tt_mac_sha1 Use for send Taptica Mac Address in SHA1 format (upper case with colon) tt_mac_sha1=fa6bb084ae52461328eb9f06039be222ef287246 Yes
Mac Address SHA1 tt_imei_sha1 Use for send Taptica IMEI in SHA1 format tt_deviceid4=44:2A:60:G5:GE:G5 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=77146852-3E33-46AB-AA04-E207BBAF094B 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
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox