What counts as a lead?
Before touching any settings, agree inside the team what a lead is. A successful form submission clearly is one. A click on a phone number or a messenger link is an intention to get in touch, not a confirmed conversation, and it is worth reporting separately. Mixing the two in one figure makes the reports look better than the sales pipeline does.
List every contact route on the site: each form and what it is for, phone numbers in the header and footer, messenger buttons, email links and booking widgets. For each one, write down the event name you will use, the parameters you want with it, such as the form name or the page, and whether it should be a key event. GA4 has a recommended event for leads, and using one consistent name across the site makes reports easier to read and compare.
This list is the foundation of GA4 conversion tracking. Without it, every new form or button gets its own improvised event, and the reports slowly fill with names nobody remembers setting up.
How do you track forms, calls and messaging apps in GA4?
Forms. The most reliable signal is a confirmed submission: the event fires only after the server accepts the form, either on a thank-you page or through a message the site sends to the tag after success. GA4’s automatic form tracking is convenient, but it can record attempts that failed validation or forms that are not enquiries at all, such as a newsletter sign-up, so check what it actually records before relying on it.
Clicks to call. A click on a phone link can be captured with a tag that listens for links starting with tel:. On a computer such a click often leads nowhere, so look at the device split before drawing conclusions. If you need to know about calls that actually took place, that requires call tracking, which is a separate tool and a separate decision.
Messaging apps. Links to WhatsApp, Telegram or other messaging apps take the visitor off the site, so GA4 sees only the click. Give these clicks their own event with the messenger as a parameter, rather than leaving them among general outbound clicks, where they are easy to lose.
When a site is built or rebuilt, plan these events together with the forms and buttons themselves. It is much easier to add a reliable success signal during business website development than to reverse-engineer one later from the page code.
How do you check that each lead is counted once?
Duplicates are the most common fault. A thank-you page that is reloaded or bookmarked, a tag that fires both on the button click and on the success page, two tags installed by different people: each one inflates the figure without a single extra enquiry. Test every route yourself with GA4’s DebugView open and watch how many events arrive for one action.
For key events, check the counting setting as well. GA4 can count a key event every time it happens or once per session, and the right choice depends on what you report. Then compare GA4 with your source of truth: the CRM, the shared inbox or the messenger account. They will not match exactly, because consent choices, blocked scripts and spam all play a part, but the gap should be stable and explainable. A sudden change in the gap usually means something has broken.
Repeat the check after every site release and every change to the forms. Once the figures can be trusted, put them where decisions are made; BI dashboard development is the natural next step when GA4 reports on their own no longer answer the questions the team asks.
Who should own the setup?
Lead tracking touches the website, the tag manager, GA4 and the CRM, and each is often looked after by a different person. Name one owner for the event list and agree that nobody adds or renames lead events without updating it. Keep a short change log next to the list: what changed, when and why.
Agree, too, who administers the GA4 property and the tag manager container, and who is told when a form or a phone number changes on the site. Most tracking breaks quietly after a routine website update, not because of a complex technical fault.
Common mistakes
- Counting button clicks as leads. A click on “Send” before validation is not an enquiry. Fire the lead event only after the server accepts the form.
- Mixing intentions and leads. Clicks on a phone number or a messenger link belong in their own events, not in the same figure as completed forms.
- Counting the thank-you page. Reloads, bookmarks and the back button turn one enquiry into several if the page view itself is the lead.
- Never comparing with the CRM. Without a regular check against the inbox or CRM, broken tracking can go unnoticed for a long time.
Lead events and how to check them
A template to adapt to your own project.
| Contact route | Signal to track | How to check |
|---|---|---|
| Form | Submission confirmed by the server | Send a test enquiry and find it both in GA4 and in the inbox or CRM. |
| Click to call | Click on a tel: link, with page and device | Click on a phone and on a computer; compare the device split. |
| Messenger | Click on a messenger link, with the messenger name | Click each button and confirm one event per click. |
| Email link | Click on a mailto: link | Report it separately from form submissions. |
| Thank-you page | Not counted as a lead on its own | Reload it and confirm that no new lead event appears. |
Checklist: GA4 lead tracking
- Agree what counts as a lead and what is only an intention to get in touch.
- List every contact route with its event name and parameters.
- Fire form events only after a confirmed submission.
- Track calls and messenger clicks as separate events.
- Test each route in DebugView and confirm one event per action.
- Compare GA4 with the CRM or inbox after every release.
Example: more leads in GA4 than in the inbox
A company sees far more leads in GA4 than enquiries in its inbox. The check shows that the contact form fires an event on the button click, before validation, and again on the thank-you page, and that visitors who return to the thank-you page from their browser history are counted once more.
The fix is a single event sent after the server accepts the form, with the thank-you page excluded from lead tracking. Calls and messenger clicks get their own events. The GA4 figures now move in step with the inbox, and the remaining gap can be explained.
