To track lead generation properly, decide what counts as a lead, send one clearly named event when that happens, and mark that event as a conversion in your analytics tool. Forms, calls and chats each need their own event, because each is captured differently and each behaves differently in reports. The aim is one trustworthy number per lead type, not a long list of clicks.
Start with the definition, not the tool
Before touching any tag, write down which actions are leads. For a typical service business that might be:
- A contact form submitted successfully.
- A tap on the phone number on a mobile device, or a tracked call number being dialled.
- A chat conversation started by a visitor who then sends a message.
- A booking or quote request completed.
Separate leads from interest signals. A click on a “Contact” menu item is interest. A submitted form is a lead. Mixing them inflates conversion rates and hides what is working.
Event design for each lead type
In Google Analytics 4, any event you collect can become a key event, and key events then appear in reports such as landing pages and acquisition, can be used in explorations, and can feed Google Ads conversions (Google, About key events). That makes the event name and trigger the part worth getting right.
| Lead type | Best trigger | Common mistake |
|---|---|---|
| Form | The success state, such as the thank-you page or confirmation message | Tracking the submit button click, which also fires on failed or invalid submissions |
| Phone | A click on a telephone link, or a call tracking service that records connected calls | Counting every tap as a call, including accidental ones |
| Chat | The first message sent by the visitor | Counting the chat window opening |
| Booking | The confirmation step | Counting the start of the booking flow |
Where possible, fire the event from what proves the outcome. A form success message is stronger evidence than a button click. A thank-you page can work, but make sure it cannot be reloaded or reached directly and counted repeatedly.
Naming and parameters
Use short, consistent event names, for example one for form leads, one for phone clicks and one for chat starts. Google’s developer documentation explains that you can send events with the gtag function, that recommended events use standard names which unlock prebuilt reporting, and that custom events are the option when nothing automatic or recommended fits (Google, Measure events with gtag.js). Check Google’s recommended events reference for the current list before inventing a name.
Add parameters that help analysis, such as which form it was or which page it was on. Do not put personal information in event names or parameters: no email addresses, names or message text.
Using a tag manager
Google Tag Manager separates tags, triggers and variables. Triggers decide when a tag fires, for example on a form submission, a link click or a page URL condition, and variables hold values from the page such as the click URL (Google, Tag Manager help). This lets you track a phone link click by matching links that start with the telephone scheme, without editing site code. The help page uses older Universal Analytics screens as its example, so follow current GA4 instructions when configuring tags.
Test before you trust the numbers
- Submit a real test form and confirm exactly one event arrives. Google notes that the Realtime report shows events as they occur, and DebugView shows parameters once configured.
- Submit an invalid form and confirm nothing fires.
- Reload the thank-you page and confirm the count does not double.
- Tap the phone link on a real phone.
- Compare analytics counts with the actual leads in your inbox or CRM for a week. Differences point to blocked scripts, consent choices or tracking gaps.
For paid campaigns, see the Google Ads conversion tracking guide and the Meta Pixel and Conversions API overview for platform-side set-up.
Calls and chats need extra care
Phone clicks tell you someone tapped, not that a conversation happened. A call tracking service can record call duration or connection, but it adds cost and privacy obligations, particularly around recording. Chat tools often have their own analytics, so reconcile them with your web analytics rather than assuming they match. Tools also differ in how consent choices affect measurement, so expect analytics to undercount somewhat.
Keep conversions meaningful
Mark only genuine leads as conversions, review them quarterly and retire any that no longer reflect real outcomes. Better still, add a lead quality step: record in your CRM which enquiries were genuine. Traffic that produces many low-quality leads looks good in analytics but not in the business. A well-built landing page matters as much as the tracking behind it.
Where Radiance Impact fits
Radiance Impact builds business websites and landing pages with measurement planned in from the start, and can help define events and test them before launch. See our Digital Technology services or contact us to talk about your lead generation set-up.
Sources
- About key events, Google Analytics Help
- Send events with gtag.js, Google for Developers
- Tag Manager help: tags, triggers and variables, Google Tag Manager Help
