GA4 lead key event: fire on form submit click or on the thank-you page?

Our lead form's key event is generate_lead, which fires on the submit click. That inflates the count, because some clicks are validation failures or double submits. Moving the trigger to the thank-you page gives cleaner numbers, but it breaks when people close the tab before the redirect finishes, and a cached page can make it fire unpredictably.

I think the thank-you page is still the right source for anything you bid on or report to a client, since it only fires when the server accepted the lead. Submit-click is fine for diagnosing form UX, just don't mix the two in one report. How do others handle AJAX forms where there's no redirect at all?

Jun, for AJAX forms I'd fire the event in the success callback, once the server comes back with a 200 and a lead ID, not on click. That gives you the same meaning as a thank-you page view without the redirect race. And if you pass that lead ID through with the event, you can dedupe double submits too.

The success callback fixes the timing, but it won't fix duplicates on its own. GA4 counts every event it receives, so passing the lead ID doesn't stop two sends from becoming two key events. You need a guard in the browser, like a flag that gets set once the callback fires. The ID is more useful as a dedupe key in whatever imports the conversion. Which system is your source of truth for a lead right now, the form backend or the CRM?

It depends on whether Google Ads is bidding on this event. If it is, I wouldn't optimize toward a browser event no matter how well you guard it. Ad blockers, closed tabs and consent settings drop hits, and the drops aren't random. They skew toward mobile users and privacy-conscious people, who may be exactly the leads you want.

For bidding, I'd send the accepted lead from the backend to Google Ads as an offline conversion, keyed on the lead ID Elena mentioned. That way the dedupe happens once, on your side, and the conversion count matches what the CRM actually received. Browser events are still useful for form UX and for the funnel view in GA4.

If you only report on leads and don't bid on them, the success callback plus a flag is probably enough, and the offline import isn't worth the extra plumbing.

It depends on how many accepted leads get tossed after the server returns a 200. If your backend takes everything and spam or unqualified leads only get filtered out in the CRM later, a success-callback event will overcount, and the offline import is the only version that matches what sales actually works. If your form already rejects junk before it returns success, the callback is close enough and the extra plumbing doesn't buy you much. Look at the CRM rejection rate over a few weeks and you'll know which case you're in.

Kai's right on bidding, but the piece people miss is that an offline import only helps if your backend can tie each accepted lead back to a click. So when the form loads, grab the gclid from the URL, drop it in a hidden field or a first-party cookie, and store it next to the lead ID. Without that, a lead the CRM accepts three days later has nothing to match against, and you're stuck leaning on enhanced conversions, which only work if the email or phone is clean.