Consent Mode

What is Trackingplan

Overview

The Trackingplan Way

Automonitoring

Events

Properties

User Attributes

Pages

Acquisition

Platform Metrics

Automated Alert System

Warnings & Updates

Pixel Monitoring

Privacy Monitoring

Naming Conventions Monitoring

Discover Releases

Data Validation

Digests

Getting Started

Installing Trackingplan

For Websites

Webhooks

For Apps

For ssGTM

Post-Install Warm-Up

Inside Trackingplan

Dashboard

Health Summary

Starred Items

Reports

Data Explorer

Tracks Explorer

Root Cause Analysis

Presence Map

Advanced Reports

Session Finder

Privacy Report

Change History

Settings & Members

Destinations

How to…

Manage Warnings

Mute Warnings

Debug Warnings

Attribution

Customize Warnings

Ensure Privacy

Privacy Report

Cookies & Consent

Consent Mode

Privacy by Design

Marketing Observability

Campaign Validation

Pixels Summary

Enhance Collaboration

Sharing

Notes & Labels

Personalized Digests

Extend detection

Google’s Consent Mode

Google's Consent Mode offers a nuanced approach to handling user consent regarding data collection and usage for advertising and analytics purposes.

These parameters, encompassing consent actions such as "granted," "denied," or "unknown," are vital for ensuring compliance with data privacy regulations.

💡

That’s why Trackingplan seamlessly integrates Google's Consent Mode parameters to ensure you’re not sending tracks to events whose consent for storing information has been denied.

Google’s Consent Mode & Trackingplan

These consent mode parameters will be tracked as attributions in Trackingplan:

gcs (Google Consent State): This refers to the overall state of consent provided by the user.
gcd (Google Consent Data): This refers to the specific data related to user consent. It includes information about which types of data the user has consented to be collected and used.
consent_ad_storage: This relates to the user's consent for storing advertising-related data.
consent_analytics_storage: This refers to the user's consent for storing analytics-related data.
consent_ad_user_data: This refers to the user's consent for the collection and usage of their personal data for advertising purposes.

Within your Google Ads and Google Analytics 4 destinations, you’ll be able to check whether the user has granted permission for their data to be stored in the following Trackingplan’s features:

Trackingplan’s Data Explorer

Google consent mode parameters will be tracked as attributions in Trackingplan’s Data Explorer, offering you a comprehensive view of user consent actions within your analytics ecosystem.

To see them, just click on the “group by” dropdown menu.

You can also use the advanced conditions menu to easily identify specific consent statuses (e.g.: denied).

Trackingplan’s Tracks Explorer

In your Trackingplan’s Tracks Explorer, you’ll also be able to easily see if you’re sending tracks to events whose consent for storing information has been denied.

For it, just use the advanced conditions filter to swiftly pinpoint specific consent actions, such as those where consent has been denied or is unknown, to facilitate proactive management and compliance with Google’s Consent Mode.

Create logical conditions

You can also create custom events or metrics to track those events whose consent has been denied or is unknown with maximum precision. This will allow you to effortlessly stay on top of them in case these start receiving tracks.

On the other way around, you can also create conditionals if, for example, you want any of your properties to be always required as long as their consent is granted.