Analytics and tracking
Fix the events that stopped firing, the double fires, and the properties that went missing.
Tracking breaks with no error message, so an event that stopped firing after a refactor can sit unnoticed until someone questions the funnel.
Check the tracking plan against what the product really sends, then add a test that catches the next break.
Add the events a funnel needs but nobody instrumented
Each event verified arriving with its properties
Add the properties an event needs before it can be segmented
Each property present on a captured event
Fix a tracking event that stopped firing after a UI change
The event captured in a browser check, before and after
Stop an event that double-fires
A single emission proven by a browser check
Align event and property names to one convention
Convention documented, a rule blocks the next divergence
Define the tracking plan as a schema and validate emissions
An invalid event fails in CI rather than in the warehouse
Gate tracking behind consent and prove nothing fires before it
Network capture showing no calls until consent is given
Stitch anonymous and identified sessions
Identity test across the sign-in boundary
Retire events nothing consumes, along with the dashboards reading them
Consumption evidence attached before removal
Put the agent team to work on your backlog
Connect a repository and assign SHIP your first issue. Your first missions are free.