GA4 Event Taxonomy Linter
Validates GA4 event names against official taxonomy, lints UTM parameters for syntax and best practices, and automates QA checks for tracking code. Analytics engineers and marketers use it to detect naming errors and parameter issues before pushing to production. Applies to campaign tracking setups, event instrumentation reviews, and data pipeline audits.
Overview
The GA4 Event Taxonomy Linter MCP server performs validation of Google Analytics 4 event names, UTM parameter linting, and automated quality assurance for tracking implementations. It checks compliance with GA4's official event taxonomy and UTM standards, identifying issues like invalid event names, malformed parameters, or tracking misconfigurations.
Key Capabilities
- GA4 event naming validation: Scans event names and parameters against GA4's predefined taxonomy to flag non-standard or deprecated usages.
- UTM linting: Parses UTM parameters (utm_source, utm_medium, etc.) for correct formatting, valid values, and adherence to Google recommendations.
- Tracking QA automation: Runs comprehensive checks on tracking snippets, gtag calls, or GA4 configurations to ensure data flows correctly without errors.
Use Cases
- Before deploying a new e-commerce site, validate all add_to_cart and purchase event names using GA4 event naming validation to match taxonomy requirements.
- Audit campaign links by running UTM linting on a batch of URLs to catch inconsistencies like uppercase sources or missing mediums.
- In a marketing team's weekly review, apply tracking QA automation to test tag manager containers and confirm no event drops occur.
- During migration from UA to GA4, systematically lint existing events to resolve taxonomy mismatches.
Who This Is For
Analytics engineers maintaining GA4 properties, marketing analysts managing UTM-tagged campaigns, and developers instrumenting client-side tracking code. Teams focused on data quality in web analytics workflows benefit most.