Skip to content

Quiz: Analytics and Data-Driven Decisions

Test your understanding of product analytics, user behavior tracking, funnel and cohort analysis, dashboard design, data visualization, and data governance with these review questions.

1. What is the primary distinction between product analytics and web analytics as described in the chapter?

  1. Product analytics focuses on in-product user behavior while web analytics encompasses the broader digital traffic ecosystem
  2. Product analytics uses paid tools while web analytics relies on free platforms like Google Analytics
  3. Product analytics tracks individual users while web analytics only tracks anonymous sessions
  4. Product analytics is used by engineering teams while web analytics is used by marketing teams
Show Answer

The correct answer is A. The chapter explicitly states that "product analytics focuses on in-product behavior" while "web analytics encompasses the broader digital ecosystem: how users find your product, which marketing channels drive traffic, how landing pages perform, and where visitors go after arriving at your site." The distinction matters because they answer different questions: web analytics tells you whether you are attracting the right audience, and product analytics tells you whether those users find value once they arrive.

Concept Tested: Product Analytics / Web Analytics

2. Which metric measures the ratio of daily active users to monthly active users and indicates how often users engage with a product?

  1. Rolling retention
  2. Churn rate
  3. Stickiness (DAU/MAU)
  4. Bounce rate
Show Answer

The correct answer is C. The chapter lists stickiness (DAU/MAU) as a common retention metric defined as the "ratio of daily active users to monthly active users, indicating how often users engage." A higher DAU/MAU ratio means users return more frequently within a month. This differs from rolling retention (users returning within a window), churn rate (users leaving), and bounce rate (a web analytics metric for single-page visits).

Concept Tested: Retention Metrics

3. A SaaS product starts the month with 2,000 customers and loses 80 during that month. What is the monthly churn rate?

  1. 2%
  2. 4%
  3. 8%
  4. 6%
Show Answer

The correct answer is B. The chapter provides the churn rate formula: Churn Rate = (Customers Lost During Period / Customers at Start of Period) x 100. Applying this formula: (80 / 2,000) x 100 = 4%. The chapter emphasizes that even seemingly small monthly churn rates compound dramatically over time. Using the chapter's example as a reference, a 5% monthly churn means losing roughly 46% of customers annually, so a 4% rate would also represent significant annual customer loss.

Concept Tested: Churn Rate

4. Why does the chapter recommend that PMs use the term "data-informed" rather than "data-driven" in some contexts?

  1. Because most product teams lack the data infrastructure to be truly data-driven
  2. Because regulatory requirements like GDPR limit the amount of data PMs can legally collect
  3. Because data-driven implies ignoring qualitative research and relying exclusively on quantitative metrics
  4. Because it emphasizes that data is one input alongside user research, market knowledge, and product intuition
Show Answer

The correct answer is D. The chapter notes that "some practitioners prefer the term 'data-informed' over 'data-driven' to emphasize that data is one input into decisions alongside user research, market knowledge, strategic context, and product intuition." This framing acknowledges that data has limitations: it shows what is happening but not why, it reflects the past, it can mislead through bias, and not everything valuable is measurable. The best PMs use data to sharpen their instincts, not replace them.

Concept Tested: Data-Driven Decisions

5. You are examining a SaaS signup funnel where the largest proportional drop-off occurs between email verification and onboarding completion (50% drop-off). What type of analysis are you performing, and what should your next step be?

  1. Cohort analysis; segment users by signup date to see if the drop-off is improving over time
  2. Funnel analysis; investigate whether the onboarding is too complex or unclear for new users
  3. Retention analysis; calculate the DAU/MAU ratio for users who complete onboarding
  4. Web analytics; examine bounce rates on the onboarding landing page
Show Answer

The correct answer is B. The chapter describes funnel analysis as measuring "how users progress through a predefined sequence of steps toward a conversion goal, identifying where and why users abandon the process." The example SaaS funnel in the chapter shows the same scenario, with 50% drop-off at the onboarding step. The chapter then suggests investigating: "Is the onboarding too complex? Are users confused about what to do next? Does the onboarding require information users don't have readily available?"

Concept Tested: Funnel Analysis

6. When reviewing a retention cohort table, you notice that Week 1 retention improves from 45% to 55% across four successive weekly cohorts. What does this trend indicate?

  1. The product's overall user base is growing at approximately 10% per month
  2. Newer users are inherently more engaged than older users due to changing market demographics
  3. The team should stop investing in retention improvements since the metric is already improving naturally
  4. Recent product changes are having a positive impact on early retention for new user cohorts
Show Answer

The correct answer is D. The chapter provides this exact scenario in its cohort analysis example, showing Week 1 retention improving from 45% to 55% across successive cohorts, and states this is "a strong signal that recent product changes are having a positive impact on early retention." The chapter emphasizes that without cohort analysis, this trend would be hidden because "older cohorts with lower retention would drag down the average." Reading down a column in a cohort table reveals whether product improvements are working.

Concept Tested: Cohort Analysis

7. A stakeholder requests that you add detailed behavioral tracking for a feature used by customers across Europe. Which GDPR requirement must you address before implementing this tracking?

  1. You must open a physical office in the European Union before collecting any user data
  2. You must delete all existing user data before implementing any new tracking capabilities
  3. You must obtain explicit consent or establish a legitimate interest basis before collecting analytics data from EU residents
  4. You must restrict the feature to non-EU users until a Data Protection Impact Assessment is completed for all product features
Show Answer

The correct answer is C. The chapter's GDPR requirements table states that a "lawful basis for processing" is required, meaning you "must have consent or legitimate interest for each type of data collection." Additionally, the chapter lists cookie consent, Privacy by Design, and Data Processing Agreements as requirements that affect analytics implementation. The chapter emphasizes that GDPR applies to "any organization that processes personal data of EU residents, regardless of where the organization is located," making compliance mandatory regardless of company headquarters.

Concept Tested: GDPR Compliance

8. Which chart type does the chapter recommend for displaying a retention cohort table that shows user engagement intensity across two dimensions?

  1. Funnel chart
  2. Scatter plot
  3. Line chart
  4. Heatmap
Show Answer

The correct answer is D. The chapter's data visualization section specifically lists heatmaps as "best for showing intensity across two dimensions" and gives "retention cohort tables, usage by day and hour" as examples. A retention cohort table naturally maps to a heatmap because it has two dimensions (cohort and time period) with intensity values (retention percentages) at each intersection. Line charts are best for trends over time, scatter plots for relationships between two variables, and funnel charts for sequential conversion steps.

Concept Tested: Data Visualization

9. Your product dashboard currently displays 15 metrics across multiple categories with no drill-down capability and no trend context. Based on the chapter's dashboard design principles, which improvement should you prioritize first?

  1. Reduce to 5-8 key metrics with trend lines and drill-down capability for deeper investigation
  2. Convert all metrics to pie charts for easier visual comparison across categories
  3. Add color coding so each metric category uses a unique background color for quick identification
  4. Add real-time refresh capability so all 15 metrics update every second
Show Answer

The correct answer is A. The chapter outlines five dashboard design principles: purpose-driven, layered, contextual, minimal, and actionable. The "minimal" principle recommends "focus on 5-8 key metrics per dashboard" rather than showing everything. The "layered" principle calls for "high-level summary metrics, then drill-down capability for details." The "contextual" principle requires "trends over time, comparisons to goals, and benchmarks rather than isolated numbers." Reducing from 15 metrics to 5-8 with trends and drill-down directly addresses three of these five principles.

Concept Tested: Dashboard Design

10. A tracking plan specifies event names, event properties, user properties, triggers, and implementation notes. Why does the chapter emphasize creating this artifact before implementing user behavior tracking?

  1. Regulatory agencies require a formal tracking plan document before any analytics tools can be deployed
  2. Without a tracking plan, inconsistent event naming and missing properties create analytics debt that produces incomplete or misleading results
  3. Product analytics platforms will reject event data that does not conform to a pre-registered tracking plan schema
  4. Tracking plans are necessary to calculate the storage costs of event data before budget approval
Show Answer

The correct answer is B. The chapter warns that "poorly planned tracking creates a form of technical debt" and specifies the consequences: "if events are named inconsistently, if critical user actions are not tracked, or if event properties are missing, your analytics will produce incomplete or misleading results." The chapter recommends investing time in a comprehensive tracking plan before implementation and auditing it regularly. The tracking plan components (event names, properties, triggers, implementation notes) prevent the chaos that makes data analysis unreliable.

Concept Tested: User Behavior Tracking