Working with Google Tag Manager?

GTM container a mess? We sort it out.

Most GTM containers that reach us have grown in layers, where every agency added a tag and nobody removed one. We work out which tags still matter, which fire twice, and which were silently broken months ago.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

gtm-debug.log

still failing

What it is

Google Tag Manager at a glance

Google Tag Manager, launched October 2012, is a way to deploy and manage tracking tags on a site without editing its code each time. A single container snippet loads once per page, and tags, triggers and variables are published from a web interface.

It supports GA4, Google Ads, Meta Pixel, Floodlight, and custom HTML or JavaScript. Server-side GTM, released in 2020, runs those tags on your own cloud instead of in the visitor's browser, which keeps third-party scripts off their device and gives you more say over what data leaves.

Type
Tag management system
First released
2012
License
Free
Maintained by
Google LLC
Typically used for
Deploying analytics and marketing tags without site code changes, consent management, server-side tracking

The honest version

Google Tag Manager pros and cons

No technology is all upside. This is where Google Tag Manager earns its place and where it tends to cause trouble.

Where Google Tag Manager is strong

  • Deploy without touching site codeMarketing and analytics tags ship through the container, so a tag change no longer waits on a developer release.
  • Version history and rollbackEvery publish is a numbered version with notes, and reverting to a known-good one takes a few clicks.
  • Preview and debug modeBefore anything goes live, you can walk through the site and watch each tag fire or skip in a side panel.
  • Server-side containerTags run on your own cloud, which cuts third-party JavaScript on the page and respects consent before data ever leaves.
  • Templates for the big platformsBuilt-in templates for GA4, Google Ads, Floodlight and Meta Pixel save you writing custom snippets for common vendors.

Where Google Tag Manager bites

  • Easy to fire a tag twiceA pixel that was pasted into the theme years ago is still there when someone adds the same one in GTM, and now every event counts twice.
  • DataLayer timing is fragile on SPAsOn a single-page app the page never really reloads, so pushes that work on a classic site arrive before or after the tag expects them.
  • Server-side setup is non-trivialYou need Cloud Run or similar, authentication between containers, a custom domain, and someone to maintain all of that.
  • Templates ask for broad permissionsMany community templates request access to arbitrary cookies or the full dataLayer, and it is on you to read what they do.
  • Preview mode is brittleStrict cookie policies, cross-domain setups and some browsers block the preview session, so debugging falls back to manual inspection.

Sound familiar?

Common Google Tag Manager problems we fix

The Google Tag Manager problems that bring people to us, and what you have once each one is fixed.

purchase events counted twice

Events are firing twice in GA4

A conversion tag lives in both the theme and the container, or a trigger matches two events for the same action.

One source of truth, verified

conversion_value: undefined

Conversions report zero revenue

A variable reference points at a dataLayer key that isn't populated yet when the tag fires, so the value arrives empty.

Values land on every event

analytics_storage: denied

Traffic disappeared after consent mode

Consent mode is blocking tags that never got the signals they needed, so legitimate pageviews stop reaching GA4.

Consent wired up, data back

container owner: unknown

The previous agency still owns the container

Nobody at your company has admin access, and the login that does belongs to someone who left two agencies ago.

Container back in your account

legacy UA tag still live

Old tags never got cleaned up

Universal Analytics, retired pixels and dead Floodlight tags still fire on every page, adding weight and noise.

Container trimmed to what's used

sgtm 504 gateway timeout

Server-side container is dropping events

The tagging server is undersized, pointed at the wrong region, or missing the custom domain that clients expect.

Server-side running clean

What we do

GTM help, from audit to server-side

Call us for one broken trigger, or hand us the whole container.

Audit
A full read of your container: what each tag does, which still fire, which overlap, and what to remove.
Repair
Duplicate events, missing conversions, broken triggers and variables that resolve as undefined.
Consent
Consent mode wired up to a banner that actually matches what your tags expect, without silently losing data.
Server-side
A tagging server on your own cloud, a custom domain, and the client containers pointed at it.
Handover
Taking ownership from a previous agency, including access, documentation and a tidy version history.
Managed Tech
Ongoing changes, monitoring and a team to call when a tag stops firing, on a retainer.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Google Tag Manager alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Google Tag Manager questions

Something else? Call+1 737 727 7327

Why are my events firing twice in GA4?

Almost always a tag that lives in two places. The GA4 snippet is hard-coded in the theme and the same measurement ID is set up in GTM, or two triggers in GTM match the same click. The fix is to find every place the tag could fire, pick one, and remove the others.

Should we move to server-side GTM?

If you rely on Meta, TikTok or Google Ads conversions and losing them to ad blockers or browser tracking protection hurts, probably yes. If your tracking is light or you are not ready to run a small cloud service, it is overkill. We will tell you which side of that line you are on.

Can you take over our GTM container from a previous agency?

Yes. We get your own Google account made an owner, document what is in there, remove whatever no longer applies, and hand you a container you can read without us.

How do we add consent mode without breaking tracking?

Consent mode only works if the signals from your banner line up with what each tag was built to wait for. We map that out first, add the banner and the GTM wiring together, and verify in preview that denied visitors are respected and granted ones still count.

Why does the Preview mode in GTM not catch our events?

Usually the preview session is being dropped by strict cookie settings, a cross-domain setup or a browser extension. Sometimes the dataLayer push happens before the GTM snippet is on the page. We find which it is and fix the underlying cause.

How much does GTM help cost?

Estimates are free. Describe what is broken or what you want to measure and you get a price before any work starts.

Free estimate

Tags firing twice or not at all?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.