Overview
Note for usage
Data postback service provided by AdTracking is available to global ad networks, DSPs, and with postback feature. This article should be used tech or product team from the companies mentioned above.
Solutions for integration
302 short link
Pass the business/device ids to the AdTracking system through 302 redirects.
Click request
TalkingData provides short links for redirects
| Requested from： | Ad Network |
| Method： | GET |
| Example： | https: //lnk0.com/FlIVhg |
(campaign ID and App ID are both hidden in the link)
Parameters
AdTracking attribution system provides precise attribution based on device ids. Ad networks pass the ids of the devices where the clicks take place to the AdTracking system.
|
Parameters |
Description |
Example |
|
idfa |
iOS's idfa，with “-”，plaintext |
458BE47D-7205-4010-BC77-DC6E551EC514 |
|
idfa_md5 |
iOS' idfa calculation MD5，with “-” and in capitals to compute MD5 and then turn it to captitals |
D4C00E03AC3BFAFE392A310E5D35807F |
|
androidid |
Android's AndroidID，original，plaintext |
a2948e662f4b4056 |
|
androidid_md5 |
Android' AndroidID，original in capitals，compute MD5 and then turn to capitals |
ABDCEC144E1BA7513FFC00D6BC87E17C |
|
androidid_md5_1 |
Android's AndroidID，original in lower case，compute MD5 and then turn to capitals |
0C15D7B13A72324DC395C70E8B334AEE |
|
imei |
Android IMEI，original，plaintext |
865790026966473 |
|
imei_md5 |
Android IMEI，original to lowercase，compute MD5 |
e86607bc47b52dc939e71e9edfe09f55 |
|
oaid |
Android OAID，original，plaintext |
5b8176b0ca089434 |
|
advertisingid |
Android advertising ID（AndroidIDFA），original，plaintext |
73af65f4-a06c-44a5-8cc6-f72465ac52ac |
|
advertisingid_md5 |
Android advertising ID（AndroidIDFA），original to uppercase, compute MD5 and then turn to capitals |
D0BD09A1199F89A6B12C4B309ED4710A |
|
callback_url |
postback address parameter, adnetworks can dynamically pass postback address via this parameter. |
http: //TalkingDataDemo/active |
|
adcampaign |
advertising series, combinations of numbers, letters, characters, and simple symbols up to 32 digits. |
双十一广告系列.123-abc |
|
adcreative |
advertising creatives, combinations of numbers, letters, characters, and simple symbols up to 32 digits. |
视频贴图.123-abc |
|
adgroup |
advertising groups, combinations of numbers, letters, characters, and simple symbols up to 32 digits. |
618大促测试组.123-abc |
Please note：simple symbols include：- _ .
For any specific platform, only one of the above-mentioned ids is required to pass to AdTracking to do the precise matching. When the parameter affiliates can provide is not certain, multiple device ids can be passed. When parameters are not available please leave it empty.
302 click example
https:// lnk0.com/FlIVhg?idfa_md5={Your_idfamd5_Here}
or
https:// lnk0.com/FlIVhg?idfa_md5={ Your_idfamd5_Here}&IMP={impressionid}
response
HTTP Status Code: 302
Location: Download page for the promoted App
S2S Integration
Pass the click request and related parameters to AdTracking through requesting server API.
Click request
TalkingData doesn't provide short links for redirects
| Request from： | Ad Network |
| Method： | GET |
| Address： | https: //lnk0.com/FlIVhg?action=none |
Parameters：
Required parameters： or
|
Parameters |
Description |
Example |
|
devicetype |
Device type and version |
iphone,GT-9300 |
|
osversion |
OS |
iphone OS 8_4, Android 4.4.4 或 8_4, 4.4.4 |
|
ip |
device ip |
36.110.87.173 |
|
clicktime |
time of the click，long millisecond UTC time（from Jan 1, 1970 to now in milliseconds） |
1437118969422 |
|
useragent |
的UA data from the browser |
Mozilla/5.0 (iPhone; CPU iPhone OS 8_4 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12H143 Safari/600.1.4 |
|
action |
server integration mark |
none |
Additional parameters：AdTracking attribution system provides precise attribution based on device ids. Ad networks pass the ids of the devices where the clicks take place to the AdTracking system.
|
Parameters |
Description |
Examples |
|
idfa |
iOS's idfa，with “-”，plaintext |
458BE47D-7205-4010-BC77-DC6E551EC514 |
|
idfa_md5 |
iOS' idfa calculation MD5，with “-” and in capitals to compute MD5 and then turn it to captitals |
D4C00E03AC3BFAFE392A310E5D35807F |
|
androidid |
Android's AndroidID，original，plaintext |
a2948e662f4b4056 |
|
androidid_md5 |
Android' AndroidID，original in capitals，compute MD5 and then turn to capitals |
ABDCEC144E1BA7513FFC00D6BC87E17C |
|
androidid_md5_1 |
Android's AndroidID，original in lowercase，compute MD5 and then turn to capitals |
0C15D7B13A72324DC395C70E8B334AEE |
|
imei |
Android IMEI，original，plaintext |
865790026966473 |
|
imei_md5 |
Android IMEI，original to lowercase，compute MD5 |
e86607bc47b52dc939e71e9edfe09f55 |
|
oaid |
Android OAID，original，plaintext |
5b8176b0ca089434 |
|
advertisingid |
Android advertising ID（AndroidIDFA），original，plaintext |
73af65f4-a06c-44a5-8cc6-f72465ac52ac |
|
advertisingid_md5 |
Android advertising ID（AndroidIDFA），original to uppercase, compute MD5 and then turn to capitals |
D0BD09A1199F89A6B12C4B309ED4710A |
|
callback_url |
postback address parameter, adnetworks can dynamically pass postback address via this parameter. |
http: //TalkingDataDemo/active |
|
adcampaign |
advertising series, combinations of numbers, letters, characters and symple symbols up to 32 digits. |
双十一广告系列.123-abc |
|
adcreative |
advertising creatives, combinations of numbers, letters, characters and symple symbols up to 32 digits. |
视频贴图.123-abc |
|
adgroup |
advertising groups, combinations of numbers, letters, characters and symple symbols up to 32 digits. |
618大促测试组.123-abc |
Please note：simple symbols include：- _ .
For any specific platform, only one of the above-mentioned ids is required to pass to AdTracking to do the precise matching. When the parameter affiliates can provide is not certain, multiple device ids can be passed. When parameters are not available please leave it empty.
S2S click example
or
Success response
HTTP Status Code: 200
Location: Tracking link doesn't redirects with this integration
Activation data postback
postback request
| Request from： | TalkingData |
| Protocal： | HTTP |
| Method： | GET |
| Example： | http: //a.adnet.com/track/AdTracking |
Postback parameters
When postbacking, AdTracking can send advertising business ids from mobile networks, like inmobi's impression id，millennniial's goal id, etc.. You only need to implement these parameters in the tracking link. When the device is activated AdTracking will postback related device IDs and business IDs to the adnetworks.
Example：
Request time：
When the TalkingData system confirms that the user who clicked the ad has been activated it will request postback (asynchronous postbacking that takes no more than 5 minutes).
Integration flow
-
Fill in the integration application form provided by the support from AdTracking then sent it to integration@tendcloud.com（please submit only through e-mail）
-
AdTracking integration Team reviews the application and replies with integration date, POC and other details
-
Two sides start testing, during which if anything disrupts the process please send the details to integration@tendcloud.com or call our support.
-
After the integration is successful, the integration team will send a formal mail to notify the network. (It's considered test period before the mail is received and during this period AdTracking is not responsible for any issues in ad campaigns.)
FAQ
Q1. Is it ok if IP, Device type, Os version are not passed with S2S?
No. These parameters are used to check device type and location, to judge if the click data is valid and are also important for detecting fraud. If these are not passed, the system will filter these clicks and won't include them in statistics or attribution system.
Q2. Is it ok to only pass server IP in S2S?
No. If a large number of clicks are coming from the same IP, the system will send you an alert and these clicks might be filtered. And server IPs will affect geostatistics and distort your observation.
Q3. What can be done when adnetworks provide custom parameters that are not on the list?
First of all please describe the parameters provided while filling in the application form and encrypted description should also be provided. Please attached all the necessary docs and wait for the response after the application is sent.
Q4. How to inform AdTracking after the adnetworks update postback address?
If you plan to change your postback address please update the info in the application form and e-mail to integration@tendcloud.com. AdTracking POC will arrange new testing after receiving the mail.
Q5. What should be done when postbacks are not received after the integration is successful?
Please confirm if the server of the adnetwork is stable and contact advertiser to check if there is any update or issues. If not, please contact our support to see if there is a delay.
You may also find the following articles helpful:
- Affise <-> Talking Data Mobile Attribution
- Affiliate Management (Talking Data)
- Parameters for Custom Data Postback (Talking Data)
- Guide For Setting Deeplink (Talking Data)
Published by Tatiana Mankevich
0 Comments