GA4 Setup: Goals, Events, and the Basics

Most B2B GA4 accounts measure the wrong thing. They count pageviews and sessions with care, then have no idea how many demo requests came in last month or which channel produced them. The analytics look busy and tell you almost nothing about pipeline.

That gap is fixable in an afternoon. GA4 ships with automatic tracking that covers a lot, but the parts that matter for a B2B business, form submissions, demo bookings, qualified-lead signals, need deliberate setup. This guide walks through the install, the events worth tracking, how to turn them into conversions (GA4 calls them key events now), and the configuration mistakes that quietly corrupt your data for months.

One note before we start: GA4's interface changes often, and Google renames things on its own schedule. Where a label might have shifted since this was written, it is worth a quick check against the current Analytics Help docs. The concepts below are stable even when the menu paths move.

What changed from Universal Analytics

If your mental model still comes from Universal Analytics, drop it. UA was built on sessions and pageviews, with goals configured as a separate layer. GA4 is built on events. Every interaction, a pageview, a scroll, a click, a form submit, is an event with parameters attached.

This matters for setup because there are no "goals" to configure the old way. You track events, then promote the important ones to key events. A demo request is just an event named generate_lead (or whatever you call it) that you have flagged as important. Everything flows from getting the events right first.

The practical upside: GA4 measures engagement across web and app in one place, and its event model is far more flexible. The downside is that nothing meaningful is tracked by default beyond the basics, so a fresh property left alone gives you traffic numbers and not much else.

Step 1: Create the property and install the tag

Create a GA4 property under your Analytics account, then set up a web data stream for your domain. GA4 hands you a Measurement ID that looks like G-XXXXXXXXXX. That ID connects your site to the property.

You have two realistic ways to get the tag onto your site:

Google Tag (gtag.js) directly. Paste the snippet into the <head> of every page. Fine for a simple site where you will not add much tracking later.
Google Tag Manager (GTM). Install the GTM container once, then deploy GA4 and every future tag through the GTM interface without touching site code. For any B2B site that will grow its tracking, this is the better choice. You will thank yourself the first time marketing asks for a new event and you do not need a developer.

If you are on a CMS or builder (WordPress, Webflow, HubSpot CMS, Shopify), there is usually a native field or plugin for the Measurement ID or the GTM container ID. Use it rather than editing theme files by hand.

After install, open Reports > Realtime, then load a page on your site in another tab. You should see yourself appear within a few seconds. If you do not, the tag is not firing, and nothing below will work until it does. Fix this before moving on.

Step 2: Understand what GA4 tracks automatically

GA4 collects a set of events with no configuration. Knowing what is already there stops you from rebuilding things that exist.

Automatically collected (always on): first_visit, session_start, user_engagement, and a few others tied to the session lifecycle.

Enhanced measurement (on by default, toggle in the data stream settings): page views, scrolls (fires at 90% depth), outbound clicks, site search, video engagement, and file downloads. Open the data stream and confirm which of these are enabled. For most B2B sites, leave them on. They cost nothing and occasionally answer a question you did not know you had.

What is not tracked automatically: anything specific to your business. A contact form submit, a "Book a demo" click, a pricing-page view that you care about, a whitepaper download tied to a gated form. Those are yours to define.

Step 3: Track the events that matter for B2B

This is where setup earns its keep. Before touching GA4, write down the actions on your site that signal buying intent. For a typical B2B company the short list looks like this:

Event	What it captures	Why it matters
`generate_lead`	Contact or demo form submitted	Your core conversion, the thing the business runs on
`sign_up`	Free trial or account creation	Product-led entry point
`file_download`	Gated asset (whitepaper, case study)	Mid-funnel intent signal
`phone_click`	Click on a `tel:` link	Often your highest-intent action in services
`pricing_view`	View of the pricing page	Strong buying-stage indicator

GA4 has a list of recommended event names (like generate_lead and sign_up) that unlock better reporting and integrations. Use the recommended name when one fits. When nothing fits, create a clearly named custom event, lowercase with underscores, for example quote_requested.

There are two ways to create these events:

In GTM (recommended). Build a trigger for the action, a form submission, a click matching a CSS selector, then fire a GA4 Event tag with your event name and parameters. A demo-form submit becomes a trigger; the tag sends generate_lead with parameters like form_id set to demo_request. You get to add context without a developer.

In the GA4 interface. Under Admin > Events, you can create new events from existing ones using conditions, for example "create a pricing_view event when page_view has page_location containing /pricing". Lighter weight, but limited to data GA4 already receives.

Send parameters with your events. An event named generate_lead is useful; the same event with form_id, lead_type, and a value is far more useful when you later want to separate a newsletter signup from a sales inquiry. Parameter names follow the same convention: lowercase, underscores, descriptive.

A short worked example for a demo-request form via GTM:

Trigger: Form Submission, fires on the element with ID demo-form (replace demo-form with YOUR_FORM_ID).
Tag: GA4 Event, Event Name generate_lead.
Parameters: form_id = demo_request, lead_type = sales, value = 100 (an illustrative placeholder value, see the note on values below).

Test in GTM's Preview mode, submit the form yourself, and confirm the tag fires once. Forms with redirects, AJAX submissions, or third-party embeds (Calendly, HubSpot, Typeform) each behave differently, so verify the actual behavior rather than assuming the trigger caught it.

Step 4: Mark key events (your conversions)

In GA4, a conversion is an event you have flagged as important. Google now calls these key events.

Go to Admin > Events (or Key events, depending on the current layout), find the event you want, and toggle "Mark as key event." That is it. From that moment, GA4 counts it as a key event in reports, makes it available in the Advertising and Attribution sections, and lets you import it into Google Ads as a conversion.

Be selective. If you mark scrolls, outbound clicks, and every micro-action as key events, your conversion reports turn into noise and you lose the signal you set this up to find. For most B2B companies, two to four key events is right: the primary lead action, maybe a secondary lead action, and possibly a high-intent signal like a pricing view or a trial start. The discipline of choosing what counts is part of the value.

A note on event values. You can attach a monetary value to a key event, which feeds GA4's revenue reports and helps automated bidding in Google Ads. For B2B, a real per-lead revenue number rarely exists at the moment of submission, so people use a proxy: average deal value times historical lead-to-close rate. If a closed deal is worth $10,000 and one in twenty qualified leads closes, a lead is worth roughly $500 as a planning figure. Treat that as illustrative and revisit it as your real data accumulates. The point is to give the bidding algorithms a relative sense of which conversions are worth more, not to claim false precision.

Step 5: Connect GA4 to the rest of your stack

GA4 on its own tells you what happened on the site. The value compounds when you connect it.

Google Ads. Link the accounts under Admin > Product links > Google Ads, then import your GA4 key events as conversions. This lets Google Ads optimize toward leads instead of clicks, which is the entire point of running paid search for B2B. Decide whether Google Ads or GA4 is your source of truth for conversions and avoid double-counting; importing GA4 conversions and also running a separate Google Ads tag for the same action will inflate your numbers.

Google Search Console. Link it to see which organic queries bring traffic alongside your behavior data.

BigQuery. GA4 offers a free export to BigQuery. For most companies this is overkill at first, but if you have a data team or you want raw event-level data for custom analysis, set it up early so the history accumulates.

The deeper connection, GA4 to your CRM, is where B2B analytics actually closes the loop. GA4 sees the lead; your CRM knows whether it became a qualified opportunity and then revenue. Tying the two together is how you move from counting form fills to attributing revenue to the channels that produced it. That work sits a layer above GA4 setup, but getting the events and parameters right here is the foundation it stands on. The broader picture of building an analytics stack that ties spend to revenue is covered in our marketing analytics guide.

Common GA4 setup mistakes

These are the ones that show up again and again in B2B accounts.

No internal traffic filter. Your team's visits, your developers testing forms, your own daily check-ins all pollute the data. Set up an internal traffic filter (define your office and team IP addresses under data stream settings, then activate the filter). Otherwise your conversion counts include the twelve times you tested the demo form yourself.

Marking everything as a key event. Covered above, worth repeating. Conversion inflation is the most common reason a B2B GA4 account is untrustworthy.

Ignoring referral spam and bot traffic. GA4 filters known bots automatically, which helps, but referral exclusions and a clean traffic strategy still matter. If your numbers look strange, traffic quality is worth investigating before you trust any report.

Inconsistent UTM tagging. GA4 reads UTM parameters to attribute traffic to campaigns. If your team tags links with Email, email, and e-mail interchangeably, GA4 treats them as three sources. Agree on a tagging convention and stick to it.

Setting it and forgetting it. A form changes, a developer redeploys the site, a button gets a new CSS class, and suddenly your generate_lead event stops firing. Nobody notices for six weeks because the report still shows a number, just a smaller one. Check your key events in Realtime after any site change, and glance at conversion trends monthly for unexplained drops.

Measuring activity instead of outcomes. Tracking sessions and bounce rate feels productive and rarely changes a decision. The metrics that move a B2B business sit further down: cost per qualified lead, lead-to-deal rate, payback. Set GA4 up to feed those rather than to produce vanity charts, and connect it to the metrics that actually matter for the business.

A minimal setup checklist

If you do nothing else, do these:

Install GA4 (via GTM if you will grow your tracking).
Confirm the tag fires in Realtime.
Define your two to four real conversion events with clear names and parameters.
Mark them as key events.
Add an internal traffic filter.
Link Google Ads and import the key events.
Test every event by performing the action yourself, then check Realtime.

That covers the 80% that drives decisions. Everything else, custom audiences, exploration reports, BigQuery analysis, builds on top of it.

Frequently asked questions

What is the difference between an event and a conversion in GA4? An event is any tracked interaction. A conversion, now called a key event, is an event you have flagged as important. You mark an existing event as a key event; you do not create conversions separately.

Do I need Google Tag Manager, or can I install GA4 directly? You can install GA4 directly with the gtag.js snippet, and for a simple site that is fine. For any B2B site that will add events over time, GTM saves you from editing site code for every change and gives marketing more control. It is the more durable choice.

How many conversions (key events) should I track? For most B2B companies, two to four. Your primary lead action, possibly a secondary one, and maybe a high-intent signal like a trial start. Marking too many turns your conversion reports into noise and defeats the purpose.

What value should I assign to a lead? There is no perfect answer, because the revenue is not known at submission. A common approach is average deal value multiplied by your historical lead-to-close rate. So a $10,000 deal that closes from one in twenty leads makes each lead worth about $500 as a planning figure. Treat it as illustrative, feed it to your bidding algorithms as a relative signal, and refine it as real data comes in.

Why are my GA4 numbers different from my Google Ads numbers? Different attribution models and conversion windows, mostly. GA4 and Google Ads count conversions on their own terms, and small gaps are normal. Larger gaps usually mean double-counting (a GA4 import plus a separate Ads tag for the same action) or a measurement window mismatch. Pick one source of truth and reconcile against it. Tying ad spend to actual revenue, rather than to either tool's conversion count, is a separate exercise worth doing; we cover it in measuring PPC performance by revenue.

Is GA4 enough on its own for B2B analytics? For on-site behavior and channel performance, yes. For true B2B reporting, no, because GA4 stops at the lead. It does not know which leads became qualified opportunities or closed revenue. You get that by connecting GA4 to your CRM, which is where the real closed-loop picture comes together.

Wrapping up

GA4 is not complicated once you ignore the parts that do not matter. Install the tag, confirm it fires, define the handful of events that signal real buying intent, mark them as key events, add an internal filter, and link Google Ads. That setup, done carefully and tested, beats an account with fifty tracked events and no clear answer to "how many qualified leads did we get last month."

The honest caveat: setup is the easy half. The harder, more valuable work is connecting these events to pipeline and revenue so you can finally say which marketing actually pays. If you want a second pair of eyes on your tracking, we will run a free 30-minute review of your GA4 and conversion setup and show you exactly where the data is leaking. No pitch, just a clear read on what to fix first.