What the configuration covers
From an audit of the container you already have to a document your own team can read to see what is counted and how. The accounts stay yours.
Audit of the current setup
We review what is already on the site: duplicate tags, legacy counters, goals that measure nothing. The output is a prioritised list of errors.
GTM container structure
One naming scheme for tags, triggers on the dataLayer, variables for parameters, workspaces for changes. A container the next person can actually navigate.
Events and key events
An event map with parameters, split into key and analytical events. Forms are captured on the server response, not on a button click.
Ecommerce
The chain from product view to purchase, with item parameters and protection against a repeated purchase event. We write the specification for your developers.
Links to ad platforms
Google Ads, Search Console and the import of key events into the accounts. The algorithms start learning from real enquiries instead of page views.
Consent mode and server-side
Consent Mode for the cookie banner, and server-side collection where part of the events dies at the blockers. We add it when the losses are genuinely measurable.
Our clients’ results
Reviews
How we work
The number of events is not a measure of quality. Thirty events nobody looks at are worth less than eight that decisions are made on.
Fewer events, more meaning
We measure what you actually respond to with budget decisions. The rest is either not collected or kept for reference without being marked as a key event.
Changes in the container, not in the code
As long as a task can be closed in GTM, the site stays untouched. We edit code only where correct data is impossible without a dataLayer, and always together with your developers.
Every event is verified by hand
We walk the journeys ourselves: DebugView, preview mode, the realtime report. A green tag is not proof that the event arrived with the right parameters.
Request a consultation or audit
What correct measurement gives you
GA4 data does not stop inside GA4: it goes to the ad platforms as a training signal and into reports as grounds for changing budgets. A faulty tag does not stay a reporting problem — it starts steering bids.
Advertising learns from the right signal
When the key event is a genuine enquiry, Google Ads looks for people similar to those who really got in touch. When it is a button click, the algorithm looks for people who like clicking.
A container that can be handed over
Consistent naming, a note on every version, the event map as a document. The next contractor starts with the work rather than with excavation.
Accounts and history stay yours
GA4 and GTM are registered to your company. If our work together ends, the data, the configuration and the access remain where they are.
How we set measurement up
The event map comes first, the tags second. A container built the other way round turns into a landfill nobody dares delete anything from.
Audit and access
Event map
Implementation in GTM
Verification and handover
Additional services
Google Ads
Targeted advertising
Display network banner advertising
Call tracking
YouTube advertising
Frequently asked questions about GA4 and GTM
The questions that come up before the work starts.