Contact

← Back to use cases

Use case #05

MarTech and data: measure correctly, within the rules

GA4, Tag Manager, Consent Mode v2, BigQuery and Looker Studio Pro: compliant measurement from the first page view, and dashboards teams actually use.

Context

Two settings. On my own projects, including EasyEnd, I set measurement up from scratch. In a large group, I take over an existing ecosystem: accumulated tags, duplicates, multiple owners, and compliance to demonstrate.

Diagram: consent, Tag Manager, GA4, BigQuery, Looker Studio

What I did, step by step

1. Write the measurement plan

Which decisions must be made, therefore which events. Events are named before they are built, not the other way around.

2. One tag container

Centralization in Google Tag Manager, removal of orphan tags, permission management and documentation. One source of truth for tags.

3. Consent first

Consent Mode v2 wired to the consent platform. No tracker before approval; collected data stays usable.

4. Structured GA4

Data streams, custom events, key events, internal traffic filters. Real debugging in the browser, not just in the interface.

5. BigQuery for the real questions

GA4 export to BigQuery and SQL queries when the interface is not enough: journeys, cohorts, joins with other sources.

6. Reporting

Looker Studio Pro rollout and structuring of the MarTech category in the service catalog: tools, permissions, documentation, tracked requests.

Pitfalls and decisions

  • When consent is not replayed at the right moment, the first page of each visit goes unmeasured. I found that defect and fixed it.
  • A keyword-tool export easily overestimates real volume: 3.3 to 4.2 times in one measured case.
  • A dashboard nobody opens costs time and brings nothing. Start from the decision to be made.

Outcome

Compliant measurement from the first page view, tags under control, shared dashboards and tracked requests. Want to know more? Get in touch.

Stack and methods

GA4
Google Tag Manager
Consent Mode v2
BigQuery
Looker Studio Pro
CMP
SQL
← Previous case: Cybersecurity and GDPR: protect without breaking search visibility → Next case: Video and music with AI: Electric Phantom

Facing something similar?

Get in touch