Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From typo3-skills
Installs and manages GTM containers: dataLayer, tags, consent mode, migration from gtag.js. Centralizes Google tags with privacy compliance.
npx claudepluginhub starraider/typo3-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/typo3-skills:google-tag-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to integrate or repair `GTM`, keep Google tagging centralized, and give the user exact `Tag Manager` instructions that stay compatible with privacy and consent requirements.
Guides Google Tag Manager setup, tags, triggers, variables, data layer implementation, debugging, custom templates, and API automation for web, apps, and servers.
Implements Google CMP for sites using AdSense, Ad Manager, Google Ads, GA4, or GTM. Configures Consent Mode v2 and meets Google-certified CMP requirements for EEA/UK/Switzerland.
Audits Google Tag Manager performance, analyzing container config, tag timing, blocking tags, and Core Web Vitals. Activates on GTM, tag manager, or tag performance mentions.
Share bugs, ideas, or general feedback.
Use this skill to integrate or repair GTM, keep Google tagging centralized, and give the user exact Tag Manager instructions that stay compatible with privacy and consent requirements.
This skill owns:
dataLayer and trigger architectureGTMGTM consent APIs, consent settings, and preview/publish workflowPair it with:
../google-cmp-adsense/SKILL.md for legal-risk framing, Privacy & messaging, TCF / GPP, banner fairness, and deeper Consent Mode v2 compliance questions../google-analytics/SKILL.md for GA4 property setup, event taxonomy, key events, and reporting decisions../google-adsense/SKILL.md for AdSense site approval, ads.txt, Auto ads, manual ad units, blocking controls, and monetization decisionsGTM console actions and publish workflow: references/gtm-console-setup-checklist.md../google-cmp-adsense/SKILL.mdGA4 workflow: ../google-analytics/SKILL.mdAdSense workflow: ../google-adsense/SKILL.mdUse this skill for prompts like:
Identify:
initial setup, migration, repair, audit, consent hardening, or server-side evaluationGTM, direct gtag.js, GA4, Google Ads, Floodlight, AdSense, or a CMPGTM should manage only Google tags or a broader third-party tag stackEEA + UK + Switzerland plus any regulated U.S. state traffic the user mentionsTag Manager console steps, repo-side implementation, or bothIf a live page URL is needed for verification, request it before claiming completion.
Default decision tree:
GA4 and no GTM exists, direct gtag.js may still be simpler. Use ../google-analytics/SKILL.md unless the user explicitly wants GTM.GTM.GTM is in scope, keep it as the single source of truth for the Google tag and related event tags. Remove duplicate in-page Google tag code during migration unless a product-specific exception is documented.GTM is in use, put consent defaults on Consent Initialization - All Pages and use GTM consent APIs, not queued gtag('consent', ...) calls inside the container.AdSense bootstrap or ad units through GTM. Use ../google-adsense/SKILL.md for the publisher implementation path, and use this skill to keep GTM, the Google tag, and consent behavior from conflicting with it.Use references/privacy-and-product-handoff.md when the legal or product boundary is unclear.
Search the codebase for:
googletagmanagergtag(dataLayergooglefcadsbygoogleGTM-G-AW-DC-consentcookieThen identify:
<head> include and <body> opening hookGTM snippet already existsUse references/implementation-playbook.md for repo-specific touchpoints and migration patterns.
Install the GTM snippets once:
<head> as possiblenoscript snippet immediately after the opening <body>Keep dataLayer initialization centralized and predictable. If the site already pushes custom events, prefer explicit dataLayer.push({ event: '...' }) contracts over scattered inline tracking.
If migrating from direct gtag.js:
GTMUse references/gtm-console-setup-checklist.md.
At minimum:
GTMInitialization - All Pages for the Google tag when the tag should load before other business tagsConsent OverviewImportant current behavior:
Google Ads or Floodlight tags can automatically load a Google tag firstFor consent:
Consent Initialization - All PagessetDefaultConsentState and updateConsentState, or a trusted CMP template that uses those APIsad_storage, ad_user_data, ad_personalization, and analytics_storageFor GA4:
../google-analytics/SKILL.md for property setup, event taxonomy, key-event design, and reportingFor Google Ads / Floodlight:
Conversion Linker deliberatelyFor AdSense:
ads.txt, Auto ads, manual units, and monetization tuning in ../google-adsense/SKILL.mdGTM and consent settings from conflicting with AdSenseFor Google's CMP or integrated CMP partners:
../google-cmp-adsense/SKILL.md for Privacy & messaging, TCF, GPP, banner fairness, and legal-risk framingGTMAlways verify:
GTM snippets appear once in rendered HTMLConsent Initialization runs before other tagsConsent Overview is enabled and coherentTag Assistant shows the expected tags and eventsbasic setuppage_view or conversion events existAdditional frontend checks:
TypoScript, Fluid, or shared JS, verify in DDEVAGENTS.md or equivalent conventions file in the repo)googletagmanager, so preserve or extend that pattern when relevantSeparate the outcome into:
GTM console actions the user still must perform$google-cmp-adsenseGA4 items handled by $google-analyticsAdSense items handled by $google-adsenseGTM, Google documentation, or Google certification alone guarantees legal compliance.GTM as a reason to bypass consent or hide tag behavior.gtag('consent', ...) calls inside GTM instead of the Tag Manager consent APIs.GTM installs in place after a migration without an explicit reason.AdSense through GTM when the product-specific docs and site integration path point to direct page integration instead.