​
Overview

You can configure how the Converge destinations should behave based on the visitor’s consent preferences. To set this up, you need to send the consent to Converge.

You still need a CMP, cookie banner provider, or your own solution to collect the preference.

While this allows you to configure how destinations handle consent, regardless of the configured consent, events will still be sent to Converge.

This documentation describes implementing Consent for Converge. It does not implement Google or Microsoft Consent Mode. Read this guide for implementing Google and Microsoft Consent Mode.

The cvg object has a consent method that you can use to send the visitor’s consent preferences to Converge. It takes two arguments, we recommend always sending both.

  • analytics: Preference for analytics tracking. Possible values are granted, and denied. If not set, Converge will assume that the visitor has denied consent.
  • marketing: Preference for marketing tracking. Possible values are granted, and denied. If not set, Converge will assume that the visitor has denied consent.

See the examples below.

You need to make sure the cvg object is available before you call the consent method. If this is not the case, include the following snippet before calling cvg.

window.cvg||(cvg=function(){cvg.process?cvg.process.apply(cvg,arguments):cvg.queue.push(arguments)},cvg.queue=[]);

Consent should be sent every time the user visits the page. Typically, you will rely on your CMP or own cookie banner implementation to retrieve the visitor’s consent and send it to Converge.

Converge stores the consent preferences in the visitor’s browser as a backup. But, to make sure that it is up-to-date, you should still specify it every time the converge snippet loads.

The preferences are also stored on the Converge profile, under the profile_properties. This is used to filter events when forwarding server-side.

When Converge has not received any consent preferences, we will default to denied consent. For that reason, we recommend calling the consent method before the Converge snippet.

Configuring consent before the tracking
<script src="https://static.runconverge.com/pixels/xxxxxx.js" async></script>
<script>
    window.cvg||(cvg=function(){cvg.process?cvg.process.apply(cvg,arguments):cvg.queue.push(arguments)},cvg.queue=[]);
    cvg({ 
        "method": "consent",
        "analytics": "granted",
        "marketing": "granted",
    })
    cvg({method:"track", eventName:"$page_load"});
</script>

The Converge consent can be updated while the visitor is browsing the page. To set a default consent, you can simply call the consent method with the static default preferences — and later on, update them as follows.

Default to granted consent until the visitor denies marketing
cvg({ 
    "method": "consent",
    "analytics": "granted",
    "marketing": "granted",
})

// When the visitor denies marketing
function denyMarketing() {
    cvg({ 
        "method": "consent",
        "analytics": "granted",
        "marketing": "denied",
    })
}

​
Identifiers

The Converge pixel leverages the following identifiers in every setup.

NameMethodDescription
__cvg_uidCookieUnique identifier for the user
__cvg_sidCookieUnique identifier for the current session
__cvg_sessionCookieInformation about the current session. It’s used to ensure consistency of the session properties sent to Converge and to trigger new sessions based on changing tracking parameters.

The following identifiers are only used for specific destinations.

NameDestinationMethodDescription
__cvg_tblcidTaboolaCookieClick ID from Taboola
__cvg_mgidcidMGIDCookieClick ID from MGID
__cvg_sccidSnapchatCookieClick ID from SnapChat
__cvg_awcAWINCookieClick ID from AWIN
__cvg_outbraincidOutbrainCookieClick ID from Outbrain

The following identifiers are only used when Converge consent integration is active.

NameMethodDescription
__cvg_consent_analyticsLocal StorageUser consent for analytics purposes
__cvg_consent_marketingLocal StorageUser consent for marketing purposes