GTM tags are snippets of code or pre-built templates that execute when a trigger fires — sending data to analytics platforms, ad networks, CRMs, and other marketing tools.
Quick Answer
GTM tags are snippets of code or pre-built templates that execute when a trigger fires — sending data to analytics platforms, ad networks, CRMs, and other marketing tools.
Use Community Template Gallery tags over Custom HTML wherever possible — templates are sandboxed and permission-restricted
GA4 Configuration tag must fire before GA4 Event tags — enforce this with tag sequencing
Test every tag in GTM Preview + GA4 DebugView before publishing; never go live without validation
Key Takeaways
Use Community Template Gallery tags over Custom HTML wherever possible — templates are sandboxed and permission-restricted
GA4 Configuration tag must fire before GA4 Event tags — enforce this with tag sequencing
Test every tag in GTM Preview + GA4 DebugView before publishing; never go live without validation
How GTM Tags Works
A GTM tag is the "what" of the GTM system — the action that executes when a trigger condition is met. GTM provides two categories of tags: built-in templates (GA4 Configuration, GA4 Event, Google Ads Conversion Tracking, Google Ads Remarketing, Floodlight, LinkedIn Insight Tag, and dozens more from the Community Template Gallery) and Custom HTML tags (arbitrary JavaScript you write yourself). Each tag is paired with one or more triggers and can be paused, versioned, and tested independently.
Why GTM Tags Matters for B2B Marketing
For B2B marketing stacks, a properly configured GTM container typically includes: a GA4 Configuration tag (fires on all pages, loads the gtag.js library), GA4 Event tags for each key interaction (one tag per conversion type), Google Ads conversion tags for each campaign conversion action, LinkedIn Insight Tag for B2B audience building and conversion tracking, Meta Pixel base code plus event tags, HubSpot tracking code (if not embedded natively), and any vendor-specific scripts like Clarity, Hotjar, or Drift.
GTM Tags: Best Practices & Strategic Application
Best practices: use tag sequencing (Setup Tag and Teardown Tag options) when a tag depends on another tag having fired first — for example, fire the GA4 Configuration tag before any GA4 Event tags. Use tag firing priority for critical tags. Always use the built-in Community Template Gallery before writing Custom HTML — templates are sandboxed and safer. Enable "Once per page" or "Once per event" firing limits to prevent double-counting. Never deploy without testing in GTM Preview mode first.
Agency Perspective: GTM Tags in Practice
A critical mistake in B2B implementations is deploying Google Ads conversion tags without linking them to the correct Google Ads conversion actions. Mismatched conversion IDs result in conversions attributed to the wrong campaign, distorting Smart Bidding optimization. Another mistake is loading heavy third-party scripts (chatbots, session recording tools) via synchronous Custom HTML tags — this blocks page rendering and hurts Core Web Vitals scores. Always defer non-critical scripts.
Frequently Asked Questions: GTM Tags
GTM tags are snippets of code or pre-built templates that execute when a trigger fires — sending data to analytics platforms, ad networks, CRMs, and other marketing tools.
A tag is the code that executes (e.g., "send a GA4 event called demo_request"). A trigger is the condition that activates the tag (e.g., "when the Custom Event 'demo_request_submitted' fires"). Every tag requires at least one trigger. Think of the trigger as the condition and the tag as the action.
Google doesn't publish a hard limit, but containers with more than 200 tags typically see degraded GTM Preview performance and increased risk of tag conflicts. More importantly, each tag adds JavaScript execution overhead. Audit your container regularly, remove unused tags, and consolidate where possible to keep page performance healthy.
No — GTM only controls the container loaded on pages where the GTM snippet is installed. If a third party hosts your landing page or booking tool on a separate domain, they need to install your GTM container snippet or an equivalent tracking tag on their side. Alternatively, use URL parameters passed to the third-party URL and track the click-to-navigate event on your own domain.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes analytics setup for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
