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
Working with Google Tag Manager?
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.
What it is
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.
The honest version
No technology is all upside. This is where Google Tag Manager earns its place and where it tends to cause trouble.
Sound familiar?
The Google Tag Manager problems that bring people to us, and what you have once each one is fixed.
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
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
Consent mode is blocking tags that never got the signals they needed, so legitimate pageviews stop reaching GA4.
Consent wired up, data back
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
Universal Analytics, retired pixels and dead Floodlight tags still fire on every page, adding weight and noise.
Container trimmed to what's used
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
Call us for one broken trigger, or hand us the whole container.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
Estimates are free. Describe what is broken or what you want to measure and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: