Campaign link parameters
Tapstream reserves several query string parameter keys on campaign links, prepended by
__ts. You can add values to
these reserved keys to improve Tapstream's performance or alter its behavior.
You can also add an unlimited number of other parameters to campaign links. Key-value pairs (sometimes referred to as "sub IDs") that you add at click time to a Tapstream campaign link's query string will be saved, and if a conversion is generated, they will be available via all of Tapstream's APIs and its postback system.
In general, Tapstream forwards all query string parameters to the destination URL.
The following systems expose the query string parameters of conversions. Note that some of these require an upgraded Tapstream account.
- Rollup reports, a dashboard screen that groups conversions by custom parameter
- Postbacks, as
- Conversion API, which shows all custom parameters for every conversion
- Conversion rollup API, which groups conversions by custom parameter
- Onboarding links, which gives your app, via the Tapstream SDK, all custom parameters associated with that app session
- Dynamic redirection, which allows you to dynamically route inbound clicks based on their query string values
Tapstream campaign links can collect any industry-standard mobile device hardware identifier, and use the hardware ID to make conversion decisions.
The following parameters can be added in the query string of your campaign links:
|Query string key||Use|
|The raw, MD5 hash, or SHA-1 hash of the device's WiFi MAC|
|The raw, MD5 hash, or SHA-1 hash of an iOS device's IDFA|
|The raw, MD5 hash, or SHA-1 hash of an Android device's Google Advertising ID|
|The raw, MD5 hash, or SHA-1 hash of an Android device's Android ID|
|The raw, MD5 hash, or SHA-1 hash of an Android device's IMEI or MEID|
Tapstream also reserves the following IDs:
||The advertised app's bundle ID or package name. Used for restricting conversions to installs of a particular target app.|
||The end user device's string-form IP address. Used for server-to-server (asynchronous) click tracking.|
||Set this to
||A Tapstream session. Used for cross-device tracking, among other flows. Only respected if
||Set to |
||Set to any value to tell Tapstream to ignore previous hit sessions. Useful for simulating conversions repeatedly on the same device.|