Detection Tag - Field Index
This page lists all possible fields that the Detection Tag accepts in different configurations.
App ID - For In-App Mobile, provide the App ID / Bundle ID, and maintain case (do not alter case by changing all to lowercase or all to uppercase).
|Environment||Value to Pass|
Client ID - A static value generated by our system to identify a client. This value is a 6 digit integer.
Cookie ID - An identifier cookie id (or session ID) as defined by client system. This field may be hashed†.
c1 ... c10
These fields will be available in the dashboard, and TLX (transaction level export). Use for low cardinality fields.
Field keys are
Tag ID - static value generated by our system to identify a tag used for a specific integration. A client will typically
have one tag, and therefore one
dt value. Some clients may have more than one tag if there are separate use cases or
need to differentiate for other reasons.
Device ID - For mobile in-app traffic provide Device ID - IDFA (iOS) or AAID (Android).
In cases where user has limited tracking or opted-out, use
Mode - static enum value (
2) per tag placement (i.e. per page / form / button). When this field is excluded
it defaults to
|Mode Value||Integration Type||Description|
||Passive non-interactive||Used for detecting a bot that's not expected to interact (e.g. scraping)|
||Passive interactive||Protecting an interaction (e.g. form submit, button press).|
||Active||Protecting & mitigating an interaction (e.g. form submit, button press). Will depend on the generated and injected session ID, encrypted data token, and payload signals; to be passed to the Mitigation API.|
Product ID - Product ID indicates which product is active. This value is always
acc for Application
r1 ... r10
These fields will NOT be reported in the dashboard. They will only be available in TLX (transaction level export).
Use for low or high cardinality fields. Field keys are
Site ID - An identifier to distinguish between different web properties. If you are deploying the Detection Tag across multiple websites, use a different Site ID for each one.
Note: This field only applies to
spa is ignored.
Single Page Application - When this parameter is set to
1, the tag will expose the SPA interface (
Note: This field is only applicable when there is a user already signed in.
User ID - A unique identifier for the authenticated user, as defined by the client system. This field may be hashed†. This field may be used to detect attacks on particular users. This field is also useful for joinability of records between system generated data and customer data.
†Hashing: Use any consistent hashing algorithm, as long as the same input value results in the same output value each time the hashing function is applied.