What analytics tagging is
Tags are the snippets that send data from your site to analytics and ad platforms. A tag manager such as Google Tag Manager or Adobe Launch loads them according to triggers and rules, so changes don't need a code release.
Where tagging goes wrong
- Publishing more than you meant to. In GTM, publishing a workspace ships everything in it. Read: Your GTM Hotfix Went Into the Default Workspace. Here's What Else Ships With It.
Spot it: a tag or trigger changes on the live site right after a quick fix, and nobody remembers changing it. Confirm it: open the workspace's changes list. It isn't a summary, it's the full list of what the next publish ships. Fix it: revert or finish anything in Default you can't explain, stop building in Default, and keep one workspace empty so the next hotfix ships alone.
- Trackers that bypass the tag manager. Hardcoded scripts and vendor SDKs never pass through it, so consent gating can't see them. Read: The Trackers That Never Pass Through Your Tag Manager
Spot it: the page talks to analytics or ad domains that no tag in your container accounts for. Confirm it: open the site in a private window, decline the banner, reload with the browser's network panel open and list every third-party hostname across two or three pages. Anything your container doesn't explain came from somewhere else. Fix it: route each one through the tag manager, block it by vendor in the consent platform if it supports that, or remove it if nobody can say what it's for.
- Platform migrations. The Google tag replacing the GA4 Configuration tag. Read: The 2026 GTM → Google Tag Migration: An Agency's Calm Upgrade Checklist
Spot it: recorded conversions dip some weeks after an automatic upgrade, or a Google product starts receiving data through a tag you never edited. Confirm it: compare the Google tag's destinations and settings in GA4 and Google Ads with what your container expects. Those can be changed outside GTM. Fix it: audit the container before you upgrade, test the change in a separate workspace, and keep the previous version ready to roll back.
- No record of what changed. Read: Your Vendor Changed 200 Things On Your Site. Can Anyone Produce The List?
Spot it: someone asks what changed on the site last quarter and the answer has to be pieced together from memory. Confirm it: read your tag manager's version history. If the names say "fix" or "update" and nothing about why, the record you need doesn't exist. Fix it: keep two records: a short written log made at the moment of each change (date, person, what, why), and a scheduled scan of what the site actually loads.
Recognize your own container here? Our tag management service covers container builds and takeovers, with QA on every deployment.
Monitoring: catching it in hours
- Monitor the monitor. A quiet week and a dead monitor look the same. Read: Nobody Monitors The Monitor
- One incident, not nine alerts. Read: Nine Alerts, One Incident and Seven Alerts, One Problem
If nobody watches your tags today, our tag management service includes 24/7 monitoring, so you know when tracking breaks before your client does.
Sitewide tagging: a setup checklist
Sitewide tagging means the Google tag or Google Tag Manager on every page of your site, setting first-party cookies so Google Ads can match a later conversion to the ad click. Google Ads only collects data on pages where the tag is deployed (Google: sitewide tagging). Every check below comes from Google Ads Help.
- On every page, in the head. Use the full JavaScript tag, not the image-pixel version.
- One Google tag or GTM container per page. Remove legacy conversion tags from converting pages so conversions aren't counted twice.
- No iframes, no piggybacking. Don't load the tag inside an iframe or through another tag such as Floodlight. Those fire from another domain, so the cookies aren't first-party.
- Auto-tagging on, and the gclid survives. Check that redirects on your landing pages don't strip the gclid parameter from the URL.
- Conversion linker on all pages if you use Google Tag Manager.
- Same domain, or cross-domain tracking. If people convert on a different domain from the landing page, set up cross-domain tracking and a sitewide tag on each domain.
- Labels and names match exactly. Conversion labels, event names and parameters must match what Google Ads expects, and an action that should count in reporting and bidding needs to be set to Primary.
- Verify, then wait. Click through the site with Tag Assistant, run Tag Diagnostics, and check the console for CORS errors. After a fix, allow 24 to 48 hours for the status in Google Ads to update.
Auto-tagging and naming
Ad platforms append click identifiers to landing page URLs, such as Google Ads auto-tagging's gclid, so analytics can join a visit to the ad click. Keep auto-tagging on and keep manual UTM naming consistent, so channel reports don't split one campaign into several rows.