Skip to main content
By default OneMRR counts billing customers: a Stripe customer, a Shopify shop or a Wix site. If one customer pays for several things you’d count separately (shops, stores, locations, seats), set up your own unit. MRR never changes; what changes is how many paying units you have, and whether a change counts as new, expansion or churn. Example: a seller with two stores starts both on the same day. Counted by customer, that’s one New and one Expansion. Counted by store, it’s two New stores.

​
Set up your unit

Open Settings → Breakdowns and counting → Count customers by:
  1. Give the unit a name, such as Shops, Stores or Seats.
  2. Pick the subscription metadata key that identifies it, such as storeId. OneMRR suggests keys from your data. Each Shopify shop is always one unit.
  3. Choose what happens when a subscription doesn’t have the key: count it with its billing customer, or count each subscription on its own.
Count customers by, with the unit and where it comes from outlined
Saving recalculates your history in the background. Pages keep showing the previous numbers until it finishes.

​
Switch what pages count

Once a unit is set up, everyone can choose Count by in the filter bar: Customers, your unit, or Subscriptions. OneMRR remembers each person’s choice. It applies everywhere: paying counts, the MRR bridge, churn rates, ARPA and LTV, cohorts, the Customers list and What changed.
The Count by switch in the filter bar

​
In a customer’s history

The customer drawer’s History by switch shows a customer’s plan and price history per customer, per unit or per subscription. For example, a store that cancels and later comes back on a new subscription shows as churn then reactivation for that store, but as contraction then expansion for the customer.