How to Connect Google Ads to Looker Studio, Step by Step

How do you connect Google Ads to Looker Studio?

Looker Studio's native Google Ads connector links a Google Ads account directly to a Looker Studio report, using Google's own built-in integration rather than any outside app. You add it from inside Looker Studio itself: sign in with a Google account that already has access to the Google Ads account, search the connector gallery, and authorize the connection. No API console, no separate software install, and no paid subscription stands between you and a working report. Looker Studio's core product carries "No charge," stated verbatim on Google's pricing page as of August 12, 2026, and the Google Ads connector is included at that price for any account with access to the ad account.

The rest of this guide walks through the exact setup steps, then covers what the connector does not publish, the mistakes that quietly break a working connection, and the point where a paid pipeline earns its cost. Readers who want to see a finished Google Ads data source next to other channels can start with the Google Ads integration page.

What do you need before connecting Google Ads to Looker Studio?

Connecting Google Ads to Looker Studio requires four things in place before you open the connector gallery: a Google account with access to the Google Ads account, a Looker Studio sign-in under that same identity, the specific account (or MCC/manager account) you plan to report on, and a decision on how granular the report needs to be. None of these carry a separate cost -- Looker Studio's own pricing page lists the product itself at no charge, as of August 12, 2026.

• A Google account with Google Ads access. Any level -- owner, admin, standard, or read-only -- works, since the connector inherits whatever permission the signed-in account already holds.
• A Looker Studio account. Free, tied to the same Google identity, with no separate signup step.
• The account ID or MCC view. An MCC (manager account, Google's term for an account that oversees several client Google Ads accounts) lets you pick one child account as a single data source, or add several child accounts as separate sources to blend later.
• A target reporting level. Account, campaign, ad group, ad, or keyword -- each level exposes a different set of fields, so deciding this first avoids rebuilding the data source afterward.

View-only access on the Google Ads account is enough to build a report; the connector never asks for more than the signed-in account already has. Someone who can only view campaigns in Google Ads can still pull every metric that access level exposes into Looker Studio -- the connector does not require edit or admin rights just to read data.

An MCC setup adds one more layer: instead of one Google Ads account, you choose among however many child accounts that manager account oversees, and Looker Studio treats each child account you add as its own independent data source. If the goal is a single agency-wide view across clients, that means building one data source per child account first, then blending them inside the report rather than expecting the MCC login to surface every client automatically. None of this requires code, a developer token, or direct API access -- that only becomes relevant later, once a report needs data volumes or account counts beyond what the interface itself supports. Looker Studio's connector catalog covers Google Ads alongside dozens of other data source integrations, all governed by the same sign-in-and-authorize pattern.

How do you connect Google Ads to Looker Studio step by step?

Connecting Google Ads to Looker Studio takes seven steps inside Looker Studio's own interface, from opening a new data source to sharing the finished report -- no code, no API console, and nothing beyond a browser and a Google account. Each step stands on its own, so this walkthrough works whether or not you have read anything else about the connector first.

1. 1

   Start a new data source

   Open Looker Studio and create a new report or a new data source from the home screen.

2. 2

   Select the Google Ads connector

   Search the connector gallery for Google Ads and choose the official Google connector from the results.

3. 3

   Sign in and authorize

   Sign in with the Google account that has access to the Google Ads account, then approve the permission request Looker Studio shows.

4. 4

   Choose the account

   Pick the specific Google Ads account, or select a child account under an MCC manager account, as the data source.

5. 5

   Pick the reporting level

   Choose account, campaign, ad group, ad, or keyword level, since each level exposes a different set of available fields.

6. 6

   Connect and review fields

   Click Connect, review the fields and metrics Looker Studio auto-detects, then add the data source to your report.

7. 7

   Schedule refresh and share

   Set a data refresh schedule, then share or embed the finished report using the sharing controls built into Looker Studio.

Once the data source connects, Looker Studio auto-detects the standard Google Ads fields -- impressions, clicks, cost, conversions, campaign name, and ad group name -- based on Google's own published integration between the two products. From there, building a chart or table follows the same drag-and-drop process as any other Looker Studio data source. Many teams add a Google Analytics integration to the same report right after this step, so ad spend and on-site behavior sit side by side.

What can't the native Google Ads connector do in Looker Studio?

Google's own Looker Studio pages do not publish an explicit row or data-volume limit for the Google Ads connector, as of August 12, 2026 -- a genuine gap in what Google discloses, not proof that no ceiling exists. The connector also reports on one Google Ads account, or one MCC child account, per data source, with no cross-platform blending built into the connector itself.

If a project moves past Looker Studio's interface into direct access to the Google Ads API (Google's programmatic interface for managing accounts and pulling data outside the UI), Google's own developer quotas take over. Explorer access allows 2,880 operations per day and Basic access raises that to 15,000 operations per day, per Google's quota documentation, as of August 12, 2026. That's a Google Ads API limit, not a Looker Studio one, and it only applies once someone builds a custom connector or pulls data directly instead of through Looker Studio's own UI. Most reports built through the native connector never touch this ceiling, since Looker Studio's UI manages the underlying API calls on the report owner's behalf.

For agencies managing many client accounts, Looker Studio Pro adds team workspaces and organization-level content ownership at $9 per user per project per month, as of August 12, 2026 -- a workflow upgrade, not a data-volume one. Reports built on Google Ads numbers show a narrower slice of the customer journey than most businesses need; pairing this connector's output with marketing attribution models is one way to see which touchpoints actually deserve credit before anyone cuts a channel's budget.

What common mistakes break a Google Ads to Looker Studio connection?

Most Google Ads to Looker Studio connections fail without ever showing an error message. The most frequent causes are a signed-in Google account with the wrong access level on the Google Ads account, mismatched date ranges or conversion definitions between Looker Studio and Google Ads' own interface, and a report built on one MCC (manager account) child account that never picks up sibling accounts automatically. Each has a specific fix once you know where to look.

• Mismatched date range or conversion action. Comparing a Looker Studio chart to Google Ads' own dashboard on different date ranges, or with a different conversion action selected in each, produces numbers that look wrong but aren't. Aligning both to the same date range and the same conversion definition resolves it.
• Assuming an MCC connection covers every child account. Looker Studio treats each child account added under an MCC as its own separate data source. Connecting the manager account itself does not automatically surface every client account underneath it.
• No refresh schedule set. A data source without a refresh schedule shows the numbers from whenever it was last pulled, not the current day's spend and conversions -- and a stakeholder looking at a dashboard has no way to tell the difference unless told.
• Sharing a report without checking underlying access. Looker Studio inherits its permissions from the Google Ads account itself, so sharing a report link with someone who lacks access to that Google Ads account produces an error or a blank view on their end, no matter how the link is shared.

Fixing these points before publishing a report saves the back-and-forth of stakeholders questioning numbers that were correct all along. Reports built on accurate, consistently refreshed data are also the ones worth feeding into marketing ROI reporting, where small mismatches compound into wrong budget decisions.

When should you use a third-party connector instead of Google's native one?

A paid pipeline such as Supermetrics or Windsor.ai earns its cost once a report needs to blend Google Ads with non-Google channels in a single destination, or needs an explicit published row cap to plan usage around -- neither of which the free native Looker Studio connector provides. Supermetrics starts at $55 per month and Windsor.ai runs a $0 per month Free plan, both as of September 6, 2026.

Every number in this comparison comes from each vendor's own pricing page, checked on the date shown. Where a vendor page states no figure, the cell reads "not published" rather than carrying an estimate.

Both Supermetrics and Windsor.ai list Looker Studio explicitly among their supported destinations, alongside BigQuery, Snowflake and several other warehouses. Moving to either one does not mean leaving Looker Studio as the reporting layer -- it means feeding Looker Studio from a different pipeline instead of the native connector.

The practical way to use this comparison is to count two numbers first: how many non-Google channels need to land in the same report, and how many separate Google Ads accounts need to be blended together. Match those two counts against the plan tiers in the comparison, rather than against marketing copy, before deciding between Supermetrics alternatives and Windsor.ai alternatives as a next step.

How do you automate Google Ads reporting in Looker Studio?

Automating Google Ads reporting in Looker Studio starts with the connector's own refresh schedule, which keeps a report current without anyone manually reconnecting it. Once a report needs more than Google Ads and Looker Studio alone -- several ad accounts, other channels, or CRM data -- a platform built to consolidate the whole marketing stack removes the need to maintain one connector per channel by hand.

Looker Studio's built-in refresh schedule alone covers most single-account, single-channel reporting needs. Set an interval once, and every chart pulls fresh Google Ads numbers on that schedule without a manual re-pull. For a team running one Google Ads account into one report, this is the entire automation story.

Teams managing many Google Ads accounts, or blending Google Ads with channels like Meta Ads or TikTok Ads, outgrow that single-connector setup. Paid pipelines such as Supermetrics and Windsor.ai automate that consolidation instead of rebuilding each connector manually inside Looker Studio.

For teams whose real need is broader marketing automation and analytics, not only a Google Ads-to-Looker-Studio pipeline, AdMetric is an AI marketing automation and analytics platform built for small and mid-size businesses. It runs a 7-day free trial with no credit card required.

Frequently asked questions about connecting Google Ads to Looker Studio

The following seven questions cover what people ask most when connecting Google Ads to Looker Studio: cost, mismatched numbers, multi-account setups, API access, row limits, the native-versus-paid-pipeline choice, and agency use. Each answer stands on its own and uses only sourced facts, including AdMetric's pricing for teams comparing a broader platform to a single connector.