Check Analytics

### Quick judgement A focused and practical skill for auditing Google Analytics (especially GA4 / GTM) usage in a codebase. It follows a clear checklist and outputs a structured “Analytics Audit Report” with severity-tagged findings and event coverage analysis. Best suited for web projects that already use GA/Tag Manager and want a quick implementation health check. ### Key strengths - Targets real-world GA issues: deprecated UA properties, SPA pageview gaps, duplicated scripts, debug mode in production, etc. - Encourages better engineering hygiene: env vars for Measurement IDs, async loading, error boundaries around analytics, TypeScript typings. - Considers privacy/UX aspects such as consent mode and ad-blocker fallbacks. - Produces a well-defined, markdown report that is easy for developers and stakeholders to consume. ### Main risks / limitations - Scope is centered on Google Analytics and GTM; coverage of other analytics providers (Mixpanel, Amplitude, Plausible) is likely shallow and mostly detection-level. - Relies on static code/text inspection (e.g., `gtag`, `dataLayer`, `G-` IDs), so it may miss more dynamic or server-side tracking patterns. - Does not appear to validate correctness of specific event schemas beyond presence/absence and coverage suggestions. ### Recommended scenarios Use this skill when: - You’re inheriting or refactoring a web project and need a quick, structured audit of its GA/Tag Manager setup. - You suspect tracking gaps (especially in SPAs) and want a checklist-driven review before instrumenting more events. - You’re cleaning up legacy analytics implementations (UA remnants, hardcoded IDs, poor loading patterns) and want prioritized recommendations. It is less suitable as a full analytics strategy tool; it’s best treated as an implementation audit helper for existing GA-centric setups.