GA4's interface can show almost anything — event counts, engagement rate, every dimension crossed with every metric. For a client report, most of that is noise. Here's what's actually worth pulling, and why a couple of GA4's default metrics are more misleading than useful in a client-facing context.
Average engagement time per session sounds meaningful but varies wildly by content type and rarely tells a client anything actionable. Same with raw event counts — a spike in "scroll" events isn't a story unless it's tied to a conversion outcome. If a metric can't answer "so what should we do differently," it's better left out of the client-facing version, even if it's useful internally.
GA4 alone can't tell a client their cost per session or which ad platform is actually driving the conversions GA4 is counting — that requires blending GA4 with Google Ads and Meta Ads data, which is where a lot of manual reporting time goes when it's done by hand every month.
Related: How to Combine Google Ads and Meta Ads Data Into One Client Report
See Reportly's GA4 reporting integration
Reportly connects to GA4 via official OAuth2 and pulls exactly this shortlist — sessions, conversions, channel breakdown, and trend — automatically, then blends it with connected ad platforms for metrics GA4 can't calculate alone.
Connect GA4 and see it in a report in under a minute — 14-day free trial, no credit card required.