Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Analytics › Troubleshooting

GA4 Not Tracking Form Submissions

Why leads reach the inbox or CRM while analytics records fewer form submissions: triggers that never fire, embedded forms, missing pushes, consent, key events.
Troubleshootingintermediate11 min readUpdated

First, count real submissions per form against GA4 for the same days

Choose a few recent closed days and list every form with its genuine submissions, taken from where they land: the shared inbox, the form tool's log or the CRM, with tests and spam removed. Then count the lead event in GA4 for the same days by the form name parameter that the form tracking tutorial sets up through Tag Manager (GTM), or by page if no such parameter exists yet, and line the lists up form by form.

The shape of the result narrows the search before any debugging. A form with submissions and no events at all points at the trigger, the frame or the thank-you page. A form with events well short of its submissions points at timing or consent. Every form short by a similar share, steady over time, usually means consent and blockers, which is expected. Events present in DebugView but absent from the key events report point at the key event mark or a filter. More leads in GA4 than in the CRM is the opposite fault, attempts counted as submissions, which belongs to the form tracking tutorial. If the event reaches GA4 but Google Ads shows no conversions, see Google Ads conversions not tracking; sending CRM outcomes back to the platforms is covered by connecting the CRM to ads and analytics. Other measurement symptoms are routed from the analytics troubleshooting collection.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
A form with submissions and no lead events; the message appears without leaving the pagePreview mode while submitting: does a form submission event appear in the timeline?A form submission trigger the form never raises, because the form sends by scriptPush a success event from the form's callback and trigger on it
No events from one form; the form loads from another domain or sends people elsewhereWhether the form sits in a frame from another domain or on a hosted pageThe form sits in a third-party frame or on a hosted pageUse the vendor's documented messages or a return page you control
Lead events missing, unnamed or short for one form after a releaseThe data layer view in preview after a successful submissionThe success push is missing, renamed or arrives at the wrong momentRestore the agreed push, keys and timing from the contract
The tag shows as not fired or held under some consent statesThe tag's consent settings, blocking triggers and the Consent tab in previewConsent state or a trigger exception blocks the tagCorrect the consent requirement or the exception; document the declined share
Lead counted from page views of the thank-you page, but none from some formsWhether the thank-you page carries the container and sits on the site's own domainThe thank-you page is reached without the tag or on another sitePut the tag on that template or return people to a page that has it
The event appears in DebugView but not in the key events report or the lead countThe key event list, the event name's spelling and active data filtersThe event arrives but is not marked as a key event or is filtered outMark the right event, fix the name, check each filter

Fix, verify and prevent each cause

A trigger the form never raises

The built-in form submission trigger listens for the browser's own submit. The form tracking tutorial explains why that misses many modern forms: a form submitted by script sends its data in the background and shows a message without leaving the page, so it may never produce the event the trigger is waiting for.

Fix: agree a data layer push with the developers, sent from the form's success callback only after the server accepts the submission, and fire the lead tag from a custom event trigger listening for it, as that tutorial builds. Remove the old form or click trigger in the same workspace so nothing counts twice.

Verify: in preview, a successful submission shows the custom event and the tag firing once; an invalid submission shows neither.

Prevent: record how each form submits in the form inventory, and make the success push part of the definition of done for any new form.

A form in a frame or on a hosted page

A form embedded from another service in a frame runs in the vendor's page, so your container cannot see the submit, the fields or the confirmation, and a form hosted on the vendor's domain is further away still. The guide to embedded widgets and hosted pages sets out what each situation allows.

Fix: where the vendor documents messages its widget posts to the parent page on completion, turn the documented message into a data layer push with a listener; otherwise set the tool's return or confirmation address to a page you control that pushes the lead once, or confirm the lead from your own systems. Use only what the vendor documents.

Verify: a test submission through the embedded form produces one lead event with the right form name.

Prevent: add every embedded and hosted form to the inventory with its chosen method, and re-test when the vendor changes its widget or the site changes vendor.

A success push that is missing, renamed or late

A redesign that drops the push, a renamed generate_lead or form name key, or a page that navigates away the instant it pushes all break the count without breaking the form. The data layer guide owns push timing and the contract, including the eventCallback and eventTimeout options that let tags send before the browser leaves; the undefined data layer variable page diagnoses keys that arrive late or under the wrong name.

Fix: restore the push as the contract describes it, with the exact event name and keys, and have the page wait for the callback before navigating.

Verify: the data layer view in preview mode shows the push after a successful submission with every key populated, and the tag reads the values.

Prevent: keep the push in the written contract, and include it in the release test of any template that holds a form.

Under Consent Mode, Google's tags read the consent state and adjust, and other tags can be held until specific consent types are granted, as the consent mode guide explains. A lead tag given a consent requirement it should not have, an update that never reaches the tags after acceptance, or a blocking trigger meant for internal traffic that matches real visitors all keep the tag from sending. The tag not firing page covers blocking triggers and consent checks in general.

Fix: set the tag's consent requirement to match the policy, confirm the consent update reaches the container after acceptance, and narrow any exception to what it was meant to block. For visitors who declined, change nothing: the gap is the choice working.

Verify: in preview, the Consent tab shows the expected state and the tag fires after acceptance; with consent refused it behaves as the policy intends.

Prevent: test one submission per consent state whenever the banner or its configuration changes, and note the change date.

A thank-you page without the tag

Some setups count a lead when the thank-you page loads, which fails when that page uses a template without the container, comes from a different system or sits on another site. The GA4 setup tutorial asks for the tag on every template, including pages served from a different system, because otherwise visitors seem to vanish.

Fix: put the container on the thank-you template, or send people back to a confirmation page on your own domain that carries it; if the page sits on another domain you control, set up cross-domain measurement as the setup tutorial describes. Where possible, replace the page view rule with a success push, because a reloaded or bookmarked thank-you page counts again.

Verify: a test submission lands on a page where preview shows the container loaded and the lead tag fired once.

Prevent: include thank-you and confirmation templates in the list of templates checked for the tag after every release.

An event that arrives but is not counted

An event can reach the property and still be missing from the count. If the lead event is not marked as a Key Event, it does not appear among key events, and the key events guide explains that marking applies going forward only. A mark on an old event name after the site renamed the event, a spelling difference in case, or an active internal or developer traffic filter catching real submissions all have the same effect. The events and parameters guide covers names and why unregistered parameters never reach reports, which is why a lead count by form name can be blank while the total is right.

Fix: mark the event the site actually sends, register the form name parameter, and check each active filter against how the leads were submitted.

Verify: a test submission from outside filtered traffic appears in the key events report after processing.

Prevent: keep the key event list and the filters in the measurement documentation, and record the date of every change.

A prevention routine: a test submission per form in every release

Form tracking breaks quietly: enquiries keep arriving while the count in GA4 drifts down. The defence is a short test on every release that touches a template, a form, the container or the consent banner.

TestWhat a pass looks likeOwner
A successful submission on each formOne lead event, with the correct form name, in preview and DebugViewWhoever publishes the release
An invalid submission on each formNo lead event; validation errors recorded if the site tracks themWhoever publishes the release
A submission with consent refusedThe tag behaves as the policy intendsThe consent owner
A submission through each embedded or hosted formOne lead from the documented message or return pageThe form's owner
A closed day reconciled against the inbox or CRMEach form's gap within its usual rangeThe analyst

Keep the form inventory as the test list: every form, how it submits, where it lives, the push it sends and its owner. A new form joins the inventory before it goes live, and the lead routing QA checklist checks the other half of the journey, where the enquiry goes once it leaves the form. Once a month, compare each form's submissions with its lead events for the closed month and read the ratio against the form's own history; a form that leaves its usual range, or moves on a release date, starts the per-form count above. Read form starts against completions with the conversion rate calculator only once the completion count is trustworthy, because a Form Abandonment Rate built on missing submissions blames the form for a tracking fault. Where the enquiries themselves are missing from the inbox or the record system, the fault lies upstream of the count, and the diagnosis of website form submissions not arriving traces where each submission stopped.

Failed submissions deserve their own events, because a form that rejects valid enquiries looks like broken tracking in the lead count. The tutorial on tracking errors and failed actions records failures as events with owners, and the form abandonment guide and the forms guide take over once the numbers are right and the question becomes why people leave.

A roofing contractor finds its missing enquiries (illustrative)

Illustrative example — not a real result

Glumtrey Roofing counts its quote requests

Glumtrey Roofing, an invented roofing contractor, receives quote requests by email from 3 forms while GA4 records leads from only 1. Over 5 closed days the inbox holds 42 genuine requests: 19 from the quote form, 14 from the survey booking form and 9 from the callback form, against 8 leads in GA4, all from the callback form. In preview, the quote form shows its thank-you message but no form submission event, because it sends by script; the developers add a generate_lead push to its success callback and remove the old trigger. The survey booking form is embedded from a scheduling tool in a frame, so the team sets the tool's documented return page to a confirmation page on its own site that pushes the lead once. Over the next 5 closed days the inbox holds 39 requests and GA4 shows 34 leads spread evenly across all 3 forms, which the team records as its consent and blocker baseline.

Common mistakes

  • Counting the site, not the forms. A total hides one form recording nothing behind others that work.
  • Trusting the form submission trigger on every form. Forms that send by script never raise it.
  • Debugging the container for a form it cannot see. A form in a vendor's frame needs the vendor's method.
  • Renaming the push without telling the container. The form still works and the count quietly stops.
  • Treating the consent gap as a fault. Declined visitors are meant to be missing; document the share.
  • Marking the event and forgetting the date. A mark applies going forward, so earlier days stay uncounted.
  • Testing only the happy path. An invalid submission that counts as a lead is the opposite fault.

Frequently asked questions

Why does the form submission trigger in Tag Manager never fire on my form?

Usually because the form never performs the browser's own submit. Many forms send their data by script and show a thank-you message without leaving the page, so the event the form submission trigger listens for never happens. The reliable fix is a data layer push from the form's success callback, sent only after the server has accepted the submission, with a custom event trigger listening for it.

Should GA4 show exactly as many leads as the CRM?

No. Visitors who declined analytics, browsers that block tags and enquiries made by phone or email never reach the property, so some gap is expected. What matters is the pattern: a gap spread evenly across forms and steady over time is collection working as designed, while one form far short of its own submissions, or a gap that opens on a release date, is a fault to fix.

Can I rely on enhanced measurement's form interactions instead of building a lead event?

As a first look only. The setup tutorial notes that the form interactions option fires on forms the tag can detect, including newsletter boxes and search fields, and it cannot know whether the server accepted the submission. Sites with a proper lead event usually switch that option off so two different definitions of a submission do not sit side by side in the reports.

Terms used on this page

Tools to try

Where this page is used

Also related

Sources

  1. The data layer — Google Tag Platform
  2. Preview and debug containers — Google Tag Manager Help
  3. [GA4] About events — Google Analytics Help
  4. Consent mode — Google Tag Platform

Related