Skip to content
GA4

GA4 not tracking form submissions

Leads are landing in the inbox or CRM, but GA4 shows no form_submit or generate_lead events, or far fewer than the real number of submissions.

Steps checked against the platforms' documentation on November 20, 2026.

Quick answer

Most missing form data comes from relying on enhanced measurement or a generic GTM Form Submission trigger on a form that never fires a standard submit event, such as an AJAX form or one embedded in an iframe. Open GA4 DebugView, submit the form yourself, and see whether any event arrives. If nothing does, the tracking never fired; if the event arrives but reports stay empty, look at key event marking, consent and processing time.

1. The form never fires a standard submit event (AJAX forms with no page change)

Enhanced measurement form interactions and the GTM Form Submission trigger both listen for the browser's form submit. Many modern form plugins send the data in the background and swap in a thank-you message, so that submit event either never happens or happens before validation, and nothing reliable reaches GA4.

How to check

  1. 1Open GTM and click Preview, enter the page URL and click Connect.
  2. 2Fill in and submit the form, then look at the event list in Tag Assistant. If no Form Submit event appears (only clicks and the page view), the form does not use a standard submit.
  3. 3Submit the form with a required field empty. If an event still appears, the trigger is firing on attempts, not successful submissions.

How to fix

  1. 1Track the success state, not the submit attempt. Best option: have the form push a dataLayer event on success (for example form_success with a form name) and use a Custom Event trigger in GTM.
  2. 2If the plugin shows a thank-you message, an Element Visibility trigger on that message is a workable fallback. If it redirects to a thank-you page, trigger on that page path.
  3. 3Send a GA4 event with a clear name such as generate_lead, plus parameters like form_name, and confirm it in DebugView before publishing.
  4. 4Turn off the enhanced measurement form interactions option if you replace it, so you do not count the same lead twice.

2. You are relying on enhanced measurement form interactions

Enhanced measurement can send form_start and form_submit automatically, but it is a generic listener, not a lead tracker. The option may be switched off, and on forms that do not behave like a standard HTML form it can miss submissions or count attempts that failed validation.

How to check

  1. 1In GA4 go to Admin > Data streams, open the web stream and look under Enhanced measurement. Click the settings icon and see whether form interactions is enabled.
  2. 2Open Realtime, submit a test form and look at the Event count by event name card for form_submit.

How to fix

  1. 1Treat enhanced measurement form events as a rough signal only, and build a dedicated lead event for each form that matters (see the first cause).
  2. 2If you keep form_submit, register form_id or form_name as custom dimensions so you can tell forms apart in reports.

3. The form lives in an iframe or on a third-party domain

Embedded booking widgets, HubSpot or Typeform embeds, and scheduling tools often load inside an iframe from another domain. Tags on the parent page cannot see what happens inside that frame, so the submit is invisible to your GA4 tag.

How to check

  1. 1Right-click the form and inspect it. If it sits inside an iframe element whose src is another domain, the parent page tags cannot see it.
  2. 2In GTM Preview, submit the form and note that no form or click events appear for anything inside the frame.

How to fix

  1. 1Use the vendor's own GA4 or GTM integration if it has one, and confirm the event lands in the same GA4 property.
  2. 2If the vendor sends a message to the parent page on success, have a developer listen for it and push a dataLayer event that GTM can use.
  3. 3If the form redirects to a thank-you page on your own domain, track that page view as the lead event. If it moves the user between domains, set up cross-domain measurement so the session is not split.

4. The GTM trigger conditions no longer match the form

Triggers often filter on a Form ID, Form Classes or page path. When the form is rebuilt, moved or renamed, the condition stops matching and the tag silently stops firing.

How to check

  1. 1In GTM Preview, submit the form, click the form event in the left-hand list and open the Variables tab. Note the actual Form ID and Form Classes values.
  2. 2Compare them with the conditions on your trigger under This trigger fires on > Some Forms.
  3. 3Check that the GA4 event tag shows as fired on that event, not just the trigger event appearing.

How to fix

  1. 1Update the trigger conditions to match stable attributes, ideally a form ID or a dataLayer form name the developer agrees not to change.
  2. 2If you keep a Form Submission trigger, turn on Check Validation so it only fires when the form is sent successfully.

5. The event arrives but is not marked as a key event

GA4 only counts an event as a key event, and only lets you use it as a lead metric in reports and Google Ads, once it is marked. Teams often build the event correctly and then forget this step, or mark a differently named event.

How to check

  1. 1In GA4 go to Admin > Data display > Events and find the event name in Recent events.
  2. 2Check whether the star icon next to it is filled in.
  3. 3Confirm the exact spelling and case: generate_lead and Generate_Lead are different events.

How to fix

  1. 1Click the star to mark the event as a key event (Editor access or higher is needed).
  2. 2If the event has not fired yet, use + Create event or mark it once it appears. Standard properties allow up to 30 key events and Analytics 360 up to 50, so keep the list to real business outcomes.
  3. 3Judge the fix on data collected after you mark the event, not on earlier dates.

6. Consent settings or report timing hide the data

With consent mode, a visitor who denies analytics_storage either sends nothing (basic implementation) or sends cookieless pings (advanced implementation), so standard reports undercount. Separately, GA4 reports are not instant and can apply thresholding, which looks like missing data on low volumes.

How to check

  1. 1Test in a clean browser, accept analytics cookies on the banner and check DebugView. Then repeat after declining. Google notes events do not appear in DebugView when consent is denied.
  2. 2In GA4 go to Admin > Consent settings and select the data stream to see whether consent signals are being received.
  3. 3If the event shows in Realtime but not in standard reports, check the date range and the data quality indicator at the top of the report for a thresholding message.

How to fix

  1. 1Make sure the consent banner updates consent before or as the form is submitted, and that the lead tag is not blocked when the user has granted consent.
  2. 2Allow for processing time: Google says daily processing can take 24 to 48 hours, so do not judge a new setup from same-day standard reports.
  3. 3If thresholding applies, widen the date range and avoid demographic dimensions in the lead report.

Stop it happening again

  • Track each important form with a success-based event (a dataLayer push or thank-you page), not a generic submit listener.
  • Agree a short list of lead event names and parameters per client and keep it in a shared tracking plan.
  • Submit a test lead through every form after any site or plugin update, and check it in DebugView and the CRM.
  • Compare weekly GA4 lead counts with CRM or inbox counts, and investigate when the gap suddenly changes.

Questions

3 questions

Not for most lead-generation sites. It can send form_start and form_submit, but it is a generic listener that can miss AJAX and embedded forms or count failed attempts. Build a dedicated event that fires on a successful submission for every form that matters.

Standard reports need processing time, which Google says can take 24 to 48 hours. Also check that DebugView traffic is not being filtered out, that the event is marked as a key event if you are looking at key event reports, and whether thresholding is applied.

A dataLayer event pushed on success is the most reliable because it does not depend on page URLs or visible text. A thank-you page is a good second choice as long as it cannot be reached without submitting the form.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.