Form Tracking Setup
Form tracking, that counts real leads.
We set up your forms so every real submission fires a trackable event, and spam or test submissions do not quietly inflate your numbers.
- We quote this free, usually within one business day
- Tuned to your actual form, not a generic template
- Backed by the standard 30 day guarantee
What we set up
The pieces that make a submission countable.
Trigger setup in GTM
We build a form submission trigger in Google Tag Manager, using the built in listener where it works, or a thank you page trigger where the form needs it.
Validation and wait settings
We turn on wait for tags and check validation so we only fire the tracking event after the form actually accepted the submission, not on every click of the button.
Spam filtering
We add basic filtering, like a honeypot field or a minimum time on page check, so bot submissions do not get counted as leads.
Event push to GA4 and Ads
We push a clean event to GA4 and connect it to a Google Ads conversion action, so form fills show up next to your other conversion data.
The access this needs, and the test that proves a lead counted.
Access we need
Access to edit Google Tag Manager, or your website's code directly, plus a working copy of the form to test against without disturbing your real lead inbox.
What is delivered
A working trigger and tag pair, a note on which spam filters were added, and confirmation the event reaches GA4 and Google Ads.
The acceptance test
We submit a real test entry and confirm exactly one event fires, appears correctly in GA4 debug view, and does not fire twice if the visitor double clicks submit.
Out of scope
We do not redesign your form fields or rewrite your form's validation logic. This project tracks the form as it exists, it does not rebuild it.
How the setup runs.
01
Test the current form
We submit the form a few times to see exactly how it behaves, what the thank you state looks like, and where a trigger can safely attach.
02
Build and filter
We build the trigger and tag, then add spam and duplicate filtering so the count reflects real leads.
03
Verify in debug view
We confirm the event fires correctly in GA4 debug view and in the Google Ads conversion report before signing off.
Form tracking, answered.
That is common with forms built in React or a similar framework. We use the built in form submission listener in Google Tag Manager, which does not depend on a page reload to detect the event.
We can reduce them with a honeypot field or a minimum time on page rule, but no filter catches every bot. The goal is a meaningfully cleaner number, not a perfect one.
No, part of the setup is making sure the tracking event only fires once per successful submission, even if the button gets clicked more than once.
Not as part of this setup. Tracking who starts a form but never finishes it is a separate, more involved build, since it usually needs field level event tracking rather than one submission event.
A redesign can break the trigger if the form's structure or class names change. We recommend a quick recheck any time the form is rebuilt, which we can scope separately.
Make sure every real lead actually gets counted.
Share a link to your form and we will map out the tracking, with a free quote in your inbox within one business day.