GA4 tracks pageviews and scrolls out of the box and looks, at a glance, like it’s already doing its job. It isn’t. Default GA4 tells you that people showed up and moved around, not whether anything they did actually mattered to the business. The gap between “installed” and “useful” is almost always the same handful of events, missing for the same reason every time: nobody went back after launch to add the tracking that answers the questions the business actually asks.
Why the Default Setup Isn’t Enough
Out of the box, GA4 answers “did traffic happen.” It doesn’t answer “did the thing we care about happen,” because it has no idea what that thing is until you tell it. A SaaS company cares about trial signups. A services firm cares about form submissions and calls. An ecommerce store cares about add-to-cart abandonment, not just purchases. None of that is automatic. It’s configuration work that has to happen deliberately, and it’s the single most common gap we find auditing a “fully set up” GA4 property.
The Five Events Worth Checking For
Form submissions, tracked per form, not as one generic event. A single “form_submit” event that doesn’t distinguish the newsletter signup from the contact form from the demo request tells you activity happened somewhere, not which offer is actually working.
Outbound and file-download clicks. If a PDF, a pricing sheet, or a link to a partner’s booking page is part of your funnel, the click needs its own event. Otherwise that entire step in the journey is invisible, and you’ll never know how many people got that far before dropping off.
Scroll depth or content engagement on pages that do the selling. Pageviews don’t tell you if anyone read past the headline. On a long-form page meant to build a case for the reader, that distinction is the difference between “this page works” and “this page gets abandoned in five seconds.”
A real conversion event tied to a value, not just a count. A lead form submission and a $50,000 enterprise inquiry shouldn’t register as the same unit of success. Attaching value, even an estimated one, is what lets GA4’s reporting reflect revenue potential instead of raw volume.
Site search queries, if you have on-site search. What people search for on your own site is some of the most direct intent signal you’ll ever get, and it’s off by default.
Set It Up Once, Trust It Longer
None of these require a developer overhaul. Most run through Google Tag Manager with a handful of triggers pointed at the buttons, forms, and pages that already exist. The work isn’t technically hard. It’s just easy to skip, because a GA4 property with default tracking still produces charts that look complete even when they’re missing the events that matter most.
Event tracking is only half the picture if the data behind it isn’t trustworthy in the first place. That’s the other half of getting analytics right: making sure the consent and privacy layer feeding these events is sound, not just the events themselves.
If your dashboard looks busy but can’t answer what’s actually converting, let’s audit what’s tracked and what’s missing, or see how this fits into our analytics and measurement work.