Google Ads MCC rebuilt for agency access and audit

What actually breaks: It is rarely the hierarchy diagram. It is that four people share one login, that conversion actions are defined inside each client account so cross-account bidding and any portfolio-level read are impossible, and that when a client asks who changed a bid on a Tuesday in March, the agency cannot answer inside a day. On the manager accounts I have rebuilt, the change history export and the access list were the two artefacts nobody had ever produced. Both take an afternoon to arrange and neither exists by default. The build: One top-level manager account, with sub-managers split by billing entity and client tier rather than by internal team, because teams reorganise and invoices do not. Linking done as invitations from the manager with the client retaining ownership. An agency that owns its clients' accounts has a commercial problem dressed as a technical convenience, and I will argue that with you before I build anything. Conversion actions defined once at manager level and shared down, so bidding strategies and every cross-account comparison rest on one definition instead of eleven. Consolidated billing and budget orders configured to match how you actually invoice, including the case where the client pays the platform directly and you never touch the money. API and automation: The developer token application written and submitted with the access level argued rather than guessed, because basic and standard access carry different limits and applications are refused for vague answers about intended use. OAuth credentials issued to a service identity rather than to whoever happened to apply and then left the company. Manager-level scripts installed with their execution limits written down, so nobody meets the ceiling during a client's peak week. Custom columns and automated rules placed at manager level where they belong instead of pasted by hand into each account. Governance, which is the part clients audit: Access levels assigned by role, with email-only used where it should be. Two-step verification enforced. An offboarding checklist that removes a leaver from every account in one pass rather than the three anyone remembers. Naming conventions written as a rule a script can check, not a wiki page nobody opens. Scheduled change history exports retained for as long as your client contracts require. And safeguards against the expensive accidents: budget ceilings, account-level negative lists, and a written rule for who may change a bidding strategy on an account above a spend threshold. Microsoft Advertising: A mirrored manager structure where it maps, and a written note where it does not, because the hierarchies are not one to one and pretending otherwise produces a second broken system standing next to the first. Not included: I do not run your clients' campaigns and I do not audit their performance. This is plumbing and governance, and mixing the two makes me a competitor to your own team, which is a poor basis for working together. No reporting tool selection, no dashboard build, no white-label decks. No help pricing or pitching your retainers. Who should not buy this: Agencies under roughly ten client accounts. One manager account and a spreadsheet is honestly adequate at that size and the fee would buy you nothing you would feel. Agencies that want the structure to mirror the org chart: I will build it once and you will pay me again after the next reorganisation, so I would rather decline than take that twice. In-house teams with a single account, for whom none of this applies. What you get: The target structure as a diagram with the migration order, the access matrix by role, the conversion action definitions, the developer token application text, the naming rule in machine-checkable form, and a half-day handover with the person who will own it afterwards.