Privacy Pillar and Google Consent Mode

Privacy Pillar integrates with Google Consent Mode!

With Privacy Pillar's integration with Google consent mode, you can manage the privacy compliances of end-users with minimal impact on your domain's ad-based monetization, analytics, and so on. You can indicate through the cookie banner whether consent has been accepted for Analytics and/or Advertising cookies and Google's tags will dynamically adapt by only utilizing cookies of specified categories.

The following Google products support Google Consent Mode.

Note: You can’t implement Google consent mode when using TCF 2.0.
  1. Go to Cookie Banner page.
  2. Under Config, scroll to Google Consent section.
  3. Turn on the “Enable Google Consent Mode” toggle button.
  4. Choose the Consent mode type i.e. “Advanced” or “Basic”.

When you implement consent mode in its advanced version, Google tags load when a user opens the website or app. The tags load the consent mode API and do the following:

  1. Set default consent states. By default, consent may be denied, unless you set your own defaults. While consent is denied, the Google tags send cookieless pings.
  2. Wait for user interaction with the banner and update consent states. Only when a user grants consent to data collection, Google tags send the full measurement data. Learn more about tag behavior.

This implementation enables improved modeling compared to the Basic one as it provides an advertiser-specific model as opposed to a general model. See the link to know more.

  1. Select “Advanced” mode from the Consent Mode dropdown.
  2. Set the default values for the Google consent types i.e. either “Denied” or “Granted” as per your business requirement.
  3. Set the “wait_for_update” time in milliseconds value to control how long to wait before data is sent.
  4. Click on the Publish button. A modal popup appears with GCM default consent script of the Advanced Consent Mode and cookie banner CDN script.

    Additionally, GCM default consent script can be modified and setup according to the user's geographic location.
What is Region-specific behaviour?
Region-specific behavior in Consent Mode allows for different default consent settings based on a user's geographic location, enabling compliance with regional privacy regulations. This means that the behavior of Google Analytics and other tags can be adjusted to comply with specific rules in different areas, without affecting the behavior for other regions. Learn more

When you implement consent mode in its basic version, you prevent Google tags from loading until a user interacts with a consent banner. This setup transmits no data to Google prior to user interaction with the consent banner. When the user grants consent, Google tags load and execute the consent mode APIs. The tags send the consent states to Google in the following order:

  1. Send default consent states.
  2. Send updated consent states.

However, when the user doesn't consent, no data is transferred to Google at all – not even the consent status. Google tags are completely blocked from firing. Consent mode's conversion modeling in Ads is then based on a general model. See the link to know more.

With gTag.js:

  1. Select “Basic” mode from the Consent Mode dropdown.
  2. Then choose “gTag” option from the Basic consent modes dropdown.
  3. Copy your Google tag ID (Measurement ID) and paste it in the “Google Tag ID” field.
  4. Set the default values for the Google consent types i.e. either “Denied” or “Granted”.
  5. Set the “wait_for_update” time in milliseconds value to control how long to wait before data is sent.
  6. Click on the Publish button. A modal popup appears with the GCM default consent script of the Basic Consent Mode and cookie banner CDN script.

With TagManager:

  1. Select “Basic” mode from the Consent Mode dropdown.
  2. Then choose “TagManager” option from the Basic consent modes dropdown.
  3. Copy your Container ID from the Admin tab of your Google Tag Manager account and then paste it in the “Container ID” field.
  4. Set the default values for the Google consent types i.e. either “Denied” or “Granted”.
  5. Set the “wait_for_update” time in milliseconds value to control how long to wait before data is sent.
  6. Click on the Publish button. A modal popup appears with the GCM default consent script of the Basic Consent Mode and cookie banner CDN script.
Make sure that the "GCM Default Consent Script" is the first script in the head tag of your website after that the "Production CDN" script must be the second one.
For best results ensure that scripts are loaded in the following order:
  1. Consent Mode
  2. Privacy Pillar CMP
  3. Google Tag Manager or gtag
Note:
The configuration of Google Consent Mode within Privacy Pillar is supported by our team. For any inquiries or assistance related to the setup and functionality of this integration, please contact our support team (support@privacypillar.com) as the first point of contact. If the issue persists and cannot be resolved by our team, we will advise you on the next steps, including reaching out to Google support if necessary.