Salesforce to Data Studio: how to connect your CRM, what each route costs and how to keep pipeline numbers right

Is there a native Salesforce connector for Data Studio?

No. 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. Salesforce is not on that list, and the April 2026 rename from Looker Studio back to Data Studio did not change it.

That leaves two families of options. Either a partner connector reads Salesforce when a chart loads, or a pipeline copies Salesforce into something Data Studio already reads natively (a Sheet, BigQuery or a SQL database). The first is quicker to set up. The second is what holds up once you need pipeline history, several years of closed-won data or a join to ad spend.

One consequence matters for budgeting: Salesforce itself charges nothing extra for API reads within your org's allocation, but every route except CSV uses that allocation. Count it before you pick a tool, especially if your org already runs marketing automation, enrichment or ERP syncs.

What are the ways to get Salesforce data into Data Studio?

There are five practical routes, and they trade setup speed against freshness, volume and control over the data model. The table compares them the way I scope them for clients.

Two questions settle most choices. How many rows does the busiest chart need (a few thousand open opportunities, or several years of every stage change)? And does the report need anything that is not in Salesforce, such as Google Ads cost, GA4 sessions or invoiced revenue? Small and Salesforce-only points to a connector. Large or joined points to BigQuery.

How much does a Salesforce to Data Studio connection cost?

Entry costs run from free to roughly $50 to $75 a month for a direct connector, and BigQuery costs depend on compute rather than rows. The figures below come from the vendors' own pages and Google Cloud's blog, read in October 2026. Vendor prices change often, so confirm on the pricing page before you commit.

Price the plan you will need in a year. Count your Salesforce orgs, the objects you need (opportunities, accounts, leads, campaigns, custom objects), how fresh the pipeline view must be, and whether the same report also needs paid media. A forecast reviewed every Monday does not need a 15-minute refresh, and paying for one is wasted money.

Should you use Google's Salesforce transfer to BigQuery?

For most orgs with more than a few thousand opportunities, yes. BigQuery Data Transfer Service has a Salesforce connector that loads Sales Cloud objects into BigQuery on a schedule, and Data Studio reads BigQuery natively, so there is no third-party connector in the reporting path.

According to Google Cloud's documentation (last updated October 15, 2026), the transfer authenticates through a Salesforce Connected App using the OAuth client credentials flow, so a Salesforce admin creates the app and grants the api scope. It supports Sales Cloud objects that work with Bulk API version 64.0, excluding objects with binary fields such as Attachment, ContentVersion and Document. The shortest interval between runs is 15 minutes and the default is 24 hours. You choose full loads or incremental loads, with incremental runs in append or upsert mode. Google's August 2026 product blog added native incremental updates for Salesforce and describes third-party ingestion as consumption based, at under 6 cents per slot-hour in major regions.

Two limits shape how I build on it. Incremental transfers do not carry deletions, so a deleted opportunity stays in BigQuery until a periodic full load or a cleanup query removes it. And append mode can duplicate rows, so I use upsert for opportunities and build every report on a modelled view (one row per opportunity, with owner name, stage dates and converted amount), partitioned by date where tables are large. If Google changes the raw schema, you fix one view instead of every chart.

Do Salesforce API limits affect a Data Studio report?

They can, because every connector, Sheets refresh and transfer run spends calls from the same daily allocation as your other integrations. Warehouse routes spend far fewer calls than live connectors, because Data Studio reads the copy rather than Salesforce.

Coupler.io's summary of Salesforce's published allocations (August 2025) puts Professional Edition with API access and Enterprise Edition at 100,000 requests per rolling 24 hours plus 1,000 per user licence, and Unlimited and Performance Editions at 100,000 plus 5,000 per licence. Developer Edition gets 15,000. A 50-user Enterprise org therefore has about 150,000 calls a day, shared with every other app connected to it.

There is a second limit that catches more people. Salesforce's Reports API returns at most 2,000 detail rows per report run, a cap documented by Microsoft for its own Salesforce Reports connector and by Xappex, and it cannot be raised. If a connector reads a Salesforce report, a list of 5,000 open opportunities quietly arrives cut short. Point the connector at the object or a SOQL query instead, or move the data to BigQuery. If the same dashboard also reports GA4, remember its separate quota of 14,000 tokens per project per property per hour.

Why do Salesforce dashboards in Data Studio show the wrong numbers?

Mostly because Salesforce's data model does not fit a flat table, not because the connector failed. Opportunities, accounts, contacts, leads and campaigns are separate objects joined by lookups and junction objects, and Data Studio wants one row per thing you count. Work through this list before you blame the vendor.

The common fix is to decide what one row means (one opportunity, one lead, one stage change), build that table once in BigQuery or a Sheet, and point every chart at it. A Data Studio blend that joins opportunities to contacts will repeat each amount for every contact role and inflate pipeline value; blends are also capped at 5 sources and support equality joins only.

• Contact roles: an opportunity with three contact roles appears three times when joined to OpportunityContactRole, tripling its amount in any SUM.
• Multi-currency: orgs with several currencies need the converted amount, not Amount, or a euro deal is added to a dollar total at face value.
• Stage history: the StageName field shows where a deal is now. Velocity and conversion reports need OpportunityHistory or field history, or daily snapshots in BigQuery.
• Owners: connectors return OwnerId, an 18-character ID, not a name. Without a User lookup, charts show IDs instead of reps.
• Converted leads: a converted lead and its new contact both carry a lead source, so counting both double counts marketing's numbers.
• Record types and closed lost: filter on record type and IsClosed or IsWon explicitly, or renewals and lost deals leak into new-business pipeline.
• Fiscal periods: if your org uses a custom fiscal year, a calendar quarter in Data Studio will not match the quarter in Salesforce reports.
• Deleted records: incremental pipelines and some connectors keep deleted rows, so totals drift above Salesforce's own reports.

What should a Salesforce dashboard in Data Studio include?

Build it around the decisions leadership makes every week: where the quarter will land, which channels create pipeline that closes, and which deals are stuck. A first version usually fits on three pages.

Page one is pipeline and forecast: open pipeline by stage and close month, weighted pipeline against quota, created and won this period, win rate by segment and average days to close. Page two is source quality: leads and opportunities by lead source and campaign, lead-to-opportunity and opportunity-to-won conversion, and won revenue beside Google Ads and LinkedIn spend so cost per opportunity is visible. Page three is team execution: pipeline by owner, deals with no stage change in 30 days, and a filterable opportunity table with a link back to the record.

Under the hood, use a calculated field with a CASE statement to map raw StageName values into the four or five labels your board uses, set the date range control on close date for pipeline pages, and keep flexible-schema sources (BigQuery or Sheets) so tables are not squeezed by the 10 dimension and 20 metric cap on fixed-schema sources. Projects I've led at Greenwolf Tech Labs include marketing dashboards built in Data Studio that bring multi-channel spend, leads and return across Google Ads, Meta, LinkedIn, GA4 and Search Console into one view, and CRM pipeline is the natural next page on that kind of report.

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

The clicks take minutes. The steps that save you later are about ownership, scope and reconciliation.

Data Studio data sources use the owner's credentials by default, so viewers see Salesforce data without a Salesforce licence. That is convenient, but if the connecting user is a contractor or someone who later leaves, every chart breaks the day that user is frozen, and Data Studio sends no warning when a connector stops working.

• Write down the six or seven numbers leadership reviews and the exact definition of each, for example won amount by close date in corporate currency, new business record type only.
• Choose the route: a free partner connector for a small single-org report, BigQuery for history, joins or more than a few thousand rows.
• Connect with a dedicated integration user or Connected App owned by a Salesforce admin, never a personal or freelancer login.
• Pull objects or SOQL, not Salesforce reports, so the 2,000-row cap never applies.
• Model one row per opportunity with owner name, converted amount, record type and stage dates before Data Studio sees the data.
• Reconcile last quarter's won amount and deal count against a Salesforce report with identical filters before anyone else sees the dashboard.
• Share the report rather than the data source, and add a scheduled email delivery for the weekly pipeline meeting.

When is Salesforce to Data Studio not worth it?

If Salesforce is your only source and every viewer already has a Salesforce licence, its own reports and dashboards may be enough. Copying data out adds a pipeline, a data model and something else to maintain, so do it for a clear reason.

Good reasons: leadership wants pipeline beside ad spend, GA4, finance or product data; people who need the numbers do not hold Salesforce licences; you need history, snapshots or definitions that Salesforce reports struggle with; or your company already reports everything else in Data Studio. Weak reasons: a different chart style, or rebuilding a Salesforce dashboard that already works.

Do it yourself with a free connector if you have one org, a single currency and under 2,000 rows in the views that matter. Bring in help when numbers do not match Salesforce, when several record types, currencies or orgs are involved, or when the report has to keep running after the person who built it moves on.

How I handle Salesforce to Data Studio projects

I start with a free review of your Salesforce objects, the questions the report must answer and any dashboards you already have. I recommend the cheapest route that will hold up, often a free connector for small orgs or Google's BigQuery transfer for larger ones, and quote a fixed price for the build.

The work covers the data model (one row per opportunity, stage history, owner and currency handling), the dashboard, reconciliation against Salesforce reports, and a handover so your team can add fields and pages without me. Everything is set up in your own Google Cloud project and Salesforce org from day one, so nothing depends on my logins.