You have GA4 installed. It's collecting data. You check it occasionally.

Pageviews, sessions, maybe bounce rate if you squint at "engagement rate." None of it tells you anything useful about whether your website is actually working.

The problem isn't the tool. The problem is that you installed it without deciding what questions you need it to answer.

This is the same mistake people make with website pages: building content without defining what that content is supposed to accomplish first. You wouldn't create a services page without knowing whether it's meant to educate prospects, handle objections, or drive immediate contact. So why would you set up analytics without knowing what success looks like?

Before you track anything, you need to answer one question: what's my site's job?

Start With The Question, Not The Tool

For most service businesses, the answer is straightforward. Your site's job is lead generation. Not traffic. Not engagement. Not brand awareness. Lead generation.

So what does lead generation success look like on your site specifically? Not theoretically, not according to some marketing framework, but on your actual website with your actual business model.

For a service business, it usually breaks down to three actions:

• Someone fills out a contact form
• Someone books a discovery call
• Someone clicks to call you

These are your conversion events. Everything else is supporting data that adds context, but these three actions tell you whether your site is doing its job.

Without this clarity, you end up tracking everything and learning nothing. You get reports full of metrics that don't connect to business outcomes. GA4 becomes something you check out of obligation rather than something that informs decisions.

The Three Core Events Worth Tracking

Let's walk through what this looks like in practice, using my own site as the example.

Event 1: Form Submissions

GA4 has default form tracking. Don't use it. It's unreliable because it fires on button clicks, not actual submissions. Someone can click "Submit" and then abandon the form when validation errors appear, and GA4 will still count it as a conversion.

You need a custom event that fires on confirmed submission after validation passes.

I use Formidable Forms, which fires an frmFormComplete JavaScript event when a form successfully submits. In Google Tag Manager, I set up a Custom Event trigger listening for that event. When it fires, GTM sends a custom event to GA4.

This is a hard conversion. They gave you their contact info. They raised their hand. This event gets marked as a conversion in GA4.

If you use a different form system (Gravity Forms, WPForms, Contact Form 7), check the documentation for which JavaScript event it fires on successful submission. Most form plugins have one. If yours doesn't, you can set up a thank-you page redirect and track the page view instead, but event-based tracking is more reliable.

Event 2: Calendar Bookings

I use HubSpot's meeting scheduler embedded on a dedicated page. This gives me two trackable moments worth capturing.

First, when someone lands on the calendar page, that's a micro-conversion. They're interested enough to look at available times. That's a standard page view in GA4, no custom setup needed, but it's worth noting as a step in the funnel.

Second, when they actually book a meeting, that's a hard conversion. HubSpot redirects to a confirmation URL after booking. I set up a Page View trigger in GTM that fires when the URL contains HubSpot's confirmation pattern. That event gets sent to GA4 and marked as a conversion.

This is higher-intent than a form submission. They didn't just give you their email; they committed to a specific time to talk to you.

If you use a different scheduling tool (Calendly, Acuity, etc.), the mechanics are similar. Most of them redirect to a confirmation page after booking. Find that URL pattern and set up a trigger for it.

Event 3: Phone Number Clicks

Even if your calls go straight to voicemail (mine go to Google Voice), tracking phone number clicks still gives you useful data. You're capturing intent. Someone wanted to talk to you badly enough to click.

In GTM, set up a Click trigger that fires when someone clicks a link with tel: in the URL. Make sure Click Variables are enabled in GTM first (Click URL, Click Text, Click Classes) so you can target your specific phone number rather than every link on the page.

When that trigger fires, send a custom event to GA4. Mark it as a conversion.

You won't get the full data that a call tracking service like CallRail would give you (which pages they visited before calling, call duration, transcriptions). But for a lot of service businesses, knowing that someone clicked to call is enough. Especially if you're handling calls asynchronously anyway.

Each of these three events tells you something concrete about whether your site is doing its job. Forms, calendar bookings, and phone clicks are the actions that turn visitors into leads. Track those first.

Supporting Data That Adds Context

Once you have conversion tracking set up, there's supporting data worth capturing that helps you understand the lead generation funnel.

Scroll depth on key pages tells you if people are reading or bouncing after the hero section. Set up scroll depth triggers in GTM for 50% and 90% thresholds, at minimum on your homepage and services pages. If people aren't scrolling far enough to see your call-to-action, that's a problem worth knowing about.

Outbound clicks matter if you link to external tools. If you use Calendly or another external scheduling system instead of an embedded calendar, you need to know how many people click through to it.

File downloads are worth tracking if you have lead magnets or case study PDFs.

These metrics don't tell you if you got a lead, but they tell you if people are engaging enough to potentially become leads. They fill in the picture between "landed on the page" and "converted."

What This Actually Gets You

When you set up GA4 this way, your analytics answer the question: "Is my site generating leads?"

Not "how much traffic did I get." Traffic is irrelevant if none of it converts.

Not "what's my bounce rate." Engagement metrics are interesting context, but they don't tell you if the site is accomplishing its job.

You can see which pages lead to conversions and which don't. You can see if people are scrolling far enough to see your CTA. You can see the full path someone took before they filled out a form or booked a call.

You have data to make decisions instead of guessing. "Should I rewrite my services page?" becomes a question you can answer with evidence rather than instinct.

The Pattern Worth Noticing

Whether you're building a page or setting up analytics, the framework is the same: intent first, execution second.

Most people skip the "what's this for" step and jump straight to "how do I set this up." They install GA4 because they're supposed to have analytics. They add a contact form because websites are supposed to have one. They create a services page because that's what you do.

The strategic thinking is what makes the tool useful. The question "what job is this supposed to do" has to come before "how do I build it."

Start with the question your analytics needs to answer. Then set up tracking to answer it.