D1 Retention %, Amplitude

D1 Retention % for Amplitude stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Analytics

At a glance

D1 Retention % is the share of a cohort that returns and performs the retention event on the day after their first activity in Amplitude. It is the earliest read on whether a first experience was good enough to bring users back, making it the most sensitive onboarding signal. The card pairs with sibling metrics in the Analytics category to build a complete diagnostic picture; cross-reference the related cards listed below for context.

What it counts	The percentage of users in a cohort who return and perform the retention event exactly one day after their first activity, using Amplitude’s N-day retention method.
Sample type	Backend API data from Amplitude, refreshed on the standard data refresh.
Why it matters	Day-one return is the strongest early indicator of onboarding quality and first-impression fit. It moves fast in response to product, content, and acquisition changes.
Reading the value	Compare the current 30-day window against the prior period. A falling D1 means newer cohorts are coming back less, often before downstream retention reflects it.
Currency	percent
Time window	30D vsP
Alert trigger	<30%
Sentiment key	amp_retention_d1
Roles	owner, marketing

Calculation

Calculated automatically from your Amplitude data. Amplitude groups users into cohorts by their first event, then measures the percentage who returned and performed the retention event on day 1, the day immediately after first activity. This card reports that day-one percentage over the 30-day window and compares it against the prior period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A representative reading of D1 Retention % for a typical merchant on Amplitude. Suppose recent cohorts return at 34 percent on day 1, down from 41 percent in the prior period. The 7-point fall is an early warning that something about the first experience has weakened, perhaps a slower landing page, a new onboarding step, or lower-intent traffic from a recent campaign. Because D1 reacts quickly, catching it here gives time to fix before D7 and D30 erode. Use Vortex Mind to trace which acquisition source or release coincided with the drop; for natural-language exploration, ask Ask Viq to compare D1 across devices.

Sibling cards merchants should reference together

Card	Why merchants reach for it
amp_retention_d7	The mid-curve stickiness gauge that D1 often leads.
amp_retention_d30	The long-run tail that a weak D1 tends to drag down.
amp_retention_curve	The full curve that puts the D1 point in context.
amp_stickiness_dau_mau	A complementary view of how often active users return.
amp_new_users	The cohort size feeding D1; a shift in mix can move the rate.

Reconciling against Amplitude

Where to look in Amplitude’s own dashboard:

Open the Retention chart, set the method to N-day, and read the day-1 column for your start and return events. Confirm the cohort range and segment filters match the Vortex IQ profile. Event Segmentation can verify the return-event volume, and the Dashboards section may pin a saved retention chart for reference.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Period boundary. Vortex IQ uses a 30-day rolling cohort window by default; an Amplitude retention chart may use a different range.	Variable	Match the cohort date range in the Amplitude retention chart.
Time zone. Amplitude defines day boundaries by the project time zone; Vortex IQ aligns to the merchant reporting time zone.	Marginal	Confirm the project time zone matches your reporting time zone.
Filter or segment scope. Profile-level filters (platform, B2B, test users) change which cohorts feed the rate.	Variable	Apply the same segment to the Amplitude retention chart.

Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does D1 Retention % update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). The most recent cohort’s D1 only finalises once its day-1 window has fully elapsed.

Q: Why does my Amplitude dashboard show a different number? The most common reasons are choosing day-range retention instead of N-day, different start and return event definitions, cohort-range differences (Vortex IQ uses 30-day rolling), time-zone day boundaries, and segment scope. Match these settings before assuming a real divergence.

Q: How does D1 Retention % relate to other Amplitude metrics? D1 is the earliest point on the retention curve and usually leads D7 and D30. Read it alongside those cards and the full curve to separate an onboarding blip from a structural decline. Single-metric reads can mislead; the diagnostic value is in the cross-reference.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. The default trips below 30 percent; adjust it to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

D1 Retention % is one of hundreds of KPI pulses Vortex IQ tracks across Amplitude and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.