GA4 for Agencies: Managing Multi-Client Properties Without Losing Your Mind (2026)

How should agencies manage GA4 access for multiple clients?

The right agency GA4 structure has clients owning their own GA4 accounts and properties, with the agency granted Analyst or Editor access via the client's Google account — not the agency's. The single biggest agency GA4 mistake: creating GA4 properties inside the agency's own Google Analytics account on behalf of clients.

When the agency relationship ends, the client loses access to their own data. Every GA4 property must be owned by the client's Google organisation. The agency then accesses it as a managed guest. This is non-negotiable from a client data ownership perspective and is increasingly a contractual expectation in agency-client agreements.

The two account structures that cause problems

Problem structure 1 — Agency-owned GA4 account

The agency creates a Google Analytics account (analytics.google.com → create account) in the agency's Gmail or workspace. Client properties are created inside this account.

What breaks:

• Agency relationship ends → client has no data. All historical data stays in the agency account.
• Client cannot see their own data without asking the agency
• Agency account admin controls what the client can and cannot view
• Not compliant with GDPR's data controller requirements (the client is the data controller, not the agency)

How common: Extremely common in smaller agencies that set up GA4 for clients informally.

Problem structure 2 — Properties under a personal Google account

Similar to the above but worse — the GA4 account is under an individual analyst's personal Gmail account. When that analyst leaves the agency, no-one can access the client's data.

This destroys client relationships and is a serious professional liability.

The three account structures that work

Structure 1 — Client-owned GA4, agency access via property-level invite

Setup:

1. Client creates their Google Analytics account (or has an existing one)
2. Client creates the GA4 property
3. Client invites agency email (ideally a Google Group, not an individual) to the property with Editor or Analyst access
4. Agency works inside the client's property

Agency access level: Property-level Editor (can create streams, configure property settings, create conversions) or Analyst (can create explorations, view reports, create audiences — no configuration access).

Appropriate for: Most client relationships. Simplest, cleanest structure.

Structure 2 — Client-owned GA4, agency invited at account level

Setup:

1. Client's GA4 account (which may contain multiple properties)
2. Agency invited at Account level with Viewer or Editor access

Agency access level: Inherits across all properties in the account.

Appropriate for: Clients where the agency manages all digital marketing and needs access to all properties.

Risk: Account-level access gives the agency visibility into all client properties, including any they're not managing. Confirm scope with the client.

Structure 3 — Google Marketing Platform (GMP) for enterprise

For enterprise agencies managing 10+ client accounts, Google Marketing Platform (GMP) provides organisation-level access management. Requires a GMP account and billing arrangements.

Appropriate for: Large agencies with enterprise clients, particularly those also managing Campaign Manager 360 or Search Ads 360.

GA4 access levels reference

Agency recommendation: Grant agency contacts Editor at the property level. Reserve account Administrator for the client's internal team only. Never give agency users account-level Administrator — this allows them to add/remove other users and delete the property.

Managing access at scale: practical workflow

For agencies managing 20+ clients:

Step 1 — Standardise with Google Groups Instead of granting access to individual analyst email addresses, create a Google Group (groups.google.com) for your GA4 team: ga4-team@youragency.com. Invite the group to client properties. When an analyst joins or leaves, you update the group — not every individual client property.

Step 2 — Maintain an access register Keep a spreadsheet or CRM entry for each client with:

• GA4 property ID
• Access level granted
• Which email/group has access
• Date access was granted
• Contract renewal/offboarding date

Step 3 — Offboarding access removal When a client relationship ends, remove agency access immediately. GA4 Admin → Property → Access Management → remove your agency's access. This is a contractual obligation in most agency agreements and a GDPR requirement (no legitimate purpose = no access retained).

Step 4 — Audit access quarterly Run an access audit: GA4 Admin → Account → Access Management → review all users. Remove stale access from former clients, former staff, or users whose roles have changed.

Common agency scenarios and solutions

Scenario: Client provides only Viewer access but agency needs to configure conversions

Solution: Formally request Editor access with a written explanation of what configuration changes are needed. If the client is uncomfortable, offer to provide them with step-by-step instructions to make the changes themselves, or schedule a screen-share where they make changes while the agency advises.

Scenario: Client's GA4 was set up by a previous agency in that agency's account

Solution: The client needs to request a full export of their data from the previous agency (BigQuery export if it was enabled), create a new GA4 property in their own account, and re-implement GA4 tracking. Historical data from the old property cannot be transferred to the new one. This is the most painful outcome of improper account structure — it results in a data history gap.

Scenario: Agency is asked to create a new GA4 property for a client

Correct process: Ask for access to the client's own Google Analytics account → create the property there → ensure the client's admin email has Administrator access → then add agency access as Editor.