Analytics
494 bites tagged Analytics — interview questions with model answers, and 60-second explainers.
How do you track events and calculate funnel drop-off?
Tests event mapping and funnel math. Answer: one event per step (page view, email submit, profile done); compute relative step conversion and overall rate from top; deduplicate users. Red flag: raw pageviews instead of uniques.
How do you attribute signups to Facebook, Google, and blog campaigns?
This tests URL-based campaign attribution and session persistence. A strong answer covers UTM tags, landing page parsing, cookie storage, and writing the source to the user record at signup.
What fields belong in an experiment tracking event?
Tests disciplined schema thinking over random fields. Strong answers cite a tracking plan with event and user properties, environment separation, and consistency. Red flag: dumping data without a schema or single source of truth.
How do you instrument a marketing funnel versus a product-led growth loop?
This tests if you distinguish linear attribution from compounding systems. A strong answer contrasts stage-tracking and CAC with viral-coefficient instrumentation, cycle-time velocity, plus identity resolution.
What counter metrics track health of weekly active users?
Tests whether you can spot growth-at-all-costs blind spots. A strong answer pairs WAU with 7-day retention, sessions per user, and error rate, mapping each to churn, shallow engagement, or bugginess.
Sessionization: Bounding Events into Visits
Sessionization groups raw user events into visits using idle timeouts. Teams use it to measure engagement and attribute conversions per sitting. The footgun is treating sessions as users, which inflates counts and wrecks retention analysis.
What metrics track e-commerce user engagement and how do you prioritize them?
Propose DAU/MAU, adoption, retention, and stickiness; prioritize by impact on trial conversion and churn. translating vague goals into measurable product journey indicators. vanity metrics untied to conversion or churn.
What metrics prove documentation business impact and how do you instrument?
Tests tying docs to revenue and costs. Strong answers present acquisition (dev signups, quickstart rate), adoption (endpoint breadth, trial conversion), and deflection (support tickets) via event instrumentation and CRM joins.
How would you track which headline wins in an A/B test?
Tests end-to-end experiment instrumentation across the stack. Outline: deterministically bucket users, serve variant A or B, emit click events, and aggregate by variant.
Track a 'Request a Demo' button click
End-to-end click instrumentation. A strong answer covers: a DOM listener on the button, a custom event name like request_demo, and a payload with page path and button ID. Using pageview tracking instead of an explicit event.
How do you implement a CTA A/B test and attribute conversions?
This tests experiment architecture from bucketing to attribution. A strong answer covers: stable user bucketing, server or client-side rendering, and conversion events tagged with experiment and variant IDs.
How does email open and click tracking work?
This tests beacon and redirect mechanics plus event schema design. A strong answer covers a 1x1 pixel fetched on open, a redirect link that logs then forwards, and data like IP, timestamp, and UA. A red flag is omitting image blocking or privacy implications.
Design a system to A/B test headlines for a single article URL
Hash users for sticky variants; store separately; emit events; compute CTR. controlled experiment design with user bucketing and attribution. client-side randomization without stickiness or event tracking.
How would you track multiple CTAs to the same conversion goal?
Tests granular event attribution beyond aggregate counts. A strong answer uses unique data attributes per CTA, routes clicks through GTM into GA4 events, and ties them to the conversion. Red flag: relying only on destination URLs, which fails if paths match.
How would you instrument a CTA button and describe its event payload?
This tests basic event instrumentation and payload design. Mention a click listener, a gtag call with an event name, and parameters like button_text and page_path. A red flag is a bare event name with no parameters or mixing pageviews and clicks.
Describe how you'd implement an A/B test for a landing page headline
Mention deterministic bucketing, anti-flicker rendering, tracking with variant IDs, and sample-size planning. Experiment integrity beyond DOM swaps. Swapping headlines client-side after paint biases data and hurts UX.
How would you track clicks on headlines and calls-to-action?
This tests DOM event handling and basic telemetry design. A strong answer covers event delegation with addEventListener, data attributes for element IDs, and a payload with timestamp and page context.
Apply AARRR to B2B SaaS vs B2C mobile game analytics
This tests mapping AARRR to instrumentation across business models. A strong answer contrasts B2B account activation and expansion against B2C session-zero funnels and whale monetization. Red flag: same metrics ignoring account hierarchies and ad attribution.
What is the difference between a metric and a KPI?
Tests strategic vs operational measurement discernment. Answer: KPIs track critical goals; metrics track processes. Page views are a metric; conversion rate is the KPI. Red flag: calling all data KPIs or using page views as success proof.
How do you root-cause a 20% revenue drop with no pipeline failures?
Reconcile against raw events, slice by dimension for silent gaps, audit schema drift. Incident leadership and validating data integrity before calling a downturn.
Design a self-service analytics platform for non-technical users
Tests separation of semantic modeling, UI, and query generation for safe self-service analytics. Strong answers cover a semantic layer with unified metrics, drag-and-drop UI with AST-based SQL generation, and caching.
How would you design an automated data quality monitoring system?
Tests turning data quality into tiered checks for exec dashboards. Strong answers combine freshness, volume, schema, and distribution validation with severity-based paging. Red flag: static thresholds without noise reduction or business-impact triage.
Instrument a mobile event and surface it in analytics
This tests full-stack analytics plumbing. A good answer hits: structured client logging, batched transmission, backend validation, warehouse aggregation, and dashboard verification. A red flag is fire-and-forget logging with no schema checks or reconciliation.
What data do you need and what steps build a WAU dashboard?
Tests defining a metric, modeling events, and wiring them into a BI tool. A strong answer names the feature event, sets a rolling 7-day window, counts distinct users by period, and configures the BI layer. Red flag: jumping to charts before defining active.
Get Analytics bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.