Stape
Tracking e dados
Alojamento e ferramentas para Google Tag Manager server-side
- To verify
- Free plan
Measure · Google Tag Manager
A messy Google Tag Manager container is one of the most common causes of duplicate data and tags firing without consent. I set up or reorganise your container so every tag has a clear purpose, name and trigger.
In short
I set up and reorganise Google Tag Manager containers on WooCommerce stores. That covers installing the container properly, migrating code scattered across the theme and plugins, naming conventions, consent integration and, where it makes sense, a server-side container. It is for stores whose tags have piled up over time, or that want all tracking in one controlled place.
The same pixel or GA4 tag installed through GTM, a plugin and straight into the theme. Every visit or purchase gets counted more than once.
Tags called ‘Tag 12’ or ‘new test’, versions published with no description. Nobody can tell what changed or safely roll back a mistake.
Triggers firing on page load, before the visitor has made a choice. GTM's consent settings are missing or clash with the CMP.
I start with a full inventory of everything that fires on the site, inside and outside GTM. Then I consolidate tracking into the container, apply naming and folder conventions and tie every tag to the right consent state, testing in preview mode before anything is published.
A list of every active tag on the site, where it is installed, what it sends and whether it respects consent.
Tags, triggers and variables renamed, grouped into folders and stripped of duplicates and leftovers.
Theme code and redundant plugins removed, with the same functions rebuilt inside the container.
Consent settings configured on each tag and tested across the different visitor choices.
A server-side container, for example hosted on Stape, set up for GA4, Google Ads and Meta.
A document covering conventions, user permissions and the procedure for changing and publishing safely.
I review the container, theme code and plugins to map everything the site sends out.
I decide what stays, what goes and what gets rebuilt in GTM, and agree the plan with you before touching anything.
I work in a separate workspace and test every change in preview mode and Tag Assistant.
I publish with version notes, remove redundant code from the site and hand over the maintenance guide.
It can go in through a plugin such as GTM4WP, which also pushes ecommerce data to the data layer, or directly in the theme. I generally prefer the plugin, as it survives theme updates and gives you a data layer already shaped for WooCommerce.
As few people as necessary, each with the right permission level. The account should belong to the store, not to an agency or freelancer, so access isn't lost when a supplier moves on.
No. The web container still collects events in the browser and sends them to the server-side container, which then passes them on to each platform. It is an extra layer, with hosting and maintenance costs worth weighing up.
Tracking e dados
Alojamento e ferramentas para Google Tag Manager server-side
Some links are affiliate links: if you sign up, I may earn a commission at no extra cost to you. It never changes my assessment. How this works

Customer Acquisition
Revenue is the number everyone celebrates: it climbs on the dashboard, it looks good in a board update, and it makes growth…
· 7 min read

Campaign Strategy
Most ecommerce teams have no shortage of website data. What they lack is a method for turning it into decisions. Dashboards fill…
· 7 min read

Campaign Strategy
Every conversion rate optimisation audit produces the same problem: a long list of things that could be improved and no obvious way…
· 7 min read
Book a discovery call. I will take a first look at your container, and at the tags installed outside it, with you.