audit-analytics

To audit analytics instrumentation, you scan a specific route or feature surface to enumerate user actions and report missing-event gaps. This verifies that page views, form submits, and CTA clicks emit correctly named events consistently.

Analytics event taxonomy drift occurs when tracked events deviate from naming conventions or property schemas. You detect drift by validating event names against your project's event catalog, checking for inconsistencies in case, tense, prefixes, and property shape.

To detect PII or secrets leaking into analytics event properties, scan tracked events to flag any email-like, name-like, or secret-like properties. This prevents accidentally shipping sensitive user data to your analytics platform.

Yes, you can audit analytics without an existing event catalog. The process detects the installed analytics SDK in your codebase and uses any available catalog as an optional naming convention source to validate tracked actions.

The best way to verify untracked user actions is enumerating action sites within a feature module's scope. This identifies destructive actions and errors that lack tracking, ensuring all important user behavior emits correctly shaped events.

Inconsistent analytics event property schemas result from taxonomy drift across different developers or features. Auditing your instrumentation validates property shape and types against your event catalog to highlight these schema inconsistencies.