Consent

​

Overview

You can configure how the Converge destinations should behave based on the visitor’s consent preferences.

​

Converge destinations

There are two ways to customize how Converge destinations handle consent: the consent category and the consent mode.

​

Consent category

You can classify Converge destinations into two consent categories: analytics and marketing. Consent is tracked separately for each category.

The consent category can be set under the Consent subtab of the destination Configuration

​

Consent mode

Destinations can send events to the integrations through both the browser and server. You can configure the destination to treat both ways of tracking differently according to the following modes:

• Off (default): No user consent is required for this destination. All events are sent to the destination.
• Browser only: Consent is only applied to events tracked directly in the browser. Server-side events are always sent to this destination.
• On: User consent is required for all events. Events are not sent to this destination if the user has denied consent. If consent was not tracked, events are still sent.
• Strict: User consent is required for all events. Events are only sent to this destination if the user has given explicit consent. If consent was not tracked, events are not sent.