Stay AI subscriptions, retention, and churn next to your orders
Retention work is invisible without the order history behind it. Stay AI subscribers, MRR, and cancellation reasons sit next to your Shopify orders.
- Access
- API key with Read Subscriptions, Read Orders, and Read Selling Plan Groups
- Where to create it
- Stay AI Merchant Portal, under Settings, then API Keys
- MCP server
- Official server, checked September 2026
Stay AI
Commerce, order, billing, and subscription systems that anchor revenue and lifecycle reporting.
Why Stay AI?
Stay AI runs the subscription program and its retention flows. SourceMedium reads Stay AI's subscriptions and orders to decide, line by line, which Shopify revenue is recurring and which is a one-time purchase. The same subscriptions fill the subscriber and cohort tables ReCharge uses.
MRR tracking
Monthly recurring revenue calculated from active Stay AI subscriptions.
Retention and cancellations
Signup-cohort retention and cancellation reasons, where Stay AI supplies them, show where subscribers leave.
Line-level order type
Stay AI's line mappings take priority over weaker Shopify signals such as order tags.
Mixed and prepaid carts
Orders are split into subscription, prepaid, one-time, and mixed subscription-and-one-time.
Before you analyze
Boundaries that change how Stay AI numbers should be read.
Pick the grain first
Subscription, subscriber, and order are separate grains with separate tables. One subscriber can hold several subscriptions, so decide what you are counting before you count it.
Details in the docsOrder type is not the lifecycle
An order classified as subscription says what was bought on that order. Active subscribers, cancellations, and MRR come from Stay AI's subscription records.
Details in the docsWhat you can ask
With SourceMedium Agent, you can query Stay AI data using natural language. Here are some examples.
What's our subscription retention rate by signup cohort? Which cancellation reasons are most common? What share of revenue came from subscription orders each month? Show the classification rules. How it works
Setup depends on the source. We confirm access requirements, history, cadence, and customer responsibilities before implementation begins.
Create a read-scoped key
In the Stay AI Merchant Portal, create an API key with Read Subscriptions, Read Orders, and Read Selling Plan Groups. Update and Delete scopes are not needed.
Connect in SourceMedium
Choose Stay AI in the connector picker and paste the key. A key missing the read scopes is rejected on the spot.
Wait for the first data
The connection reads Awaiting first data until its first sync lands, then Connected.
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