For a B2B SaaS company, GA4 only becomes useful once you tell it what matters. Track five events (lead captured, demo booked, trial started, activation milestone, and paid conversion), mark them as key events, send a user ID once you know who someone is, and register the parameters you filter on as custom dimensions. That gives you a funnel you can actually read, which the default setup never will.
Below we go through the events we pick, the Google Tag Manager setup, how events differ from key events, and the mistakes we keep finding when a client hands us an existing GA4 property.
Why doesn't default GA4 work for B2B SaaS?
Out of the box, GA4 collects page views, scrolls, outbound clicks and, with enhanced measurement switched on, some form interactions. That's enough to say how many people visited. It's nowhere near enough to say how many of them became customers.
We've seen this pattern more than once. Marketing reports a big number of demo bookings for the quarter. Sales says only a fraction of them were real. Both teams are reading GA4 correctly. The problem is that nobody ever told the property what a demo booking is, so a thank-you page view, a form start and a confirmed calendar slot all get counted the same way, or not at all.
B2B SaaS makes this harder than most businesses. The buying journey is long, several people from the same company visit, and the moment that matters most (a trial turning into a paying account) usually happens inside your product, not on the marketing site. If GA4 can't connect those two places, it can't tell you which channel is worth paying for.
What events should a B2B SaaS company track in GA4?
We start every property with the same five. They map to the steps your revenue depends on, and five is few enough that a small team will keep them working after the person who set them up has moved on.
| Event | When it fires | Parameters worth sending |
|---|---|---|
| lead_captured | A form creates a contactable record: a contact request, a gated asset, a newsletter signup | method, form_id, content_offer |
| demo_booked | A calendar booking is confirmed in Chili Piper, Calendly or HubSpot Meetings | booking_source, rep_assigned, account_domain |
| trial_started | A user creates a trial workspace | plan, seat_count, signup_method |
| activation_milestone | The in-product action that predicts paying, such as inviting a teammate or connecting an integration | milestone_name, time_to_activation_sec |
| paid_conversion | The first successful charge | plan, billing_cycle, value, currency |
The activation milestone takes the most thought. Pick the action your paying customers took early and your churned trials mostly didn't. If you don't know what that is yet, start with something sensible like 'invited a teammate' and revisit it once you have a few months of data.
Google also publishes a set of recommended events for lead generation: generate_lead, qualify_lead, disqualify_lead, working_lead, close_convert_lead and close_unconvert_lead. They feed GA4's lead acquisition reports and are designed for businesses where the sale closes offline, which describes most B2B deals. If you're starting from scratch, use generate_lead instead of a custom lead_captured name, since the meaning is the same and the recommended name gets you the built-in reporting. The later stages are worth adding once your CRM can send them back to GA4.
What's the difference between GA4 events and key events?
Every interaction GA4 records is an event. A key event is an event you've flagged as important to the business. Google renamed 'conversions' to 'key events' in 2024, which is why older guides still use the old word.
Flagging an event changes how GA4 treats it. It appears in the key event and attribution reports, and you can import it into Google Ads as a conversion to bid against. You do it in Admin, under the events or key events list, by marking the event.
Our rule is simple: only mark events that represent real progress toward revenue. All five above qualify. Scroll depth, video plays and file downloads usually don't. Mark too many and the key event rate stops meaning anything, and if you import them into Google Ads, it will happily optimize for the cheap ones.
How do you set up custom events in GA4?
Fire events from your application code when the action actually completes, not from CSS selectors or page URLs. Selectors break the day a developer renames a class, and URL-based triggers count every reload. The pattern we use is a dataLayer push:
// Fire from your app code when the action actually completes
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: 'lead_captured',
method: 'demo_form',
form_id: 'enterprise-contact-v3',
content_offer: 'roi-calculator',
user_id: 'usr_8f3a2c',
account_domain: 'acmecorp.com'
});Then, in Google Tag Manager:
- 1Create a Custom Event trigger that listens for the event name, for example lead_captured.
- 2Create a Data Layer Variable for each parameter you pushed (method, form_id and so on).
- 3Add a GA4 Event tag that uses your measurement ID, sets the event name, and maps each variable to an event parameter.
- 4Test in GTM Preview mode and in GA4's DebugView before you publish the container.
- 5Publish, then check the Realtime report to confirm the event arrives with its parameters.
Some events shouldn't come from the browser at all. A paid conversion is best sent from your server when the payment provider confirms the charge, for example from a Stripe webhook, using the GA4 Measurement Protocol. Keep the same event name and parameter names so the schema stays consistent whichever side sends it.
How do you set up user ID tracking in GA4?
user_id is what lets GA4 connect a visit to your product page with a trial started three weeks later on a different laptop. Without it, the funnel breaks exactly where B2B SaaS needs it most: between the marketing site and the product.
Set it as soon as you know who someone is, after sign-in or form capture, and send it with every event from then on. Use your internal user ID or a hashed value. Never send an email address, phone number or name. Google's terms don't allow personally identifiable information in GA4, and it's the fastest way to put a property at risk.
Then check that the property's reporting identity is set to use it (Blended or Observed, in Admin). If you sell to companies rather than individuals, also send account_domain or an account ID as a parameter. That lets you look at activity per company, which is much closer to how B2B deals actually happen.
Why are my GA4 custom events not showing?
It's the question we get most often after a setup, and the answer is usually boring. Work through these in order:
- Standard reports lag. New events can take a day or two to show up in reports, even when they appear in Realtime and DebugView within seconds.
- The parameters haven't been registered. GA4 collects event parameters, but they stay out of standard reports until you register them as custom dimensions under Admin, Custom definitions. Register only the ones you'll filter on, such as plan, milestone_name, booking_source and account_domain.
- The tag never fired. GTM Preview shows whether the trigger matched, and a typo in the event name between the code and the trigger is a classic.
- Consent mode or an ad blocker dropped it. Some visitors will never be measured in the browser, which is one more reason to send the paid conversion from your server.
- The name doesn't match. Event names are case-sensitive, so lead_captured and Lead_Captured are two different events.
Where do teams usually get GA4 wrong?
Beyond events that don't show up, a handful of problems come up in almost every property we audit.
The first is personal data in parameters: an email address passed as the user_id, or a name tucked into a form parameter. Hash it or use an internal ID instead.
The second is double-firing. A thank-you page that fires demo_booked on every reload inflates the count, and it's hard to spot because the number looks like good news. Fire on the booking confirmation instead of the redirect. This was part of the problem in our D2C organic growth case study. GA4 had been set up in a hurry, conversion events double-fired on certain flows, and leadership didn't trust channel reporting enough to value organic search at all. We reinstalled GA4 against a clean event taxonomy, and looking back, we'd ship that rebuild in week one, not month one. It was the most useful thing we delivered on the project.
Then there's the property with fifteen key events. That usually means nobody decided which ones matter.
And finally, no naming convention. Pick lowercase with underscores, write the event list down with what each one means, and keep it where the next developer will find it. A one-page tracking plan settles a surprising number of arguments.
A worked example (hypothetical)
This is an illustrative scenario, not a real client. A B2B SaaS company with a free trial sees healthy signup numbers in GA4 but can't say which channel produces paying customers. After adding user_id at signup and sending paid_conversion from the server, the team builds a funnel exploration from first visit to paid conversion, broken down by first-user source.
It turns out organic search sends fewer trials than paid ads, but a larger share of those trials reach the activation milestone and pay. Nothing about the website changed. The budget conversation did, and this time it's based on the company's own data rather than someone else's benchmark.
How does this fit with the rest of your reporting?
Events are the plumbing. What you put on the dashboard is a separate decision. Once the five events fire cleanly, our post B2B marketing metrics that matter, and the three we always delete covers which numbers belong in front of leadership. And if you're about to send paid traffic to a page, check the page first with The landing page teardown we run before spending a dollar on ads.
Frequently asked questions
Is GA4 good for B2B SaaS?
Yes, once it's configured. It's free, connects to Google Ads and BigQuery, and can follow people across devices with user_id. What it won't do on its own is understand your funnel; you have to define the events. Many SaaS teams use a product analytics tool for detailed in-app behavior and GA4 for acquisition and the path to signup.
How many key events should I have in GA4?
As few as it takes to describe your funnel. For most B2B SaaS companies that's three to five. If everything is a key event, nothing is.
Should I use GA4 recommended events or custom events?
Use a recommended name when one fits, such as sign_up or generate_lead, because GA4 uses those in built-in reports. Use custom names for things Google doesn't cover, like your activation milestone.
Do I need Google Tag Manager for GA4 events?
No. You can send events with gtag.js directly. We prefer Tag Manager because marketing can adjust tags without a code release, while the application still decides when an event fires.
Can GA4 track events from my app's backend?
Yes, through the Measurement Protocol. It suits events the browser can't see reliably, such as a payment confirmed by your billing provider. Send the same client ID or user ID so GA4 attaches the event to the right person.
How long does a proper GA4 setup take?
In our conversion analytics engagements it's the first two weeks of work. Most of that time goes into agreeing definitions with sales and testing every event, not writing code.
The short version
Default GA4 counts visits. A B2B SaaS company needs it to count progress. Track five events, mark them as key events, send a user ID, register the parameters you filter on, and send the paid conversion from your server. Most SaaS teams we meet don't have this in place. It isn't hard work; it just keeps slipping behind the next launch. If you'd like a second pair of eyes on your setup, our Digital Marketing team can go through your GA4 property with you in a 30-minute call.
See it in practice · D2C / E-commerce
D2C brand 3.2x organic traffic in 6 months
Curious how your own site scores?
Run our free website audit. Simple report, about 10 seconds, no sign-up.



