When a button click is counted as a completed lead, another broad rewrite or another batch of output may leave the underlying problem intact. Diagnose the relevant failure before changing the whole process.
Find the likely cause
The event fires before the form succeeds.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Track the actual successful submission or confirmed outcome appropriately.
A measurement plan should connect a business question to an observable action and a decision the team can make.
Check that the repair worked
Test failed and successful submissions separately.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: different teams define a lead differently. Document the qualification definition and map each system's status.
Monitor the useful outcome
Track the coverage and reliability of decision-critical events rather than the total number of tracked events.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.
Official reference for the platform or standard discussed: Google Analytics: key events.