GA4 for B2B requires configuration its defaults do not provide: meaningful conversion events, extended attribution windows matching your sales cycle, internal traffic filtering, and a join to CRM outcomes. Default reporting assumes short consumer journeys and misrepresents long B2B ones.
GA4 installed and left alone will produce reports. Whether those reports describe your business is a separate question, and for B2B the default answer is usually no.
The defaults are built around short journeys ending in an immediate transaction. A six-month, multi-person, mostly-invisible B2B evaluation fits that model badly.
What should you configure in GA4 first?
Out of the box you get page views, scrolls, and outbound clicks. None of those is a conversion in any sense a revenue team would recognize.
Define events for the actions that indicate real intent: demo requests, trial starts, pricing page engagement, and document downloads that require a form. Then assign values reflecting their different worth, because counting them equally makes the report useless for allocation.
Extend the attribution window
Default lookback windows are far shorter than a B2B sales cycle, so the channel that created demand months ago gets no credit and the channel that captured it looks solely responsible.
Set the window from your observed cycle length. This one change frequently reverses conclusions about which channels are working.
Clean the data before trusting it
- Filter internal traffic. Your own team, contractors, and agencies inflate engagement on exactly the pages you are evaluating.
- Exclude bots. Unfiltered automated traffic distorts every rate you report.
- Enforce UTM conventions. Without a naming standard, channel reporting fragments into near-duplicates nobody reconciles.
- Cross-domain setup. If your marketing site and app are separate domains, an unconfigured install breaks the journey in two.
Connect it to what actually matters
GA4 alone can tell you a form was submitted. It cannot tell you the deal closed nine months later for a meaningful amount, which is the only fact that settles whether the channel was worth it. That join is what turns GA4 into analytics reporting rather than traffic counting, and it is what makes attribution possible at all.
Pass an identifier through to the CRM so sessions can be joined to opportunities. That plumbing is the difference between traffic reporting and revenue reporting.
What GA4 will not tell you
Consent requirements and cookie restrictions mean a growing share of real behavior goes unrecorded. Treat the numbers as a directional sample rather than a census.
Server-side tracking recovers some of it and adds complexity. Decide whether you need that precision before building it, because it is not free to maintain.
- ✓ GA4 defaults assume short journeys. Unconfigured, it misrepresents B2B funnels confidently.
- ✓ Set the attribution window from your real cycle length. This alone often reverses channel conclusions.
- ✓ Filter internal and bot traffic before drawing any conclusion from engagement data.
- ✓ Without a CRM join, you have traffic reporting rather than revenue reporting.
FAQ
What should B2B companies configure in GA4 first?+
Meaningful conversion events with assigned values, an attribution window matching your sales cycle, internal traffic filtering, and cross-domain tracking if your site and app are on different domains.
Why does GA4 show different numbers than our CRM?+
They measure different things over different windows, and GA4 misses sessions where consent was declined or tracking blocked. Treat GA4 as directional and the CRM as the record of what happened.
Do B2B companies need server-side tracking?+
It recovers data lost to cookie restrictions and blockers, at the cost of real setup and maintenance. Worth it when measurement precision drives significant budget decisions, hard to justify otherwise.