GA4 and Google Tag Manager for B2B: how to set up analytics that reports pipeline, not pageviews
GA4 cannot tell a B2B team which channels create pipeline on its own, because pipeline lives in the CRM. A good setup does three things: it tracks the few key events that signal buying intent, it passes the identifiers your CRM needs to tie a lead back to its visit and ad click, and it keeps enough history to compare quarters. Server-side tagging helps when data control and tag reliability matter, but it does not replace a clean CRM connection.
Key takeaways
- Track a short list of key events tied to buying intent. Dozens of events nobody reports on are a cost, not an asset.
- Pass campaign, click and visitor identifiers into hidden form fields so the CRM can connect leads to visits and ads.
- GA4 standard properties keep event data for 2 or 14 months, and that setting only affects explorations and funnel reports. Set it to 14 months on day one.
- Server-side tagging gives you control over data before it reaches vendors. It is an infrastructure project, not a tag change.
- Measure the setup by the share of CRM leads with a known source and campaign, not by the number of tags.
The B2B analytics problem
Most B2B GA4 properties were migrated from Universal Analytics in a hurry. They count sessions, scroll depth and dozens of events, but a head of digital experience still cannot answer the question the CMO asks: which channels and pages create qualified pipeline.
The reason is structural. A B2B buyer visits several times over weeks, often from different devices, and the deal closes in the CRM months later. GA4 sees the visits. The CRM sees the revenue. Value comes from connecting the two, and that is a design job, not a reporting job.
Settings and limits that shape the design
Google’s documentation states that standard GA4 properties can keep user-level and event data for 2 or 14 months, and that 360 properties can keep event data for 26, 38 or 50 months. The retention setting only affects explorations and funnel reports, not standard aggregated reports. Properties that grow to Large or XL size are limited to 2 months. If you plan to analyze long B2B cycles, set 14 months immediately and export raw data to a warehouse such as BigQuery for anything longer.
GA4 is also the wrong place to store revenue. Keep pipeline and closed-won data in the CRM, and bring the identifiers together there or in a warehouse.
What a B2B GA4 and Tag Manager setup should include
| Layer | What to set up | Why it matters |
|---|---|---|
| Key events | Demo or contact request, pricing view, high-intent content views, chat start | Bidding and reporting focus on signals that predict pipeline |
| Identifiers into the CRM | UTM values, Google Click ID and the GA client ID in hidden form fields | The CRM can tie each lead to its campaign and visit |
| Consent and privacy | Consent banner wired to tags, with regional rules | Data you collect is data you are allowed to use |
| Tag governance | Naming rules, a change log and a test workspace in Tag Manager | Tags stop breaking silently when the site changes |
| Ad platform feedback | Offline conversion imports from CRM stages | Google Ads learns from qualified leads, not form fills |
| History | 14-month retention plus a warehouse export | Quarter-over-quarter comparisons stay possible |
We fix source data, routing and attribution so sales and finance trust the numbers.
When server-side tagging is worth it
Google describes server-side tagging as running a Tag Manager container on infrastructure you control, in your own Google Cloud project or another environment, rather than in the visitor’s browser. Data reaches that server first, and only you have access to it until you choose to send it on. Permissions and policies let you set boundaries on what each tag can do.
For enterprise B2B, that control is the main reason to do it: fewer third-party scripts in the browser, the ability to remove fields before they reach vendors, and more consistent delivery to ad platforms. It also adds hosting, monitoring and ownership. Do it after the key events and CRM identifiers work, not instead of them.
Common mistakes
- Tracking every click as an event, so the events that matter are lost in the noise.
- Leaving retention at 2 months and discovering the gap when the board asks for a year-over-year funnel.
- Capturing UTMs on the landing page but losing them when the visitor converts on a later visit.
- Changing tags directly in production without a test workspace or change log.
- Reporting GA4 conversions as pipeline when nobody has checked them against the CRM.
How to measure the setup
- List the five key events and the CRM fields each one should populate.
- Submit test leads from every major channel and check that source, campaign and click ID arrive in the CRM.
- Track the share of new CRM leads with a known source and campaign each month.
- Compare GA4 key events with CRM leads weekly, and investigate any gap above 10%.
- Review the Tag Manager change log monthly and remove tags nobody uses.
Why work with a GA4 and Tag Manager specialist
The tools are free or close to it. The expense is the time your team loses to reports nobody trusts. A specialist brings a tested event plan for B2B, CRM field mapping, consent wiring and a governance model, and checks the setup against real leads rather than tag previews.
At PlanConversion we design analytics backwards from the pipeline report. For KNIME, rebuilding measurement end to end meant 9 in 10 leads were verified in the CRM and 100% of paid leads were traceable to closed deals.
Frequently asked questions
How long does GA4 keep data?
Standard properties can keep user-level and event data for 2 or 14 months. 360 properties can keep event data for 26, 38 or 50 months. The setting only affects explorations and funnel reports.
Can GA4 report pipeline and revenue for B2B?
Not reliably on its own. Pass campaign and click identifiers into the CRM and report pipeline there or in a warehouse.
Is server-side tagging required?
No. It is worth it when data control and tag reliability matter, after key events and CRM identifiers already work.
What should a GA4 consultant deliver?
A key event plan, CRM field mapping for identifiers, consent wiring, Tag Manager governance and a monthly check that GA4 and CRM numbers agree.
Sources
Related service: RevOps and marketing operations. See also pricing and client results.
We run enterprise B2B demand generation for teams in Montreal, Toronto, Ottawa and the United States.
