Define what counts as a lead

A button click, a successful form submission and a qualified lead are different events. Agree what you are measuring first. For a website enquiry, record confirmed acceptance of the data and assess lead quality separately in your CRM or working records.

GA4 recommends generate_lead for an appropriate lead-generation action. You can mark it as a key event. The name does not repair incorrect triggering: firing it on every click will overstate results.

From click to confirmation: Visitor clicks; Form validates; Server confirms; generate_lead event; Team receives the enquiry
From click to confirmation

Use a reliable success signal

The application’s confirmed outcome is a useful trigger. For an AJAX form, that may be a successful server response. A thank-you page needs consideration of direct visits and reloads: viewing it does not always mean a new submission occurred.

Do not send the same event independently from the theme, a plugin and Google Tag Manager without coordinating them. Map the installation first: where GA4 is loaded, what sends the event and what condition triggers it.

Test with debugging tools

Use the appropriate preview mode and DebugView to inspect the event sequence, names and parameters. Compare the event with the actual enquiry record. Standard reports can take longer to update; reporting delay is not necessarily a broken implementation.

Test four situations:

  1. A valid submission creates an enquiry and the expected single event.
  2. A required-field error does not trigger a successful-lead event.
  3. A repeated click does not create duplicate enquiries.
  4. Reopening the confirmation page is not automatically treated as another lead.

Keep enquiry content out of analytics

Names, phone numbers, email addresses and free-text messages should not be passed into GA4 event parameters. Check URLs too: form data should not expose personal information in query strings. Form type, page and agreed technical attributes are usually sufficient for analysis.

Account for consent settings, blockers and device differences. Measurement may be incomplete; do not promise that analytics will observe every visitor.

Connect tracking to business outcomes

Review enquiry volume, suitability and sales separately. An enquiry for a service you do not offer is not equivalent to a qualified prospect. Where attribution is uncertain, do not assign a sale to SEO simply by assumption.

Search Console clicks and GA4 sessions need not match because the tools measure different events and have different limitations. Use the Search Console guide to interpret search visibility.

Document and repeat the checks

Keep an event map, trigger conditions, tested scenarios and owner access details. Retest after changes to forms, plugins, caching or consent controls. If enquiries are delivered to Telegram, check the handoff to the manager separately: an analytics event alone does not establish notification delivery.

Need a plan for your website?
Explore our services: SEO Services, pricing or discuss your project.