Form Submission Tracking

We begin by listing every form on your site: its URL, purpose, platform (Impreza forms, Contact Form 7, Gravity Forms, WPForms, HubSpot, Typeform, embedded iframe, or custom code), what happens after submission, and who receives the data. We then decide what counts as a conversion. A contact form submission is usually a lead; a newsletter sign-up may be a secondary goal; a failed submission is an error, not a conversion. Next we choose the detection method for each form. The most reliable is a dedicated thank-you page with a unique URL, since a pageview there confirms success. If the form shows an inline message, we look for a data layer push, a custom event fired by the form plugin on success, or a visible success element. Many plugins offer events we can listen to in Google Tag Manager. For third-party and iframe forms, we use the provider’s own events or a postMessage listener where available. We avoid generic form-submit triggers unless tests show they match real success. In Google Tag Manager, we create triggers, variables for form ID, page URL and form name, and a GA4 event tag with a clear name such as generate_lead, plus parameters for form type and page. In GA4, we mark the event as a key event. For paid campaigns, we import or create the Google Ads conversion from the same signal so counts agree, considering enhanced conversions; see enhanced conversions implementation support. We add source parameters, such as UTM values and click IDs, into hidden form fields where the form allows it, so your CRM or email shows the origin of each lead; see CRM and lead source tracking and lead source attribution. We handle spam and duplicates by filtering known test submissions and using honeypot-friendly triggers. Before launch, we test every form in preview mode and in real usage: valid submit, invalid submit, repeated submit, mobile, different browsers and, where used, consent denied. We compare the number of tracked events with form entries over a week and investigate gaps. We document the setup in a short sheet showing each form, its trigger, event name and test date. Where websites use consent banners, tags fire according to the consent settings; see consent-aware analytics configuration. We cannot track forms hosted on sites we cannot access, and we cannot guarantee that every user is counted, since browser privacy settings and ad blockers may hide some events, but a tested setup gives you dependable numbers.