Analytics · Advanced Topics · Google Consent Mode v2

Google Consent Mode allows web and app developers to adjust tag and app SDK behavior based on user consent choices. Onesecondbefore fully integrates Google Consent Mode v2 in their CMP offering.

Supported Google Consent Mode types

Automatic integration with our IAB TCF Consent Wall

In case you use our IAB TCF Consent Wall, we provide an automatic connection to Google Consent Mode. In case a user denies all consent, we set all Google Consent Mode types to 'denied'. In case a user selects to accept all consents, we set all Google Consent Mode types to 'granted'. In case a user wants to manually select (special) purposes and (special) features, we set the Google Consent Mode type to 'granted' only if they accepted the purposes and special features as set below.

Please be advised that Onesecondbefore offers this as a recommendation. Neither the IAB or Google supplied a mapping between the two consent frameworks. If you would like to change the default behaviour, please read on in the next section.

Manual integration of your CMP

In case you use the consent banner of our CMP or a third party CMP, you can use the code examples below to enable Google Consent Mode on your website.

You enable Google Consent Mode in Onesecondbefore with adding the googleConsentMode config parameter to the page tag. The parameter should contain a call to an existing function or an anonymous function that return a JSON object with the Google Consent Mode types set to either 'denied' or 'granted'. The following example contains a configuration with an existing function.

Example

osb('config', {
    accountId: 'act123',
    cookieDomain: 'mydomain.com',
    cookieNamePrefix: '_osb_',
    cookiePath: '/',
    cookieSettings: 1,
    siteId: 'mygreatsite',
    forceGET: false,
    ipSettings: 0,
    userCookieTimeout: 31536000,
    googleConsentMode: (purposes) => {
        return {
            ad_storage: purposes.includes('all') || purposes.includes('advertising') ? 'granted' : 'denied’,
            ...
        }
    }
});

And the example below contains the configuration with an existing function.

function getGoogleConsentMode(purposes) {
    return {
        ad_storage: purposes.includes('all') || purposes.includes('advertising') ? 'granted' : 'denied’,
        ...
    }
}
osb('config', {
    accountId: 'act123',
    cookieDomain: 'mydomain.com',
    cookieNamePrefix: '_osb_',
    cookiePath: '/',
    cookieSettings: 1,
    siteId: 'mygreatsite',
    forceGET: false,
    ipSettings: 0,
    userCookieTimeout: 31536000,
    googleConsentMode: getGoogleConsentMode
});

Default purposes

Below is a list of default purposes that can be expected when using our Consent Bar. Source

IAB TCF purposes

In case you would like to rewrite the default behaviour of the Consent Wall, all purpose and feature names are sent as a string array argument. The table below contains the purpose or feature and the readable name we chose to identify a particular purpose.