get
https://api.purchasely.io/management/v1/applications//dashboard_v2/paid_subscription_movements
Paid subscription movements: for each period, how many PAYING subscriptions (full price or paid offer) entered the paid base and how many left it.
- Returns an array of
{period, group_by, group_by_public_id, group_by_name, total_activations_count, total_churns_count, net_movement_count}rows. total_activations_count: subscriptions that entered the paid base (direct purchases, trial/intro/promo conversions, reactivations).total_churns_count: subscriptions that left it (voluntary churn, involuntary/billing-failure churn, refunds).net_movement_count:total_activations_count - total_churns_count.- Unit: count of subscriptions. A flow: summable across periods.
- Always restricted to the paid segment (no
segmentparameter). This is the paid counterpart ofsubscription_activations. - These movements do not reconcile exactly with
subscription_evolution: a close is not the previous close plusnet_movement_count, because the two follow different rules. Movements count only classified store events and apply the paid filter to each event. ENTERED_BILLING_RETRY and GRACE_PERIOD_TERMINATED count as involuntary churn on their date, and a switch from paid to free without DEACTIVATE counts no churn. - For the exact base on a date, use
subscription_evolution(its last row on thedate_rangeend date, orperiodicity=DAY), not a close minus movements. - Recommended periodicity: MONTH.
- Single application only.
Required scope: analytics.dashboards:view
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…

