Customize the Google Consent Mode 'update' event mapping

Before you start

• You'll need admin access to Configuration > CMP Settings.
• You should be comfortable editing JavaScript and adding it to your page or tag manager.
• For the custom-service and multiple-services scripts below, you must deactivate the Google Consent Mode toggle in Configuration > CMP Settings first. This stops the banner from firing its own consent update event, which would otherwise conflict with your custom script.

Default mapping

Usercentrics CMP maps the values of the consent update event as follows:

The other Google consent-related storage types, (functionality_storage, personalization_storage, and security_storage) are not updated by the native Usercentrics mapping. You can update these separately using a custom event listener.

Set up a custom event listener

1. Deactivate the Google Consent Mode toggle in Configuration > CMP Settings, if you haven't already.

   

2. Go to Implementation > Data Layer & Events and create a new window event.

   

3. Add the event listener script (examples below) to your page, ideally before the banner script loads.

Remap to a custom service

To base a consent signal on a single service, replace SERVICE NAME with the service name exactly as it appears in the Usercentrics Admin Interface and the dataLayer event. This can be a predefined or custom service.

If a parameter is not needed for your setup, remove it from the serviceMap object.

For this setup, deactivate the Google Consent Mode toggle in Configuration > CMP Settings. This prevents the native Usercentrics mapping from sending a second consent update event.

<script>
   window.addEventListener("ucEvent", function(e) {
    // Only proceed if event exists, is a consent update, and is explicit
    if (e.detail && e.detail.event === "consent_status" && e.detail.type.toLowerCase() === 'explicit') {

        // Map GCM v2 keys directly to your CMP service names
        var serviceMap = {
            ad_user_data: 'SERVICE NAME',
            ad_personalization: 'SERVICE NAME',
            ad_storage: 'SERVICE NAME',
            analytics_storage: 'SERVICE NAME',
            functionality_storage: 'SERVICE NAME',
            personalization_storage: 'SERVICE NAME',
            security_storage: 'SERVICE NAME'
        };

        // Build the consent update object dynamically
        var consentUpdate = {};
        Object.entries(serviceMap).forEach(([consentSignal, serviceName]) => {
            if (serviceName && e.detail.hasOwnProperty(serviceName)) {
                consentUpdate[consentSignal] = e.detail[serviceName] ? 'granted' : 'denied';
            }
        });

        // Update Google Consent Mode if at least one category exists
        if (Object.keys(consentUpdate).length > 0) {
            gtag('consent', 'update', consentUpdate);
        }

    }
});
</script>

Note: ad_user_data and ad_personalization are listed separately because this script lets you map each one to a different service if you choose to. In the default Usercentrics mapping, both follow the value of ad_storage.

Remap to update privacy parameters / storage types only

The native Usercentrics mapping does not update the following Google storage types:

• functionality_storage
• personalization_storage
• security_storage

You can use a custom event listener to update these parameters based on Usercentrics consent.

To base a consent signal on a single service, replace SERVICE NAME with the service name exactly as it appears in the Usercentrics Admin Interface and the dataLayer event. This can be a predefined or custom service.

If a parameter is not needed for your setup, remove it from the serviceMap object.

Keep the native Google Consent Mode mechanism active in Configuration > CMP Settings. The custom script should contain only these three parameters. Adding the other Consent Mode parameters would cause the native and custom scripts to send overlapping update events, which can affect tracking on Google products.

<script>
   window.addEventListener("ucEvent", function(e) {
    // Only proceed if event exists, is a consent update, and is explicit
    if (e.detail && e.detail.event === "consent_status" && e.detail.type.toLowerCase() === 'explicit') {

        // Map GCM v2 keys directly to your CMP service names
        var serviceMap = {
            functionality_storage: 'SERVICE NAME',
            personalization_storage: 'SERVICE NAME',
            security_storage: 'SERVICE NAME'
        };

        // Build the consent update object dynamically
        var consentUpdate = {};
        Object.entries(serviceMap).forEach(([consentSignal, serviceName]) => {
            if (serviceName && e.detail.hasOwnProperty(serviceName)) {
                consentUpdate[consentSignal] = e.detail[serviceName] ? 'granted' : 'denied';
            }
        });

        // Update Google Consent Mode if at least one category exists
        if (Object.keys(consentUpdate).length > 0) {
            gtag('consent', 'update', consentUpdate);
        }

    }
});
</script>

Remap multiple services

Alternatively, you can use an event listener to map multiple custom Usercentrics consents to Google consent parameters.

For this setup, deactivate the Google Consent Mode toggle in Configuration > CMP Settings. This prevents the native Usercentrics mapping from sending a second consent update event.

window.addEventListener('ucEvent', e => {
  const c = e.detail;
   // Only proceed if c exists, event is 'consent_status', and type is explicit
  if (c && c.event === 'consent_status' && c.type && c.type.toLowerCase() === 'explicit')
    gtag('consent', 'update', {
      ad_storage: (c["TikTok Advertising"] && c["Reddit Advertising"]) ? 'granted' : 'denied',
      functionality_storage: (c["Live Chat"] && c["Customer Support Tools"]) ? 'granted' : 'denied'
    });
});

This pattern can be reused for any Google consent parameter by changing the consent names and the corresponding parameter.