Google Ads MCC : stratégie multi-comptes 2026

The official 2026 Google Ads limits set 20 level-1 sub-MCCs per root MCC, 6 nested hierarchy levels maximum, and 200,000 child accounts in the complete tree (official documentation on support.google.com). On French PPC agencies observed in public Google Ads benchmarks, the switch to an MCC structure typically starts between 5 and 8 managed accounts, and the introduction of sub-MCCs between 30 and 50 accounts — well before the technical limits, it's operational readability that guides the decision.

Should you open an MCC from the 3rd client account? Not systematically — the MCC introduces a layer of governance and steering that only makes sense from a certain volume. This article exposes the complete methodology: MCC vs isolated accounts decision criteria, sub-MCC architecture and permission hierarchies, consolidated billing vs separate billing choice, cross-account reporting stack (Looker Studio, BigQuery export, scripts), industrializable MCC-level scripts, and multi-account audit. For account-by-account audit mechanics, read in parallel our Google Ads audit checklist. For ready-to-copy scripts, see our 10 Google Ads scripts guide.

When to switch to an MCC? Decision criteria

The MCC (My Client Center, renamed Manager Account in the Google Ads UI since 2018 but the acronym remains everywhere in documentation and scripts) is a management layer that oversees multiple child Google Ads accounts. Concretely, it's a specific account without its own ad serving, used to centralize permissions, billing, reporting, scripts and audiences for all child accounts it administers.

The decision to open an MCC rests on 4 practical criteria, to evaluate simultaneously. First criterion: number of managed accounts. From 3-4 accounts, the MCC becomes practical for quickly switching between accounts via a single Google login. From 8-10 accounts, the MCC becomes nearly indispensable for coherent steering — without MCC you change windows, multiplied by 10, per day, and steering quality drops mechanically.

Second criterion: resource sharing between accounts. If you manage multiple brands of the same e-com group sharing part of their audience (cross-brand site visitors, consolidated Customer Match, common remarketing lists), the MCC allows native cross-account audience sharing. Without MCC, you duplicate audiences manually account by account — high operational cost and desynchronization risk. Our MER calculator (Marketing Efficiency Ratio) measures overall marketing efficiency, not channel by channel.

Third criterion: consolidated reporting. If financial direction or an agency client requests aggregated multi-account monthly reporting, the MCC radically simplifies production: a single Looker Studio export connected to the MCC is enough to aggregate 100 accounts. Without MCC, aggregation goes through individual BigQuery export or through account-level API scripts — viable but much more complex.

Fourth criterion: permission delegation. An agency with 5 account managers managing 10 clients each needs to isolate permissions: each manager sees only their clients, the agency director sees everything, the client sees their single account. The MCC allows this granularity via sub-MCC hierarchy. Without MCC, permission management is manual account by account, with risk of access leak.

Reading: the "pragmatic limit" corresponds to the number of child accounts beyond which the Google Ads UI experience and script latency become daily annoyances. It's far below the official technical limits. The deeper the tree, the more the trade-off shifts: you gain in permission granularity but lose in steering simplicity. The practical rule: never add a hierarchy level without explicit business use case.

The common trap: opening an MCC too early, on only 2-3 accounts, on the pretext of "preparing for growth." The MCC introduces a complexity layer (different login, tree switching, permission settings) which has no ROI under 5 accounts. Conversely, delaying MCC opening after 15+ accounts accumulates huge operational debt — each late migration to an MCC costs 0.5 to 1 person-day per transferred account, plus the risk of breaking OAuth integrations (Looker Studio, scripts, custom API). The optimal switch window sits between 5 and 10 managed accounts.

MCC architecture: sub-MCC, hierarchies, permissions

MCC architecture rests on a tree hierarchy. The root MCC is the top account, which can administer up to 20 level-1 sub-MCCs (strict 2026 limit), each able to administer its own level-2 sub-MCCs, and so on up to 6 maximum levels. Child accounts (accounts actually serving advertising) can be at any tree level, attached to any MCC or sub-MCC.

Google Ads MCC permission levels are 4 in number: Email-only (notifications only, no UI access), Read-only (read without modification), Standard (read + modification, no permission management), Admin (read + modification + permission and billing management). For an agency, the proven practice: agency direction in Admin on root MCC, account managers in Standard on their dedicated sub-MCC, clients in Read-only or Standard on their single child account — depending on contract.

An often-overlooked point: a Google user with Admin access to the root MCC has recursive access to the entire sub-MCC tree and all child accounts. This propagation is powerful but dangerous: a root MCC Admin can modify or delete any child account. Limit the root Admin role to 2-3 people maximum in an agency, never to operational account managers. For quarterly permission reviews, set up a script or manual audit listing who has access to what across the tree.

Cross-domain access is the other critical MCC feature. If you manage 4 Google Ads accounts for 4 brands of the same e-com group sharing site visitors, you can configure cross-account audience sharing at the parent MCC level. This configuration is done once (in Tools > Audience Manager > Audience sources, MCC level) and benefits the entire tree automatically. Official documentation on support.google.com. GDPR limitations: cross-country sharing requires explicit legal agreement between entities controlling accounts.

Consolidated billing vs separate billing accounts

The billing choice is one of the most structuring — and one of the most frequently misconfigured. MCC consolidated billing allows having a single payment method (card or IBAN) that monthly debits all spending of attached child accounts, with a single aggregated Google invoice. Separate billing keeps each child account its own billing setup (card, IBAN, distinct invoices per account).

The decision rule depends on the business model. For a multi-brand or multi-country company managed by an internal team, consolidated billing is generally optimal: a single monthly invoice addressed to headquarters, a single payment method managed by financial direction, radical simplification of internal accounting. For a PPC agency managing client accounts in media billed directly by Google to the client, separate billing is often preferable: each client receives their Google invoice directly, pays Google directly, and the agency invoices management fees on top of the media service.

The frequent agency trap: confusing the management role (who steers the Google Ads account) with the payer role (who pays Google's invoice). The MCC allows separating both. An agency can administer a client account (MCC role) without being the payer of that account (billing setup role) — it's even the recommended configuration for most agency-client contracts. On the contractual side, this separation simplifies end-of-contract transfers: revoking MCC access doesn't touch the billing setup and the client retains control of their payment method.

On the VAT and European billing side, consolidated MCC billing raises specific questions. If your MCC consolidates spending across multiple EU countries (France, Germany, Spain for example), Google issues a single invoice with VAT according to payer headquarters country rules (intra-community or local). For multi-country analytical accounting, you'll have to disaggregate spending country by country via a script or BigQuery export, since the consolidated invoice no longer has per-account granularity. Official VAT documentation on support.google.com.

For accounts with Google promotional credit (welcome offers, commercial vouchers), beware: credits are attached to a specific billing setup. Transferring an account from one billing setup to another typically cancels remaining credits. Before any billing reorganization, verify the active credit balance and plan the transfer with your Google Account Strategist if the amount is significant.

Cross-account reporting: Looker Studio, scripts, BigQuery

Consolidated multi-account reporting is one of the primary MCC benefits. Three complementary approaches exist in 2026: native Looker Studio MCC-level connector, MCC-level Google Ads scripts with Sheets/CSV export, and BigQuery Data Transfer Service with consolidated Google Ads dataset. Each meets different needs.

Approach 1 — Looker Studio MCC connector (low effort, low flexibility). The native Google Ads connector in Looker Studio supports MCC connection, automatically aggregating all child accounts in a single dashboard. It's the quick solution to produce a monthly client reporting or direction dashboard. Limits: no custom joins with other data sources (CRM, GA4 cross-domain), latency on refreshes when more than 50 child accounts are consolidated, and schema fixed by the native connector. Ideal for 5-30 accounts, heavy beyond.

Approach 2 — MCC-level Google Ads Scripts (medium effort, high flexibility). An MCC-level script iterates on the list of child accounts and writes consolidated KPIs in Google Sheets via the Sheets API. Advantage: total control over computed metrics, periods, filters, conditional alerts. Disadvantage: code maintenance, execution latency (15-45 minutes for 50-100 accounts), Google Ads API quota limits (4,000 ops/day per account). Suits 30-100 accounts with custom business logic needs (weighted ROAS calculation, CPA drift alerts, etc.). For concrete examples, see our 10 Google Ads scripts guide.

Approach 3 — BigQuery Data Transfer Service (high effort, maximum flexibility). Google offers a native BigQuery connector that exports daily the totality of Google Ads datasets (campaigns, ad groups, keywords, conversions, change history, etc.) to a BigQuery project. Once in place, you join this data with your CRM, GA4 BigQuery export, internal financial data, and build a complete BI reporting. It's the stack adopted by most enterprise agencies and €50M+ revenue companies. Official documentation on cloud.google.com. BigQuery cost typically €30-150/month for a consolidated 50-100 account MCC.

The practical rule observed on aggregated agency Google Ads benchmarks: under 20 accounts, Looker Studio MCC connector is enough. Between 20 and 80 accounts, MCC scripts + Sheets are the sweet spot. Above 80 accounts or with external data join needs, BigQuery Data Transfer becomes essential. Reporting SaaS (Supermetrics, Funnel.io, AdEspresso) are a pragmatic alternative for agencies without internal dev capacity — monthly cost €200-2,000 depending on volume, but with delegated maintenance. For a structured client reporting guide, see our 10-KPI Google Ads client reporting guide.

MCC-level scripts: 4 industrializable use cases

MCC-level scripts are one of the most under-exploited levers by mid-market agencies in 2026. An MCC-level script is exactly like a classic Google Ads script, but it executes at MCC level and programmatically iterates over child accounts via the MccApp.accounts() object. Each execution can process a few targeted accounts via labels, or the entire tree, and produce consolidated actions or reports.

Here are the 4 most mature use cases on observed aggregated Google Ads benchmarks. All are deployable in 2-5 person-days by a developer familiar with Google Apps Script.

Use case 1 — Consolidated tracking anomaly audit. The script traverses all child accounts, verifies for each account that (1) at least one main conversion is defined, (2) the conversion status is "Recording conversions" and not "Inactive", (3) the Google Ads tag is present and functional via API diagnostic, (4) attribution is in data-driven and not last-click for accounts having 50+ conversions/month. The script writes the result in a consolidated Sheet with conditional coloring (red if anomaly). Time saving: 4-6 hours/month manual becomes 5 minutes auto + 30 minutes review.

Use case 2 — Budget burn rate alerts. The script runs 3-4 times per day, traverses all accounts, and alerts by email if an account has consumed more than 90% of its monthly budget before the 25th of the month (or more than X% of daily budget before 4pm). Configuration: thresholds parameterizable per account via labels. Target: avoid an account falling "out of budget" at 6pm on the 28th of the month on a poorly calibrated Smart Bidding scaling trigger. For budget pacing fundamentals, see our budget pacing guide.

Use case 3 — Bulk update of negatives or ad copy on regulatory evolution. When new regulation arrives (for example: prohibition of a superlative term, Quality Score update, new vertical compliance), an MCC bulk update script can add a list of negative keywords to 100 child accounts in a few minutes, or massively pause non-compliant ads. This lever alone justifies script investment for agencies managing regulated verticals (health, finance, alcohol, gambling).

Use case 4 — Custom consolidated reporting. The script produces every Monday morning a consolidated multi-account report sent by email to agency direction or account managers, with: main KPI of the week (revenue, conv, CPA, ROAS), variation vs previous week, top 5 growing accounts, top 5 in alert, quality metrics (average Quality Score, search lost IS budget, search lost IS rank). Avoids weekly manual production and guarantees cross-portfolio reading at regular frequency.

Here is a minimal MCC-level script skeleton to start:

function main() {
  var accountIterator = MccApp.accounts()
    .withCondition("Status = ENABLED")
    .withLimit(100)
    .get();

  var results = [];

  while (accountIterator.hasNext()) {
    var account = accountIterator.next();
    MccApp.select(account);

    var stats = AdsApp.currentAccount().getStatsFor("LAST_7_DAYS");
    results.push({
      accountId: account.getCustomerId(),
      accountName: account.getName(),
      cost: stats.getCost(),
      conversions: stats.getConversions(),
      cpa: stats.getCost() / Math.max(stats.getConversions(), 1)
    });
  }

  // Push results to Sheet, send email, raise alerts...
  Logger.log(JSON.stringify(results, null, 2));
}

Limitations to know: an MCC-level script has an execution quota of 30 minutes maximum per run. To handle 100+ accounts with heavy operations (changes history, structural modifications), you have to either split into multiple MCC scripts targeting distinct sub-MCCs, or parallelize via MccApp.accounts().executeInParallel(...) which executes the code in parallel on multiple accounts simultaneously. Official documentation on developers.google.com.

Multi-account audit: consolidated checklist

Auditing 50 accounts in pure manual mode is a 30-40 person-day investment. With a scripts + dashboard + targeted qualitative audit stack, the same perimeter is handled in 4-6 person-days while increasing audit depth. Industrialization goes through 3 successive audit levels, from automated quantitative to human qualitative.

Level 1 — Automated audit via MCC script (day 1-2). The audit script produces a consolidated export for each child account with 25-35 automatable controls:

• Average Quality Score weighted by impressions excluding brand
• Percentage of keywords in exact match vs phrase vs broad
• Presence of at least 3 active RSAs per ad group
• Active conversion tracking and in data-driven attribution
• Search lost IS budget above 20% (under-investment signal)
• Search lost IS rank above 30% (competitiveness signal)
• Critical missing negative keywords ("free", "internship", "cheap" depending on vertical)
• Daily budget vs actual spend (account that caps daily)
• Minimum Smart Bidding compliance (30 conv/month for Target CPA, 50/30d for Target ROAS)
• Presence of an active Customer Match list

The script flags out-of-norm accounts with severity score (red / orange / green), producing a prioritized view for the human auditor.

Level 2 — MCC Looker Studio dashboard (continuous review). In parallel with scripts, an MCC-level Looker Studio dashboard continuously displays main KPIs per account with drift heatmap. Allows visually identifying alert accounts and cross-portfolio trends (for example: all Shopping accounts dropping simultaneously over a week — signal of common Merchant Center feed problem).

Level 3 — Targeted human qualitative audit (day 3-6). The human auditor focuses on the 10-20 accounts flagged by levels 1 and 2, and proceeds to in-depth qualitative review: campaign structure, landing page quality, creative-keyword-LP consistency, strategic opportunities (uncovered verticals, missing audiences, untested formats). It's at this level that the senior auditor's value-add concentrates — levels 1 and 2 industrialize low-value-add work.

For structured annual or quarterly multi-account audit, our free Google Ads audit provides a consolidated report in 72h: Quality Score analysis weighted by investment, detection of cross-account tracking and bidding anomalies, inter-account budget allocation recommendations, and prioritized optimization roadmap. For an agency managing 30+ accounts, the report serves as input for the annual portfolio review. For detailed account-by-account audit mechanics, see our Google Ads audit checklist.

Migration and account transfers

Three migration scenarios come up frequently: (1) consolidation of multiple isolated accounts into a newly created MCC, (2) transfer of an account from one MCC to another (agency change or internal reorganization), (3) restructuring an existing MCC into sub-MCCs to gain granularity.

Scenario 1 — Migration of isolated accounts to MCC. The operation is technically simple: from the root MCC, request linking the child account via Customer ID; on the child account side, accept the invitation from Tools > Setup > Account access. Linking doesn't break ongoing campaigns, doesn't change tracking, doesn't disrupt Smart Bidding learning. One major trap: if the child account had its own individual billing setup and you want to switch to consolidated MCC billing, the operation requires creating a new billing setup at MCC level, and progressive closure of the account's billing setup. During transition (typically 7-15 days), keep both billing setups active to avoid any serving interruption.

Scenario 2 — Account transfer between MCCs. The child account can be moved from one parent MCC to another via simple revocation + new invitation. Elements that automatically follow: campaigns, ad groups, keywords, ads, conversions, audiences, history. Elements that may break: (1) MCC-level scripts targeting the old MCC, (2) GA4 or Looker Studio links configured at the old parent MCC level, (3) cross-account audience sharing if configured at source MCC level. Before any transfer, inventory dependencies and reconfigure on the new MCC side.

Scenario 3 — Restructuring existing MCC into sub-MCCs. This is the most complex scenario. If you've accumulated 60-80 child accounts directly attached to the root MCC and want to introduce 4-5 sub-MCCs to better organize, the sequence is: (1) create new empty sub-MCCs from the root MCC, (2) move each child account one by one from root to target sub-MCC (revocation + invitation), (3) reconfigure account manager permissions on new sub-MCCs, (4) update scripts and reporting to account for new hierarchy. Typical time investment: 0.5-1 person-day per 10 migrated accounts, i.e. 4-8 days for an 80-account portfolio.

Pre-migration best practice: locally export all critical configurations (shared audiences, scripts, change history of last 30 days, Google Analytics links) before any transfer. If a regression occurs post-transfer (rare but possible on complex accounts), the pre-migration snapshot serves as reference for rollback or manual reconstruction.

On the execution calendar, two yearly windows should be avoided for any MCC migration: the Black Friday / Cyber Week period (mid-November to mid-December) where the slightest Smart Bidding learning disruption can cost dearly in performance, and the Q1 e-com recovery period (January-February) where accounts emerge from low season and start a new budget pacing. Prefer calm periods (March-April, June-July, October) for structural migrations. For seasonality budget arbitration, see our worldwide budget seasonality guide. For real estate lead gen accounts that have their own seasonality, see our 2026 Google Ads real estate lead gen guide.

Building and steering a coherent MCC architecture for 2026 is less a question of tool than operational governance. The real value of an MCC measures by the agency's or group's ability to industrialize audit, reporting, scripts and permission management across the entire portfolio — not the simple administrative aggregation of accounts. Agencies standing out aren't those with the most accounts under MCC, they're those with the lowest steering quality dispersion between their accounts, measured by Quality Score, tracking compliance, and CPA standard deviation excluding brand. A well-governed MCC is a sustainable competitive advantage; a poorly structured MCC is operational debt paid in lost hours every month.

Sources

Official sources consulted for this guide:

• support.google.com
• support.google.com
• support.google.com
• blog.google

FAQ