How to measure leads in GA4 (not just visits)

Measuring leads in GA4 means stopping looking only at sessions, users, or page views and starting to record the actions that can end in a sale. To do it, you need to create key events that fire when someone submits a form, clicks a WhatsApp Business link, taps the phone number on mobile, or completes any other commercially relevant action. Those events are then used to analyze which channels, campaigns, and pages generate real opportunities. The difference is huge: a site can grow in visits and still not bring useful customers. If your GA4 is already installed but only talks about traffic and engagement, the problem is usually not the tool but the setup. In this guide you will see how to organize measurement so you can answer the question that matters: which digital actions are generating business contacts.

How to measure leads in GA4 (not just visits)

Measuring leads in GA4 means counting the actions that matter to the business: form submit, phone or WhatsApp click, booking, or quote request. Visits only say someone arrived. You can have a thousand sessions and zero bookings. Sessions and bounce rate do not decide budget; key events do.

This is not the "Google Analytics 4" login query (thousands of searches, Google owns that SERP). It is the owner's dashboard: which contact arrived, from which page, and from which channel. If there is traffic and no customers, first look at the site: why it does not convert. Then check whether you are actually measuring the contact.

What a key event is

In GA4, a key event (formerly "conversion") marks the action you want to optimize: generate_lead, a call, a purchase. Do not mark scroll or "button click" as key. That inflates the dashboard and campaigns learn junk.

Three layers: behavior (reading), intent (opening the form), and real contact (confirmed submit). Only the third — and sometimes the call or WhatsApp, with caveats — deserves to be a key event. Few events, with clear names: lead_form, lead_call, lead_whatsapp. If there are several forms, add a type or page parameter.

Forms, calls, and WhatsApp

List on mobile and desktop where someone can contact you. A "general contact" does not weigh the same as "request a quote" or "book an appointment."

Form. Fire the event when the submit succeeds (thank-you page, success message, or app event). A click on "Submit" with a validation error is not a lead. Test real submissions and DebugView.

Phone. A click on tel: is intent, not a conversation. For a local business it is often the most honest mobile lead. Separate the event from the form and note which URL it came from.

WhatsApp. The click opens chat outside the site. Measure it separately. It is not a sale. Cross it with time of day and landing: an 11 p.m. click is not worth the same as a 10 a.m. click.

GA4 alone or with Tag Manager

If the form always lands on /thanks and there are no edge cases, GA4 may be enough. If you measure specific buttons, tel:, WhatsApp, or forms without a success URL, you need GTM. Setup and duplicate-tag mistakes: set up GA4 and GTM.

The report that matters

Source/medium × landing × lead type. A campaign with many sessions and zero key events attracts curiosity. Informational SEO without a CTA is not "broken GA4": you are missing a service page or a visible button. Which channel pays: channel attribution.

Review trends, not a single row. A mobile WhatsApp lead at 11 p.m. does not read the same as a B2B quote form.

Why GA4 and the CRM do not match

GA4 counts digital events (cookies, attribution, sessions). The CRM counts people after a sales filter: duplicates, tests, bots, "no budget." Two submits can be one contact. A valid GA4 submit can be junk in sales.

Do not force a tie. Define which figure marketing uses (events) and which leadership uses (opportunities). Each month, cross-check a sample. If the gap is huge, either you measure the click instead of success, or sales does not log the source. The monthly KPIs should use the same lead definition in both tools.

Indicators and references for measuring results rigorously

Reliable GA4 lead measurement needs basic controls: well-defined key events, debug-mode tests, internal traffic exclusion by IP, and review of mismatches with the CRM. It also helps to separate leads by type, because form, call, and WhatsApp do not have the same traceability or commercial depth. If your team often visits the site to review changes, those visits can inflate events if they are not filtered correctly. I would keep a monthly checklist with event names, main sources, duplicates, internal traffic, and recent changes to forms or buttons.

Conclusion

In short: measure customers, not just visits. GA4 can help you know which channels generate real opportunities, but only if you set up key events for forms, calls, and WhatsApp Business clicks with clear commercial logic. Sessions and engagement provide context, though business decisions start when you know which actions produce contacts. I would treat measurement as a living system: define events, validate triggers, compare with the CRM, and refine reports. That way, configuring GA4 conversions stops being an isolated technical task and becomes a tool for investing better.

Frequently asked questions about how to measure leads in GA4 (not just visits)

Can GA4 measure calls and WhatsApp clicks as leads?

Yes, GA4 can record calls and WhatsApp clicks as key events if the site can detect those actions. For calls, the usual approach is to measure clicks on phone links, especially on mobile. For WhatsApp Business, you measure the click on the link or button that opens the conversation. Interpret it carefully: GA4 does not know whether the call was completed or whether the conversation ended in a sale. Even so, these events are very useful for understanding which pages and campaigns generate commercial intent.

Do I need GTM or can I do it with GA4 alone?

It depends on how complex the measurement is. If your form redirects to a unique, stable thank-you page, you can configure part of the measurement directly in GA4. If you need to measure specific buttons, forms without a redirect, WhatsApp clicks, phone links, or custom parameters, Google Tag Manager is usually more flexible. The decision should not be driven by technical fashion but by reliability. If measuring poorly could lead you to invest in the wrong channels, use a more controlled and validated setup.

How do I avoid counting my own employees as leads?

To keep employees from contaminating measurement, exclude internal traffic in GA4, usually with IP-based rules when possible. That helps prevent tests, site reviews, and internal form submissions from appearing as real leads. It is also wise to have a testing protocol: use labels, test environments, or identifiable records when the team reviews forms. Exclusion does not always cover every case, so also periodically review duplicates and suspicious contacts in the CRM.

Why does GA4 give different figures from my CRM?

GA4 and the CRM often give different figures because they measure different points in the process. GA4 records digital events subject to cookies, attribution, sessions, browsers, and possible blocking. The CRM collects contacts managed by sales, where duplicates may be merged, fake requests discarded, or source data corrected. A user may submit two forms and appear as two events in GA4 but as a single contact in the CRM. Compare trends, review common mismatches, and define which system you will use for each decision.

Need a marketing team?

Let’s talk and grow your business