Events and Conversions: What to Track in GA4

Most B2B analytics setups track too much and learn nothing. The team fires an event on every button, every scroll, every video play, then opens GA4 three months later and cannot answer one question: which of these actions leads to a deal?

Tracking is not the goal. A short list of events that map to real buying signals is. For a B2B company with a long sales cycle, that usually means five to eight events worth naming, one or two of them marked as conversions, and the rest kept as context. Everything else is noise that slows down your team and your reports.

This guide covers what an event is in GA4, how it differs from a conversion (now called a key event), which actions actually deserve tracking in B2B, and how to send that data somewhere it pays off, namely your CRM and your ad platforms.

Events vs conversions: the difference that trips people up

In GA4, almost everything is an event. A pageview is an event. A click is an event. A form submission is an event. GA4 collects them automatically or through your setup, and on its own an event is just a record that something happened.

A conversion, which Google now labels a key event, is an event you have flagged as important. You take an existing event, flip a toggle, and GA4 starts treating it as a business outcome: counting it in conversion reports, making it available for ad bidding, and letting you build funnels around it.

So the workflow is always two steps. First the event exists. Then you promote the meaningful ones to key events. You cannot mark something a conversion if you never sent the event in the first place.

One practical consequence: send more events than you mark as conversions. Events are cheap and reversible. You might track file_download, pricing_page_view, and demo_request, but only demo_request becomes a key event because only it signals real intent. The other two stay as supporting context you can segment by later.

What to actually track in B2B

The trap is tracking actions because you can, not because they tell you anything. Here is a tiered way to decide.

Primary conversions (mark these as key events)

These are the actions that put a lead in front of your sales team. They are the events your ad platforms should optimize toward and the ones leadership asks about.

  • Form submissions that request contact: demo requests, "talk to sales", quote requests, contact forms.
  • Phone calls from the website, if you sell over the phone. These need call tracking to capture, since a call never touches your site analytics on its own.
  • Qualified chat conversations, where a visitor books a meeting or asks for a quote through chat.
  • Meeting bookings through Calendly, HubSpot, or a similar scheduler.

For most B2B companies, one or two of these are the real conversion. A demo request is worth far more than a newsletter signup, and your tracking should make that hierarchy obvious instead of dumping everything into one "conversion" number.

Secondary events (track, but keep as events)

These show intent or movement toward a sale without being the sale itself. Keep them as plain events so you can segment and analyze, and resist the urge to mark them all as conversions.

  • Pricing page views. A strong intent signal in B2B. Worth tracking, rarely worth bidding on.
  • Resource downloads: whitepapers, case studies, guides. Useful for lead nurturing and scoring.
  • Video engagement past a threshold (50% or 75% watched), if video is part of how you sell.
  • Newsletter or blog subscriptions. Top of funnel, low commitment.

Engagement signals (track sparingly or not at all)

Scroll depth, time on page, generic button clicks. GA4 captures much of this automatically through enhanced measurement. You rarely need to act on it, and turning every one into a custom event clutters your account. Track these only when you have a specific question they answer.

The table below shows a typical B2B priority order. Numbers are illustrative.

Action GA4 treatment Why
Demo / quote request Key event (conversion) Direct sales signal, optimize ads toward it
Phone call from site Key event (conversion) Direct sales signal, needs call tracking
Pricing page view Event High intent, useful for scoring and segments
Whitepaper download Event Mid-funnel interest, feeds nurturing
Scroll depth 75% Event (often skip) Weak signal, rarely actionable

How to set events up in GA4

GA4 gives you four ways to create events, and most setups use a mix.

Automatically collected events fire with no work from you: first_visit, session_start, and others. You do not configure these.

Enhanced measurement covers common interactions once you toggle it on in your data stream: outbound clicks, scrolls, file downloads, site search, video engagement. Check what is already on before you build anything custom. Many teams rebuild events GA4 was already collecting.

Recommended events are a Google-defined naming list for common actions like generate_lead or sign_up. Use these names when one fits, because some GA4 features and reports expect them.

Custom events are the ones you define for actions specific to your business. You create them either in the GA4 interface (Admin, then Events, then Create event) or, better, through Google Tag Manager.

For anything beyond the basics, use Google Tag Manager. It lets you fire events on specific triggers, attach parameters, and change tracking without touching your site code every time. A clean GTM setup is worth the afternoon it takes to build, and it pays off the first time you need to add an event without a developer. If your GA4 base is still bare, our walkthrough on GA4 goals and events from scratch covers the install step by step.

Naming events so future-you can read them

This is the part people skip and regret. Pick a convention and hold to it.

  • Use lowercase with underscores: demo_request, not Demo Request or demoRequest.
  • Name the action, not the location: quote_request beats footer_button_click.
  • Keep it consistent across the site. One event name per action, even if that action lives on three pages.
  • Add parameters for the detail. Instead of three events for three form locations, send one form_submit event with a form_location parameter.

Parameters are where the value hides. A single form_submit event with parameters for form type, page, and plan interest gives you more analytical room than a dozen narrowly named events ever will.

Connecting events to revenue, not just counts

Here is where most B2B tracking quietly fails. You can have perfect GA4 events and still not know which campaign produced a paying customer. A form fill is not a sale. In B2B, weeks or months separate the two, and the deal closes in a CRM that GA4 never sees.

To close that gap you need two connections.

First, pass a click identifier and source into your CRM. When a lead submits a form, capture the GA4 client ID (or the GCLID from Google Ads) and the UTM parameters on hidden form fields, then store them on the CRM record. Now every lead carries the campaign that created it.

Second, send deal outcomes back. When that lead becomes a qualified opportunity or a closed deal in your CRM, push the event back to Google Ads as an offline conversion. This is how your ad platform learns to find more people who actually buy, not more people who fill out forms and vanish. The mechanics of that loop are covered in our guide to importing offline conversions from your CRM.

This closed loop changes what you optimize toward. Without it, your bidding chases form fills, and form fills are easy to get cheaply from low-quality traffic. With it, your bidding chases qualified pipeline. The difference shows up in your cost per deal within a quarter.

Visitor → form_submit event (GA4) → lead in CRM (with client ID + UTMs)
   → sales qualifies → opportunity → closed_won
   → offline conversion sent back to Google Ads

Common mistakes that waste the setup

Tracking everything as a conversion. If fifteen actions are all "conversions", none of them mean anything, and your ad bidding optimizes toward a meaningless blend. Keep the conversion list short. Two to four key events is plenty for most B2B sites.

Double-counting. A form on a thank-you page plus a form-submit trigger plus an enhanced-measurement event can fire two or three times for one submission. Always test in GA4 DebugView before you trust a number.

No deduplication between GA4 and the CRM. When the same conversion comes from two sources, set a transaction ID or use a single source of truth so you do not inflate results.

Forgetting consent. In the EU, UK, and a growing list of regions, you need a consent banner wired to Google Consent Mode, or your events simply will not fire for users who decline. Build this in from the start rather than bolting it on after a legal review.

Marking micro-conversions as primary. A newsletter signup is real, but it is not a demo request. Mixing them in one conversion count hides which campaigns drive actual pipeline. Once your events feed clean data, the broader picture lives in your marketing analytics setup.

A minimal setup that works

If you are starting fresh, you do not need a sprawling tracking plan. You need this:

  1. Turn on enhanced measurement in your GA4 data stream.
  2. Add Google Tag Manager and one custom event for your main conversion (the demo or quote request).
  3. Mark that one event as a key event.
  4. Add call tracking if phone matters to your sales.
  5. Capture client ID and UTMs on form submission into hidden fields.
  6. Pass those into your CRM, and plan the offline-conversion import back to Google Ads.

Five things tracked well beat fifty tracked carelessly. You can always add the pricing-page event and the whitepaper download next month, once the core loop runs and you trust the numbers.

FAQ

What is the difference between an event and a conversion in GA4?

An event is any tracked interaction, like a click or a form submit. A conversion (now called a key event) is an event you have flagged as a business outcome so GA4 counts it in conversion reports and ad platforms can bid toward it. Every conversion is an event first; not every event is a conversion.

How many conversions should a B2B site track?

For most B2B companies, two to four. Usually a demo or quote request, a phone call if you sell over the phone, and maybe one meeting-booking action. Keep the list short so your ad bidding optimizes toward signals that actually become deals. Track other useful actions as plain events, not conversions.

Do I need Google Tag Manager to track events?

No, but it helps. GA4 collects some events automatically and through enhanced measurement, and you can build simple custom events in the GA4 interface. For anything beyond the basics, especially events with parameters or specific triggers, Tag Manager makes setup and changes far easier and keeps you from filing a developer ticket every time.

Why do my GA4 conversions not match my CRM numbers?

Usually one of three reasons: double-firing events that inflate GA4, leads that GA4 counts but your CRM disqualifies, or no shared identifier linking the two systems. The fix is to test events in DebugView, pass a client ID into the CRM, and treat the CRM as your source of truth for revenue.

What is an offline conversion and do I need one?

An offline conversion is a deal outcome from your CRM (a qualified opportunity or closed deal) sent back to Google Ads. You need it whenever there is a gap between the form fill and the sale, which in B2B is almost always. It teaches your bidding to find buyers, not just form fillers.

Should I track scroll depth and time on page?

Rarely. GA4 captures basic engagement automatically, and these signals are weak in B2B. Track them only when you have a specific question they answer, for example whether a long landing page gets read before the form. Otherwise they add clutter without changing a decision.

The short version

Get tracking right and you stop guessing which marketing makes money. Get it wrong and you collect data nobody can act on.

  • Send events generously, mark conversions sparingly (two to four key events).
  • Name events by action, push detail into parameters.
  • Check enhanced measurement before building custom events.
  • Capture client ID and UTMs into your CRM on every form.
  • Send deal outcomes back to Google Ads as offline conversions.
  • Test in DebugView before you trust any number.

If your analytics tells you how many forms came in but cannot tell you which campaign produced a customer, the events are firing but the loop is broken. That is the gap we close most often for B2B clients. If you want a second pair of eyes, ask us for a short audit of your event and conversion setup, and we will tell you what to keep, what to cut, and what to connect to revenue.