A GA4 audit for agencies is not just a larger version of a single-property review. The challenge is operational: keeping access controlled, documenting what was verified, spotting configuration drift, and explaining findings consistently across different clients, platforms, and stakeholders. The goal is not to force every client into one template. The goal is to use one defensible review standard.
use one intake workflow so access, scope, and evidence standards do not change from client to client
treat browser review, Admin review, GTM review, and API access as different audit surfaces
record client-side changes so reporting shifts can be investigated against a known history
Access management practices to get right
GA4 uses a role-based access system with five levels: Viewer, Analyst, Marketer, Editor, and Administrator. These five roles are available at the property level. At the account level, the available roles are Viewer, Editor, and Administrator — the Marketer and Analyst roles are property-level only. Access can be granted at the account level (applies to all properties) or at the property level (applies to that property only). When the same agency manages many accounts, it pays to define this policy alongside a broader approach tomanaging multiple GA4 properties.
For agency-client relationships, it is usually safer to grant access through organization-controlled accounts or groups rather than informal one-off invites tied to a single employee. Most agency analysts need Analyst or Marketer access, not Editor. Editor access allows property changes such as filters, custom definitions, and attribution settings, so it should be limited to approved remediation work.
Agency audit workflow for new client properties
Every new client property intake should follow the same structured workflow. This ensures nothing is missed and creates a consistent baseline for all properties in your portfolio. The standardGA4 audit checklistis a good starting point, with additional steps layered on for client onboarding and evidence capture.
Gain property access
Request the minimum role needed for the review. Start with read-oriented access where possible and request Editor access only for approved remediation or configuration changes.
Capture a property configuration snapshot
Document timezone, currency, data retention, attribution settings, filters, reporting identity, linked products, custom definitions, and events marked as key events.
Run a baseline data quality review
Compare GA4 output with another trusted source over a representative period. For ecommerce, reconcile orders and revenue against the commerce platform or finance-approved reporting. Investigate any unexplained material gap instead of relying on a fixed benchmark.
Validate tagging and event behavior
Use Tag Assistant, browser inspection, and DebugView to confirm the correct property is receiving hits, duplicate implementations are not present, and priority conversion flows still work.
Review consent and privacy-sensitive behavior
Check whether consent signals are being received where expected and whether the current setup matches the client's chosen consent framework. Keep the language operational rather than legal.
Deliver a prioritised findings report
Explain what was verified, what was not verified, which findings are access-dependent, and which issues are likely to affect business reporting most materially.
Property configuration review baseline
Each new client property should be set up against a standard configuration template. Use this as an intentional review baseline, not as a claim that every client should use one identical setup:
- Data retention reviewed against the client's reporting and privacy needs
- Internal Traffic filter: Active
- Developer Traffic handling reviewed intentionally rather than assumed from a template
- Google Ads, Search Console, and BigQuery links reviewed where relevant to the client's use case
- Attribution settings reviewed against the client's sales cycle and reporting needs
- Enhanced Measurement reviewed against any custom GTM tracking before changes are made
Cross-client reporting infrastructure
Build a master report template inLooker Studio. For each client, create a copy and swap the GA4 data source. The template approach ensures consistent KPI definitions and visual formatting across all client reports. Templates also pair naturally withwhite-label GA4 reportsso clients see your agency identity rather than a raw third-party export. For client-facing language, the patterns inproving analytics value to clientscover how to frame audit findings commercially.
If multiple client properties export toBigQueryin the same GCP project, you can write SQL queries that aggregate across properties or compare performance. Ensure clear dataset separation (each property exports to its own dataset named analytics_PROPERTYID). When commercial scoping comes up, theGA4 audit pricing guidecovers how to map that scope to a defensible quote.
Agency client intake action plan
Use this plan when onboarding a new client GA4 property. Complete validate steps before making any configuration changes.
Validate
- Access granted at the correct account or property level with the minimum viable role
- Full property configuration snapshot documented against the standard template
- GA4 output reconciled against another trusted source for a representative period
- Tag Assistant confirms single GA4 hit per page load to the correct property
- Consent-related behavior reviewed with the client's implementation constraints in mind
- Priority key events verified through live testing or recent evidence
Fix
- Request Editor access only for configuration fixes that are approved by the client
- Apply the review baseline intentionally: data retention, traffic filters, attribution settings, and linked products
- Fix duplicate tag implementations before any data quality analysis
- Disable conflicting Enhanced Measurement settings where custom GTM tracking is in place
Watch for
- Client-side configuration changes that are not communicated to the agency
- A new ecommerce plugin or site deployment introducing a duplicate GA4 tag
- Consent banner or CMP updates changing signal behavior without a reporting review
Agency property management checklist
- Access is granted through organization-controlled accounts or groups where possible
- Most agency team members have Analyst access, not Editor
- Automated reporting uses dedicated service accounts with Viewer access
- Each new client property audited against the standard configuration template
- Change history is reviewed on a recurring basis for unexplained client-side updates
- Shared Looker Studio or warehouse reporting definitions are documented before reuse across clients
Related guides to read next
GA4 Audit Checklist
The complete checklist for auditing GA4 implementations from tag to conversion.
GA4 Audit Pricing Guide
How to scope the work before pricing a GA4 audit for a new or inherited client setup.
GA4 Data Hygiene Audit
How to identify and fix the most common GA4 data quality problems across client properties.
Review agency audit findings with more context
GA4 Audits can surface implementation and configuration issues, but agencies should still review the evidence before using findings in client reporting or remediation plans.