GA4 Lead Tracking: Count Successful Enquiries, Not Just Clicks

Someone clicks “Request a quote”, sees a validation error and leaves. If the button click is counted as a completed enquiry, the campaign report exaggerates what the website actually delivered.

Define the event boundary

A successful lead event should correspond to the intended confirmed outcome. For a form, that commonly means the server has accepted the submission. A WhatsApp click is a contact attempt; it does not prove a message was sent or that a qualified enquiry followed.

Keep the event payload small

Send useful non-sensitive context, such as the service category or form identifier, where appropriate. Do not include free-text descriptions, email addresses, phone numbers or credentials. Check the existing consent arrangement before enabling measurement.

• Use one agreed event name and owner.
• Avoid firing from both the click and success handler.
• Test invalid, failed and successful submissions separately.
• Keep page reloads from duplicating a completed outcome.
• Compare analytics with the enquiry system where authorised.

Verify the actual journey

In a controlled test, trigger validation, then a server failure if the environment permits it, and finally an accepted submission using an approved test route. Confirm which events appear. Do not send real customer information or create unwanted notification emails merely to populate a dashboard.

Keep qualified leads distinct

The first accepted enquiry and a later sales-qualified enquiry are different stages. Report them honestly and do not rename a click as a purchase. Measurement becomes useful when the team understands precisely what each number represents.