← ClaudeAtlas

google-tag-managerlisted

Design and troubleshoot Google Tag Manager container architecture — tags, triggers, variables, and server-side setups. Triggers on 'set up Google Tag Manager', 'my tags aren't firing', 'GTM container audit', 'add a new tracking pixel', or 'server-side tagging'. Infrastructure layer underneath GA4, Google Ads, and Meta/other pixel tracking.
gmmh1/claude-paid-media-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill gmmh1/claude-paid-media-skills
# Google Tag Manager > **Currency & scope note (last reviewed 2026-07-19):** Platform mechanics referenced here (character limits, campaign-type names, feature availability, thresholds, benchmark figures, policy specifics) reflect general practice as of the review date above and are **not guaranteed current** — ad platforms change quickly. Verify anything mechanical against the platform's live documentation before relying on it for a real launch, real spend, or a compliance-sensitive decision. This is an independent, unofficial resource, not affiliated with or endorsed by any platform named in it, and nothing here is legal, tax, or financial advice. ## Purpose Build and maintain the tag infrastructure that every other tracking skill depends on — GTM is the deployment layer beneath GA4 (`google-analytics-ga4`), Google Ads conversion tracking (`google-ads-measurement`), and any other pixel (Meta, LinkedIn, TikTok) the business runs. ## Trigger Conditions - "Set up Google Tag Manager for my site" - "My tags aren't firing / conversions aren't tracking" - "Audit my GTM container" - "Add a new tracking pixel / tag" - "Set up server-side tagging" ## Required Inputs - Website platform/CMS (affects container installation method) - All tracking destinations needed: GA4, Google Ads conversion tags, Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, other - Existing container status: net-new vs. auditing/fixing an existing one - Consent/privacy requirements affecting tag firing (cookie