A GA4 setup that answers the only question that matters

Most GA4 setups I audit are technically installed and practically useless. The tag fires, the real-time report shows visitors, and nobody in the business can answer “which channel produced revenue last month” without opening a spreadsheet and doing arithmetic by hand.

Here’s the shortest path from installed to genuinely useful.

Step 1: Decide what a conversion is — on paper, first

Before you touch the interface, write down every action that indicates real commercial intent, and what each one is worth. For a service business that’s usually: form submission, phone click, quote request, booking completed.

Put a dollar value against each. Expected value works fine: if 20% of quote requests close at an average of $3,000, a quote request is worth $600. Rough numbers beat no numbers, because they let you compare channels on the same axis.

Step 2: Mark key events and give them values

In GA4, mark those actions as key events. Pass a value parameter with each one. This is the step most setups skip, and skipping it is why the acquisition reports show traffic instead of outcomes.

If you’re firing events through Google Tag Manager, set the value in the tag configuration rather than hardcoding it in the page — you’ll want to revise those numbers quarterly without a developer.

Step 3: Fix the traffic that lies to you

Three quick corrections that materially change the numbers:

• Internal traffic filter. Your own team browsing the site for hours is not engagement.
• Unwanted referrals. Add your payment processor to the referral exclusion list, or every purchase will appear to come from Stripe.
• Cross-domain measurement. If the booking flow lives on another domain, configure it, or one session becomes two and the original source is lost.

Step 4: Link Search Console and Google Ads

Two clicks each, and they unlock the reports people actually want. Search Console linkage gives you query data alongside behaviour. Ads linkage lets you see the full path rather than just the last click.

Step 5: Build one report worth opening

Not a dashboard with forty tiles. One exploration, saved and shared, with:

• Session primary channel group as the row dimension
• Sessions, key events, key event value, and value per session as metrics
• A month-over-month comparison already applied

That single table answers the question the business is actually asking: where should the next dollar go?

Step 6: Set data retention to 14 months

The default is two months. Change it on day one, because you cannot backfill. Year-over-year comparison is impossible without it, and you will want that comparison exactly when it’s too late to enable.

The part that isn’t configuration

An analytics setup is only as honest as the conversation around it. Put the one report on a recurring calendar invite, walk through it with whoever owns the budget, and let the numbers change decisions. Otherwise you’ve built a very sophisticated way of not looking.