Skip to main content

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

​
Automatic CMP integrations

Converge automatically detects and integrates with popular Consent Management Platforms (CMPs). When one of these CMPs is present on your page, Converge will automatically read the visitor’s consent preferences and apply them—no additional code required.
This integration handles Converge’s consent tracking. If you’re using Google Ads, GA4, or Microsoft Ads, you’ll also need to implement Google and Microsoft Consent Mode. Read the Implementing Consent Mode guide to learn how to set this up with your CMP.

​
Supported CMPs

The following CMPs are automatically detected and integrated:
Converge automatically integrates with Avada’s cookie consent banner on Shopify stores. The integration:
  • Detects Avada’s consent banner using the Shopify Customer Privacy API
  • Maps analytics and marketing consent from Shopify’s consent framework
  • Updates automatically when visitors change their consent preferences
No additional configuration is needed if you’re using Avada on Shopify.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the Shopify Cookie Banner implementation example in the Consent Mode guide.
Converge automatically integrates with Cookiebot’s consent framework. The integration:
  • Maps Cookiebot’s statistics category to Converge’s analytics consent
  • Maps Cookiebot’s marketing category to Converge’s marketing consent
  • Listens for the CookiebotOnConsentReady event to capture consent updates
No additional configuration is needed if you’re using Cookiebot.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the Cookiebot implementation example in the Consent Mode guide.
Converge automatically integrates with CookieFirst’s consent banner. The integration:
  • Maps CookieFirst’s performance category to Converge’s analytics consent
  • Maps CookieFirst’s advertising category to Converge’s marketing consent
  • Listens for the cf_consent event to capture consent updates
  • Waits for the CookieFirst banner to load before reading consent
No additional configuration is needed if you’re using CookieFirst.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the custom implementation examples in the Consent Mode guide for help integrating CookieFirst with Google Consent Mode.
Converge automatically integrates with CookieYes’s consent banner. The integration:
  • Maps CookieYes’s analytics category to Converge’s analytics consent
  • Maps CookieYes’s advertisement category to Converge’s marketing consent
  • Listens for the cookieyes_consent_update event to capture consent changes
  • Waits for the CookieYes banner to load before reading consent
No additional configuration is needed if you’re using CookieYes.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the CookieYes implementation example in the Consent Mode guide.
Converge automatically integrates with OneTrust’s consent framework. The integration:
  • Maps OneTrust’s category C0002 (Performance) to Converge’s analytics consent
  • Maps OneTrust’s categories C0004 (Targeting) and C0005 (Social Media) to Converge’s marketing consent
  • Integrates with the OptanonWrapper callback to capture consent updates
No additional configuration is needed if you’re using OneTrust.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the custom implementation examples in the Consent Mode guide for help integrating OneTrust with Google Consent Mode.
Converge automatically integrates with Usercentrics’s consent platform. The integration:
  • Maps Usercentrics’s functional category to Converge’s analytics consent
  • Maps Usercentrics’s marketing category to Converge’s marketing consent
  • Listens for the UC_CONSENT event to capture consent updates
  • Waits for the Usercentrics CMP to load before reading consent
No additional configuration is needed if you’re using Usercentrics.
For Google Ads and GA4, you’ll also need to implement Google Consent Mode. See the custom implementation examples in the Consent Mode guide for help integrating Usercentrics with Google Consent Mode.
If you’re using one of these CMPs, you don’t need to manually call the cvg consent method. Converge will automatically detect the CMP and sync consent preferences. However, you can still manually call the consent method if you need to override or supplement the automatic integration.

​
Limitations

The automatic CMP integrations have a few limitations to be aware of:
  • Loading order: The CMP must load and initialize before Converge can read consent preferences. Most integrations include timeout logic (typically 5 seconds) to wait for the CMP to load.
  • Category mapping: Converge only tracks two consent categories (analytics and marketing). Additional categories from your CMP are not captured.
  • Custom configurations: If you’ve customized your CMP category names or structure, the automatic integration may not work correctly. Use the manual consent method instead.
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