Study first
Review the ideas behind the questions
Check form tracking in GTM before treating a submit event as ready. Focus on the form submission trigger, validation, wait behavior, trigger scope, form variables, and preview testing.
Use The Form Trigger For Real Form Sends
A form submit tag needs a trigger that matches the form behavior. GTM's form submission trigger is designed for forms, but its options matter.
- The form submission trigger fires a tag when a form has been sent.
- Check Validation makes the trigger fire only when the form is successfully sent.
- Without Check Validation, the trigger fires whenever a user attempts to submit the form.
In Practice
Match the trigger to the form outcome
If the business only wants successful leads, configure the form trigger so failed validation does not count.
Do not count every attempt as a lead
A form attempt can happen even when validation fails, so the trigger settings need to match the reporting goal.
Common mistakes
Counting invalid submit attempts as completed leads.
Use Check Validation when the tag should fire only after a successful form send.
Q&A
Which trigger is made for form sends?
Use the form submission trigger when a tag should fire after a form is sent.
Why use Check Validation?
Use it when the tag should fire only for a successfully sent form.
Give Tags Time And Keep Scope Narrow
Form submits can move a user to another page quickly. GTM has settings and best practices that reduce missed tags and overbroad triggers.
- Wait for Tags can delay the form submission until dependent tags fire or the timeout passes.
- If Wait for Tags is not selected, slow tags may not fire before the next page loads.
- For best performance, specify conditions where the form submission is expected to happen.
In Practice
Use a timeout-aware delay
Wait for Tags is not an endless pause. It waits until dependent tags fire or the configured timeout is reached.
Prefer Some Forms conditions
A form trigger should usually be scoped to the tested form page instead of listening across the whole site.
Common mistakes
Using an all-site form trigger for one tested lead form.
Limit the form trigger to the tested page or form conditions where the submit should happen.
Q&A
What does Wait for Tags protect against?
It helps reduce the risk that slow dependent tags miss the submit before the next page loads.
Why scope a form trigger to tested pages?
Narrow scope reduces unexpected firing and keeps form tracking tied to pages where the behavior was tested.
Test Forms Before Publishing
Form and link triggers can be affected by site scripts and browser behavior. Preview testing is part of deciding whether the trigger is ready.
- Form and link triggers should be tested with preview mode before publishing.
- Another script can interrupt a form or link trigger before GTM reaches it.
- When a form trigger fires, GTM populates form-related built-in variables such as the form ID detail (Form ID).
In Practice
Inspect variables in preview
Preview checks should confirm both tag firing and form details, such as the form ID detail (Form ID), if the trigger relies on them.
Test required browser support
If the product must support older browsers, test form behavior there before deployment.
Common mistakes
Calling the form tag ready after checking only one happy path.
Use preview mode to test the form and confirm the tag fires properly and form data is sent properly.
Q&A
Why can form trigger checks fail even when the setup looks right?
Another site script can interrupt the form process before GTM reaches the trigger.
What should preview mode confirm for a form tag?
Confirm that the tag fires properly and that the expected form data is sent properly.