Doppler Dashboard

Six cards at the top give you the health of your workspace at a glance. Each card has a sparkline showing 14-day trend.

• Total Users — Total number of users Doppler has ever seen (all identify() calls).
• Inactive Users — Users who haven't been seen within the project's inactivity threshold (configurable in Settings).
• At Risk — Users whose engagement score has dropped to a warning level. These are pre-churn signals.
• Emails Sent — Total recovery emails dispatched by the Doppler engine.
• Recovered — Users who became active again after receiving a Doppler email. The gold metric.
• Reactivation Rate — Recovered ÷ Inactive × 100. Tells you how effective Doppler's engine is for your product.

Below the metric cards, you'll see an Activation Gap breakdown if Doppler detects users who haven't reached key milestones:

• Signed up but never set up — Users who have never called onboardingStarted() or later milestones. These users haven't engaged at all.
• Set up but never hit core action — Users who completed onboarding but never called coreAction(). They started but didn't get real value.

These percentages are of total inactive users — not all users. A 100% in "Set up but never hit core action" means every inactive user went through onboarding but stalled before the AHA moment.

A notification panel shows you what the engine is actively doing right now — how many inactive users were detected, how many have been recovered so far, and the current engine status. This refreshes automatically.

An SVG line chart showing daily recovery counts over the last 14 days. Each point is a day; the Y axis scales to your peak recovery day. Use this to see if your recovery rate is growing or flattening.

• email_sent — A recovery email was sent to a user. Shows subject line, flow type, and recipient.
• churn_feedback — A user submitted a cancellation reason via captureChurnFeedback(). Shows their reason and optional comment.
• revenue — A revenue event was tracked via trackRevenue(). Shows amount and label.

A "recovery" is recorded when a user who was previously inactive sends any new event — a heartbeat, a milestone, a revenue event. Doppler marks reactivatedAt and increments that day's recovery count.

A flat line near zero means no inactive users are coming back. A rising line means your recovery emails are working. A spike followed by a drop often means a one-time broadcast email went out — check the Broadcast tab for the date.

• User — Email address of the user. Avatar is their initial.
• Flow — Which recovery flow they're in. See the Flows section for what each flow means.
• Last Seen — Time since Doppler last received any event from this user (heartbeat or SDK call).
• Core Event — Time since their last coreAction() call. "Never" means they've never hit the AHA moment.
• Health — Healthy / At Risk / Critical based on the decay score model.
• Status — Active (seen recently) or Inactive (beyond inactivity threshold).

Status is binary: active or inactive based purely on time since last seen vs your inactivity threshold.

Health is a gradient: it measures core event decay. A user can be "Active" (seen recently) but "At Risk" (their core event cadence has slowed). This is how Doppler catches early-stage churn before the user fully disappears.

You can filter by flow type: All, No AHA, Drifted, Trial End, Returning, Usage Drop. Use the search box to find a specific user by email.

Currently: view and inspect. Individual user recovery actions (manual email, suppression, unsubscribe override) are coming in a future release. Unsubscribed users are visible but marked — Doppler will never email them.

• Subject — The subject line of the email as sent.
• Flow — Which recovery flow triggered this email (A, B, C, D, E).
• Type — The email type within the flow (e.g. initial nudge, follow-up, final reminder).
• Sent to — The recipient's email address.
• Sent at — Exact timestamp of when the email was dispatched.
• Recovered? — Whether this specific email resulted in a user becoming active again.

Currently view-only. Email editing, A/B testing, and per-user suppression are on the roadmap.

• Recovery Emails — Sent automatically by the engine. Triggered by user behavior. Personalized per-user based on their flow state.
• Broadcast — Sent manually by you. Not behavior-triggered. Same message to a filtered audience segment.

• All Users — Every tracked user in this workspace.
• Active Users — Users seen in the last 7 days.
• Inactive Users — Users with no activity beyond the inactivity threshold.
• At-Risk Users — Users whose health score is "at_risk" or "critical".

• Email — Sends an email to each user in the selected segment. Requires a subject and body.
• In-App — Sends an in-app notification (requires in-app SDK integration — coming soon).

The AI Draft button (coming soon) will generate a subject and body for your broadcast based on your product description and the selected audience. Saves you from starting with a blank page.

• Send to unsubscribed users — Doppler enforces this automatically.
• Schedule broadcasts for a future time (coming soon).
• Create recurring broadcasts (use the engine's automated flows for that).

When a user cancels or downgrades, you can call captureChurnFeedback(reason, comment) in your cancel flow. The reason must be one of:

• too_expensive — Price was the blocker
• too_complex — Too hard to use or learn
• found_alternative — They switched to a competitor
• not_needed — They solved the problem a different way
• other — Catch-all, requires a comment

This is your qualitative churn signal. If 60% of feedback says "too expensive", that's a pricing problem. If it's "too complex", that's an onboarding/UX problem. Combine this with the Flows data to see which flow type correlates with which churn reason.

• Product description — Used by the AI to generate more relevant, contextual recovery emails. Be specific: what does your product do, who uses it, what's the core action.
• Inactivity threshold (days) — How many days of silence before a user is classified as "inactive". Default: 7. Adjust based on your product's natural usage cadence (a daily tool = 2 days, a weekly tool = 10 days).
• Avg. Revenue Per User (ARPU) — Monthly revenue per user in USD. Used to calculate Revenue Recovered and Revenue at Risk on the Overview.

The Settings tab also has a Delete Workspace option. This permanently deletes all users, emails, activity, and metrics for this project. Type the workspace name to confirm. This is immediate and irreversible.

• ✅ Unlimited user tracking
• ✅ All 5 recovery flows (A–E)
• ✅ Broadcast emails
• ✅ Dashboard analytics and metrics
• ✅ Churn feedback collection
• ✅ Full API access

After 14 days, if you haven't upgraded to a paid plan, the Doppler engine is paused. Your data is preserved — no users or emails are deleted. You can upgrade at any time from the Billing page in your account settings to resume the engine immediately.

You can cancel your subscription at any time from Account → Billing. Your access continues until the end of the current billing period. After that, the engine pauses and you return to a read-only view of your data.