Form Tracking in GA4 Using Google Tag Manager: Triggers, Thank-You Pages and dataLayer Code

Need this done for you? GrowthSparx offers a fixed-scope lead tracking and attribution setup: GA4, Google Ads, Meta, WhatsApp, calls and CRM wired into one dashboard, usually live in 2–3 weeks.

Which form tracking method should you use in GTM?

This guide covers how to detect a successful submission. Which GA4 events to send for leads (generate_lead, call and WhatsApp taps, CRM stages) and how to mark them as key events is in our GA4 lead generation tracking setup. Get detection right first; every event plan depends on it.

Most Indian business websites we audit run on WordPress with Contact Form 7, Elementor or WPForms, or on a page builder, and the form posts with JavaScript (AJAX) without loading a new page. That is why "just use the Form Submission trigger" so often under- or over-counts.

Method 1: How do you track a form with a dataLayer push?

The developer adds a push to the code that runs after the server responds with success. Google's data layer guide sets the rules: declare window.dataLayer = window.dataLayer || [], push events with an event key, never overwrite or re-assign window.dataLayer, and match names and casing exactly.

// Developer adds this inside the form's success callback (after the server saves the lead)
window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'form_success',
  form_name: 'site_visit_request', // which form
  form_location: 'project_page_hero', // where on the site
  lead_id: 'L-2026-48213' // your own ID, not a phone or email
});

In GTM:

1. Variables: create Data Layer Variables DLV - form_name, DLV - form_location, DLV - lead_id.
2. Trigger: Custom Event, event name form_success. Use one generic success event for all forms and tell them apart with form_name, rather than one event name per form.
3. Tag: the GA4 event tag described below.

Brief for your developer, in one sentence: "after the server confirms the lead is saved, push form_success with the form name and our lead ID; do not push on validation errors, and do not include the visitor's name, phone or email." The lead ID matters later: it becomes the transaction ID that stops duplicates, as explained in fixing duplicate conversions.

Method 2: How do you track a thank-you page?

If the form can redirect to a dedicated URL such as /thank-you/site-visit/, that page view is your conversion. It needs no code beyond the redirect, and it works for every form tool.

1. Give each form its own thank-you URL, or add a parameter: /thank-you/?form=brochure.
2. Add noindex to the thank-you pages and keep them out of the sitemap, so visitors do not arrive from Google search and count as leads.
3. Trigger: Page View, fires on Some Page Views, Page Path starts with /thank-you/. Add a second condition, Referrer contains your domain, so a direct visit or a bookmark does not fire it.
4. Read the form name from the path or the form parameter with a URL variable.

Weakness: reloading or pressing back and forward re-fires the page view. If the thank-you page is your only option, add a small sessionStorage check in a Custom HTML tag, or accept a few per cent of over-count and reconcile against the CRM. Never put the visitor's details in the thank-you URL; form tools that redirect with ?name=...&phone=... send personal data into GA4, which Google's PII policy forbids.

Method 3: How do you track an AJAX form with element visibility?

Many forms show a message such as "Thank you, our team will call you within 30 minutes" in place, without a new page. GTM's element visibility trigger fires when that element appears.

1. Submit a test form, right-click the success message, Inspect, and note an ID or class that appears only on success, e.g. .wpforms-confirmation-container or .elementor-message-success. Do not use a generic class shared with error messages.
2. Trigger: Element Visibility, selection method CSS Selector, your selector; When to fire: Once per page; tick Observe DOM changes (essential, because the message is inserted after load); minimum percent visible defaults to 50%, which is fine.
3. On long pages where the message may render below the fold on mobile, lower the visible percentage to 1% so it still fires.

Weakness: a theme update that renames the class silently stops tracking. Add the selector to your release checklist.

Method 4: When is GTM's Form Submission trigger enough?

The Form Submission trigger listens for the browser's submit event. Its two settings decide its reliability:

• Check Validation: when ticked, it fires only if the form is successfully sent; when unticked, it fires on any submit attempt, including ones that fail. Always tick it.
• Wait for Tags: delays the submission until tags fire or a timeout passes. Without it, Google warns, "slow tags may not fire before the form submit causes the next page to load."

Limit it with "Some Forms" and a condition such as Form ID equals enquiry-form; the built-in variables Form ID, Form Classes, Form Element, Form Target, Form URL and Form Text help. It is fine for a plain HTML form that posts to a new page and has server-side validation shown on that new page. It is unreliable for AJAX forms, which may never fire a standard submit event, or may fire it before the server has rejected the entry.

GA4's own enhanced measurement form interactions (form_start and form_submit, with form_id, form_name, form_destination and form_submit_text) works on similar detection. Leave it on for funnel analysis (how many people start a form versus finish it), but do not mark form_submit as a key event if you also send a lead event, and register its parameters as custom dimensions if you want them in reports.

How do you track WordPress plugin forms and embedded forms?

Contact Form 7. CF7 fires its own DOM events, documented on its DOM events page: wpcf7mailsent (submission succeeded and mail sent), wpcf7invalid, wpcf7spam, wpcf7mailfailed and wpcf7submit (fires whatever the outcome). Listen for wpcf7mailsent only, and convert it into the same form_success push as Method 1:

<script>
// GTM Custom HTML tag, trigger: DOM Ready on pages with a Contact Form 7 form
document.addEventListener('wpcf7mailsent', function (event) {
  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({
    event: 'form_success',
    form_name: 'cf7_' + event.detail.contactFormId,
    form_location: location.pathname
  });
}, false);
</script>

Do not read event.detail.inputs into the data layer: those are the visitor's answers, including phone and email.

Other plugins (WPForms, Gravity Forms, Elementor forms) also expose success hooks or confirmation messages; use the hook if your developer can, otherwise the element visibility method.

Forms inside an iframe (embedded Typeform, Google Forms, some CRM web forms) cannot be seen by your GTM container, because the form lives on another domain inside the frame. Options, best first: use the form tool's redirect-on-submit to your own thank-you page (Method 2); use the tool's native GA4 or postMessage integration if it offers one; or rebuild the form natively on your site, which also lets you add hidden UTM fields. Cross-domain linking does not fix iframes; it is for full-page journeys, covered in cross-domain tracking for landing pages.

How do you set up the GA4 event tag?

1. Tag type: Google Analytics: GA4 Event. Measurement ID: your G- ID (or reference your Google tag).
2. Event name: generate_lead for enquiry forms. Keep newsletter sign-ups and job applications as separate events (sign_up, job_application), or a careers form will inflate your lead count.
3. Event parameters: form_name = {{DLV - form_name}}, form_location = {{DLV - form_location}}, plus value and currency = INR if you assign lead values.
4. Trigger: the success trigger from whichever method you chose. One trigger per tag; do not attach both a thank-you page trigger and a visibility trigger "to be safe", which double counts.
5. Register form_name and form_location as event-scoped custom dimensions in GA4 Admin so they appear in reports.
6. If you also fire a Google Ads conversion or Meta Pixel Lead, attach them to the same trigger so all platforms count the same moment. For Meta's browser and server events, see the Conversions API guide.

How do you pass UTMs into the form with GTM?

GA4 knows the campaign behind a session; your CRM only knows it if the form sends it. Add hidden inputs named utm_source, utm_medium, utm_campaign, utm_content and gclid to the form, then fill them with a Custom HTML tag. This version stores the values in a 90-day cookie on landing so they survive page changes:

<script>
// GTM Custom HTML tag, trigger: DOM Ready. Fills hidden fields named utm_source, utm_medium, utm_campaign, gclid
(function () {
  var p = new URLSearchParams(location.search);
  ['utm_source','utm_medium','utm_campaign','utm_content','gclid'].forEach(function (k) {
    var fromUrl = p.get(k);
    var fromCookie = (document.cookie.match('(?:^|; )' + k + '=([^;]*)') || [])[1];
    var v = fromUrl || (fromCookie ? decodeURIComponent(fromCookie) : '');
    if (fromUrl) document.cookie = k + '=' + encodeURIComponent(fromUrl) + ';path=/;max-age=7776000;SameSite=Lax';
    document.querySelectorAll('input[name="' + k + '"]').forEach(function (el) {
      if (v) el.value = v;
    });
  });
})();
</script>

Map each hidden field to a CRM property, and use clean campaign values from a shared convention; our UTM parameters guide has the naming rules. For write-once first-touch fields and deal-level reporting, use the fuller approach in CRM revenue attribution setup.

How do you test form tracking before publishing?

Open GTM Preview (Tag Assistant) and GA4 DebugView, then run every case below. Each row should give exactly the result in the last column.

Publish with a version name such as "Form tracking v2: form_success data layer, CF7 listener", then compare GA4 generate_lead counts with real form entries for the next week. A small gap is normal because some visitors block analytics or decline consent. We investigate whenever GA4 shows more than 10% fewer leads than the form tool, because that usually means a form or path is not covered; the lead tracking audit checklist is the place to start.

Sources

• Tag Manager Help: Form submission trigger (Check Validation, Wait for Tags, built-in form variables)
• Tag Manager Help: Element visibility trigger (selection method, firing options, Observe DOM changes, 50% default)
• Google Tag Platform: The data layer (initialisation, event key, never overwrite)
• Google Analytics Help: Enhanced measurement events (form_start, form_submit and parameters)
• Contact Form 7: DOM events (wpcf7mailsent and related events)
• Google Analytics Help: Avoid sending PII (no personal data in URLs or event parameters)