How to Track Form Submissions in Google Tag Manager (Without Losing Conversions)

Form submissions are usually the most valuable thing you can track, they're leads, signups and contacts. They're also where GTM trips people up the most, because the page often navigates away before the tracking hit is sent. Here's how to track form submissions reliably, and how to dodge the redirect gotcha that quietly loses conversions.

Three ways to track a form submission

There isn't one "form" in tracking terms, there are several mechanisms, and the right one depends on how your form is built. In rough order of reliability:

1. A dataLayer event from your code: the most reliable. Your form's success handler pushes generate_lead (or similar) only when the submission truly succeeds.
2. GTM's built-in Form Submit trigger: no code, but it listens to the browser's native submit and can miss JavaScript-driven or embedded forms.
3. A success-page or thank-you-page view: fire on the confirmation URL. Simple, but only works if there is a distinct page.

Method 1: GTM's built-in Form Submit trigger

The fastest path when your form does a normal HTML submit. Set it up like this:

1. In GTM, go to Variables → Configure and enable the built-in Form variables (Form ID, Form Classes, Form URL).
2. Create a trigger of type Form Submission. Tick Wait for Tags and Check Validation so it only fires on genuinely valid submits.
3. Scope it: fire on Some Forms where Form ID equals contact-form (or a class/URL condition) so you don't track every form on the site.
4. Attach a GA4 event tag that sends a generate_lead event.

The redirect gotcha (and why your tag "doesn't fire")

Here's the classic failure. The form submits, the browser immediately starts loading the next page, and the page unloads before the analytics request leaves the browser. Your tag technically fired, but the hit never made it. In Tag Assistant it can even look fine on a slow connection and fail on a fast one, which is maddening.

The two robust fixes:

• Use Wait for Tags. The Form Submission trigger can delay navigation for a short timeout (e.g. 2000ms) so tags have time to send. Pair it with Check Validation.
• Better: push a dataLayer event on success (Method 2). Modern GA4 uses sendBeacon, which survives page unload, so a hit fired from a real success event is far more dependable than racing the navigation.

Method 2: the reliable dataLayer approach

For embedded forms (React, AJAX, third-party widgets) the native trigger often never sees the submit. The bullet-proof pattern is to have the form's own success callback announce the event:

// In your form's success handler, fires only when the lead is really captured.
function onContactSuccess(response) {
  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({
    event: "generate_lead",
    form_id: "contact-form",
    form_destination: "/thank-you",
    lead_value: 50
  });
}

Then in GTM:

1. Create a Custom Event trigger with Event name generate_lead.
2. Create Data Layer Variables for form_id and lead_value.
3. Attach a GA4 Event tag (Event name generate_lead) and map those variables as event parameters.

Sending it to GA4 and Google Ads

GA4

generate_lead is a recommended GA4 event. Send it from a GA4 Event tag, then mark it as a key event (conversion) in the GA4 interface. Include a value and currency if you assign monetary value to leads.

Google Ads

Fire your Google Ads conversion tag on the same Custom Event trigger so the platforms agree on what counts. Pass a stable transaction_id if you have one, so repeat thank-you page loads or back-button revisits don't double-count the lead.

Quick QA checklist

• Does the tag fire only on a successful, valid submission?
• Does the hit actually leave the browser? Check the Network tab, not just "tag fired".
• Is it scoped to the right form, not every form on the site?
• Are you double-counting on thank-you-page reloads? Add a fire-once or stable id.
• Is any PII (email, phone) accidentally riding along in the event? Keep it out of analytics.