B2B Website Analytics: What to Track & Setup Guide

Most B2B websites are running analytics that measure the wrong things. Sessions and page views tell you how much traffic you have. They do not tell you whether your site is generating pipeline.

B2B website analytics must be configured to connect visitor behavior to contact creation, form submissions to lead source, and page performance to revenue outcomes. Most setups miss this entirely because GA4 out of the box is not configured for B2B lead attribution.

Key Takeaways

• GA4 out of the box does not track B2B leads: You must configure custom events for form submissions, CTA clicks, and conversion goals before the data is useful for lead attribution.
• The most important metric is attributed form submissions by source: Which traffic channels are delivering contacts matters more than which channels are delivering sessions.
• UTM parameters are non-negotiable: Every campaign link and outbound channel must be UTM-tagged before launch. Without them, source attribution defaults to "direct" and the data is unusable.
• Cookie consent configuration affects data completeness: If the analytics script fires before consent is granted, GDPR-compliant visitors are excluded and traffic figures are understated.
• Heatmaps and session recordings explain why, not how many: GA4 tells you where users drop off. Session recording tools tell you what they were doing when they did.
• Pipeline metrics should lead stakeholder reports: Sessions are a supporting data point, not the headline. Reports leading with sessions signal an analytics setup that is not measuring what matters.

B2B Website Development

Websites That Win Enterprise Clients

We build high-converting B2B websites with modern no-code technology—designed to generate leads, build trust, and support your sales team.

Let's talk

What Should a B2B Website Analytics Stack Include?

The core stack for a B2B analytics setup has three components: GA4 for quantitative traffic, behavior, and conversion data; a CRM with source attribution connecting contact records to the traffic source that generated them; and a qualitative tool using heatmaps or session recordings to cover the full picture of what a B2B site should measure.

What GA4 contributes: traffic volume by channel, page-level engagement data, conversion events including form submissions and CTA clicks, and user journey paths. What GA4 does not contribute: individual user identification or company-level data.

• What CRM source attribution adds: The connection between a specific contact record and the channel, campaign, or page that generated them. This is the data that connects website analytics to pipeline and revenue.
• What qualitative tools add: Visual evidence of how users interact with specific pages, where they scroll, where they click, and what they do just before they leave. This explains conversion rate problems that quantitative data can only surface.
• What is missing from most B2B analytics setups: Conversion events not configured in GA4, UTM parameters not applied consistently across all inbound channels, and CRM source fields not mapped to GA4 campaign data. Any one of these gaps makes the data partially blind.

The most common gap is the CRM connection. Without it, the analytics setup measures activity rather than outcomes.

Which Metrics Actually Tie to Revenue in B2B?

For the full KPI framework and how each metric connects to revenue outcomes, B2B website KPIs tied to revenue covers the complete list with benchmarks.

Three tiers of metrics organize B2B website data by decision-making value.

• Tier 1, pipeline-connected metrics that lead reporting: Form submission rate by page, lead source attribution by channel and campaign, assisted conversions showing which pages appeared before a form submission, and time to first form submission measured in sessions.
• Tier 2, engagement metrics that contextualize Tier 1: Average engagement time per page where time below 30 seconds typically indicates the visitor did not find what they were looking for. Scroll depth on high-intent pages including pricing and case studies. Return visitor rate on target account segments for ABM-oriented sites.
• Tier 3, vanity metrics useful for trend analyzis only: Total sessions, unique users, and page views are directionally useful for traffic trend analyzis but not for understanding whether the site is doing its lead generation job.
• The one-question test: Before adding a metric to your reporting dashboard, ask: "What decision would I make differently if this number changed?" If the answer is nothing, it is a vanity metric.

The one-question test removes the metrics that look impressive in a dashboard but never inform a decision.

How Do You Set Up GA4 for B2B Lead Attribution?

The step-by-step GA4 setup for B2B lead attribution guide covers each configuration step in detail, including the GTM setup required for custom event tracking.

Six configuration steps make GA4 useful for B2B lead generation measurement. Most default installations skip at least four of them.

• Step 1, custom event configuration: GA4 does not automatically track form submissions as conversions. Configure custom events for every form submit, CTA click, and goal action using Google Tag Manager. This is the recommended approach over custom GA4 event code.
• Step 2, conversion event designation: Custom events become conversion goals only when explicitly marked as conversions in the GA4 property. Without this step, form submissions are recorded as events but not attributed as conversions in the Acquisition report.
• Step 3, UTM parameter standardization: Every link from a campaign, email, LinkedIn ad, or partner channel must carry UTM parameters. Create a UTM naming convention and enforce it. Inconsistent UTM tagging fragments the data.
• Step 4, internal traffic filtering: GA4 must be configured to exclude your own team's IP addresses. Without this, internal visits inflate traffic figures and skew engagement metrics.
• Step 5, Google Search Console connection: Linking GA4 to Search Console surfaces organic keyword data alongside on-site behavior. Essential for understanding which search terms drive form-submitting visitors versus research-only visitors.
• Step 6, consent mode configuration: GA4 must be configured to operate in consent mode compliant with GDPR and CCPA. This affects how data is collected for visitors who reject tracking and must be tested against the cookie consent banner before go-live.

Each of these steps has a specific consequence if skipped. Missing Step 2 means attribution reports do not show form fills. Missing Step 3 means 30 to 50 percent of attributed leads fall into "direct."

What Privacy and Consent Rules Apply to B2B Website Analytics?

A GDPR-compliant analytics setup is not optional for B2B sites serving European markets. This guide covers the specific consent configuration and its effect on data completeness.

GDPR applies to analytics. Collecting session data on visitors from EEA countries requires explicit consent. The practical implication is that your analytics script must not fire until the visitor accepts cookies.

• What changes when consent is properly configured: GA4 only fires for visitors who have accepted analytics cookies. This means your traffic data is understated relative to total visitors. GDPR-compliant GA4 data typically captures 40 to 70 percent of actual traffic depending on consent rates.
• Google Consent Mode v2: Google's framework allows GA4 to operate in a limited, cookie-free mode for non-consenting visitors using modeling to estimate aggregate behavior. Required for sites running Google Ads.
• The consent banner requirements: The banner must present accept and reject options with equal prominence. Pre-ticked boxes are not compliant. The user must be able to withdraw consent as easily as they gave it.
• The practical effect on reporting: A B2B site with 5,000 monthly sessions might report 2,500 to 3,500 in GA4 after proper consent configuration. The gap is not a tracking problem. It is the data that privacy-compliant analytics legally reflects.

Understanding the data gap prevents teams from misinterpreting lower session counts as a traffic drop when they are actually the effect of correct consent configuration.

What Qualitative Analytics Tools Add to B2B Website Analyzis?

Heatmap and session recording analyzis for B2B sites covers what to look for in the data and how to use it to prioritize page and CTA improvements.

GA4 shows you that visitors leave a page after 45 seconds. It does not show you whether they scrolled to the pricing section, hovered over the CTA, and then left. That level of evidence requires a qualitative tool.

• Heatmaps: Aggregate visual representation of where users click, scroll, and focus attention. Useful for identifying whether important CTAs are being seen, whether visitors read to the point where key conversion information appears, and whether navigation elements are confusing.
• Session recordings: Individual visit playbacks showing exactly what a visitor did during their session. Used to diagnose pages with high drop-off rates, understand why form completion rates are low, or identify mobile UX problems that desktop testing missed.
• When to prioritize qualitative data: When GA4 shows a conversion problem on a specific page and the cause is not obvious from quantitative data. Session recordings on that page typically reveal the answer within 10 to 20 recordings.
• The tools: Hotjar costs $39 to $99 per month for most B2B sites. Microsoft Clarity is free with strong session recording. FullStory is enterprise-tier with more powerful analytics integration but higher cost.
• The GDPR implication: Session recording tools capture individual user behavior and typically require explicit consent. Include them in your cookie consent configuration alongside GA4.

For most B2B sites, Microsoft Clarity provides sufficient qualitative data at zero incremental tool cost.

How Do You Build a B2B Analytics Reporting Structure?

The B2B analytics reporting guide covers how to structure dashboards and reporting cadences for different stakeholder audiences, from weekly pulse reports to quarterly pipeline attribution reviews.

The reporting cadence determines whether analytics data drives action or accumulates in a dashboard no one opens. Three cadences cover the full B2B reporting picture.

• Weekly pulse report, three to five metrics: Total form submissions, form submissions by source, top five pages by form-submission-assisted rate, and any anomalies in traffic volume from key channels. This is the operational signal that tells you if something is working or broken.
• Monthly review, trend view and performance analyzis: All weekly metrics in trend view, new versus returning visitor ratio by source, content performance showing which blog posts generate form submissions, and comparison to 30-day and 90-day averages.
• Audience determines what leads the report: A CEO cares about leads, pipeline influenced, and revenue attributed. A marketing manager cares about channel performance and conversion rates by page. A content team cares about which posts generate form submissions. Build separate views, not one report for everyone.
• Dashboard tool decision: Use GA4 Exploration reports for internal marketing team use. Looker Studio is free from Google and suitable for stakeholder reporting. GA4 plus CRM reporting in HubSpot or Salesforce covers pipeline attribution. Avoid pulling these into a single spreadsheet manually.

Reporting without a defined cadence and a defined audience becomes a data dump that no one uses and no one trusts.

Conclusion

B2B website analytics is not a setup task. It is an ongoing system that only works when GA4 is configured for conversion tracking, UTM parameters are applied consistently, consent is handled correctly, and the reporting structure connects site behavior to pipeline.

Most B2B analytics setups are incomplete in at least one of these areas, which means the data exists but the decisions it should inform cannot be made. The fix is not a new tool. It is the configuration and discipline to use the tools already in place.

Open your GA4 property and check whether you have any conversion events configured. If form submissions are not showing as conversions, not just events, your analytics setup is not measuring B2B lead generation. Configure that first.

B2B Website Development

Websites That Win Enterprise Clients

We build high-converting B2B websites with modern no-code technology—designed to generate leads, build trust, and support your sales team.

Let's talk

How LowCode Agency Sets Up Analytics in B2B Website Builds

Analytics that connects website behavior to pipeline does not happen by default. It requires deliberate setup at build time: custom event tracking, UTM standardization, consent mode, and a CRM connection. Most B2B websites are launched without these in place, which means the marketing team inherits a data gap that takes months to close.

Analytics that actually connects website behavior to pipeline is built into every B2B website development project LowCode Agency delivers, not added as an afterthought. At LowCode Agency, we are a strategic product team, not a dev shop. We configure GA4, GTM, consent mode, and CRM integration as part of the build spec so the data is reliable from the first session after launch.

• GA4 custom event configuration: We configure conversion events for every form type, CTA action, and lead goal at build time, tested in DebugView before handoff.
• Google Tag Manager setup: We install GTM as the tag management layer so analytics events can be updated and added without developer involvement on every change.
• UTM naming convention: We establish a shared UTM naming document and enforce it across all channels before any campaigns launch against the new site.
• CRM source attribution: We connect form submissions to CRM contact records so every lead can be attributed to its source channel and traced to pipeline.
• GDPR consent mode: We implement Google Consent Mode v2 with a certified CMP so the analytics setup is legally compliant from launch and captures the maximum allowable data.
• Reporting structure: We deliver a Looker Studio dashboard with the pipeline, conversion efficiency, and acquisition metrics in the structure your team can use immediately.
• Full product team: Strategy, UX, development, and QA from a single team that treats analytics configuration as a delivery standard, not a client responsibility.

We have built 350+ products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. See how this looks across client projects, or discuss your analytics setup if you want to understand what a properly configured B2B analytics stack looks like for your site.