Detection Tag

The Detection Tag is used to detect and determine whether traffic is bot (e.g. automated). Before setting up the tag, you'll need to decide on the mode you want to run.

Content Security Policy

Refer to the Content Security Policy Instructions to update your Content Security Policy (CSP) to accommodate the Detection Tag.

Modes

Application Integrity can run in three distinct modes with varying integration requirements. Each mode helps to protect you against different types of threats. Only the Active mode requires a server-side integration with the Mitigation API, which provides the capability of handling bot traffic in real time.

Mode 0: Passive, Non-Interactive

The Passive, Non-Interactive mode helps you to understand the bot traffic that is loading pages on your web properties. This integration type focuses exclusively on page loads and ignores subsequent events, like logging in, liking posts, playing songs, etc.

To set up this mode, follow instructions here: Passive, Non-Interactive Setup Instructions

Mode 1: Passive, Interactive

The 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.

To set up this mode, follow instructions here: Passive, Interactive Setup Instructions

Mode 2: Active

The Active mode helps you to understand and mitigate the bot traffic that is initiating interactive events on your web properties. This integration type ignores page loads and focuses exclusively on events that occur after the page loads, like logging in, liking posts, playing songs, etc. In addition, this integration type requires a backend, server-to-server call to the Mitigation API, which provides a bot decision in real-time that you can use to log or take action upon bot interactions.

To set up this mode, follow instructions here: