The most common mistake agencies make when sharing an audit is presenting the technical findings as-is and expecting the client to understand why they matter. A finding that reads "Consent Mode v2 not implemented — consent signals absent" is accurate and important. It is also completely opaque to a marketing director who manages campaigns and budgets but has never opened the GA4 Admin panel.
Your job as the analyst presenting the audit is translation. Not simplification — the issues are genuinely important and shouldn't be downplayed. Translation: taking findings that are expressed in GA4 terminology and expressing them instead in terms of business outcomes the client actually cares about.
Lead with the score, not the findings
The health score is the most important thing to establish first, because it gives the client a frame for everything that follows. A score of 58 out of 100 means something immediately — it's below average, it needs attention, there are specific things causing it to be where it is. Before you list a single finding, make sure the client understands the score and what the scale means.
Three sentences is enough: what the score is, what the range means, and what score you're working toward. The score anchors the whole conversation and prevents the client from losing perspective when individual findings are presented.
Translating findings into business language
For every technical finding, there's a business-outcome translation that makes the same point in terms the client can act on. The structure is always the same: what it is in plain English, what it's costing them, and what fixing it would change.
"Data retention set to 2 months. Historical user-level data beyond this window has been permanently deleted."
Your GA4 is set to delete your data every 2 months. You can't compare this Christmas to last Christmas, can't build retargeting audiences from customers who bought more than 8 weeks ago, and have permanently lost any data older than that. The fix takes 30 seconds but only works going forward — you can't recover what's already gone.
"Payment processor referral not excluded. checkout.stripe.com and paypal.com appearing in top referral sources. Purchase events firing in new sessions attributed to payment domains."
Every time a customer pays via PayPal or Stripe and comes back to your order confirmation page, GA4 records the sale as coming from PayPal — not from whichever ad or search result originally brought them to your site. Your paid campaigns are driving sales that GA4 is crediting to a payment processor. Your ROAS figures are understated as a result, and any budget decisions made from them are being made on incorrect numbers.
"Consent Mode v2 not implemented. No consent signals detected. EU user behaviour unmodelled."
In the EU, when a visitor declines the cookie banner, GA4 currently receives zero information about them — not even an anonymised count. In markets like Germany and France, 35–50% of visitors decline. That means potentially a third of your European traffic is completely invisible to GA4 and to the algorithms running your Google Ads campaigns. Your EU campaign performance looks worse than it actually is because the data is missing, not because the campaigns aren't working.
Prioritising findings for the client
A full audit report can contain 15 or 20 findings across 7 modules. Presenting all of them in sequence overwhelms the client and dilutes attention from the issues that actually matter. Your job is to filter and sequence them into three tiers before the meeting.
Handling questions from non-technical clients
A well-presented audit will prompt questions — which is exactly what you want. Here are the ones that come up most frequently and how to answer them clearly.
"How long has this been a problem?"
Be honest about what you can and can't determine. For some issues — like data retention — you can calculate approximately how much data has been lost based on when the property was created. For others — like a broken conversion event — you can identify when it stopped firing from the event log. Saying "we can see it stopped firing 34 days ago, which coincides with your site update on March 8th" is more useful than a vague answer.
"Why didn't anyone catch this before?"
This is the most delicate question, especially if the client has an existing agency relationship or internal team. Don't assign blame. The honest answer is that GA4 doesn't surface these issues proactively — there are no alerts for a zombie conversion event or misconfigured data retention. You have to specifically look for them. Most people read from GA4 without auditing it. That's the gap you're filling.
"How much will fixing this cost?"
Separate the fixes by complexity. Data retention — 30 seconds, no cost. Payment processor exclusion — 10 minutes, no cost. Consent Mode v2 — requires a certified CMP, implementation time, ongoing CMP subscription cost. Broken conversion events — depends on the cause, usually 1–3 hours of developer or GTM specialist time. Having these estimates ready before the meeting prevents the conversation from stalling on uncertainty.
"Will fixing this change our historical numbers?"
Mostly no, and it's important the client understands this. GA4 data filters are not retroactive. Fixing payment processor attribution from today forward doesn't correct the last six months. This is important to set expectations correctly — the value of the fix is preventing further corruption, not recovering past data. Where you can recover or reframe past data, explain how.
After the meeting: the follow-up document
Send a one-page summary within 24 hours that covers: the overall score, the three tier-one findings and their business impact, the proposed fix timeline, and who owns each action. This document doesn't need to be elaborate — a clear email with structured sections is enough. Its purpose is to create a record of what was agreed and give the client something to share internally if they need to get budget or developer time approved.
Clients who receive a well-structured follow-up after an audit presentation are significantly more likely to proceed with the remediation work — not because the follow-up is persuasive, but because it removes the friction of having to remember and reconstruct what was discussed.
