This set builds vocabulary for tracking, testing, and analyzing product usage data.
0 / 5 completed
1 / 5
At standup, a dev mentions tracking the sequence of pages and actions a user takes before completing a signup. What is this analysis technique called?
Funnel analysis tracks the sequence of steps, like page views or button clicks, a user takes toward a defined goal such as completing signup, revealing exactly where users tend to drop off along the way. This turns raw event data into an actionable view of conversion performance. Product analytics platforms like PostHog are built around making this kind of analysis quick to set up.
2 / 5
During a design review, the team wants to test two versions of a signup button and measure which one converts better. Which capability supports this?
A/B testing, or feature experimentation, randomly assigns users to different variants, like two button designs, and measures which one performs better against a defined metric such as conversion rate. This gives the team data-driven evidence rather than relying on subjective preference. Product analytics platforms typically bundle this experimentation capability alongside their event tracking.
3 / 5
In a code review, a dev adds a call that fires a custom named event, like "checkout_completed," along with structured properties describing the order. What does this represent?
Custom event tracking fires a named event with attached properties, like order value or item count, giving the analytics platform structured data beyond generic pageviews. This lets the team later query and segment behavior around meaningful business actions rather than just navigation. Deciding which events and properties to track deliberately is a key part of setting up useful product analytics.
4 / 5
An incident report shows a critical conversion metric was miscalculated because an event was fired twice due to a duplicate tracking call. What practice would prevent this?
Validating event tracking implementation, such as confirming an event fires exactly once per user action during testing, catches duplicate or missing calls before they silently corrupt a reported metric. Skipping this verification is how a duplicated event can inflate a conversion number without anyone noticing until it's questioned later. This testing discipline is essential once metrics are used to drive real product decisions.
5 / 5
During a PR review, a teammate asks why the team tracks structured custom events instead of relying only on generic pageview counts. What is the reasoning?
A generic pageview count shows that a page was visited but not why or with what outcome, while custom events with attached properties capture specific, meaningful actions like a completed purchase along with relevant context. This richer data is what enables funnel analysis and experimentation to be tied to actual business outcomes. Pageviews alone are a much blunter signal for driving product decisions.