Track Success and Guardrail Metrics for Push Notifications
MetaData Scientist · Technical ScreenLast updated
Evaluates success and guardrail metrics for a push-notification feature in a networked travel app. Strong answers measure incremental itinerary engagement and retention, monitor opt-outs and fatigue, and design a cluster or graph-aware experiment to reduce spillovers.
Scenario
Designing and evaluating push notifications for a travel-recommendation mobile app (TripAdvisor-like).
Question
What primary success metrics would you track for a new push-notification feature and which guardrail metrics would you include (e.g., uninstalls, unsubscribes)? The app has strong network effects (users share itineraries). How would you design an A/B test for the notification while mitigating interference? Describe the unit of randomization and why.
Hints
Think engagement, retention, negative‐impact guardrails, and cluster-based randomization to reduce spillover.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.