How to Track Website Leads in GA4 Beyond Traffic

Your Website Traffic Is Up. Are You Getting More Leads?

To measure whether your website is generating inquiries, track successful lead actions in Google Analytics 4, mark them as key events, and review them alongside traffic sources. Check those numbers against actual form entries or your CRM before treating them as business results.

A traffic increase feels good. More people found your website, opened a page, and spent some time looking around.

But if your website’s job is to bring in project inquiries, appointments, or quote requests, traffic only answers part of the question.

The next question is: Did those visits turn into something useful?

You don’t need a dashboard packed with charts to start answering that. You need a clear definition of a lead, a reliable way to measure it, and a habit of checking what the numbers actually represent.

Start with the action you want someone to complete

For a service-based business, a useful website outcome might be a completed inquiry form or a confirmed consultation booking.

Opening the contact page is a step toward that outcome. Clicking Submit is another step. Neither necessarily means an inquiry reached your business.

A visitor could click the button with required fields missing. A booking could stop before confirmation. A form might save an entry while its notification email fails.

Write down one specific action first:

A visitor successfully submits the project inquiry form.

That definition gives you something concrete to build and test. “Track engagement” leaves too much room for interpretation.

What GA4 calls a key event

In GA4, an event records an interaction. A key event is an event you’ve identified as particularly important to your business. You first collect the interaction, then mark it as a key event. Google’s explanation of key events covers that relationship.

For an inquiry form, Google recommends using the event name generate_lead where appropriate.

The name doesn’t make the tracking accurate on its own. What matters is when the event fires.

If it fires when someone opens the form, your report measures form views. If it fires after a successful submission, it’s much closer to the outcome you intended.

A simple starting point: track a confirmation page

A dedicated confirmation page can make an initial setup easier.

For example, a successfully submitted form might redirect to:

https://www.example.com/inquiry-received/

Before using this approach, you’ll need:

• A working GA4 installation that records page views.
• Access to configure events in the correct property. Editor or Administrator access is a practical starting point.
• A confirmation page reached after a successful submission.
• A check that another plugin or tag isn’t already sending generate_lead.

In GA4:

1. Open Admin > Data display > Events.
2. Select Create event.
3. Enter generate_lead and enable Mark as key event.
4. Choose Create without code.
5. Select page_view as the existing event.
6. Enter your actual confirmation-page URL.
7. Create the event.

This follows Google’s confirmation-page tutorial. Check the URL rule presented in your property so it matches the intended page.

If your form displays an inline success message without changing pages, this particular method won’t fit. Your developer should connect tracking to the form system’s confirmed-success behavior.

A confirmation-page view is also a proxy for a submission. Reloading or revisiting that page can produce another event. Don’t describe its count as a guaranteed number of unique inquiries.

Test the whole journey before trusting the report

Submit a clearly labeled test inquiry through the actual form.

Check three separate things: the form accepted the submission, the entry reached its destination, and GA4 recorded the intended event.

For an initial analytics check, look for generate_lead in Realtime after the configuration has taken effect. For more detailed troubleshooting, Google’s DebugView documentation explains how to enable debug mode with Tag Assistant and inspect events under Admin > Data display > DebugView. Consent settings can affect what appears.

Also test an unsuccessful submission. It shouldn’t produce a successful-lead event.

If one successful submission produces multiple events, investigate duplicate tags or overlapping tracking rules before using the totals.

Standard reports can take up to 24 hours to reflect key-event data. Marking an event as important doesn’t retroactively turn earlier activity into key events, so record your setup date.

Compare traffic with the outcome you care about

Once you have usable data, open Reports > Acquisition > Traffic acquisition. If your navigation has been customized, an Editor may need to restore the report.

Review traffic by channel or Session source / medium, then select your lead event under the Key events column where available.

Three useful measures are:

Google defines session key event rate as sessions containing a key event divided by total sessions. Check which event is selected before interpreting it.

Don’t divide raw event totals by sessions and assume you’ve calculated that rate. A session can contain repeated events.

A higher rate doesn’t automatically mean a better channel

Imagine these illustrative numbers, with the same lead action selected:

Email has the higher rate. Search brings more sessions containing a lead event.

Both observations matter. Neither tells you which inquiries became good projects.

Before changing your marketing budget, check lead quality, campaign cost, and whether the audiences had different reasons for visiting.

A handful of inquiries can also make percentages swing sharply. Give a small dataset time before treating a change as a dependable pattern.

Keep analytics connected to actual inquiries

GA4 shouldn’t be your only record of leads.

Compare trends with saved form entries, booking records, or your CRM. Investigate large gaps rather than expecting every system to match perfectly.

Keep personal details out of analytics while doing this. Don’t send names, email addresses, or message contents as event parameters, and check that confirmation URLs don’t contain them. Google’s guidance on avoiding personally identifiable information specifically addresses URLs and user-entered data.

Start with one important form. Define success, verify the tracking, and write down what the measurement includes.

Then your next website report can answer a more useful question: Are the right people reaching out, and where should we investigate next?