Stripe to Data Studio: how to connect payments data, what it costs and how to get revenue numbers that match Stripe

Can you connect Stripe to Data Studio without a paid connector?

Yes, with limits. The free routes are a connector vendor's free tier, Google's Stripe transfer into BigQuery while it stays in Preview, or CSV exports from the Stripe dashboard uploaded to a Google Sheet. What you give up is refresh frequency, history and the hours someone spends keeping it current.

Data Studio's native connectors cover Google products and a set of databases: GA4, Google Ads, Search Console, Sheets, BigQuery, YouTube, Campaign Manager 360, Display and Video 360, Ad Manager, Cloud SQL, MySQL, PostgreSQL, SQL Server and Redshift. Stripe is not among them, and the April 2026 rename from Looker Studio back to Data Studio did not change that. Every Stripe route therefore runs through a partner connector or lands the data somewhere Data Studio already reads.

On the free tiers I checked in October 2026: Coupler.io's free plan refreshes manually only, with 1 account, 1 destination and 100 rows per run, which is too small for most live Stripe accounts. Windsor.ai's forever free plan allows 1 user, 1 data source and 1 account, with a 30-day history limit. Google's documentation states there is no cost to transfer Stripe data into BigQuery while that feature is in Preview, although BigQuery storage and queries are billed as usual once you pass the free tier.

What are the four ways to get Stripe data into Data Studio?

Each route trades setup speed against freshness, cost and control over the numbers. The deciding questions are how many transactions you process, how far back you need to report, and whether Stripe must sit beside ad spend, CRM or accounting data.

A partner connector appears in the Data Studio connector gallery and fetches Stripe data, or the vendor's copy of it, when a chart loads. A Sheets route writes Stripe records into a Google Sheet on a schedule and Data Studio reads the sheet. A BigQuery route loads Stripe tables into your own dataset, through Google's transfer service, Stripe Data Pipeline or an ETL vendor. A CSV route means downloading a report from the Stripe dashboard and uploading it by hand.

How much does a Stripe to Data Studio connector cost?

Entry prices run from free to about $32 a month, and costs climb with refresh frequency, row volume and the number of accounts. The figures below come from each vendor's own pricing page, read in October 2026. Vendors change prices often, so confirm before you buy.

Price the plan you will need in a year, not the cheapest tier. Count your Stripe accounts (separate entities or regions often mean separate accounts), the objects you need (charges, refunds, balance transactions, invoices, subscriptions, payouts), how fresh the numbers must be, and which other sources belong in the same report. A finance team that closes monthly does not need an hourly refresh; a growth team watching a launch might.

Should you use Google's Stripe transfer or Stripe Data Pipeline for BigQuery?

Use Stripe Data Pipeline if you need complete, regularly refreshed data and can pay for it; use Google's transfer if you want a free start and can live with its limits. Both put Stripe in BigQuery, which Data Studio reads natively and which handles large transaction histories far better than a sheet.

Google's Stripe connector for BigQuery Data Transfer Service is in Preview under the Pre-GA Offerings Terms, according to Google Cloud's documentation last updated October 26, 2026. It authenticates with a Stripe secret key or a restricted API key plus the account ID, runs on a repeat schedule, once or on demand, and defaults to a start date three years back. The catches are written into the documentation: it only transfers pre-generated reports for each Stripe account and does not generate new ones, so up-to-date reports must be generated in the Stripe dashboard first, and it does not support webhook events, real-time updates or Stripe Sigma. One transfer configuration can run only one transfer at a time.

Stripe Data Pipeline is Stripe's own export. Its documentation lists Snowflake, Amazon Redshift, Databricks and BigQuery as warehouse destinations: Stripe sends a data share, your core data is available within 12 hours of accepting it, and after that a full load arrives every 3 hours. Every table carries a merchant_id column, so several Stripe accounts can share one warehouse. Two cautions: Stripe states it does not offer Data Pipeline to businesses in India because of data localisation rules, and some derived tables refresh more slowly than core payments data.

My rule: whichever route you pick, use a restricted read-only key owned by a company admin, never a personal or contractor login, and never point charts at raw tables. Build modelled views on top, partition large tables by date, and connect Data Studio to the views. If a schema changes when Google's connector leaves Preview, you fix one view instead of every chart.

Why don't Stripe revenue numbers in Data Studio match the Stripe dashboard?

Usually because the report is measuring something slightly different from Stripe's screen, not because data went missing. Go through the causes below in order before you blame the connector.

A worked example shows how far apart two honest numbers can be. Take a month with $10,000 of successful charges, $600 of refunds and $320 of Stripe fees. Gross volume is $10,000. Net of refunds it is $9,400. What lands in the bank account before payout timing is $9,080. A Data Studio scorecard summing the charges table shows the first figure, a finance team reconciling payouts expects the last, and both are correct for their own question. Decide which one each chart shows and label it.

• Cents: Stripe stores amounts in the smallest currency unit, so a raw $49.00 charge arrives as 4900. Divide by 100 in a calculated field, and remember zero-decimal currencies such as JPY must not be divided.
• Gross vs net: the charges table holds what customers paid; the balance_transactions table holds amount, fee and net per movement. Revenue-after-fees charts belong on balance transactions.
• Refunds and disputes: a refund is a separate object dated when it happened, so last month's charge refunded this month lowers this month's net, not last month's.
• Failed and uncaptured payments: filter on status so declined and authorised-only charges are not counted as revenue.
• Currencies: charges keep the customer's currency. Summing EUR and USD amounts in one column produces a meaningless number; use the converted settlement amount on balance transactions or convert in your model.
• Time zones: Stripe's prebuilt Billing reports use UTC while its dashboard charts use your account's time zone, so month totals can differ by a day's revenue at the edges.
• Test data: Data Pipeline separates live and sandbox data into STRIPE and STRIPE_TESTMODE schemas; some connectors need a filter to exclude test mode.

How do you build an MRR dashboard from Stripe in Data Studio?

Decide first whether you will copy Stripe's MRR definition or calculate your own, because a board deck showing two MRR figures loses trust fast. Stripe defines MRR as the sum of the monthly-normalised value of all active and past_due subscriptions, excluding taxes, free plans and metered usage products. Cancelled or unpaid subscriptions count as churn. Legacy free trials are excluded for the trial's duration, and you can configure whether recurring and one-time discounts are subtracted.

Stripe's own documentation gives the normalisation arithmetic: 100 subscribers on a $100 monthly plan plus 50 subscribers on a $600 yearly plan is (100 x $100) + (50 x $600 / 12) = $12,500 MRR. In Data Studio that means a CASE statement on the price's billing interval that divides yearly prices by 12 and multiplies weekly ones up, applied to subscription items, not to invoices. Summing paid invoices gives you cash collected, which is a different metric and spikes every time an annual plan renews.

The fastest honest route is to start from Stripe's prebuilt Billing reports, such as MRR per subscriber per month and Customer MRR changes, loaded into BigQuery or a Sheet. You inherit Stripe's definition and your numbers match the Stripe dashboard. Build your own calculation from subscriptions and subscription items only when your definition genuinely differs, for example when you count usage revenue or treat past_due differently.

A practical first version fits on three pages. Page one: MRR, net new MRR split into new, expansion, contraction and churn, active subscribers and ARPU. Page two: revenue and cash: gross volume, refunds, fees, net and payouts by month. Page three: retention by signup cohort and a filterable customer table. Projects I've led at Greenwolf Tech Labs include CFO and finance dashboards built in Data Studio that bring cash, revenue, spend and margin into one view, and Stripe is usually the revenue half of that picture.

Do Stripe API limits affect a Data Studio report?

They can, on large accounts using a live connector. Stripe's documentation sets a global limit of 100 requests per second in live mode, 25 per second for most individual endpoints, and 20 read requests per second on the Search API. Exceeding them returns 429 errors, which show up in Data Studio as charts that fail or come back partial.

There is also a read allocation: an account's read requests must not exceed an average of 500 per transaction over a rolling 30 days, with a minimum of 10,000 read requests a month. A small account with few transactions and a connector refreshing many charts all day can come closer to that ceiling than people expect. Stripe itself points data-heavy analytics towards Sigma or Data Pipeline instead of the API, and calls to its data and reporting products are excluded from the allocation.

If charts time out, reduce live load first: extend the data freshness setting on the data source, delete duplicate charts that request the same fields, and move high-traffic reports to BigQuery or a Sheet so Data Studio reads a copy. If the same report also pulls GA4, its separate quota of 14,000 tokens per project per property per hour applies too.

How do you connect Stripe to Data Studio step by step?

The clicks take minutes. The steps that protect you later are about keys, definitions and reconciliation, so they are part of the list.

Data Studio data sources run on the owner's credentials by default, which lets viewers see revenue without a Stripe login. That is convenient, but it also means anyone with edit access to the report can explore the data source, so share the report with view access and keep editors to the people who should see every transaction. Data Studio also gives no warning when a connector stops working, so add a last-updated date to the first page.

• Agree definitions: write down what revenue, MRR, churn and refunds mean for your business, and which Stripe number each should match.
• Choose the route: partner connector for one account and simple charts, BigQuery for MRR, cohorts and joins, Sheets for a small account on a budget.
• Create a restricted API key with read-only scopes under a company admin account, and store it with the business, not with whoever builds the report.
• Pull only what you need: balance transactions, charges, refunds, invoices, subscriptions, subscription items, prices and customers cover most dashboards.
• Model it: convert cents, convert currencies, flag test data, and build one table per question (one row per balance transaction, one row per subscription per month).
• Reconcile: match last month's gross volume, refunds, fees and MRR against the Stripe dashboard with the same time zone before anyone else sees the report.
• Share and schedule: share the report, not the data source, and schedule an email delivery for the month-end or weekly revenue review.

When is Stripe to Data Studio not worth it?

If Stripe is your only source and the questions are MRR, churn and trial conversion, Stripe's Billing analytics already calculates them, lets you configure the definitions and exports prebuilt reports. Adding a connector, a data model and another tool to maintain only pays off when you need something Stripe's screens cannot give you.

Good reasons: revenue must sit beside ad spend, CRM pipeline, GA4 or accounting data in one place; people who should see the numbers should not have Stripe dashboard access; you need history or segments Stripe cannot hold, such as revenue by acquisition channel; or several Stripe accounts must roll up into one view. Weak reasons: nicer charts, or rebuilding a Stripe screen that already works.

Do it yourself if you have one account, one currency and someone comfortable in Data Studio; a free tier and an afternoon is the right spend. Bring in help when totals do not match Stripe, when several currencies or accounts are involved, when MRR goes in front of investors, or when the report must keep running after its builder moves on.

How I handle Stripe to Data Studio projects

I start with a free review of your Stripe setup, the decisions the report must support and any spreadsheets you use today. I recommend the cheapest route that will hold up, which is often a connector you already pay for or Google's free BigQuery transfer, and quote a fixed price for the build.

The work covers the data model (cents, currencies, fees, refunds and an agreed MRR definition), the dashboard, reconciliation against the Stripe dashboard, and a handover so your team can add pages without me. Keys, datasets and reports live in your Stripe and Google accounts from day one, so nothing depends on my access.