MT/Measurement

Consent Mode v2 · server-side tagging · for agencies · EU

Consent Mode v2 and server-side tagging for agencies, remote across the EU

Agencies bring me in for the layer their team does not want to own: consent, tag management and the data that reaches the bidding. I work as your subcontractor on a white-label basis, so the client relationship stays with you, or I contract directly with your client, whichever you prefer. I work remotely from Croatia and invoice through my own Croatian practice, MT-MEASUREMENT, with EU VAT ID HR18247511346.

  • Available now
  • Remote · CET
  • Croatia (EU)
  • EU VAT ID HR18247511346 · direct invoicing

01What I take on

  • Consent Mode v2, implemented or audited

    All four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) denied by default before any tag, updated the moment the visitor chooses, and the CMP wired into it.

  • Basic or Advanced, decided by the numbers

    Basic as the portfolio standard. Advanced only where traffic clears Google's modelling thresholds: 700 ad clicks over seven days per country and domain for Google Ads, and a thousand daily denied events and a thousand consented users for GA4.

  • Tag gating in Google Tag Manager

    Consent settings on every tag, and triggers that still fire when consent arrives mid-visit. A once-per-page tag blocked at initialisation does not get a second chance, and that is how page views quietly go missing.

  • Server-side GTM and the Google tag gateway

    Built and running in my own environment, with the tag gateway on Cloudflare, not on a client account yet. Said up front.

  • The rest of the layer

    Measurement implementation, GA4 audits and configuration, Google Business Profile and location assets, and reporting systems in Looker Studio.

02How I prove it works

  1. Before a choice

    No tag sends anything; the defaults are in place before the tag manager loads.

  2. After a refusal

    Nothing reaches analytics or ad platforms.

  3. After acceptance

    The page view and the events arrive, each carrying the consent state it was sent under (the gcs parameter), checked hit by hit.

  4. A returning visitor

    The stored choice applies at initialisation, so the first page view is not lost.

  5. The server container

    What leaves for Google and every other vendor is checked on the way out, not assumed.

03Proof you can check

  • This website

    Consent Mode v2 in Basic mode with Google Tag Manager and GA4, tested exactly as above with every GA4 hit intercepted: refusing sends nothing; analytics only arrives with gcs G101; everything allowed arrives with G111.

  • Client work

    On the largest account I worked on at Omnicom Media Group, conversion modelling was genuinely active, not nominally implemented.

  • wot-is-gtm.com, my measurement lab

    Server-side GTM, the Google tag gateway on Cloudflare and consent scenarios on a live WooCommerce test store. Open the lab.

04Questions

Do you work white-label?

Yes. I work as your subcontractor on a white-label basis, so the client relationship stays with you, or I contract directly with your client, whichever you prefer.

Basic or Advanced Consent Mode?

Basic as the standard. Advanced where traffic clears Google's modelling thresholds: 700 ad clicks over seven days per country and domain for Google Ads, and a thousand daily denied events and a thousand consented users for GA4.

Have you run server-side tagging on client accounts?

Not yet. Server-side GTM and the Google tag gateway are built and running in my own environment. I would rather say that now than in the first technical call.

Where are you based, and how do you invoice?

Croatia, working remotely on CET. I invoice directly through my own practice, MT-MEASUREMENT, a Croatian sole proprietorship with EU VAT ID HR18247511346.

Can you also fix the reporting?

Yes. GA4 data quality, conversion definitions, and reporting systems in Looker Studio over Supermetrics and native connectors.

Let's talk
measurement.

mihael.turkalj1999@gmail.com →

+385 99 276 5670 · LinkedIn · GitHub · MT-MEASUREMENT, a Croatian sole proprietorship with EU VAT ID HR18247511346