Home / Services / Tracking and Reporting / GTM
Google Tag Manager, set up once and set up properly
One container, one data layer, every platform fed from the same events — with server-side tagging where it earns its place.
Tag Manager should make tracking simpler. Most containers make it worse: undocumented, duplicated and fragile.
We build clean containers your developer and your next agency can understand.
GTM is one service inside layer 05 of the Growth System. The hub covers the full scope and how it connects.
What usually goes wrong
The patterns we see most often before we are involved.
Tags fire twice
Hard-coded pixels and GTM tags run side by side, doubling conversions.
Nobody knows what is in the container
Years of agencies, no naming, no notes, no versions worth reading.
Everything depends on CSS selectors
A theme update silently breaks conversion tracking.
Consent is ignored
Tags fire before consent, exposing the business to privacy risk.
The work inside GTM
Scoped to what your business needs, not a fixed package.
Audit and rebuild
A clean, documented container or a repaired one.
- Tag, trigger and variable audit
- Naming and folder standards
- Version notes and change log
- Removal of hard-coded tags
Specification and implementation
Reliable events instead of click-scraping.
- Data layer spec by page and action
- Developer or theme implementation
- Lead, call and eCommerce events
- QA in preview and debug tools
Server-side and consent
When accuracy and privacy require it.
- Server-side GTM on your domain
- Consent mode and CMP integration
- Enhanced conversions and CAPI
- Monitoring for tag failures
GTM sits in layer 05 of nine
Highlighted below. We check the layers either side as part of the work, because that is usually where the result is decided.
Outputs you keep
Documented, in your accounts, readable without us in the room.
Container audit
Every tag accounted for, with what to keep, fix or remove.
Clean container
Rebuilt or repaired, with naming standards.
Data layer specification
A document your developer can build from.
Consent and server-side setup
Where warranted, implemented and tested.
How it runs
Three stages, with a review before anything scales.
Audit
Container, hard-coded tags and consent state reviewed against your platforms.
Output: audit and tag plan
Build
Data layer, tags and consent configured; tested in every platform.
Output: published container and documentation
Monitor
Tag health monitored; changes go through a documented process.
Output: monitoring and change log
Is GTM the right next move?
We will say so plainly if another layer should come first.
Good fit
- Multiple platforms need the same events
- Tracking has broken more than once
- You need consent handled properly
Fix something first
- The site has no analytics goals at all
- A single simple form is the only conversion
- No one internally will own changes
Connected services
Start with the parent hub, or follow the layer that concerns you most.
GTM FAQ
Do we need server-side tagging?
Only if tracking loss, accuracy or data control justify the cost. We tell you plainly either way.
Can you work in our existing container?
Yes. We audit, document and repair before we suggest starting again.
Will you need developer access?
For a data layer, someone needs to touch the theme. We can do this on WordPress and Shopify or brief your developer.
How do you handle consent?
Consent mode with your consent platform, tested so tags respect user choices.
Find out what is actually in your container
The free growth plan includes a review of your tags, conversions and consent handling.