hey squad
shall we settle in?

01 · TRK · 02/03

Google Analytics.

Not a default config. Not a GTM copy-paste. A platform aligned on your business.

We audit your GA4 config, clean up the noise, link conversions back to your real business events. The platform delivers readable figures, not a raw board hard to interpret. Tracking becomes the foundation of everything else.

By Jérôme · Strategy & data

Get my GA4 config quotedSee the Brasero mission

02 · OPERATION NOTE · OPS GOOGLE ANALYTICS

Google Analytics, decoded

The field report

Your GA4 figures no longer match what your ERPthe internal management software (stock, invoicing) tells. Conversions show up doubled, some key business eventsthe customer actions we measure never land, or you still haven't migrated your old Universal Analyticsthe previous Google Analytics version config. The weekly report becomes a debate topic rather than a shared reading.

The cost of waiting

A mis-configured GA4 turns into a minefield for every layer above: dashboards, ad platforms, server-side, automation. You build on sand. The opportunity cost: every budget call rests on figures no one trusts.

In black and white

A GA4 config aligned on your real business eventsthe customer actions we measure. A GA4 / ad platforms / ERPthe internal management software (stock, invoicing) consistency that holds over time. The ability to plug a dashboard or a server-side on top without inheriting historical noise.

The manoeuvre

We start by looking at the gap between GA4 and your ad platforms, before touching the config. DataLayerthe site data layer audit, target tagging planthe measurement tooling setup via GTMthe Google tag manager, clean UA migration if needed, BigQuerythe Google dedicated data warehouse export turned on for advanced analyses. No key business event left out of scope.

The lock that breaks

A reliable measurement foundation to plug dashboards, server-side and AI automation on top. A reading that holds up against a prospect audit or an agency change. Budget calls finally rest on data you can defend.

03 · WHAT WE WON'T WRITE IN AN RFP

Google Analytics is a business platform. Not a web tool.

GA4 only serves you if its events are aligned on what your business actually measures. An out-of-the-box standard config delivers traffic, not business numbers. The right question before signing: which 8 to 12 events does your business need to see? If the answer is fuzzy, the right order is to lay the tagging plan first, then the deployment. The dashboard that makes those events readable comes right after.

  • 01

    GA4 / ad platforms consistency

    GA4 conversions finally match what Google Ads and Meta see. No more numbers debate in the meeting. Budget calls rest on a consistent cross-source reading.

  • 02

    Business events over page views

    You measure what pays: quote sent, cart validated, qualified form. No more pollution from vanity events that trigger no decision. The data finally tells your business.

  • 03

    Clean UA → GA4 migration

    If you still drag a UA config, we switch without losing the critical history. Legacy events are mapped, the year-over-year stays preserved, your team does not rediscover data from scratch.

  • 04

    BigQuery export enabled

    You unlock advanced analysis via SQL query and prepare the data lake layer (raw data warehouse) for what comes next. No more GA4 sampling limits on sensitive analyses. The raw data stays with you.

04 · THE MISSION THAT PROVED IT

We tuned it for these clients.

Brasero estate, corporate retreats and weddings in Liège province

Brasero Group

Hospitality & events

24-month GA4 config + tagging plan.

Read the Brasero mission
Ecostal Group team handling a solar panel in their warehouse

Ecostal Group

B2B photovoltaic e-commerce

6-month GA4 + BigQuery export.

Read the Ecostal mission
Amecam Van Conversion, mobile workshop fitted out in Wallonia

Amecam Van Conversion

B2B professional vehicle conversion

3-year B2B funnel tracking.

Read the Amecam mission

05 · THE PLAY-BY-PLAY

Four steps. Four weeks on average. Zero technical debt left.

  1. STEP 01

    We audit the existing config.

    DataLayer audit (the site's data layer) + current tagging plan (measurement tooling setup). GA4 (opens in a new window) vs Google Ads vs Meta Ads vs ERP comparison. We identify missing, duplicated or broken events. Tools: GA4 DebugView, GTM (opens in a new window) (Google Tag Manager) Preview, Tag Assistant.

  2. STEP 02

    We write the target tagging plan.

    Shared tagging plan spreadsheet: 8 to 12 key business events, custom parameters, target conversions. Marketing + exec sign-off before deployment. No mid-flight scope drift. Scope frozen in writing.

  3. STEP 03

    We deploy via GTM alongside.

    GTM (opens in a new window) container versioned, progressive deployment on staging then prod. UA → GA4 migration if needed with history mapping. BigQuery (opens in a new window) (Google's dedicated data warehouse) export turned on. No production freeze on your site.

  4. STEP 04

    We validate 14 days and hand over.

    14-day consistency measurement: GA4 vs ad platforms vs ERP. Notion documentation: tagging plan, event owners, QA procedures. 1-hour handover to your team or your media agency. Full ownership.

06 · THE FLOW AT A GLANCE

The path each business event takes between your site and your reading platforms.

EXISTING AUDITGA4 ↔ Ads gapSITEbusiness eventslead · purchase · signupGTMtagging planclient-sideGA4event collectiontuned conversionsBIGQUERYraw export · analyticsCUSTOM REPORTSexec readoutsUAhistorical migration

GA4 vs Ads gap audit, tagging plan via GTM, GA4 tuned, BigQuery export and custom reports. UA cleanly migrated if still around.

07 · NOT YET FOR YOU IF

Three cases where reworking GA4 is not the top priority.

  • You refuse to touch the existing CMP.

    A reliable GA4 config requires a sound Consent Mode V2 (Google's GDPR framework) behind it, set via your cookie banner (CMP). If the CMP is untouchable, we lose 30 to 40% of the signal and cannot guarantee GDPR compliance on the Belgian DPA side.

  • Your monthly traffic is under 10,000 sessions.

    At these volumes, GA4 statistics turn noisy and calls are made on gut feel more than data. The cost of a tailored config does not pay back. We would rather say it than walk you into the dark.

  • No one on your side will read the numbers.

    If no recurring weekly meeting exists to open GA4 or a dashboard plugged on top, tracking (measurement tooling setup) becomes a forgotten tab. Governance matters as much as config. We only deploy if you actually steer with it.

08 · THE QUESTIONS WE ACTUALLY HEAR

Questions whispered after the second meeting. Honest answers.

The cost is not in GA4 itself, it's in the layers above. An out-of-the-box standard config delivers 60 to 70% of the expected business reading. The rest gets lost in doubled events, ghost conversions, broken consistency with your ad platforms. On media above 50 k€ a year, that gap easily pays back the scoping. The broader agency vs freelance vs in-house debate sits here.

GA4 well-configured with strict Consent Mode V2 (Google's GDPR framework) stays GDPR-compatible on the Belgian DPA side. Matomo and Plausible have solid sovereignty arguments (EU hosting), but they remain less rich in native integration with Google Ads and Meta Ads. For 90% of SMEs in the 5-50 M€ range tied to the Google ecosystem, GA4 stays the right call. Beyond that, Matomo becomes relevant when data sovereignty trumps. On the reading side, Looker Studio dashboards stay the natural complement of GA4.

Not to our knowledge as of late 2026 on GA4 itself. Documented APD sanctions mostly hit the lack of a well-wired Consent Mode, tracking without legal basis, and unframed transfers outside the EU. GA4 properly deployed with strict Consent Mode V2 + IP anonymisation + EU-US transfer agreement holds up. An out-of-the-box config without CMP, however, takes real risks.

Healthy V1 range: 8 to 12 key business events, no more. Beyond that, the tagging plan becomes unmanageable and noise returns. Typical SME e-commerce list: view_item, add_to_cart, begin_checkout, purchase, generate_lead, form_submit, scroll_75, video_play, contact_click, store_locator. Typical B2B list: qualified page_view, document_download, form_submit, demo_request, calendly_booked. The server-side layer that secures what comes back stays the natural complement.

GA4 side: 0 € per month (free from Google up to 10M events / month). BigQuery export side: 50 to 150 € HTVA per month depending on volume. Maintenance: 1 to 2 dev days per quarter to follow GA4 evolutions (Google reshapes the schema 2-3 times a year) and iOS / Chrome changes. If we leave, you keep the Notion doc + GTM access + tagging plan spreadsheet. Consistency with your Google Ads campaigns needs to be held at the same rhythm.

Yes. We do this on 30% of our missions. The rule: who steers the tagging plan and the post-deploy QA. If your existing agency stays pilot, we frame scope and timeline. If they execute our plan, we accompany. We never step on the other agency without saying. The Ecostal mission shows that co-existence held all the way to client ownership.

Field note

GA4 is not a web topic, it is a business topic. As long as the config does not tell your events that pay, the rest follows in noise. We start by listing what your business actually measures, we tune GA4 on top, then we talk dashboards and server-side. With us, it is in that order, never the other way round.

Jérôme · Strategy & data
JérômeStrategy & data · HeySquad

Other sub-services TRACKING & MEASUREMENT

We open your GA4 config. We tell you what your platform does not yet tell.

Get my GA4 config quotedBack to the Tracking & measurement service