Help us improve
Share bugs, ideas, or general feedback.
From typo3-skills
Implements GA4 on websites, configures Google tag/GTM measurement, defines events and key events, links AdSense revenue, and provides exact UI steps for privacy-compliant analytics.
npx claudepluginhub starraider/typo3-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/typo3-skills:google-analyticsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to add or repair `GA4`, define a clean event taxonomy, and give the user exact Google Analytics, Google tag, and reporting steps that stay inside a privacy-first implementation.
Guides GA4 property setup, event tracking (automatic, recommended, custom), custom dimensions, BigQuery integration, gtag.js/GTM implementation, reporting, and privacy compliance for web/app analytics.
Installs and manages GTM containers: dataLayer, tags, consent mode, migration from gtag.js. Centralizes Google tags with privacy compliance.
Helps set up, audit, and improve analytics tracking (GA4, Mixpanel, Segment, GTM) with tracking plans, event naming conventions, and data quality checks.
Share bugs, ideas, or general feedback.
Use this skill to add or repair GA4, define a clean event taxonomy, and give the user exact Google Analytics, Google tag, and reporting steps that stay inside a privacy-first implementation.
Pair it with ../google-cmp-adsense/SKILL.md when consent architecture, Consent Mode v2, banner fairness, TCF, or legal-risk framing are in scope. Pair it with ../google-adsense/SKILL.md when the task also includes AdSense approval, ad placement, Auto ads, manual units, or monetization optimization. Pair it with ../google-tag-manager/SKILL.md when the site uses GTM, needs a Google tag inside GTM, or needs trigger/variable/container guidance instead of direct gtag.js.
../google-cmp-adsense/SKILL.md../google-adsense/SKILL.md../google-tag-manager/SKILL.mdUse this skill for prompts like:
Identify:
initial setup, repair, migration, event design, reporting, or privacy hardeninggtag.js, GTM, AdSense, Google Ads, or a CMPshopper sign-up, store owner registration, newsletter, search, login, AdSense revenueEEA + UK + Switzerland plus any regulated U.S. state traffic the user mentionsbasic or advanced consent behaviorIf the page URL is needed for verification, request it before claiming the work is complete.
Default decision tree:
gtag.js unless GTM is already in place or the user explicitly wants GTM. If GTM is in scope, hand the container work to ../google-tag-manager/SKILL.md.basic consent mode by default for the legally safer baseline.advanced consent mode only when the user wants modeled measurement and legal review accepts denied-state cookieless pings.config/sites/<site-id>/ directory.../google-cmp-adsense/SKILL.md before finalizing implementation.Search the codebase for:
gtag(googletagmanagergoogle-analyticsG-googlefcconsentcookieadsbygoogleThen identify:
Use references/account-and-measurement-checklist.md for the exact steps in Analytics and AdSense.
At minimum:
GA4 property and Web data streamEnhanced Measurement should stay enabledkey eventsAdSense if the user wants publisher revenue inside GA4Follow references/implementation-playbook.md.
For a typical site package, start with:
packages/my-site-package/Configuration/Sets/MySitePackage/settings.definitions.yamlpackages/my-site-package/Configuration/Sets/MySitePackage/settings.yamlpackages/my-site-package/Resources/Private/Layouts/Pages/Default.fluid.htmlpackages/my-site-package/Configuration/Sets/MySitePackage/TypoScript/page.typoscriptpackages/my-site-package/Resources/Public/JavaScript/main.jspackages/my-site-package/Resources/Private/Templates/Keep the implementation simple:
page_view and duplicate success eventsIf GTM is the chosen architecture, this skill still owns the event taxonomy and GA4 outcome mapping, but the container-side Google tag, triggers, and consent settings should be implemented through ../google-tag-manager/SKILL.md.
Use references/event-and-key-event-mapping.md.
Default mapping:
sign_upgenerate_leadclose_convert_lead or a second-stage server-side event only if that lifecycle really existsgenerate_leadloginAdSense and GA4, not custom web ad-impression eventsAlways verify:
Realtime and DebugView show the expected eventsGA4 area after linkingFor frontend and e2e checks:
AGENTS.md or equivalent conventions file in the repo)googletagmanager and google-analytics the same way existing tests doSeparate the outcome into:
$google-tag-manager$google-cmp-adsense$google-adsensePII or sensitive data to GA4.ad_impression event for AdSense revenue tracking.