For an agency, GA4 is rarely one property. It is one per client, each set up by a different person at a different time, with different key events, filters and links. The client reports look the same from the outside. Underneath, “conversions” means something different in every account, and that is where the disputes start.
Start with ownership and access
The client should own their GA4 account and property. Your team gets access as users on it. When an agency creates properties under its own account, the client’s history is tied to the agency, and handover gets messy if the relationship ends.
Record, for each client, who owns the property, who on your team has access and at what role, and which property and data stream the site actually sends to. The last one catches more problems than you would expect: an old property still on a subdomain, or a staging measurement ID left in a template.
The per-client setup check
Run this when you take on a client, and again whenever the site or tag manager changes:
| Setting | What to check | Why it matters in reports |
|---|---|---|
| Key events | Only real outcomes are marked, and they match the client’s KPIs | Every “conversions” number in GA4 is built from these |
| Measurement ID | The ID on the site matches the property you report on | Data lands in a property nobody reports from |
| Data retention | Event data is set to 14 months, not 2 | Explorations and funnels can’t look back further than retention |
| Internal traffic | Agency, client and developer traffic is filtered | Launch weeks look better than they were |
| Google Ads link | The right Ads accounts are linked | Paid traffic and cost data are missing or misattributed |
| UTM conventions | Campaign tags follow one naming scheme | Channels split into “(other)” and unassigned traffic |
Retention is easy to misread. Google says the setting only affects explorations and funnel reports, not the standard reports. But if you build year-over-year analysis in explorations, a 2-month setting quietly limits what you can show.
Campaign tagging is its own discipline. The dynamic UTM parameters guide covers naming rules that keep channel reports clean across clients.
The GA4 numbers worth reporting
Most of GA4’s default menu doesn’t belong in a client report. A short, repeatable set does:
- Key events the client agreed on. Named, defined, and trended against last period and target.
- Sessions and engaged sessions by channel. Where visits come from, and whether they did anything.
- Landing-page performance. Which pages turn paid and organic traffic into key events.
- Purchases and revenue for ecommerce clients, with a note on how they compare with the store platform.
Keep the definitions the same across clients where you can, and write them down where they differ. A weekly client brief or monthly review that uses the same GA4 section for every client is faster to build and easier to check.
The gotchas that cause client disputes
GA4 and Google Ads disagree
Google Ads conversions are configured in Google Ads, and Google notes they don’t appear in standard GA4 reports. Key events in GA4 are counted by GA4, with its own attribution. The two will not match, and that is expected. Decide which one is the source of truth for each KPI and show the other as context. The full explanation is in why Google Ads and GA4 conversions don’t match.
Missing rows from thresholds
GA4 withholds data from a report when it includes demographic data or search query data and there aren’t enough users. Small clients and short date ranges are hit hardest. If a number looks low, check for the thresholding notice before you report it.
Attribution changes
The attribution settings in GA4 change how credit is split between channels. If someone changed them mid-year, channel trends shift without any change in performance. Note the change on the report.
Dashboard quotas
Agencies that report GA4 through Looker Studio across many clients often hit API quota errors. See how to fix “dataset has been accessed too many times”.
When to turn on BigQuery export
GA4’s BigQuery export gives you the raw events, which you need for custom attribution, joining GA4 to CRM data or keeping history beyond the UI. Turn it on early for clients where you expect to need it, because the export starts from the day you enable it. For what you can do without it, see GA4 attribution reports without BigQuery.
How Maven fits
In Maven, each client is a workspace. GA4 connects to it as a source alongside the client’s ad platforms and CRM, and Maven models the data into documented tables you can report on. Connect the client’s Google Tag Manager too, and Maven’s audit flags GA4 measurement-ID mismatches, tags with no trigger and pixels or events that stopped firing. Changes to the container are staged with QA evidence and go live only after you approve them.
From there, your team asks Claude or ChatGPT for the client’s report through the MCP. GA4 sits next to Google Ads, Meta and the CRM in the same report, and the report is published to the client’s portal only after you approve it. The weekly client brief and the lead-to-revenue dashboard are two examples that use GA4 this way. The GA4 integration page lists what Maven pulls.
A checklist for every new client
- The client owns the GA4 property; your team has user access.
- The site sends data to the property and stream you report on.
- Key events match the client’s agreed KPIs, and nothing else is marked.
- Event data retention is 14 months.
- Internal and developer traffic is filtered.
- The right Google Ads accounts are linked.
- Each KPI has a named source of truth: GA4, the ad platform or the CRM.
- BigQuery export is on if you will need raw events later.
Part of: Agency client reporting
Also in Report each channel: How to calculate ROAS for client reports, with and without your agency fee, Google Ads client reporting: the metrics to put in front of clients
Frequently asked questions
How should an agency get access to a client’s GA4 property?
Have the client add your team as users on their own GA4 account or property, so the client keeps ownership. Avoid creating client properties under the agency’s account, which makes handover painful if the client leaves.
Which GA4 numbers belong in a client report?
Key events the client agreed on, sessions and engaged sessions by channel, landing-page performance and, for ecommerce, purchases and revenue. Leave most of the default reports out and give each number a source note.
Why don’t GA4 conversions match Google Ads?
They count different things. Google Ads conversions are configured in Google Ads and don’t appear in standard GA4 reports, and the two tools use different attribution and dates. Pick one as the source of truth for each KPI and explain the other.
What GA4 settings should agencies check for every client?
Which events are marked as key events, the data retention setting, internal traffic filters, the Google Ads link and whether the measurement ID on the site matches the property you report on.
Does GA4 data retention affect client reports?
Not the standard reports. Retention affects explorations and funnel reports, so a short retention setting limits year-over-year analysis built in explorations. Standard properties can keep event data for 2 or 14 months.
