Arsenal Insights
How to set up GA4 so it counts calls and forms as leads, and how to read the results.
Open GA4 and you will see plenty of numbers: users, sessions, engagement. What most owners want is simpler. How many people asked to talk to us, and which marketing brought them in?
GA4 can answer that, but only if it is set up to. This guide covers what counts as a lead, how to set up the events, how to track phone calls and the mistakes that make lead numbers wrong.
Quick answer: GA4 lead tracking means setting up each way a customer reaches you, such as form submits, phone calls and chats, as events, marking the important ones as key events and reading them by source. Test every event yourself, remove spam and duplicates, and write down what counts as a lead.
GA4 counts events, not leads. A page view is an event, and so is a form submit or a tap on a phone number. A lead is whichever events you decide mean a real person asked to talk to you.
Write the definition down. For most businesses it includes a completed contact form, a tracked phone call of a minimum length and a chat that captured contact details. It leaves out newsletter sign ups unless you treat them as leads.
Google explains events and key events in its Analytics help center. In 2024 it renamed conversions to key events, so you may see both terms. The setup follows the same steps either way.
A tap on a phone number only shows that someone tried to call. To count real calls, use call tracking numbers that swap onto your site by traffic source and send each call back to GA4 as an event.
Call tracking also shows call length, which helps you separate real conversations from wrong numbers and hang ups.
In GA4, look at key events by session source and medium. Organic search, paid search, social, email and direct each tell you something different. A channel that brings many visits and few leads is working less hard than one with fewer visits and more leads.
Tag your campaign links with UTM parameters so ads and emails don't blur into direct traffic. For paid channels, compare cost per lead. For free ones, compare leads per month.
Most inflated lead counts come from a short list of causes. Check these first.
Never assume an event works because it was set up. Test each one yourself before you trust the numbers.
If an event fires twice or not at all, fix it before moving on. Write down the date of the test and what you saw.
One page is enough. Put the month at the top and a short list under it: raw leads, qualified leads and sales, each with last month's number beside it.
Below that, a small table of leads by source, such as organic search, paid search, social, email and direct, with the count and the cost where there is one. Add one sentence on what changed and one on what you will do about it.
Keep the definitions at the bottom of the page so nobody has to guess how a lead was counted. If the numbers come from more than one tool, say which is the source of truth for each.
Many small businesses use a booking tool, a payment page or a form service that lives on a different web address. When a visitor moves from your site to that address, GA4 can treat it as the end of one visit and the start of another, and the original source is lost. Leads then show up as direct traffic.
GA4 has a setting to connect the domains so one visit stays one visit. You list the domains in the data stream settings, and the tool on the other site needs to use the same GA4 property. Ask the person who manages the other tool to confirm that it does.
Test it the same way you test any event. Start from a tagged link, move through the booking or payment page, finish the action and check that the source is still the one you started from. If it isn't, fix it before you rely on the numbers.
GA4 has many reports, and a small business needs only a few. Start with the traffic acquisition report to see where visits come from, and the events report to see how many of each event happened.
Then filter your key events by source and medium. That one view answers the question most owners care about: which channels bring leads. Leave the rest for later.
Check the date range before you read anything. Comparing a full month with a partial one is a common mistake. Use the same period each time, and compare it to the month before.
If a number surprises you, look for a cause before you act. A holiday, a website change, a broken form or a new campaign can each move results, and the fix depends on which one it was.
Send us your GA4 access and we will check your events, filters and lead definitions, free of charge.
A key event is an event you mark as important to your business, such as a form submit or a purchase. It used to be called a conversion.
Test each event yourself in DebugView or the Realtime report, and check that the numbers roughly match your phone and email records.
They count different things at different times. GA4 counts events on the site, and a CRM counts records. Duplicates, spam and offline calls cause gaps, so write down how each is counted.
Not by itself, except for taps on a phone link. Call tracking numbers can send real calls to GA4 as events.
It depends on your industry and traffic. Compare your own rate over time and across channels instead of chasing a benchmark.
Add basic spam protection to forms, review submissions regularly and leave obvious junk out of your reports. Count only the leads you would call back.
They are tags added to a link, such as source and campaign, that tell GA4 where a visit came from. They keep email and ad traffic from showing up as direct.
It helps if you want one dashboard that combines GA4 with ad spend. For simple needs, the GA4 reports are enough.
Monthly for decisions, weekly if you run paid ads, and right away after any website change.
Consent settings can reduce the data GA4 collects, depending on your setup and visitors' choices. Your numbers may run low, so keep a second source such as call logs.
A user is a person or device. A session is one visit. One user can have many sessions.
Missing tags, some apps and privacy features hide the source. Tagging your links and fixing cross domain tracking reduces it.
Event data follows your retention setting, which can be two or fourteen months in standard properties. Export or report on what matters before it ages out.
Mostly no. Changes apply from the day you make them, so fix tracking early and note the date.
You should. An agency can have access, but the property belongs in your account.
We check events, filters and lead definitions.
Request your auditDashboards that show leads by source.
View GA4 reporting