MCC (manager account / My Client Center)

What it is

The manager account does not run ads itself; it holds permissions rather than campaigns. You link client accounts by sending an invitation or by creating new accounts underneath, then reach all of them from one place. MCCs can be nested: regional MCCs under an agency MCC, individual advertiser accounts under those.

Linking is a permission relationship, not a transfer of ownership. The account remains the client's, and the client can unlink at any time.

Why it matters

The real gains are access management and shared assets. You assign roles to team members at the manager level and permissions flow downward. Cross-account reporting, consolidated billing, shared negative keyword lists and cross-account conversion tracking only work when accounts sit under the same manager.

It is also required on the API side: Google grants developer tokens to manager accounts only, and calls made on behalf of a client account carry the manager's ID in the login-customer-id header.

How Tecrube uses it

The Agency plan treats the MCC structure as the default assumption: the correct manager context is resolved automatically, each client's data is isolated, and every action is logged per account. You switch between clients without reconnecting anything.

The free trial and the Pro plan work with a single ad account. Acting across several client accounts in one request is the reason the Agency plan exists; the approval gate and the 50% single-step budget cap apply identically in every account.

Example

“Sweep every client under my manager account: campaigns that exhausted their budget, got stuck in learning or have no active ads, in one table by client.” As a read request it returns immediately; when you then say “raise client X's budget”, a preview arrives for that account only.