audit-analytics

Auditing analytics instrumentation involves detecting your tracking SDK, enumerating user actions within a route, and validating event naming consistency against an existing catalog to report missing events and taxonomy drift without auto-modifying code.

To detect PII in analytics event payloads, scan track call properties for sensitive data like emails, names, passwords, and tokens, then escalate severity and offer user-approved fixes to remove the risky properties from the payload.

Yes, the analytics audit automatically detects common analytics SDKs including PostHog, Amplitude, Segment, Mixpanel, and GA4, as well as wrapped SDKs, to validate tracking events accurately across your front-end routing.

No, you cannot automatically rename inconsistent analytics events during an audit; the process is non-destructive, only producing a structured report and offering safe, user-approved fixes for critical PII gaps and missing MUST-track events.

The best way to check for missing product instrumentation is to perform a surface audit that compares tracked versus untracked user actions within a specific front-end route or feature module and reports coverage gaps.

No, you do not need an existing event catalog to check analytics naming consistency, but when one is available, the audit uses it as the naming convention source to flag verb tense, prefix, and property-shape inconsistencies.