Get user lifecycle stages (New / Returning / Power user / Resurrected / At Risk / Churned)
Counts wallet users by lifecycle stage based on activity within the date range. The reference date is date_to.
Default stage thresholds can be overridden per-request with the lifecycle threshold query params (new_window_days, churn_window_days, power_user_min_active_days, power_user_window_days, resurrected_gap_days, at_risk_min_days_inactive, at_risk_prior_active_days_threshold); each is an optional integer 1 to 90. When omitted, the project’s saved Settings → Lifecycle values apply, then the platform defaults.
Authorizations
Workspace API key (e.g. formo_xxx). Create one in the Formo dashboard under Team Settings > API Keys.
Query Parameters
Inclusive start date (YYYY-MM-DD). Defaults to 7 days before date_to.
Inclusive end date (YYYY-MM-DD). Defaults to today.
Restrict results to a single lifecycle stage.
New, Returning, Power user, Resurrected, At Risk, Churned When true, returns both current and previous period metrics for week-over-week comparison. The previous period is non-overlapping and equal in length to the current range.
Override: a wallet is New if first seen within this many days of the reference date (default 30). Caller value wins over the project's saved setting.
1 <= x <= 90Override: a wallet is Churned once last seen this many days before the reference date (default 30).
1 <= x <= 90Override: distinct active days within the power-user window required to qualify as Power user (default 5).
1 <= x <= 90Override: trailing window in which active days are counted for Power user qualification (default 30).
1 <= x <= 90Override: minimum inactivity gap that marks a re-engaging wallet as Resurrected (default 30).
1 <= x <= 90Override: minimum days since last activity for an established, still-active wallet to be At Risk (default 14; must be < churn_window_days).
1 <= x <= 90Override: minimum active days a wallet had in the window before the recent quiet stretch to qualify as At Risk (default 1).
1 <= x <= 90Response
Lifecycle counts
Analytics endpoint response. The data array contains the rows; the exact row shape depends on the endpoint. meta carries column type information for rendering, rows is the row count, and statistics holds query timing metadata.