Geography & Product Mix
Where your revenue comes from, and which product it's tied to.
Put this metric to work: explore FlowMRR's Stripe MRR analytics to track revenue movements, retention and forecasts from your Stripe account, or see how FlowMRR compares as a Baremetrics alternative for Stripe.
A country × product matrix of current MRR. In FlowMRR the rows are your top 8 countries and the columns your top 6 products, both ranked by current MRR in the reporting currency; each cell shows the product's share of that country's MRR, its MRR change against 12 months ago, or its average monthly gross MRR churn over the last 12 closed months. The country is the customer's billing country: the customer's address, else the shipping address, else the billing address on the default payment method, never the card's issuing country. Crossing the two dimensions shows what a total by country or by product hides (e.g. "Product A dominates in the US, Product B is where France actually grows").
Worked example
US customers contribute $30,000 MRR: $20,000 on the Pro plan and $10,000 on Team, so the US row reads 67% Pro and 33% Team. France contributes $14,000, almost entirely on Team. That tells you Team, not Pro, is the plan to localise and market in France.
Other definitions you will see
Some tools place customers by card issuing country, IP address or billing currency instead of billing address; the card country is the bank's location, and many customers pay in USD or EUR wherever they are. Others express each cell as a share of total MRR rather than of the country's MRR, which shows where the money is rather than the mix within each market.
Illustrative comparisons
Reading the matrixThese unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.
Why it matters
Geography without product (or product without geography) hides the decision you actually need to make. A country that looks flat in aggregate MRR can be growing fast on one product and shrinking on another — packaging, pricing, and localisation decisions should follow the cell in the matrix, not the row or column alone.
Common mistakes
- Reporting country-level MRR without segmenting by product — masks which offer is actually working where.
- Ignoring the customer-count view alongside the MRR view — a country can carry a lot of MRR from very few whales, which is a concentration risk in disguise.
- Letting an "unknown" or missing-country bucket grow unaddressed instead of fixing billing-address capture.
Calculating it from Stripe data
A Stripe subscription has no country of its own, so the country comes from the customer. Look in this order: the customer's address, then the shipping address, then the billing address on the default payment method, which is where Checkout keeps the address the buyer typed unless your account copies it onto the customer. Do not use the card's country: it is where the issuing bank is, not where the customer is. FlowMRR follows exactly this order and reports customers with none of the three as unknown. Because the country sits on the customer record, a customer who changes address carries their history with them.
Then attach MRR. Compute headline MRR per subscription (annual plans ÷ 12, forever discounts deducted, trialing, incomplete, incomplete_expired and paused excluded), convert it into one reporting currency, and group by country and by product. Count a customer once in their country even when they hold several products, and once in each product cell they appear in: the product cells of a country can then add up to more customers than the country total, while MRR still sums exactly. Billing currency is not a proxy for country, since customers in many countries pay in USD or EUR.
Make products meaningful before crossing them with countries. Several near-identical Stripe products for one plan split a cell in two, and a long tail of small products produces cells too small to read. FlowMRR's matrix shows the top eight countries and the top six products by current MRR, so a plan split across two product IDs can drop out of it: one more reason to consolidate them in Stripe. In its by-product views, FlowMRR treats the top five products by customer count as always significant, adds any other product holding at least 1% of customers or of MRR, and folds the rest into an Others bucket.
Reading the result
Read each cell for size and trend together. A country with high MRR from a few customers is a concentration question; one with many customers and low ARPU is a pricing or packaging question. Compare the plans new customers choose in each country with those of the installed base: if new customers in a market pick a cheaper plan than earlier ones, that market's ARPU will fall before its total shows it.
Treat the unknown bucket as a quality signal. If it holds a material share of MRR, fix address collection at checkout before drawing conclusions about countries, because unknown customers are rarely a random sample: they tend to come from an older integration or a particular channel. When you decide where to localise a price, a language or a payment method, start from the cell that is growing, not from the country with the largest total.
Frequently asked questions
How do I see revenue by country in Stripe?
Stripe stores location on the customer, not on the subscription, so you need to join the two: export customers with their address country, export active subscriptions with their amounts, normalise those to a monthly value and sum by country. Use the billing address rather than the card's country, which is the issuing bank's. Analytics tools connected to Stripe, FlowMRR included, do this join for you.
Why are so many of my Stripe customers missing a country?
Usually because no address was ever stored on the customer. Checkout and payment forms collect what you ask for: with minimal address collection you may only have a country and postal code on the payment method, or nothing at all. Turn on billing address collection for new customers and, for existing ones, read the billing details of their payment method.
What is a product mix analysis in SaaS?
It splits MRR and customers by product or plan to show which offers carry revenue, which grow and which lose customers. Crossed with geography, it shows which offer works in which market, something a total by country or by product alone cannot show.
Is MRR by country the same as sales by country for tax purposes?
No. MRR by country is a monthly run rate grouped by the customer's address. Tax reporting is based on taxable transactions and each jurisdiction's rules, including what was invoiced and refunded and where the customer is located for tax purposes. Use your tax reports, such as those from Stripe Tax if you use it, for filings.