In case anyone needs them:
For a Direct to URL click activity, you can have various campaign tracking information transmitted directly to your server logs (they will be appended to your click URL). You may find this helpful in measuring your campaign performance.
To include these tracking parameters, when creating your ad simply checkYes to “Append tracking parameters to your destination URL”.
You have two options: 1) use standard tracking parameters; or 2) customize the tracking parameters
Option 1: Standard tracking parameters
Use standard tracking parameter names to pass campaign values to your system. Check Yes to “Append tracking parameters to your destination URL”. When a user clicks on your ad, the following information will be transmitted to your servers:
- jtcampaign=<campaign name> (the name of the campaign responsible for the user’s click)
- jtadbundle=<ad bundle name> (the name of the ad bundle responsible for the user’s click)
- jtkeyword=<keyword> (the category or keyword matched from the advertiser’s campaign)
- jt-reqid=<request id> (the unique ID for the ad request)
- jt-handset=<handset name> (the handset/device associated with the ad request)
- jt-publisher=<publisher id> (the publisher ID associated with the ad request)
- jt-query=<search query> (the search query passed by the publisher; if applicable)
- jt-operator= <carrier> (the carrier associated with the ad request)
They append these parameters to your click URL. Example: www.yourclickurl.com?jtcampaign=<campaign name>&jtadbundle=<ad bundle name>& etc, etc
When a user clicks on your ad, the tracking values will be transmitted to your servers.
Option 2: Custom tracking parameters.
Use your own custom tracking parameter names to pass the same campaign values to your system. Check Yes to “Append tracking parameters to your destination URL”. Include your specific custom tracking parameters in the click URL you submit. Associate a Jumptap Replacement String with each of your custom tracking parameters. The eligible Replacement Strings are:
- JT_CAMPAIGN: the name of the campaign responsible for the user’s click
- JT_ADBUNDLE: the name of the ad bundle responsible for the user’s click
- JT_KEYWORD: the category or keyword matched from the advertiser’s campaign
- JT_REQID: the unique ID for the ad request
- JT_HANDSET : the handset/device associated with the ad request
- JT_PUBLISHER: the publisher ID associated with the ad request
- JT_SITE: the site ID (for a given publisher) associated with the ad request
- JT_QUERY: the search query passed by the publisher; if applicable
- JT_OPERATOR: the carrier associated with the ad request
- JT_TIMESTAMP: the time associated with the ad request
Submit your click URL using the following format: http://www.yourclickurl.com?Campaign…er=JT_ADBUNDLE… etc, etc.
For example, say your system uses ‘mycampaign’ and ‘myhandset” as parameter names. The click URL you submit might look like the following: http://www.yourclickurl.com?mycampai…set=JT_HANDSET. When a user clicks on your ad, the tracking values will be transmitted to your servers.
