Detection Tag - Passive, Interactive
Passive, Interactive mode helps you to understand the bot traffic that is initiating interactive events on your
web properties. This integration type focuses exclusively on events that occur after the page loads, like logging in,
liking posts, playing songs, etc., and it ignores the page loads, themselves.
ci: Customer ID
dt: Tag ID
mo: Tag mode. Value is always
1for Passive, Interactive
pd: Product key, always
accfor Application Integrity
ap: App ID
ck: Cookie ID
dv: Device ID
si: Site ID
ui: User ID
c1 - c10: Custom fields
r1 - r10: Reporting fields
For detailed information on the full set of Detection Tag fields, refer to the Detection Tag Field Index.
<script src="https://s.update.example.com/ag/123456/clear.js? ci=123456 &dt=1234567890123456789012 &mo=1 &pd=acc &ap=com.example.Example <!-- in app only --> &ck=ddeedb6f4adf80dd2d8b0eb81c69da13 &dv=c3f927f4-3ef9-4b53-8887-d794c4daea82 <!-- in app only --> &si=xyz1234 &ui=04a1ad8a40e296df0d385e46c3796cd3 &c1=v123 &c2=x987 &r1=y314"></script>
The tag should be loaded as soon as possible after the form provided via
fi already exists in the page's HTML.
If the HTML of the page is fully rendered on the server-side, then you should place the tag should in the
section of the HTML, and should be loaded synchronously. The
async attribute should not be used. Loading the tag as
early as possible will improve the efficacy of the Detection that the tag provides.
If your website renders HTML on the front-end dynamically, then you should inject the tag only after the form that it will protect has already rendered in the page. The form should already exist in the webpage when you inject the Detection Tag.
2KB ~ 4KB, followed by the main payload that is
~40KB. Postbacks are made one to a
few times, and are generally a few hundred Bytes.