Explain a drop in in-app subscription MRR, from ChatGPT or Claude

The problem: MRR is down, and the board wants a reason

The Purchasely dashboard shows the curve. To say why it drops, you open churn by plan, then by platform, then by country, check refunds, see whether trials convert less, and finally read store reviews to understand what departing users say. An hour of clicks and screenshots, to redo before the next board meeting.

An AI assistant walks that path in one conversation, as long as it can read Purchasely and the reviews.

What the assistant does, step by step

With Persyst’s Purchasely connector, the question “Where does the MRR drop come from?” runs this reasoning:

1. Measure the gap (get_purchasely_revenue, by month): MRR, subscription and one-time purchase revenue, churn and refunds, for the month and the previous one.
2. Break down the movement (get_purchasely_subscription_trends): new subscriptions, reactivations, paid entries and exits, trials and introductory offers, then the same split by platform and by plan.
3. Isolate the segment that moves by reading again with the filter found: the monthly plan on Android, or one country.
4. Look for the cause in the reviews, when Google Play or App Store Connect are connected (search_play_reviews, search_app_store_reviews): “price”, “subscription”, “cancel”, with several phrasings.

The answer separates what comes from exits, entries and refunds, and quotes the reviews that illustrate it.

Asking the right question

• Name the period and the reference: “October, against September” or “against the same month last year”.
• Ask for the breakdown: “exits, entries, refunds and trials, separately”.
• Name the app when several are open: the assistant does not add them up.

Three questions to try

• “Are annual plan exits rising too, or only the monthly plan?”
• “What share of trials started in September converted to paid, by platform?”
• “Do October’s refunds come from one country in particular?”

Setup

1. An administrator of the Purchasely account creates a Management API key with viewing scopes only, and the Persyst administrator plugs it into Data sources: the Purchasely guide covers the steps.
2. They pick the open apps, then open them to product, marketing or leadership. For the review side, the Google Play and App Store Connect guides come on top.
3. Each member adds Persyst to their assistant (getting started) and asks their question.

Limits to know

• Read-only: the assistant analyzes, it changes no plan, paywall or campaign.
• Purchasely limits the number of calls per key, especially on dashboards: over a long period, the assistant may have to wait or narrow the requested range.
• The figures are Purchasely’s: a subscription sold outside its SDK is not in them.
• Reviews only explain part of the churn: a user who cancels without writing anything only shows up in the figures.