What “agency account” usually means
In Google Ads, an “agency account” is not a hidden product tier with its own policy exemptions. It usually means advertising access structured through an agency or partner: you run campaigns inside a Google Ads advertiser account that sits under a manager account (MCC), with documented permissions, billing workflows, and operational support. The label varies by vendor — clarify what you actually receive before you compare quotes.
You still advertise under current Google Ads policies, verification requirements, and review systems. Agency infrastructure is about how spend is provisioned, who owns what, how billing is funded, and who you escalate to when something breaks — not immunity from disapprovals or suspensions.
Agency access vs client-owned accounts
Client-owned setups are straightforward: your company controls the Google Ads account (and often the manager account above it), attaches its own payments profile, and grants agency users access through standard Google roles. That model keeps ownership clean and exits simple.
Agency-managed infrastructure flips parts of that map. The agency may own or control the manager account and provision advertiser accounts you operate under. You may receive admin or standard access without owning the legal billing entity behind the payments profile. Neither model is “safer” by default — they trade ownership clarity for operational support and continuity options when those are written into the engagement.
Ask early: who can invite users, who can change billing, who can transfer the account, and what you keep if the relationship ends. Verbal answers are not enough when media spend is material.
- Client-owned: your org typically owns the Ads account and payments profile
- Agency-provisioned: clarify MCC owner, your role level, and exit rights in writing
- Both models run under the same Google Ads policies and review systems
- Access should use Google user invitations — not shared personal passwords
Manager account relationship
A manager account (historically called an MCC) is a control layer above one or more Google Ads accounts. It is not the same thing as the advertiser account where campaigns live. Agencies often use a manager account to grant cross-account access, standardize reporting, and organize billing relationships across clients or brands.
Being linked under a manager account does not automatically mean the agency “owns” your advertising identity, and owning a manager account does not make every child account agency infrastructure. Map the hierarchy: which manager links to which Ads account, whether links are administrative or ownership-oriented in practice, and whether multiple brands share one manager tree. Shared trees create blast-radius risk when verification or policy issues appear.
Ownership, billing, permissions, and tracking
Ownership questions that matter: who controls the Google account that administers users, who owns the payments profile and billing setup, who can accept terms, and who can move conversion actions or linked assets. If those answers are fuzzy, fix them before you scale.
Billing may sit on an agency payments profile, a client profile, or a hybrid depending on the setup. Confirm currency, invoicing vs automatic payments, who funds spend, what happens to prepaid or outstanding balances if an account is limited, and whether invoices reconcile to the Ads account you actually use. Do not invent assumptions about Google privileges a vendor cannot grant.
Permissions should follow least privilege: campaign managers need campaign access; finance needs billing visibility; nobody needs personal Gmail passwords shared in Slack. Tracking continuity depends on who owns conversion actions, Google tags / gtag / Google Tag Manager containers, and linked Analytics properties — not only on which Ads account is spending this month.
Support, restrictions, and when agency infrastructure fits
Responsible agency setups usually include eligibility review (offer, markets, claim posture), onboarding into the correct account type, and a defined support path when delivery stops. Support quality varies. Prefer providers who describe process — diagnosis, documentation, account changes when contracted — over those who imply guaranteed restoration.
Restrictions and suspensions can still happen on agency-linked accounts. Payment failures, destination issues, policy flags, and integrity reviews remain possible. Architecture may affect how quickly you can restructure or replace a spend node when the plan includes that; it does not rewrite Google’s policies.
Consider agency infrastructure when spend continuity, funding workflows, multi-brand manager architecture, or contracted operational support matter more than owning every Ads account yourself — and when the provider will decline non-viable offers rather than force a launch. Stay client-owned when internal ownership is already clean, spend is manageable, and your team can handle billing and verification alone.
- Fit for agency model: continuity, documented billing, multi-account ops support
- Fit for client-owned: clear internal ownership, modest complexity, strong in-house ops
- Never a fit: claims of policy bypass, invented Google partnership status, or guaranteed approvals
Questions before you onboard
Get answers in writing. Vague answers are a reason to wait.
- Who owns the manager account, the Ads account, and the payments profile?
- What Google Ads roles will I receive, and how is access revoked?
- How is billing funded, topped up, and reconciled if an account is limited?
- Who owns conversion actions, tags, and Analytics links during and after the engagement?
- What happens operationally if the account is suspended — support scope vs what is not covered?
- Will you decline offers that look non-viable under current Google Ads policies?