In GA4, a lead is whatever event you decide to mark as a key event. For a service business that usually means four actions: a tap on the phone number, a tap on the WhatsApp button, a submitted enquiry form and, for clinics, a booking request. Plan the event names first, create and mark them, test them in the realtime report, then read them in the Landing pages and User acquisition reports. Remember that a tap is not a conversation: GA4 counts the click, not the quality of the call or chat that follows.
Start with the question GA4 can answer, and the one it cannot
Google Analytics 4 is very good at one thing: telling you which pages and sources lead to actions on your website. It is not good at telling you whether the person who tapped your phone number then spoke to the right person, got a quote and became a customer. Keep that boundary in mind, because most disappointment with analytics comes from asking GA4 a question that belongs to your sales process.
Google defines a key event as a marked event that tracks an action important to your business, and any collected event can be designated as one (About key events). Once an event is marked, reports such as Landing pages and User acquisition show a Key events column, and explorations can break the counts down further. For an owner this means you can finally answer a simple question: which pages and which sources produce enquiry actions, and which only produce visits?
| Question | Can GA4 answer it? | Better source |
|---|---|---|
| Which landing page produced the most enquiry taps? | Yes | GA4 Landing pages report |
| Which channel produced the most form submissions? | Yes | GA4 User acquisition report |
| How many phone calls were actually answered? | No | Call tracking or the phone log |
| Which chats became bookings? | No | Your WhatsApp pipeline or CRM |
| Which keywords brought paying customers? | Only indirectly | Search terms plus lead records |
Our guides on conversion tracking for calls and WhatsApp and a lead tracking spreadsheet cover the sales-side half of the picture. This guide covers the GA4 half.
Step 1: write a lead event plan before you touch GA4
The most common setup failure is creating events as you think of them, with inconsistent names such as Call, call_click, Phone Tap and phoneclick all in the same property. Write a one-page plan first. For most service businesses and clinics four to six events are enough, and Google allows up to 30 key events on a standard property, so there is no need to mark everything.
| Event name (suggested) | Fires when | Mark as key event? | Notes |
|---|---|---|---|
| phone_click | A visitor taps a tel: link | Yes | Tap, not an answered call |
| whatsapp_click | A visitor taps a WhatsApp link or button | Yes | Count per page and per button position |
| form_submit_enquiry | The enquiry form is successfully submitted | Yes | Fire on success only, not on button click |
| booking_request | A clinic booking form is submitted | Yes | Keep separate from general enquiries |
| directions_click | A visitor taps the map or directions link | Optional | Useful for walk-in businesses |
| quote_calculator_complete | A visitor completes a price estimator | Optional | Only if the site has one |
| pdf_download | A visitor downloads a brochure | No | Interest signal, not a lead |
Use lowercase letters, underscores and no special characters. Google specifically notes that special characters are not allowed in event names when you create an event in the interface. Decide the names once and share the sheet with whoever manages the website tag. If your site is in Arabic and English, use the same event names on both versions and add a language parameter so you can compare them. Our article on UTM tagging and campaign naming applies the same discipline to campaign names.
Step 2: decide what each event really means
An event definition needs a trigger rule and a quality rule. The trigger rule says when the event fires. The quality rule says what you will do with it later. Take the WhatsApp button as an example: the trigger is a tap on the link; the quality rule is that the number of taps is reviewed against the number of conversations that actually arrive in the WhatsApp inbox, once a week, for the first month.
Be careful with forms. GA4's enhanced measurement includes form_start and form_submit events, but Google notes that you can only use their parameters in reports if you create custom dimensions for them, and that you must make sure no personally identifiable information is collected (Enhanced measurement events). For lead forms we prefer an explicit success event that fires after the server confirms the submission, because a click on the send button can happen even when validation fails. Never pass names, phone numbers or email addresses into event parameters. Describing the form (for example enquiry or booking) and the service chosen is enough.
For clinics, add a rule about sensitive health information. A parameter that stores the exact treatment a person is asking about can become sensitive in combination with other data, so keep categories broad and let the patient details stay in your clinic system. If your business is in healthcare, also read our checklist on medical advertising rules for clinics.
Step 3: create, mark and test the events
Setting up the technical side is usually done in the site's tag setup or by a developer, but the GA4 side is straightforward. Google's instructions say you need the Marketer role or above on the property to mark events as key events, and you set up the event first. You can mark an existing event from Admin, Events, using the star next to it, or create a new event and turn on the Mark as key event toggle (Mark events as key events).
Two facts from the same page change how you test. First, marking an event affects reports only from that point forward; it does not change historical data. Second, standard reports can take up to 24 hours to show a key event, while realtime reports update a few minutes after a user triggers it. So test in realtime, then check the standard reports the next day. Use this checklist for every event:
- Open the live site on a phone, not only on a desktop browser.
- Tap the phone link and confirm the event name appears in realtime.
- Tap the WhatsApp button on three different pages, including a service page and the contact page.
- Submit a real test enquiry and confirm one event, not two.
- Submit a form with an error and confirm that no success event is sent.
- Repeat in Arabic and English versions of the page.
- Write down the date you marked each event as key, because earlier data will not include it.
Keep the test record. If a later site update breaks the button, the record tells you what normal behaviour looked like.
Step 4: connect GA4 with Google Ads without double counting
Google states that you can create a Google Ads conversion from a GA4 key event and manage it in either interface, which helps keep conversion counts consistent between the two platforms, and that it enables reporting on non-Google and organic channels, bidding on conversions and building remarketing audiences. It also notes that Google Ads conversions do not appear in standard GA4 reports; you evaluate them in Google Ads or in the Advertising section of GA4 (About key events).
The practical risk is counting the same lead twice. If one conversion action comes from a Google Ads tag and another from a GA4 key event, and both are set as primary for bidding, the campaign may be optimising for a duplicated signal. Decide which conversion action is primary, keep the others as observation only, and write that decision in the tracking document. Our guide on enhanced conversions for leads explains the next level of accuracy, and offline conversion import covers feeding real lead quality back to Google Ads.
Step 5: the reports to read every month
You do not need dozens of reports. Read three views in the same order each month, and keep notes next to them.
| View | What to look for | Action it should trigger |
|---|---|---|
| Landing pages with the Key events column | Pages with many visits and few key events; pages with few visits and many key events | Improve weak pages; send more traffic to strong ones |
| User acquisition by channel | Which channels bring visits that end in key events | Shift budget away from channels that bring only visits |
| Key events by device | Whether mobile visitors tap phone and WhatsApp more than desktop | Fix mobile layout first if mobile is weak |
| Events by language version | Whether Arabic and English pages convert differently | Review the weaker version, see bilingual SEO |
If you prefer a dashboard to the interface, our guide to a Looker Studio lead dashboard shows what to include, and the monthly marketing report article explains how to present it to a business owner.
Why GA4, Google Ads and your real enquiries will never match exactly
Expect differences and learn to explain them. A phone tap in GA4 can be a person who changes their mind before the call connects. A WhatsApp tap can open a chat that is never sent. A form submission can be spam. On the other side, calls from a printed brochure or a Maps listing never touch your website tags. Attribution models also assign credit differently between GA4 and Google Ads, and both may differ from what a receptionist remembers.
A hypothetical month shows the typical gap. Imagine a clinic whose GA4 shows 120 phone taps, 90 WhatsApp taps and 30 form submissions, a total of 240 key events. The reception log shows 85 answered calls from new patients, the WhatsApp inbox shows 52 new conversations and the form inbox shows 24 real enquiries, a total of 161. The gap of about a third is not a failure; it is the normal difference between intent and contact. What matters is that the ratio stays stable. If taps double and real contacts stay flat, something is wrong with the page or the traffic.
| Source | Counts | Typical blind spot |
|---|---|---|
| GA4 key events | Taps and submissions on the website | Cannot see call outcome |
| Google Ads conversions | Actions attributed to ads | Different attribution to GA4 |
| Call log or call tracking | Calls received and their duration | Calls not linked to a page |
| WhatsApp inbox | Messages that actually arrived | Not linked to the website unless prefilled text carries a source |
| Your lead sheet | Qualified leads and outcomes | Depends on staff entering data |
To tie WhatsApp chats back to pages, use a prefilled message that mentions the page or service, and record the source in your sheet. Our guide on call quality scoring shows how to grade calls so that quality, not only volume, is reviewed.
How we work at ZED
Tracking is a stage of our process, not an add-on. Before spending starts we make sure the actions that matter are counted: phone calls, WhatsApp messages and form enquiries. That follows our four stages of research, setup, call and WhatsApp tracking, and monthly reporting. The monthly review covers the actions agreed at the start, grouped by source where tracking allows it, and the numbers come from your own accounts so you can ask where any figure came from. We do not report likes or views as if they were business results, and we say so when a month is quiet. Read about our conversion tracking service, our Google Ads service, the about page, and the cleaning services case study. We publish no price list and promise no results; send your site address and we reply with an initial plan.
Frequently asked questions
What is the difference between a conversion and a key event in GA4?
GA4 now uses the term key event for an event you mark as important to your business. Google Ads still uses conversions, and Google says you can create a Google Ads conversion from a GA4 key event. Keep the naming clear between the two when you document your setup.
How many key events can I mark?
Google states that a standard property can have up to 30 key events, and Analytics 360 properties up to 50. A service business rarely needs more than four to six.
Why do I not see my new key event in reports?
Marking an event affects reports only from that point forward, and standard reports can take up to 24 hours to show it. Realtime reports update a few minutes after the event fires, so test there first.
Does GA4 track phone calls?
It can track taps on a phone link if you set up an event for that. It cannot know whether the call was answered, how long it lasted or whether it became a customer. Use a call log or call tracking for that.
Can I send customer names or phone numbers to GA4?
You should not. Google states you must make sure no personally identifiable information is collected. Send broad, non-identifying parameters such as form type or service category instead.
Should I mark WhatsApp taps as a key event?
Yes if WhatsApp is a main enquiry channel for your business, but treat the number as taps, not conversations. Compare it weekly with the real chats in your WhatsApp inbox.
Why does Google Ads show different numbers from GA4?
They may use different tags, attribution models and counting rules, and Google notes that Google Ads conversions do not appear in standard GA4 reports. Choose a primary conversion action for bidding and use the other source for comparison.
Can ZED set up GA4 lead tracking for my website?
Yes, tracking is one of our core stages. Send your site address and the channels you use on WhatsApp and we reply with an initial plan. We do not promise specific results.
Check your lead tracking setup
Send your website address, your phone and WhatsApp numbers and your main ad channel. We reply with an initial list of what to count first, with no promise of results.
Send site details on WhatsApp Call 01097079170