Updated 2026-11-06

Multi-account Google Ads roll-up in Looker Studio for agencies (without a $1k connector)

An agency owner should not have to open twelve client accounts to answer a simple Monday question: which accounts need attention first? But a roll-up is useful only if it preserves the definitions behind each number. Adding every client’s spend into one impressive chart can hide a broken conversion action, mixed currencies, or a client who can suddenly see another client’s data.

You can build the internal version with Google’s native Google Ads connector and a manager account (MCC). There is no Porter Metrics or Supermetrics subscription to buy for this Google-Ads-only setup, and no $1k connector bill. The native connector supports up to 50 selected sub-accounts per data source, according to Google’s connector documentation.

This guide builds a compact triage page, then adds client-safe detail pages. Start with the free Google Ads Looker Studio template if you want the campaign fields already arranged, or follow the steps in a blank report.

What the agency roll-up should answer

Keep the opening page operational, not decorative. It should answer four questions:

1. Did an account stop spending, recording conversions, or receiving clicks unexpectedly?
2. Which accounts have the largest efficiency change compared with the previous period?
3. Which accounts need a budget, tracking, or campaign review?
4. Where do I open the client-specific report to investigate?

A single table with Account name, Cost, Clicks, Conversions, Cost / conv., and previous-period comparisons covers most of that. Add a written status column only if your team maintains it; Looker Studio cannot know that a tracking migration or a planned promotion explains a change.

Do not make a cross-client ROAS chart your first build. Lead-oriented accounts often use Conversions without values, ecommerce accounts may have different primary conversion actions, and account currency can differ. Pick a common operational baseline first. Compare efficiency trends inside each account before declaring a portfolio-wide winner.

Before you connect: a 10-minute account audit

A little preparation prevents a misleading dashboard:

• Confirm MCC access. Use a Google identity that can access the manager account and all intended sub-accounts. Read-only Ads access is sufficient for reporting; Looker Studio access alone does not grant Ads access.
• List the included accounts. Record their names, customer IDs, time zones, currencies, and primary conversion goals in your agency’s account register. Do not infer goals from the number labelled Conversions.
• Choose the reporting window. Last 28 days compared with the previous period smooths some day-to-day noise. Add last 7 days as a separate view if accounts have enough volume.
• Decide what “conversion” means. The native connector exposes Conversions and All conv.; keep one definition across charts. For a consistent portfolio view, ask each account owner which actions are primary and included in Conversions.
• Separate currencies before adding cost. Cost is not automatically a comparable business metric across currencies. Use account filters and local-currency detail pages, or maintain an explicitly labelled currency-normalisation source outside this native-only report.

This audit is also where you document known gaps. A new account with three conversions cannot be managed with the same threshold as one with three hundred.

Step 1: connect the MCC with the native Google Ads connector

1. In Looker Studio, choose Create → Data source → Google Ads.
2. Authorise the Google identity with the appropriate Ads access.
3. In the Accounts panel, choose MANAGER ACCOUNTS, select the MCC, and then select the sub-accounts you want to include. You can select up to 50 per data source.
4. Use Overall Account Fields for the account-and-campaign reporting described here, then choose Connect.
5. In the field list, locate Account name, Cost, Impressions, Clicks, Conversions, and Cost / conv. Keep the configuration note with your MCC ID and selection date for maintenance.

You now have a multi-account source; you do not need to blend 50 individual account sources just to show Account name beside Cost. Blending selected accounts one by one is unnecessary for this native MCC connection.

If your agency manages more than 50 accounts, native-only reporting requires splitting accounts into deliberate groups across additional sources. That introduces blend and maintenance trade-offs; a warehouse or paid connector may then be reasonable. Do not buy one merely to solve a 10-account Google Ads roll-up.

Step 2: build the triage table

Add a table and use these settings:

Use comparison deltas and sort by Conversions or efficiency change, not just Cost. Avoid summing mixed currencies.

Add a date range control and an Account name drop-down. Optional scorecards should never replace the rows; their totals need currency and conversion-definition notes.

Flag unexpected zero conversions or efficiency changes alongside absolute volume. A 70% improvement on two conversions is not the signal it is on two hundred; confirm tracking before changing bids.

Looker Studio comparisons are diagnostic, not automated quality assurance. Avoid labelling a universal CPA ceiling across every client unless their commercial targets genuinely match.

Step 3: add account-level drill-down pages

The roll-up tells you where to look. A second page tells you what to inspect. Reuse one single-account Google Ads template structure for this detail view:

1. Add the same MCC data source and an Account name control.
2. Add Campaign as the primary dimension, with Cost, Conversions, Cost / conv., and Search impression share.
3. Add the campaign scatter and lost-impression-share review described in How to spot wasted Google Ads spend in Looker Studio.
4. Include keyword and search-term pages only for campaign types where those dimensions apply.
5. Put an account ownership note on the page: who checks it, when, and which conversion action the client considers valuable.

For client-facing presentation, follow the white-label Looker Studio report guide: separate copies are usually the cleanest permission boundary, while a shared master keeps your chart design consistent.

Link the roll-up to separate client reports through your account directory; that is safer than expecting clients to use a filter.

Step 4: choose credentials and sharing without exposing clients

This is the most important setup decision.

Internal roll-up: share it only with staff allowed to see every account. Google’s credential guidance explains that owner’s credentials let viewers query using the source owner’s access, whereas viewer’s credentials require each viewer to have their own underlying data access. Viewer credentials are a useful second boundary for internal reporting; owner credentials can be convenient, but they do not restrict rows to the viewer’s own Ads permissions.

Client report: use a separate report containing only that client’s data. Do not give a client the all-account roll-up and assume a filter, page-level control, or hidden page creates a security boundary. Share the client copy as viewer-only, then test it using a non-editor identity that represents the client.

Template distribution: connect sample data for a public preview, not live client accounts. Keep client-facing reports, the internal roll-up, and public templates distinct.

At hand-off, check report access, source credentials, included accounts, and scheduled-email recipients. Repeat after an account leaves the MCC.

A 20-minute Monday agency workflow

1. Confirm the account selection and exclusions.
2. Review last 7 days and 28 days; an empty recent interval may be a tracking issue.
3. Open the drill-down and identify campaigns explaining efficiency changes.
4. Check conversion configuration and the Google Ads UI before recommending an intervention.
5. Record one owner and one next action per flagged account: tracking review, search-term cleanup, budget reallocation, creative work, or client question.
6. Use local-currency detail views; do not total mixed currencies.

The portfolio page is for prioritisation, not uncontextualised client rankings.

Native connector versus a paid connector

For Google Ads data alone, the native connector already supplies the MCC roll-up, familiar fields, and no separate connector subscription. You can build the first version without Porter, Supermetrics, or a $1k annual add-on.

Evaluate a paid service when you need non-Google platforms, exceed native limits, or need governed historical storage. That is not a prerequisite for Google Ads agency reporting.

If repeated template setup is the bottleneck rather than connectors, ReportKit Pro provides the multi-account and white-label pack for $39 one-time, with a 14-day refund under the published refund policy. It uses native Google connections rather than replacing them with another monthly connector subscription. The free starter remains useful for individual client pages; Pro is a time-saving option, not an artificial limit on the free report.

FAQ

Is an MCC required?

You need an MCC to select multiple sub-accounts in one native source. Otherwise, separate single-account reports are simpler than manual blending.

Can I include more than 50 accounts?

Not in one native Google Ads data source. Google documents a maximum of 50 selected sub-accounts. Additional native sources can cover deliberate account groups, but a unified larger portfolio needs careful blending or a different data pipeline.

Does Looker Studio convert account currencies?

Do not assume a native Cost total is currency-normalised. Keep cost by account, verify each account’s currency in Google Ads, and introduce a documented conversion layer if you need one portfolio total. Clearly label its exchange-rate source and date.

Why does Conversions differ between clients?

Primary conversion actions, attribution, time zones, and Conversions versus All conv. can differ. Match the Ads UI settings and document unresolved differences.

Is a client filter enough to protect other accounts?

No. Treat a filter as navigation, not a client-data security boundary. Give each client a separate report with only their data and test the shared view with a non-editor account.

Do I need a connector subscription for this tutorial?

No. It uses Google’s native connector; paid options matter for non-Google platforms or requirements beyond native limits.

Does this replace campaign optimisation?

No. The roll-up prioritises account reviews. Search-term waste, budget constraints, and Ad Rank issues still belong in the wasted-spend workflow and Google Ads itself.

A trustworthy agency roll-up is deliberately boring: explicit account selection, common definitions, visible currency limits, and a clear path to investigation. Native MCC reporting gets you there without another connector invoice; careful permissions make it safe to use.