Google Consent Mode:

At a high level, the system should work like this:

Visitor Arrives

↓

Consent Defaults Are Established

↓

Visitor Makes a Choice

↓

Consent Management Platform Records Choice

↓

Consent Signals Update

↓

Google Tags Adjust Behavior

↓

Permitted Measurement Continues

The most important word is adjust.

Consent Mode is about changing technology behavior based on consent status.

What Consent Mode Does Not Do

Before explaining what it does, it helps to understand what it does not do.

Consent Mode does not:

• • create your cookie banner
  • determine your organization’s privacy policy
  • decide which consent categories your company should use
  • replace a consent management platform
  • automatically make a website compliant with every privacy regulation

Those decisions exist outside Consent Mode.

Consent Mode provides a technical mechanism for communicating consent state to supported Google technologies.

The Four Consent Signals Marketing Teams Should Recognize

Consent Mode includes several signals, but four are particularly important to most marketing teams.

analytics_storage

• • Controls storage associated with analytics.

ad_storage

• • Controls storage associated with advertising.

ad_user_data

• • Communicates whether user data related to advertising may be sent to Google.

ad_personalization

• • Communicates whether data may be used for personalized advertising.

Marketing teams do not necessarily need to configure these directly.

They do need to know they exist so they can validate whether their consent management platform and tagging implementation are communicating the expected states.

Basic Consent Mode:

Block Google Tags Until Consent

In a Basic Consent Mode implementation, Google tags are blocked before the user grants the relevant consent.

This is the more restrictive implementation model.

Before consent, the blocked Google technologies do not operate in the same way they would for a consented visitor.

Once the required consent is granted, the applicable tags can load and measurement can begin.

The tradeoff is straightforward.

Stricter blocking can mean less measurement information is available for visitors who do not consent.

Advanced Consent Mode:

Load Google Tags With Restricted Behavior

Advanced Consent Mode works differently.

Google tags may load while consent defaults remain denied.

When consent is denied, supported Google technologies adjust their behavior and do not use analytics or advertising cookies in the same way they would for a consented visitor.

Limited measurements can still be sent without those cookies.

If consent is later granted, the tags can update their behavior accordingly.

This can provide Google with additional information that may support measurement and modeling while continuing to communicate the visitor’s consent state.

The important point is that Advanced Consent Mode does not mean ignoring a denied choice.

It represents a different technical implementation of how supported Google tags behave when consent is denied.

Why Basic and Advanced Matter

The choice between Basic and Advanced Consent Mode can affect measurement.

It can also affect privacy implementation requirements.

That means it should not be chosen casually by an analytics team because one approach appears to produce more data.

Organizations should establish their approved privacy approach first.

The technical team should then implement measurement according to that decision.

Step 1:

Confirm the Consent Management Platform Integration

Most organizations do not manage consent signals manually.

Their consent management platform handles part or all of the integration.

We validate whether the platform is actually communicating consent states to Google technologies.

That includes checking the initial state before the user makes a selection.

Step 2:

Verify the Default State

Timing matters.

Consent defaults need to be established before technologies begin acting on an assumed consent state.

If tags execute before the consent system establishes the appropriate state, data may be collected before the platform has had an opportunity to enforce the intended behavior.

This is why implementation order matters.

Step 3:

Test Consent Updates

Next, we test what happens when the visitor makes a choice.

For example:

• Initial State
  • analytics_storage = denied
• Visitor Accepts Analytics
  • analytics_storage = granted

The exact combination of signals depends on the visitor’s selection and the organization’s configuration.

We verify that those states actually change when expected.

Step 4:

Test Google Tag Manager

Consent Mode and GTM are closely connected for many organizations.

Google tags contain built in consent behavior.

Other GTM tags may need explicit consent requirements.

That means we inspect both:

• the consent state itself
• whether individual tags behave correctly under that state

A correct consent signal does not automatically guarantee that every third party tag in the GTM container is properly controlled.

Step 5:

Validate the Browser

We do not stop at GTM Preview.

We also inspect the browser.

Depending on the implementation, we may review:

• analytics cookies
• advertising cookies
• consent state
• network requests
• tag behavior
• local storage
• session storage

This allows us to compare the theoretical configuration with actual browser behavior.

Step 6:

Test Measurement After Consent

When consent is granted, important measurement still needs to work.

We test:

• page views
• key events
• form submissions
• advertising conversions
• campaign tracking
• other important events

Consent implementation is not complete if privacy controls work but approved measurement is accidentally broken.