Skio subscribers, MRR, and churn alongside the rest of Shopify
Skio subscription activity needs order context. Track active subscribers, MRR, and churn next to Shopify customer and revenue history.
Skio
Commerce, order, billing, and subscription systems that anchor revenue and lifecycle reporting.
Why Skio?
Mixed carts, prepaid subscriptions, and incomplete metadata complicate recurring-order analysis. SourceMedium classifies order lines before rolling them up to an order, so the definition stays inspectable. Skio's own subscription records feed the same subscriber and retention tables as ReCharge, so its churn reads the same way.
Subscriber lifecycle
New, active, cancelled, and dunning subscribers and subscriptions are tracked from Skio's own records.
MRR tracking
Monthly recurring revenue calculated from active Skio subscriptions.
Order-type distinctions
The commerce model distinguishes subscription, prepaid, one-time, and mixed subscription-and-one-time orders.
Subscriber linkage
With Skio connected, customer records carry the Skio subscriber ID, so repeat behavior can be compared between subscribers and everyone else.
Before you analyze
Boundaries that change how Skio numbers should be read.
Order type is not the lifecycle
An order classified as subscription says what was bought on that order. Active subscribers, cancellations, and MRR come from Skio's subscription records, which sit at a different grain.
Details in the docsWhich signal wins
Skio's line data comes first, then Shopify line-item metadata, then order tags. A line with none of them counts as one-time, and explicit one-time metadata beats a tag.
Details in the docsWhat you can ask
With SourceMedium Agent, you can query Skio data using natural language. Here are some examples.
What is our Skio MRR, and how has subscriber churn moved over the last six complete months? Compare subscription and one-time order revenue, separating mixed and prepaid orders. Show the classification rules. How does repeat purchase behavior differ by first-order type at the same cohort age? State the available customer history. Joins with other integrations
Skio data is designed to join with your other data sources for unified analysis.
How it works
Setup depends on the source. We confirm access requirements, history, cadence, and customer responsibilities before implementation begins.
Generate a Skio API key
In Skio, open API & Integrations, then API. Name and generate the key, and copy it when it is first displayed.
Connect Skio in SourceMedium
Choose Skio in the connector picker and paste the key without a prefix. SourceMedium validates it before saving.
Wait for the first data
The connection shows Awaiting first data until its initial sync lands, then Connected. Inspect the available data before building a report.
Ready to stop debating the numbers?
In 30 minutes, we will
-
Map your current systems and reporting gaps.
-
Show one workflow relevant to your team.
-
Outline likely fit, implementation scope, and next steps.
Book a walkthrough
Share a little context, then choose a time immediately after submitting.
Choose a time for your walkthrough
We couldn't load available times here.
Open the scheduling calendar in a new tab. If you cannot schedule now, we will still follow up.
Open scheduling calendar