Before the A/B test began, Priya M. asked Chloe B. to build the Resurface experiment dashboard in Amplitude so the team could monitor the experiment in real time and have the results analysis ready on test completion day. The dashboard needed to serve two audiences: Priya and the product team (daily monitoring during the test) and Marco S. (weekly executive check-ins requiring a single-screen summary). Chloe documented the requirements to ensure the dashboard was built once, correctly, rather than assembled ad hoc during the test window.
Source Notes:
Stephen Few, “Information Dashboard Design” (perceptualedge.com) . the dashboard design principles applied in the layout specification; Few’s guidance on minimizing chart junk, using small multiples for comparison, and placing the most important metric in the top-left position informed the visualization specifications.
Amplitude, “Dashboard Best Practices” (amplitude.com/blog/analytics-dashboards) . the Amplitude-specific guidance on chart types, cohort definitions, and filter configuration used to translate the requirements into implementable specs.
Edward Tufte, “The Visual Display of Quantitative Information” (edwardtufte.com) . the data-ink ratio principle applied to the chart specifications; Tufte’s emphasis on maximizing the data-to-ink ratio influenced the decision to use line charts over bar charts for time-series metrics and to avoid decorative chart elements.
Dashboard Name: Resurface Experiment (RSF-EXP-001)
Requestor: Priya M., Product Manager
Date: February 28, 2026
Priority: High
Target Delivery: March 7, 2026 (2 days before A/B test start)
Operational monitoring of the digest send pipeline (send failures, retry rates, Resend API health) . these are tracked in the Datadog operational dashboard, not Amplitude
Individual user debugging (“why didn’t user X receive their digest?”) . use Amplitude’s user timeline for individual-level investigation
Post-experiment deep analysis (regression models, causal inference) . the dashboard provides descriptive metrics; post-experiment analysis will be done in a separate notebook
When will this be viewed?
Daily at 9:00 AM by Priya and Chloe (after the morning digest cycle completes). Weekly on Mondays by Marco (5-minute screen share in the exec check-in).
What device/format?
Desktop browser (Amplitude web app). Marco views via screen share . the dashboard must be readable at a glance on a projected screen without scrolling.
Refresh Frequency: Near real-time (Amplitude default)
Refresh Time: No batch processing required; all events stream to Amplitude in real time
Historical Data Needed: Experiment window only (March 9 - April 5, 2026); 2-week pre-experiment baseline for return rate comparison
Data Retention: 12 months (standard Amplitude retention)
Apple Mail Privacy Protection inflates resurface_digest_opened events; the dashboard does NOT include an open rate metric for this reason
The item_position property on resurface_item_clicked events should be validated: values must be 1 - 5; any values outside this range indicate an instrumentation bug
Server-side events (digest_sent, digest_skipped) are dependent on the cron job’s availability; if the cron job fails, these events will not fire, creating a data gap that must be reconciled with the Resend delivery logs