Structure Google Ads manager accounts around clear client boundaries, named users and an agreed access hierarchy. Keep each client’s advertising records identifiable, decide whether manager ownership is needed and document how the client can retain control. A shared dashboard is useful only when the people using it understand which account they are viewing and what they may change.
Before creating anything, draw the account relationships on one page. Include the business owner, account identifiers, existing managers and intended users. A simple diagram exposes an unnecessary extra layer or an ambiguous ownership request before it becomes part of routine campaign work.
What does the manager account change?
A Google Ads manager account can manage multiple advertising accounts, including other manager accounts. A manager account is a new account rather than an upgrade of an existing advertising account. The manager-account overview describes it as an umbrella linking individual accounts. Treat it as an access and operating structure, rather than a reason to combine separate clients’ campaigns into one account.
Client-account users do not gain access to sibling accounts through the manager link. This documented separation is useful, but it does not replace a user review. Someone invited to a manager account has a different position in the hierarchy from someone invited only to a client account. Identify the level at which every invitation is intended to apply.
Manager-account ownership of a client account enables management of that client account’s user access. Decide whether this responsibility is part of the agreed engagement before requesting it. Do not treat ownership as an incidental checkbox in a campaign setup task. Record who authorises access changes and who reviews them when staff or agency responsibilities change.
An administrator of a client account can end the manager relationship by unlinking it. Include that control in the handover discussion alongside the client’s own administrator access. An understandable exit route supports a clearer working relationship from the start; it should not require the client to reconstruct the account structure after an engagement ends.
Which creation choices need deliberate approval?
The manager account name is visible to clients in their client account. Use a recognisable name and verify that it represents the intended managing business. The creation guide also distinguishes managing one’s own accounts from managing other people’s accounts, so the setup brief should state which situation applies.
The manager account time zone is used for reporting and billing and cannot be changed. The manager account currency is a permanent selection. Write both into the proposed setup record before creation and have the responsible owner check them. A convenient default is not a substitute for an agreed reporting basis.
Client accounts are billed in their individually selected currencies. Therefore, a manager-level reporting view should not be described as changing every client’s billing currency. Label the account and currency in exported reports so the reader knows what the figures represent. Where a manager view converts values, record that context rather than silently comparing unlike reports.
Creating a sub-manager includes optional user invitations with Admin, Standard or Read only access. Choose the level by the actual job. A person reviewing reports, a campaign operator and someone administering access do not automatically need the same authority. Keep the proposed access record specific enough for the account owner to approve it.
| Decision | Required record | Review question |
|---|---|---|
| Account boundary | One identified client account per agreed boundary | Can every campaign be traced to the correct client? |
| Manager hierarchy | Parent and any sub-manager | Does each extra layer have a purpose? |
| Ownership | Requested relationship and authoriser | Is user-access administration included? |
| User access | Named user, level and account | Does this person need this scope? |
| Reporting basis | Time zone and currency | Can the report be interpreted correctly? |
| Exit | Client administrator and unlink process | Who can complete the handover? |
How can client separation be tested?
Use the actual proposed roles in a controlled review. Ask a client-side user to identify their account and inspect the areas available to them. Ask the manager-side reviewer to identify the selected client before opening a campaign. Record the account identifier in each observation so a plausible screen cannot be mistaken for the intended client’s screen.
Check report naming as well as access. A correctly separated account can still be mishandled if an exported report has only a generic filename or contains unexplained totals. Agree a naming convention that identifies the client and reporting period without embedding unnecessary personal information.
Measurement choices also need a separate owner. The conversion tracking guide covers events and test evidence; the manager structure does not establish that those events are correct. Record who may alter conversion definitions and how the business owner will review a proposed change.
Use business email account controls when reviewing the identities behind account access. A role mailbox may be useful for communications, but the manager access register should still make individual responsibilities understandable.
Original three-client access rehearsal
Use this hypothetical exercise for a managing organisation with three independent clients: a training provider, a retailer and a consultancy. The original artefact is an account boundary register with a row for each person-to-account relationship and a linked evidence note for the permitted task.
Map the hierarchy. Draw one proposed manager and the three client accounts. Add a sub-manager only if the business can explain its purpose. Record each customer ID privately in the operational register. Keep public training examples fictional so real client relationships are not exposed through documentation.
Define the reporting role. The report reviewer needs to inspect results for the training provider. Record the chosen access level and the scope at which it is granted. During the review, have that person identify the selected account and produce the agreed report. Compare what is available with the intended boundary rather than assuming the invitation was made at the correct level.
Define the campaign role. The operator needs to work on the retailer’s campaigns. Have the operator demonstrate account selection and a non-published review task. The purpose is to confirm understanding of the boundary, not to make a live advertising change. Note any workflow that makes it easy to confuse clients and adjust the operating instructions.
Define the access-administration role. If the manager is intended to own a client account, record why that relationship is required and who approved it. Have the responsible administrator explain the supported process for adding and removing users. Keep approval of that responsibility separate from approval of a campaign’s creative or budget.
Rehearse the end of an engagement. Identify the client’s administrator, the manager link and the records that must be handed over. Record the intended unlink responsibility and the point at which access would be reviewed. This exercise should produce a clear exit plan without actually terminating an active relationship as a test.
The register’s decision column should read accepted, revise scope or unresolved owner. Resolve an ambiguous owner before routine work begins. A dashboard that works for one experienced operator can still be unsuitable for a team if account boundaries depend on memory.
What makes the final handover useful?
Retain the hierarchy, named access register, reporting basis and exit responsibilities in one controlled record. Review it whenever a person changes role or a client relationship changes. Keep credentials and recovery codes outside that record.
For the broader advertising brief, see Google Ads. To discuss an account structure, get started with the number of client boundaries, existing account relationships and the tasks each user needs to perform.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.