Get Free Audit

Make Consent and Measurement Work Together.

The Problem

  • Tags ignore or misread consent choices
  • Required consent signals are missing or incomplete
  • GA4 and Google Ads behave inconsistently

Our Solution

  • Configure consent-aware tag behaviour
  • Implement the required Consent Mode v2 signals
  • Connect and test consent logic across the Google stack

The Impact

  • Measurement responds correctly to consent status
  • Cleaner communication to Google tags
  • More dependable consent-aware measurement

What We Do for Consent Mode v2

A focused implementation covering the measurement components required for reliable Consent Mode v2 implementation.

  • Consent Signal Mapping

    Configure Consent Mode v2 signals correctly.

  • Consent Mode v2 Configuration

    Connect consent states with GTM behaviour.

  • CMP & GTM Integration

    Map required Google consent parameters.

  • GA4 & Google Ads Behaviour

    Test consent updates across key user states.

  • Consent Testing & Diagnostics

    Document the implemented consent measurement flow.

Track the Actions That Matter for Consent Mode v2.

Measure the key actions and outcomes that support clearer Consent Mode v2 implementation decisions.

Form Submissions

Leads & enquiries

Purchases & Revenue

Sales & values

Bookings

Appointments

Registrations

Sign-ups & registrations

Key Page / Content Views

Important content views

Custom Business Action

Business-specific actions

Works With Your Existing Setup

Platforms & Integrations

We work with the tools you already use.

Other Platforms

Know What’s Covered Before We Start

Our Consent Mode v2 service covers the measurement and implementation work required for Consent Mode v2 implementation. Work outside the agreed measurement scope remains separate.

WHAT WE HANDLE

  • Consent Signal ConfigurationConfigure the required Google consent signals and their default and updated states.
  • CMP IntegrationConnect supported consent-management output to the Google tagging implementation.
  • GTM Consent ControlsApply appropriate consent requirements and behaviour to relevant Google tags in GTM.
  • GA4 Consent BehaviourValidate how GA4 measurement responds to the configured analytics consent state.
  • Google Ads Consent BehaviourValidate the relevant advertising consent signals and Google Ads measurement behaviour.
  • Testing & ValidationTest consent choices and state changes and review available Google diagnostics before handover.
OUR SPECIAL ASSURANCE

15-Day Post-Setup Assurance

Post-setup support designed to give you extra confidence after delivery.

A Clear Process. Reliable Data.

From the initial audit to final validation, we follow a structured process to make sure your tracking is accurate, reliable, and ready for better decisions.

Audit & Understand

Plan & Implement

Test & Validate

Support & Improve

WHY US

Why Businesses Choose Us for Consent Mode v2

Consent Signals Mapped Deliberately

We map the consent states first instead of adding generic settings without understanding the CMP output.

Consent and GTM Work Together

Relevant tags are configured to respond to the consent framework rather than operating as a separate layer.

Google Requirements Kept in Scope

We focus on the Google measurement signals and implementation behaviour required by the agreed setup.

Consent Choices Actually Tested

We test multiple consent states and changes instead of checking only the default page load.

Clear Consent Implementation Handover

You get a clear view of the signals, tag controls and measurement behaviour that were configured.

Structured for CMP Changes

A clear consent implementation is easier to review when the CMP or tagging setup changes.

FAQ

Tracking Questions? We've Got Answers.

Clear answers to common questions about Consent Mode v2 implementation, implementation, validation and support.

What does Consent Mode v2 do?

Consent Mode v2 allows Google tags to adjust their measurement behaviour based on the consent signals provided by your consent-management setup.

Can you connect Consent Mode v2 with my existing CMP?

Yes, when the CMP provides a supported way to expose the required consent states. We review its current behaviour before configuring the Google tags.

Do you configure Consent Mode v2 in Google Tag Manager?

Yes, when GTM owns the relevant Google tags. We map the consent signals and configure the tag behaviour within the existing measurement architecture.

What do you need from my current consent setup?

We review the CMP behaviour, available consent signals, relevant Google tags and access needed to test how consent choices affect measurement.

How do you test Consent Mode v2?

We test relevant consent states and changes, inspect tag behaviour and review available Google diagnostics to confirm the signals are being applied as intended.

Does this service include the cookie banner, consent wording or legal advice?

No. This service covers the technical Consent Mode implementation. CMP selection, consent wording and legal compliance decisions remain with the appropriate privacy or legal stakeholders.

What do you check during a tracking audit?

We review how important actions are measured, where tags and events fire, how conversions are configured, whether values and identifiers are correct, and whether data is reaching the intended platforms without duplication.

How do you verify that tracking is working correctly after implementation?

We test real conversion paths, inspect browser and platform diagnostics where appropriate, validate event parameters and values, and confirm that each important action is being recorded as intended before handover.

What happens after the tracking setup is completed?

After validation, we hand over the completed setup and explain the important measurement points, changes and any actions your team should be aware of.

What if my tracking stops working after implementation?

If something changes or stops working, we can review the issue under the agreed support terms and determine whether it is related to the implementation, website changes or another platform dependency.