Parameters can be used when promoting campaigns

For tracking purpose, you can or may be required to append some parameters to your target URL.

Here are parameters can be used when promoting campaigns:

 

  • General parameters

If you need to pass some parameters that you expect to get back in your callback after each transaction, please use the TID parameters (tid1 to tid6). You can pass whatever you want in those parameters but keep in mind we won’t calculate statistics on those.

However if you would like to pass a specific information on which you expect us to calculate statistics (for example: ad placement, sub-affiliate, page name…), you can use the SUBID parameter.

Name Description Comment
tid1, tid2, tid3, tid4, tid5, tid6 

You can send any value you want in these. It will be stored in Cheetah Media Link database and can be returned in your callback if desired. Examples of data you may want to send: click id, offer id in your system, transaction id…

You can read article about tid here.

The type is VARCHAR 255 and its value needs to be URL encoded
subid

Any value you need to have in Cheetah Media Link statistics. For example: sub-affiliate value. If you need a unique ID that is returned in your callback, please use one of the tid instead.

You can read article about subid here.

The type is VARCHAR 255 and its value needs to be URL encoded

 

  • Automatic parameters

Cheetah Media Link adserver will get the following values from the HTTP headers. However if the call is not made by the end-user device or if the HTTP headers are unavailable for some reason, you will need to pass those values using the following parameters:

Name Description Comment
ip Original IP address of the end user The IP must remain in the dotted format. Example: 46.218.39.170
ua User agent of the end user This has to be URL encoded. Example: Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%205_0%20like%20Mac%20OS%20X)%20AppleWebKit%2F534.46%20(KHTML%2C%20like%20Gecko)%20Version%2F5.1%20Mobile%2F9A334%20Safari%2F7534.48.3
lang Language setting of the end user The value is the two-letters code of the language (iso 3166-1)
headers HTTP headers of the end user. This is the URL encoding of a PHP serialized headers array. Example in PHP: $array=apache_request_headers(); $head=addslashes(urlencode(serialize($array)));

 

  • Unique device information

For tracking purposes, some campaigns may require one of these parameters. Please refer to the campaign description to know more about the tracking solution used.

In any case, if you can provide any of these for your visitors, we highly recommended that you do.

Name Description Comment
macaddress MAC address of the end user device. This can be required for both iOS and Android campaigns.
idfa IDFA of the end user device. This can only be required for iOS campaign.
androidid Android ID of the end user device. This can only be required for Android campaign.
gaid Google Advertiser ID of the end user device. This can only be required for Android campaign.

 

You can read article about promoting a campaign here.

 

Have more questions? Submit a request

Comments

Powered by Zendesk