Skip to content
Google Consent Mode

Google Consent mode

CookieHub provides integration with Google Consent Mode, a feature that enables advertisers to measure analytics and conversions more effectively while respecting user consent choices for ad and analytics cookies.

With CookieHub's integration with Google Consent Mode, Google tags supporting Consent Mode can automatically adjust their behavior based on signals from CookieHub, which determine whether or not the user has given permission to use cookies for advertising or analytical purposes. This means that you can use Google tags without making any changes to your scripts, while ensuring that your website remains compliant with data privacy regulations and respects user consent choices.

By using CookieHub's integration with Google Consent Mode, you can provide a seamless user experience for your website visitors while also gaining valuable insights into your website's performance.

What is Google Consent mode?

Google Consent Mode is a feature of Google's advertising and analytics products that enables advertisers and publishers to comply with data privacy regulations such as the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

Google Consent Mode works by allowing users to specify their consent preferences for tracking and analytics before any data is sent to Google's servers. When a user visits a website or app, the website or app owner can request the user's consent for tracking and analytics by using a Consent Management Platform (CMP) like CookieHub.

Once the user's consent preferences have been obtained, Google Consent Mode uses that information to determine which Google tags should be loaded on the page. This ensures that only tags that have been authorized by the user are loaded, and that data is only sent to Google for authorized purposes.

Google Consent Mode supports a range of advertising and analytics products, including Google Analytics, Google Ads, and Floodlight. By using Google Consent Mode, website and app owners can ensure that they comply with data privacy regulations, while still being able to gather valuable insights about their users and deliver personalized advertising experiences.

How does it work?

Google Consent mode operates by passing an additional parameter to requests made to Google's servers, which indicates whether or not the user has provided consent for ad personalization. This parameter is sent with requests for ads, analytics, and other services that require consent.

When a user first visits a website, the Google Consent mode parameter is not set, which means that the user has not yet provided consent. In this case, Google will still receive a limited amount of information about the user, including their IP address and the URL of the page they're visiting.

Once the user has provided consent, either by explicitly accepting cookies or by selecting a preference in a preference center, the Google Consent mode parameter is updated to reflect the user's choice. This parameter is then sent with all subsequent requests to Google's servers.

Google Consent mode also supports a "wait for consent" mode, which delays the sending of requests to Google until the user has provided consent. This can be useful for preventing tracking or data collection before the user has given their explicit consent.

Overall, Google Consent mode provides a way for websites to comply with data privacy regulations while still allowing for effective tracking and analytics. By passing an additional parameter to Google's servers, it allows for more granular control over the data that is collected and shared.

Google Tag Manager

Google Consent mode can be easily integrated with Google Tag Manager (GTM) using the CookieHub Google Tag Manager template. When Google Consent mode is enabled, GTM will automatically add the appropriate Consent mode headers to all tags that support it, including Google Analytics, Google Ads, and Floodlight.

For tags that don't have built-in support for Consent mode, additional consent can be configured in GTM by selecting the correct cookie category and modifying the firing triggers accordingly.