Google Ads Manager (MCC) Accounts: The Complete Guide

If you're managing more than one Google Ads account — for different clients, different brands, or different locations of the same business — a manager account (MCC) is the structure Google expects you to use, and trying to work around it by logging in and out of separate accounts individually gets unworkable fast.

This covers what an MCC actually is, how to set one up and link accounts to it properly, the permission levels worth understanding before you invite anyone, and a section most guides skip entirely: why third-party tools connected to your MCC sometimes can't see campaigns at all, even though the connection looks successful. That last part comes from direct experience fixing exactly that problem, not from a general description of the feature.

None of this requires any tool beyond Google Ads itself to set up correctly — the setup, linking, and permission steps below are all native functionality. The API/integration section further down matters specifically once you start connecting other software to an MCC-managed account, which is common enough that it's worth understanding before it trips you up rather than after.

What an MCC actually is

MCC stands for "My Client Center" — Google's original name for the feature before rebranding it to "manager account" around 2018. The acronym never went away; it's still what most agencies, job postings, and third-party tools call it, so both terms mean the same thing.

Structurally, an MCC is a parent account that gives you visibility and management access into multiple child accounts from a single login, without needing separate credentials for each one. It can hold campaigns of its own in some configurations, but its primary purpose is oversight and access — viewing performance, managing users, and in some cases consolidating billing across everything underneath it.

The hierarchy can nest: a manager account can have other manager accounts as children (called sub-MCCs), which matters once you're managing enough client accounts that flat, single-level organization stops being manageable — more on that below.

Worth distinguishing early: an MCC is different from simply adding a user to an existing account. Adding a user grants access without changing the account's structure at all — the account remains fully independent, with no parent-child relationship created. Linking an account to an MCC is a structural relationship, not just an access grant, which is why it requires the two-sided accept process covered below rather than a simple invite.

Setting one up

Go to the Google Ads Manager Accounts homepage and select "Go to Manager Accounts," signed in with whichever Google account you want tied to the MCC — this matters, since you can't easily migrate an MCC to a different Google account later.

You'll name the account (visible to any client accounts you link, so pick something recognizable rather than internal shorthand), choose your primary use case — managing your own accounts, managing other people's, or both — and select country, time zone, and currency. Time zone and currency cannot be changed after setup, so confirm them before submitting rather than after; this trips up more new agencies than any other step in the process, usually because someone defaults to whatever the browser's locale suggests without checking it against the actual business location.

If your account activity is expected to be large — Google's threshold here is measured in monthly page views on the ad account rather than spend — you may be redirected to a contact form instead of the standard self-serve flow, and a Google representative reaches out to help complete setup directly. This is uncommon for most small-to-mid-size agencies and businesses, but worth knowing about so it doesn't look like an error if it happens.

Linking existing client accounts

Linking is a two-sided process — you can't simply pull a client's account under your MCC unilaterally, which is a deliberate access-control design, not a limitation to work around.

From your manager account, go to Accounts, then Sub-account settings, click the plus button, and select Link existing account. Enter the client's Customer ID (the 10-digit number in the format XXX-XXX-XXXX, found at the top of their own Google Ads account). You can enter several Customer IDs at once, one per line, if you're linking multiple accounts in the same session.

The client then has to accept the request from their own account: Admin, then Access and security, then the Managers tab, where your pending request appears under "Link request." Until they click Accept, you have no actual access — the request sitting in your MCC's sub-account list doesn't grant anything on its own, which is worth knowing if you're troubleshooting why a newly "linked" account still shows no data.

One detail that trips people up: the Customer ID you need is specifically the client's, not yours, and it must be entered exactly as shown, dashes optional but digits exact — a single transposed digit sends a link request to an entirely unrelated, unrelated Google Ads account, which then sits there as an unexplained pending request on a stranger's account until either of you notices and cancels it.

Permission levels worth understanding before you invite anyone

When you invite a user into your MCC (or into a specific child account), you choose a role: Admin, Standard, Read-only, or Email-only. Admin can do essentially everything, including inviting and removing other users — worth reserving for people who genuinely need that level of control, not extending by default because it's the first option in the list.

Standard can manage campaigns and settings but can't manage user access itself — the right level for most team members actually doing campaign work. Read-only is exactly what it sounds like, useful for a client who wants visibility into their own account's performance without the ability to change anything, or for anyone you want auditing the account without risk of an accidental edit.

This matters more than it might seem at first, because access sprawl is a common, quiet problem in agencies that have been operating for a while — former employees, former clients, or long-closed engagements whose access was never revoked. Reviewing Access and security periodically and removing anyone who no longer needs to be there is worth treating as a recurring task, not a one-time setup step.

There's also an Email-only role, worth mentioning separately since it's easy to overlook: it sends performance summary emails to someone without giving them any login access to the account interface at all — useful for a stakeholder who wants visibility into results without needing, or wanting, to actually navigate Google Ads directly.

Account limits and when to use a sub-MCC

Google caps the number of Google Ads accounts you can manage directly under a single manager account, and separately limits how many manager accounts can be linked to one email address. If you're running up against either limit, or you manage client accounts across genuinely distinct business lines that benefit from separate reporting and access boundaries, a sub-MCC is the right structure rather than trying to flatten everything into one manager account.

A sub-MCC is created the same way as a top-level one, from inside an existing manager account's Sub-account settings, selecting "Create new manager account" instead of linking an existing one. This is worth doing deliberately, with a naming convention that makes the hierarchy legible at a glance — by client vertical, by team, or by region, whichever matches how your agency actually organizes work — rather than reactively once you've already hit a limit and need to restructure under time pressure.

Sub-MCCs also isolate risk usefully: an Admin invited into a sub-MCC for one client vertical doesn't automatically see every other client across the whole agency, which is a cleaner access boundary than trying to manage that same restriction through individual per-account permissions across a flat structure.

What an MCC lets you do across accounts

Beyond simple visibility, a manager account adds a handful of genuinely time-saving cross-account features once you have several client accounts linked. Cross-account bulk actions in Google Ads Editor let you pause campaigns, adjust budgets, or update ad copy across multiple accounts in a single pass instead of repeating the same change manually in each one — a real time saver once you're managing more than a handful of accounts with any shared structure between them.

Automated rules can also be applied across linked accounts from the manager level — pausing underperforming keywords, adjusting bids on a schedule, or sending alerts when a metric crosses a threshold — without needing to log into each child account individually to configure the same rule repeatedly.

Cross-account conversion tracking is another one worth knowing about specifically: it lets you view conversion actions from one account inside another, useful when a client runs separate accounts for different regions or brands but wants a unified view of total conversion volume without merging the accounts themselves, which usually isn't desirable for billing or reporting separation reasons.

MCC-level reporting

The manager account's own dashboard gives you an aggregated view across every linked child account without needing to open each one separately — useful for a quick pulse check across a full client roster, but worth treating as a starting point rather than a substitute for account-level detail, since an aggregated number can hide a single account performing badly inside an otherwise healthy-looking average.

For anything you need to share externally — a client report, a monthly summary — most agencies pull data through Looker Studio connected via the MCC, since it lets you build one template and point it at different child accounts rather than rebuilding a report structure per client from scratch. The connection itself still authenticates per account or per manager relationship, so a report template built once can be reused across the roster with only the data source swapped per client.

One thing worth checking specifically at the MCC reporting level: whether metrics like invalid click rate and conversion tracking health are being reviewed per account, not just at the aggregate. A rolled-up, account-wide number smooths over a single problem account the same way a rolled-up conversion number can hide one broken tracking tag — the audit habit described elsewhere on this site applies per child account under an MCC just as much as it does to a single standalone account, arguably more so, since problems are easier to lose track of the more accounts there are.

It's also worth knowing that not every metric aggregates cleanly across accounts with different currencies or conversion goal setups — a rolled-up ROAS figure across five accounts using five different conversion definitions is a number that looks precise but isn't meaningfully comparable to any single account's own ROAS. Treat cross-account aggregates as directional, and go to the account level for any number you're using to make an actual decision.

Why third-party tools sometimes can't see campaigns under your MCC

This is the part most MCC guides don't cover, because it's a backend integration issue rather than something visible in the Google Ads UI itself — but it's one of the most common points of confusion once you start connecting reporting, automation, or fraud-detection tools to an MCC-managed account, and it's worth understanding the actual mechanism rather than just the symptom.

The symptom looks like this: you connect a third-party tool, authorize it with your Google account, enter your MCC's Customer ID, and click something like "load campaigns." Nothing loads. The tool might show your MCC ID reflected back as the only "available account," with no child accounts listed underneath it, even though you can see dozens of client accounts clearly linked when you check Google Ads directly.

Here's why: Google's Ads API requires two separate pieces of information for any request touching an account that sits under a manager — the target customer ID (whose data you want) and a login-customer-id header (which manager you're acting as, when you're not calling on your own behalf). Manager accounts don't own campaigns themselves in the way a child account does, so a tool that queries campaigns directly on the MCC's ID, without first identifying and querying its child accounts specifically, gets back nothing — not because the connection failed, but because it's asking the wrong account for data it was never going to have.

The child-account discovery step itself requires a separate, specific API call — a query against what Google calls the customer_client resource, sent with the login-customer-id header set to the manager's own ID — that's structurally different from the call used to check which accounts a user has direct access to. A tool built only for single, direct-account connections, without this MCC-specific discovery step added deliberately, will work perfectly for a standalone account and return nothing useful the moment you point it at a manager account instead — which is exactly the pattern that shows up as "it works for my individual accounts but not through my MCC."

This same gap shows up in a related, slightly different symptom worth knowing about too: a tool that does successfully list your account, but only shows the manager account's own ID as an "available account," with nothing else underneath it, even though your MCC has dozens of children genuinely linked and visible in Google Ads itself. That's usually because the tool used a call meant for discovering accounts a login has direct access to — which correctly returns just the manager account you authenticated as — rather than a separate call meant for walking the accounts underneath that manager specifically. Those are two structurally different questions to Google's API, and a tool built to answer only the first one will never surface the second, no matter how long you wait or how many times you retry the connection.

What to check if this happens to you

First, confirm what you're actually looking at. Log into Google Ads directly with the same account the tool is using, and check whether the ID you entered sits at the top of the account switcher with child accounts nested beneath it (a manager account), or whether it's a standalone account with no children (in which case the fix is different — you're just pointed at the wrong ID, not dealing with an MCC-specific issue at all).

If it is genuinely a manager account, confirm the Google login used to authorize the tool actually has admin or standard access at the manager level, not just direct access to one specific child account. A login that only has visibility into a single child account will only ever see that one account, regardless of how the tool queries things, because Google is correctly reporting the limits of that login's actual access.

If both of those check out and the tool still returns nothing, it's very likely the backend integration issue described above — the tool isn't sending the login-customer-id header, or isn't running the child-account discovery query at all. That's worth reporting to the tool's support with the specific manager account ID and the exact symptom, since it's a fixable backend gap, not something you can work around from the Google Ads side alone.

It's worth ruling out one more thing before assuming it's a backend bug: confirm the child account you're trying to reach is showing as Active in Google Ads, not Pending. A link invitation that was sent but never accepted on the child account's side will appear connected-looking in some interfaces while genuinely carrying no usable access yet — the same underlying two-sided-acceptance mechanism covered earlier for linking accounts applies here, and an unaccepted pending link explains a "connected but empty" symptom just as often as the API header issue does.

Common mistakes when setting up or running an MCC

Defaulting every invited user to Admin is the most common one, usually done out of convenience during initial setup rather than deliberate choice. It works fine until someone with Admin access accidentally changes a setting they didn't fully understand, or leaves the agency and the access review that should have caught it never happens. Standard access covers what most day-to-day campaign work actually requires.

Not confirming time zone and currency before finalizing setup is the second-most common, and the least fixable after the fact — both are permanent. An MCC created with the wrong time zone doesn't just look wrong, it actually shifts how daily budget resets and reporting windows align with the business's real operating hours, which is a genuinely confusing thing to discover months later during a performance discrepancy investigation.

Letting the account hierarchy grow unstructured is the third. An agency that starts with five client accounts flat under one MCC and grows to fifty without ever introducing sub-MCCs or a naming convention ends up with a manager account that's technically functional but practically hard to navigate — the kind of structure where finding a specific client account means scrolling and searching rather than navigating logically.

Forgetting to remove access when an engagement ends is the fourth, and probably the most consequential from a security standpoint. A former client relationship or a former team member with lingering Standard or Admin access isn't just clutter — it's a real access surface that should be closed the same week the engagement actually ends, not whenever someone eventually notices during an unrelated cleanup.

Removing or transferring a child account

To remove a linked account from your MCC, go to Accounts, select the account, and choose Unlink — this can be initiated from either side of the relationship, the manager account or the child account itself, and takes effect immediately once confirmed.

If a client is moving from one agency's MCC to another's — ending an engagement with you and starting with someone else — the cleanest sequence is: your MCC unlinks first, then the client accepts a new link request from the incoming agency's MCC. There's no direct account-to-account transfer mechanism between two manager accounts; it's always framed as one link ending and a separate new link beginning, which is worth explaining to clients up front so an offboarding doesn't feel more complicated than it actually is.

Removing access doesn't delete any historical data on your side either — reporting you've already pulled or exported stays exactly as it was, since unlinking only affects ongoing live access, not anything already retrieved before the relationship ended.

Can I convert a regular Google Ads account into a manager account?

Not directly — a standard advertiser account and a manager account are structurally different account types from the start. If you originally set up a regular account and now need manager-level functionality, the practical path is creating a new manager account and linking your existing advertiser account underneath it as a child, rather than trying to convert the existing account in place.

Can a Google Ads account be linked to more than one MCC at once?

Yes, an account can have multiple manager account links simultaneously — useful when, for example, an in-house team and an outside agency both need access to the same account. Each manager relationship is independent, with its own accepted link and its own access level, so removing one doesn't affect the other.

What happens to campaigns if I unlink a client account from my MCC?

Nothing changes in the account itself — campaigns keep running exactly as configured. Unlinking only removes your manager account's access and visibility into it; it's a permissions change, not a change to the underlying account, its billing, or its campaign data.

Does billing automatically consolidate across all accounts under an MCC?

Not automatically — consolidated billing is a specific, separate setup you configure deliberately within the MCC, not a default behavior that comes with simply linking accounts. Plenty of agencies run MCCs purely for management and reporting access while leaving each client's billing entirely separate and client-owned, which is often the more appropriate setup contractually.

Do I need a manager account if I only run ads for my own single business?

Not necessarily — if you're managing one account for one business with no plans to add more, a standalone Google Ads account works fine on its own, and adding an MCC on top is unnecessary complexity. An MCC becomes worthwhile once you're managing more than one account, whether that's multiple brands under one company, multiple locations with separate accounts, or client work for others.

That said, some solo advertisers set one up anyway even at one account, purely for the sub-account settings menu and the option to add a read-only bookkeeper or partner without sharing full account credentials — a reasonable reason, just not a required one.

Can my client see that I'm managing their account through an MCC?

Yes — when a client checks their own account's Access and security page, your manager account appears under the Managers tab with the access level you were granted. There's no way to manage an account invisibly; the relationship is always visible to the account owner, which is by design.

Is there a cost to creating or maintaining a manager account?

No — creating and maintaining an MCC itself is free. You only pay for actual ad spend in the child accounts running campaigns, the same as you would without a manager account in place. The MCC is purely an access and management layer on top of accounts that are billed normally.

Getting the structure right early

Most of what causes real friction with an MCC later — access sprawl, an unstructured hierarchy, a third-party tool that mysteriously can't pull data — traces back to a decision made casually during initial setup rather than a limitation of the feature itself. Taking the extra ten minutes to set permission levels deliberately, confirm time zone and currency before submitting, and plan for a sub-MCC structure before you're forced into one under time pressure pays for itself many times over as the account roster grows.

The technical integration gap covered above is worth the same treatment: if you're evaluating a reporting, automation, or protection tool to connect to your MCC, ask directly during evaluation whether it supports manager-account discovery and the login-customer-id header specifically, rather than finding out the hard way after you've already onboarded a client's account and the tool comes back empty.