rpt_subscriptions_performance_daily

Pro warehouses only. Subscription tables are not delivered on Foundation warehouses. See Foundation and Pro.

Daily subscription performance: new and cancelled subscription flows plus running counts of active, churned, and dunning subscriptions and MRR.

Grain: One row per store per day per channel.
Date field: date, in your reporting timezone.
Filters to start with: sm_store_id in multi-store warehouses.

sm_channel, sub_channel, country, and country_code are placeholders in the current version and always hold unknown_placeholder. Do not segment by them yet.

A Recharge bundle arrives as several component subscriptions, each counted separately, so subscription counts and MRR are component-grained and run high for bundle-heavy stores.

Columns

Column	Type	Description
`sm_store_id`	STRING	SourceMedium’s unique store identifier.
`churn_active`	INT64	FLOW: actively churned subscribers on this date, recorded on the first full day of inactivity.
`churn_passive`	INT64	FLOW: passively churned subscribers on this date, recorded on the first full day of inactivity.
`churn_total`	INT64	FLOW: subscribers churned on this date, recorded on the first full day of inactivity and excluding same-day activation-and-churn periods.
`country`	STRING	Constant `Unknown` placeholder. ReCharge does not supply subscription geography.
`country_code`	STRING	Constant `Unknown` placeholder. ReCharge does not supply subscription geography.
`date`	DATE	Date represented by the daily subscription metrics.
`mrr`	FLOAT64	Active MRR as of this date.
`mrr_cancelled`	FLOAT64	FLOW: subscription-grain MRR removed by actively cancelled subscriptions on this date; used to reconcile active MRR stock.
`mrr_cancelled_passive`	FLOAT64	FLOW: subscription-grain MRR removed by passively cancelled or expired subscriptions on this date; used to reconcile active MRR stock.
`mrr_dunning`	FLOAT64	STOCK: MRR in dunning as of this date (rolling window of mrr_dunning_new, same window as subscriptions_dunning).
`mrr_dunning_new`	FLOAT64	FLOW: MRR of subscriptions that entered dunning on this date.
`mrr_new`	FLOAT64	FLOW: subscription-grain MRR added by subscriptions_new on this date, excluding same-day activation-and-churn rows.
`reporting_timezone`	STRING	Your store’s reporting timezone, used for the date columns on this row.
`sm_channel`	STRING	Constant Online DTC placeholder required by the report grain. ReCharge does not supply marketing channel or geography, so this is not an attributed channel. The published value stays `Online DTC` and is not normalized like `obt_orders.sm_channel` (`online_dtc`). Do not join or filter this field as if it segmented subscription activity by marketing channel.
`smcuuid`	STRING	Hashed store identifier.
`sub_channel`	STRING	Constant `Unknown` placeholder required by the report grain. It does not segment subscription activity.
`subscribers_active`	INT64	Running active subscribers (stock). Non-negative.
`subscribers_cancelled`	INT64	Same as `churn_active`. Active subscriber churn on this date.
`subscribers_cancelled_passive`	INT64	Same as `churn_passive`. Passive subscriber churn on this date.
`subscribers_churn_rate`	FLOAT64	Active subscriber churn divided by beginning-of-day active subscriber stock.
`subscribers_churned`	INT64	Running count of subscribers who have actively churned as of this date.
`subscribers_churned_passive`	INT64	Running count of subscribers who have passively churned as of this date.
`subscribers_dunning`	INT64	STOCK: subscribers in dunning as of this date (rolling window of subscribers_dunning_new, same window).
`subscribers_dunning_new`	INT64	FLOW: subscribers that entered dunning on this date.
`subscribers_first_time`	INT64	FLOW: subscribers whose first non-same-day activity period starts on this date.
`subscribers_new`	INT64	FLOW: subscribers starting an activity period on this date, excluding same-day activation-and-churn periods.
`subscribers_returning`	INT64	FLOW: subscribers whose later non-same-day activity period starts on this date.
`subscriptions_active`	INT64	Running active subscriptions (stock: cumulative inflow - outflow). Non-negative.
`subscriptions_cancelled`	INT64	FLOW: actively cancelled subscriptions on this date, excluding same-day activation-and-churn rows.
`subscriptions_cancelled_passive`	INT64	FLOW: passively cancelled or expired subscriptions on this date, excluding same-day activation-and-churn rows.
`subscriptions_churned`	INT64	Running count of subscriptions that have been actively cancelled as of this date.
`subscriptions_churned_passive`	INT64	Running count of subscriptions that have been passively cancelled or expired as of this date.
`subscriptions_dunning`	INT64	STOCK: subscriptions in dunning as of this date = date-relative ROLLING-WINDOW sum of subscriptions_dunning_new over the trailing recharge_default_dunning_window_days. Build-clock independent (recency vs the spine date), so the historical trend is stable across rebuilds.
`subscriptions_dunning_new`	INT64	FLOW: subscriptions that entered dunning on this date (dunning_entered_date = date).
`subscriptions_new`	INT64	FLOW: new and returning subscriptions created on this date, excluding same-day activation-and-churn rows.
`subscriptions_returning`	INT64	FLOW: returning subscriptions created on this date at subscriber/product grain, excluding same-day activation-and-churn rows.

Three nuances to know when reconciling this report:

Subscriptions that activate and churn on the same day are excluded from the new and churn flows, matching how ReCharge reports them.
sm_channel on this report is a placeholder (Online DTC), not a marketing channel. Do not use it for channel analysis.
Medusa subscriptions count toward active subscriptions and MRR, but Medusa has no charge stream, so charge-based revenue exists only on the ReCharge charge tables (obt_subscription_charges).

When reporting-currency conversion is enabled, MRR fields use the exchange rate for each report date. Daily MRR can therefore change because of exchange-rate movement as well as subscription activity. See Reporting Currency.

A ReCharge bundle currently lands as multiple component subscriptions. Counts and MRR can be inflated for bundle-heavy stores until SourceMedium can collapse those components. Use dim_subscriptions.is_bundle_component to measure that exposure.

Get into BigQuery

Activate

SQL Query Library

Common analyses (SQL)

Tables

Schema Standards

rpt_subscriptions_performance_daily

Columns

​Columns

Columns