Google Ads Agency Account Ownership: What App Teams Should Verify

Separate agency manager ownership, direct access, billing and measurement dependencies before onboarding or changing a Google Ads partner.

An agency proposal says the client will “own the account.” The access request arrives from a manager account, invoices come through a different business, and purchase conversions appear under a source nobody on the app team administers. Before approving the arrangement, make each relationship explicit. One reassuring sentence in a contract cannot describe all of them.

Google Ads agency account ownership is a specific manager-account privilege, separate from direct user access, payment responsibility and contractual rights. Linking an agency to an existing account does not give it ownership by default. Before onboarding or changing agencies, verify business-controlled access and identify billing, conversion and audience dependencies that could be affected by a later unlink. Google's ownership documentation explains the platform distinction.

This guide is for app founders, heads of growth and acquisition leads evaluating an agency arrangement or a handover. The register and acceptance process below are editorial recommendations, not a claim about a Sharply Labs client engagement. They help define what must be demonstrated before control changes.

What does ownership mean in Google Ads?

Google uses owner status for a manager account with additional administrative privileges over a client account. It says this does not take the client's data ownership or administrative rights away. A manager that creates a new client account becomes its owner automatically; a manager linking an existing account does not. Google recommends granting ownership only when those additional privileges are needed. See the official ownership explanation.

That technical status does not settle who owns creative files, who may reuse research, or what a contract requires at termination. Treat those as separate commercial and, where needed, legal questions. Do not read an interface label as a legal opinion about the entire relationship.

Likewise, an employee being an administrator is different from the company controlling a manager account. A business can have direct administrators while an agency manager has owner status. Ask what each arrangement enables and why it is required. Avoid approving a broad label without understanding the practical authority behind it.

Build a control register before granting access

Use a register that distinguishes the asset, the person who can act and the evidence proving that authority. The following is a suggested procurement tool, not an additional Google requirement.

Control boundary Evidence to request Decision it supports --- --- --- Client account identity Customer ID and business app or product mapping Are both parties discussing the same account? Direct business access Named business administrators and a successful authorized sign-in Can the company operate independently of the agency? Agency manager relationship Manager ID, hierarchy and owner status What authority is delegated, and why? Billing responsibility Current payer arrangement, payment setup and finance owner What must happen before a transition? Measurement dependencies Conversion source IDs, product links and responsible teams Which signals could be affected by a change? Shared resources Audience dependencies and reporting or automation owners What must be replaced or retained? Contractual deliverables Agreed files, documentation and exit obligations What does the business expect to receive?

Keep the register in a controlled workspace. A procurement discussion rarely needs raw user data, passwords, full payment details or identity documents. Redacted evidence should establish the relationship without spreading access credentials across email threads.

Give each unresolved row a responsible person and a next observation. “Agency will handle it” is insufficient when the agency is the party whose access will eventually change. A finance representative may own the billing question; a measurement engineer may own the conversion question. The growth lead coordinates the decision rather than pretending to own every dependency.

Should the agency create a new account or link the existing one?

Begin with the existing account's purpose, condition and history. A change of service provider alone is weak justification for rebuilding a working acquisition system. Ask the proposed partner to explain the business need for a new account and the consequences for measurement, reporting and continuity. Account creation should be an explicit decision, not an administrative convenience hidden inside onboarding.

Google documents a process for requesting a link to an existing account using its customer ID, followed by acceptance through the authorized account or manager interface. That is a delegated relationship, rather than a reason to share a personal login. Use the official linking instructions for the current workflow and verify the exact requesting manager before accepting.

If an agency proposes creating a new client account, agree how the business will obtain direct administrative access and how the manager relationship will be documented. Ask for a demonstration of the final arrangement. A promise to provide access later leaves a material acceptance item open.

This guide does not recommend creating replacement accounts to escape restrictions, verification or enforcement. If account health is the issue, resolve that issue through the applicable legitimate process. An agency transition does not erase policy obligations or establish permission to advertise.

Match permissions to the work being purchased

A campaign operator, a reporting analyst and the person responsible for managing users have different jobs. Google's access-level table distinguishes read-only, standard, administrative and billing capabilities. For example, standard access permits campaign editing, while administrative access includes user and manager-link controls. Review the current table against the actual assignment instead of asking everyone to become an administrator.

The buyer's question is operational: which named task cannot be completed under the narrower arrangement? If a partner requests more authority, record that reason, the person approving it and when it will be reviewed. This is particularly useful when an initial diagnostic later becomes an ongoing execution engagement.

Verify business access through the authorized person's own sign-in. An agency screen share proves that the agency can see the account; it does not prove that the business can. Similarly, a dashboard invitation may provide a report without access to the underlying campaign configuration. Test the permission needed for the agreed job, without making a production change merely to demonstrate that a button exists.

Avoid describing any role as harmless. Google's current access table includes billing capabilities across several roles. Have the finance owner review permissions relevant to the actual setup; a role selected for campaign work can still have implications beyond creative and bids.

Treat the payer as a separate handover decision

An agency invoice and a Google Ads manager link do not, by themselves, explain the account's payment arrangement. Record who receives the platform invoice, which organization is responsible for payment and who is authorized to change the setup. Distinguish the agency service fee from media charges and outstanding obligations.

Google's agency transfer documentation describes a Change Who Pays process for transferring billing responsibility from a previous agency's paying manager. The current guidance includes beta limitations and support-dependent cases. Do not assume that every advertiser has the same transfer options or that accepting an account link completes the billing work.

For accounts on monthly invoicing, Google specifically warns that unlinking the paying manager stops serving unless the necessary billing setup is changed beforehand. That conditional warning comes from its unlinking guidance. It is a reason to inspect the arrangement before removing access, not a claim that every manager unlink stops every campaign.

Have finance confirm the required evidence before scheduling the change. The media buyer should not improvise payment authority during a handover. Where support is needed, preserve the case reference and the affected account IDs, and distinguish a submitted request from a completed transition.

Inventory measurement and shared-resource dependencies

For an app team, the important question is whether the same defined acquisition outcomes will remain observable and usable after the handover. Map each material conversion to its source, identifier, responsible administrator and use in campaign decisions. Include external analytics or attribution relationships in the inventory where they actually exist. Do not infer those relationships from a campaign name.

Google warns that unlinking can affect manager-provided shared audiences and cross-account conversion tracking. Its documentation describes loss of access to shared lists and different treatment for clicks before and after an unlink. Read the official dependency explanation against your configuration. It does not establish that every app event or third-party integration automatically follows an identical migration path.

Ask the outgoing and incoming operators to identify dependencies rather than simply confirming that “tracking works.” An export showing event names may omit who administers the source. A campaign report showing conversions may omit whether the receiving team can inspect the definition. Both are useful observations, but neither completes the control map.

Use the app conversion-tracking diagnostic if the event pathway itself is uncertain. That is a different investigation from deciding who should hold manager privileges. Keep those workstreams connected without turning a handover into an unplanned measurement rebuild.

Sequence a handover around evidence, not a fixed calendar

The following sequence is a recommended review process. Actual platform actions depend on the account, permissions and billing arrangement; this is not a universal click-by-click transfer procedure.

First, preserve a dated baseline. Capture relevant campaign configuration, active objectives, conversion definitions, user and manager relationships, billing evidence and current reporting extracts. Record who produced each extract and when. Preserve the context needed to interpret it, including the report's time basis and filters.

Second, confirm that the business has usable authorized access and that the incoming team has the scope needed for the agreed work. Verify account IDs independently in the approved request. A similar account name is not sufficient identity evidence when a group has multiple apps, markets or business entities.

Third, resolve the billing and measurement rows that could prevent continuity. Ask the responsible teams to describe the before-and-after arrangement and the observation that will prove it. Where a replacement dependency is necessary, approve its design and validation before the old dependency is removed.

Fourth, authorize a bounded change window. Name the operator, reviewer, communication path and spending authority. Separate access changes from optional campaign restructuring so that a handover defect is easier to identify. If several changes are unavoidable, document their order and why each is necessary.

Finally, review the observed state after the change. Check access, billing status, campaign eligibility and the relevant event pathway. Preserve unresolved differences rather than declaring success because the incoming agency can log in. Remove remaining unnecessary access through the authorized process only after the associated continuity questions are answered.

A fictional acceptance review for an app company

Consider a fictional subscription app changing agencies. Its founder can sign in directly, and the incoming agency's link request is valid. The outgoing manager has owner status. The growth team initially treats those facts as sufficient to complete the switch.

The control register reveals two unresolved rows: finance has not established whether the outgoing manager is the paying manager, and the purchase-event documentation names a reporting source without identifying its administrator. Neither uncertainty proves that advertising will fail. Both could materially change the safe order of work.

The team separates acceptance into three decisions. Direct access is verified. Billing remains pending until finance identifies the arrangement and any required transfer. Measurement remains pending until the event owner documents the dependency and a proving check. Campaign restructuring is deferred because it does not solve either missing fact.

Suppose the billing review establishes that a transfer is required. The team follows the applicable supported process before unlinking. Suppose the event review establishes that the relevant source is independent of the outgoing manager. The team still records and validates that finding; it does not create a replacement event simply because the agency changed.

The result of this fictional review is a better-supported sequence, not a predicted CPA improvement or a guarantee of continuous delivery. Its value is avoiding an irreversible operational decision based on an incomplete description of control.

What should an agency handover scope include?

Ask for deliverables that can be checked. A useful scope names the accounts and dependencies under review, identifies excluded systems, assigns responsibilities and specifies the evidence required for acceptance. It should also state what requires a separate engineering, finance, platform-support or legal decision.

Request a dated control register, an unresolved-dependency list, a proposed change sequence and a validation record. Where the agency cannot independently verify a fact, it should name the owner and the evidence still needed. An honest unresolved item is more useful than an unsupported assurance that the account is “fully yours.”

Agree how access, configuration exports, creative source files and documentation will be handled at the end of the engagement. These deliverables may involve different rights and systems. Resolve contractual questions with the appropriate adviser rather than assuming that a manager ownership setting decides them.

For the broader operating relationship, use the agency onboarding acceptance framework. If the provider has not yet been selected, the mobile app agency selection guide helps evaluate working evidence before a retainer is agreed.

Common buyer questions and limits

Does linking an agency automatically give it ownership? No, Google distinguishes linking an existing account from creating one under a manager. Check the actual owner status rather than inferring it from the existence of a link. Google's explanation is the controlling platform reference.

Can the client unlink an owner manager? Google documents that ability for the client account, subject to the relevant access and workflow. Confirm authorized access and inspect dependencies first. This article cannot recover a missing login, adjudicate a contract dispute or establish the facts of a particular account.

Does unlinking delete campaign history? Google says the individual account retains its own campaign history. That does not mean every manager-shared resource remains available. Keep historical-data preservation separate from continuity of operational dependencies. Unlinking documentation explains the distinction.

Is owner status always inappropriate for an agency? A universal prohibition is too broad. The relevant question is whether the additional privileges are necessary, understood and approved, with business access and exit dependencies documented. Platform permissions and legal rights still need separate review.

Bring the control map to the first conversation

For established app teams onboarding or replacing an agency, Sharply Labs' mobile app growth work and paid acquisition services provide the relevant commercial context. Bring redacted account IDs, manager and user-role evidence, the known payer arrangement and your conversion-source map to an initial conversation.

The conversation can scope the control questions, responsible parties and proving checks a handover review would require; a detailed audit or implementation engagement is separately agreed. Access recovery, contract resolution, uninterrupted serving and acquisition performance are not promised. The immediate decision is which dependencies must be demonstrated before anyone changes control.