A well-structured audit presentation handles most of the conversation on its own — lead with the score, translate findings into business language, prioritize into tiers. But a handful of moments in almost every review don't respond to structure. They respond to how you handle the room. Getting these three right is often what determines whether a client trusts you enough to act on what you've found.

When an existing agency or in-house team is implicated

Every finding you present was, technically, someone else's miss. Sometimes that someone is an agency the client still works with. Sometimes it's an internal marketing hire who's in the room. The instinct to soften findings in this situation is understandable, but softening them undermines the whole point of the audit — the client needs to act on what you found, and they won't act with urgency on something you've downplayed.

The instinct to avoid
Naming or blaming the person or team responsible

Don't say "whoever set this up didn't know what they were doing." It's unnecessary, it's usually wrong — most GA4 misconfigurations are inherited defaults or reasonable decisions that became wrong over time, not incompetence — and it puts the client in the position of defending a colleague or vendor instead of focusing on the fix.

Describe the system, not the person. "GA4 defaults to a 2-month retention window" is accurate and blame-free. "Your last agency should have caught this" adds nothing except tension.

Script "This is a really common gap — GA4 doesn't flag it, there's no warning in the interface, and it's one of those settings that gets set once at launch and never revisited. It's not a sign anything was done carelessly. It's exactly the kind of thing an audit exists to catch."

When the data is gone for good

The hardest version of this conversation is explaining that historical data cannot be recovered. GA4's filters and settings are not retroactive — fixing a data retention setting today doesn't restore the user-level data already purged under the old 2-month window; excluding a payment processor domain today doesn't reattribute the last six months of misattributed purchases.

Clients often ask this directly, and the honest answer disappoints them. The way to handle it is to be clear about what's actually lost versus what can be partially reconstructed, rather than letting "it's gone" be the entire answer.

Script "I want to be straight with you on this one — the historical data affected by this issue isn't recoverable. What we can do is fix it so it stops happening today, and where the underlying numbers exist somewhere else — your CRM, your payment processor — we can reconstruct an accurate picture for reporting purposes. But the GA4 record itself, for that period, isn't coming back."

Setting this expectation clearly, once, prevents a slower and more damaging version of the same conversation happening later — a client discovering months from now that a "fix" didn't retroactively repair their year-over-year comparison, and concluding they were misled.

When you're auditing your own past work

This comes up more than people expect: you inherit a client relationship, take over from a departing colleague, or get asked to re-audit a property you set up yourself a year ago. Finding your own mistake in front of a client is uncomfortable in a way that finding someone else's isn't.

The instinct to avoid
Over-apologizing or over-explaining why it happened

A brief, direct acknowledgment lands better than an extended explanation. Clients don't need the backstory of why a setting was left at default 14 months ago — they need to know it's been caught and it's being fixed. Long justifications read as defensiveness, even when that's not the intent.

Script "This one's on us — we should have caught it sooner. It's fixed now, and here's what we're doing to make sure the rest of the property gets checked on a regular basis instead of only when something looks wrong."

The second sentence matters as much as the first. An acknowledgment with no forward-looking change reads as an apology with no substance behind it. Pairing it with a concrete process change — a recurring check, a monitoring step — is what turns the moment into something that builds trust instead of eroding it.

Why the honesty holds up

All three of these situations share a common thread: the temptation is to smooth over the uncomfortable part, and the better move is almost always direct, brief honesty followed immediately by the fix and the forward plan. Clients are far more forgiving of a clearly explained problem than they are of a vague one they later discover was softened.

The pattern that works across all three: name what happened factually, skip the blame or the extended apology, and move immediately to what's being done about it. The credibility you build in the hard moment is what makes the client trust the rest of the report.
GA4 Health Check's audit report gives you the facts, not the framing. Findings are stated plainly and without blame — the conversation on top of them is yours to handle. Run your next client audit — $79 →
Travis Gunn
Travis Gunn
Founder of GA4 Health Check. Working with Google Analytics since 2013, with over 250 clients audited across almost every industry vertical. 100% Job Success on Upwork for over a decade.