analytics-event-tracking

Define stable milestone events using Object:Action names like checkout:started and order:completed, then place contextual details such as device, plan, and experiment variant in event properties. Instrument these events explicitly in code rather than relying on autocapture.

Use the Object:Action format, for example sign_up:completed or product:added_to_cart. Avoid unstructured names like UserClickedRegister or addToCart, which make filtering and funnel analysis unreliable.

Yes, the taxonomy principles apply to PostHog, Segment, Mixpanel, Amplitude, and Google Analytics. The Skill detects your existing analytics tooling and maps the conventions to it without forcing a stack migration.

Generate a random anonymous_id stored in cookies for pre-login events, then call identify or alias at sign-in to link it to the backend user_id. The analytics engine merges both behavioral streams into one funnel.

Do not use behavioral event tracking for application performance monitoring, database query logging, or server exception handling. Those belong to observability and APM tooling such as OpenTelemetry traces, not product analytics events.