The short answer
Measure a confirmed successful submission and check for duplicate events before reporting leads.

A three-step workflow
Define success state
Define the event as an accepted submission, not a click that could fail validation. Identify where success is confirmed.
Test event behavior
Test successful and failed submissions and check for duplicate firing. Include page refresh and repeated-click behavior in the check.
Reconcile stored entries
Compare recorded events with authorized form entries for the same period. Resolve mismatches before presenting the event as a reliable lead count.
Illustrative example
Put the decision in context
A submit-button click can occur even when validation fails. Count the accepted submission event and compare it with actual form entries.
What to record in your working sheet
Keep the evidence beside the decision so the work can be checked and handed over. For this task, use these fields:
- Page, event or report name
- Metric scope and counting rule
- Observed record and comparison period
- Known tracking gaps and next validation
A mistake to avoid
Using a button click as proof that the lead was stored.
References and further reading
The workflow and illustrative example are SEOByIndia editorial guidance. Use the linked primary documentation for platform requirements; interfaces and policies can change.
Need help applying this to your site?
Share your website, the problem you are investigating and the evidence you already have. We can discuss a focused scope and the next useful check.
Discuss lead measurement