How to Track Form Submissions From Google Ads

A Google Ads campaign can generate clicks without generating useful leads. To tell the difference, you need reliable conversion tracking: a way to record when someone submits a form after interacting with an ad, then connect that submission to the campaign, ad group, and keyword that helped produce it.

That sounds simple, but form tracking often breaks when a website changes, a thank-you page is removed, or a tag fires on a button click instead of a completed submission. This guide explains how to set up form tracking with Google Tag Manager (GTM), Google Analytics 4 (GA4), and Google Ads, how to test it, and how to choose a specialist if you need help.

Start with the conversion you actually want to measure

Before adding tags, define what counts as a lead. A completed quote request, consultation booking, or contact form may be a primary conversion. A phone-number click, brochure download, or form start is usually a secondary action: useful for diagnosing the funnel, but not equivalent to a qualified lead.

Write down the conversion definition and where it happens. For example: “Count one lead when a visitor submits the consultation form and sees the confirmation page.” This gives you a clear basis for implementation and testing. It also helps prevent an inflated conversion count when one person submits twice or a tag fires before the form is accepted.

Choose a form-tracking method

There are two common approaches. A thank you page is often the simplest option: after a successful submission, the site sends the visitor to a distinct confirmation URL. Alternatively, GTM can detect a successful form submission on the same page, which is useful for forms that confirm success without reloading the page.

Method Best suited to Watch out for Thank-you page view Forms that redirect to a unique confirmation URL Page refreshes, repeat visits, or other routes to the same URL can cause duplicate counts GTM form trigger Forms that submit successfully without a page change Some form plugins prevent GTM’s built-in listener from detecting the submission Data layer event Custom websites and AJAX forms with developer support The event must fire only after the server confirms success

Whenever possible, track a confirmed success—not merely a click on the submit button. A person can click “Send” and still get a validation error, lose their connection, or fail to complete the form.

Set up a thank-you page conversion

Create or confirm the page. Use a distinct URL, such as /contact/thank-you/. The page should appear only after a successful submission, not when someone clicks a link or loads the form.
Install and verify your tags. Make sure the Google tag and Google Tag Manager container load on the relevant pages. Use Tag Assistant and your browser’s developer tools to check for missing or duplicated installations.
Create a GA4 event. In GTM, create a GA4 event tag with an event name such as generate_lead. Add a trigger for the thank-you page, commonly using a Page View trigger with a condition that matches the page path.
Test the event. Submit the form in a test session and confirm the GA4 event appears in DebugView or Realtime. Check that it does not fire on the form page or on unrelated pages.
Mark the event as a key event. In GA4, mark the lead event as a key event so you can report on it consistently. GA4 labels have changed over time, so check the current property interface.
Import or create the Google Ads conversion. You can import the GA4 key event into Google Ads, or create a Google Ads website conversion action directly. Choose one primary method for bidding and reporting to avoid counting the same lead twice.

A thank-you URL is not automatically a perfect conversion signal. If the page is publicly accessible, a visitor may load it directly. If users can return to it by refreshing, the event may fire again. Consider whether that behavior is likely to materially distort your data, and use a more controlled success event or deduplication logic if needed.

Use a GTM form trigger for on-page forms

For an embedded or AJAX form, a GTM form trigger can detect a submission without sending the visitor to a new page. In Google Tag Manager, enable the built-in form variables, create a Form Submission trigger, and restrict it to the correct form using reliable conditions such as a form ID or a specific page path.

Do not assume that the trigger’s default “Wait for Tags” or “Check Validation” settings will work for every form. Test the actual form. Many modern forms use JavaScript, iframes, or custom validation, so GTM’s built-in listener may detect a click but miss the successful submission—or fail to detect it at all.

When the built-in trigger is unreliable

Ask a developer to push a data layer event after the form is accepted by the site. For example, the site can push an event named form_success only after its server confirms the submission. GTM can then use a Custom Event trigger for that event and fire the GA4 event tag.

This is usually more dependable than tracking a button click. If the form sends personal information, do not pass names, email addresses, phone numbers, or other personally identifiable information into GA4 or Google Ads event parameters. Keep event data limited to what you need, such as the form type or a non-sensitive form ID.

Connect GA4 and Google Ads carefully

There are two practical ways to report a lead in Google Ads: import the GA4 key event, or send a Google Ads conversion tag from GTM. Either can work. Choose based on your reporting needs and implementation, then avoid making both versions google cache primary for the same action. Otherwise, a single submission may be counted twice in bidding or campaign reports.

When setting up the conversion action, check its counting setting. For lead generation, “One” is often the sensible choice because several submissions from one ad interaction should not necessarily be treated as several new leads. The right choice depends on your sales process, so document the reason for it.

Also verify that auto-tagging is enabled in Google Ads and that your site preserves the Google click identifier through redirects. Consent settings, browser restrictions, cross-domain forms, and slow tag loading can affect what is observed. Conversion modeling may help fill some gaps, but it is not a substitute for testing a working implementation.

Test before you trust the numbers

Do not judge a tracking setup by a screenshot that has no date, property, or test context. Run a fresh test and keep a record of what you checked. Use GTM Preview, Tag Assistant, GA4 DebugView, and Google Ads’ conversion diagnostics where available.

Submit each important form on desktop and mobile.
Confirm the event fires only after a successful submission.
Check that it fires once, not on button clicks, errors, or page refreshes.
Confirm the event name and parameters in GA4.
Check that the right Google Ads conversion action is receiving data.
Record the test date, URL, browser, and expected result.

Google Ads conversion reporting can take time to populate, and GA4 and Ads may use different attribution and reporting rules. A difference between their totals does not automatically mean tracking is broken. First confirm that the event fires correctly, then compare equivalent date ranges and conversion definitions.

What a 410 Gone error means for marketing resources

While auditing conversion tracking, you may find that an old setup guide, campaign landing page, or agency resource no longer exists. A server response of 410 Gone means the resource has been intentionally removed and is not expected to return. A 404 Not Found means the server cannot find the requested page; it does not, by itself, say whether the page is permanently gone.

Status code Meaning Typical SEO consideration 410 Gone The resource has been deliberately and permanently removed Can signal that a URL should be removed from search results; use only when there is no suitable replacement 404 Not Found The requested resource is not currently found May be temporary or permanent; fix accidental errors, and redirect only when a genuinely relevant replacement exists 301 Redirect The resource has moved permanently Appropriate when a close, useful replacement exists

Neither a 410 nor a 404 automatically causes a broad SEO penalty. Search engines can remove unavailable URLs over time. The practical impact depends on what the page did: an old campaign landing page receiving valuable links deserves more attention than a forgotten test URL.

How to replace a dead marketing resource

Check the URL and its history. Confirm it is not a temporary outage, typo, or deployment issue. Review server logs and analytics if available.
Find the closest useful replacement. If an updated guide covers the same need, redirect the old URL to it with a 301. Do not redirect every removed URL to the homepage; that can confuse visitors and search engines.
Use 410 when there is no replacement. If the resource is intentionally retired and nothing comparable exists, a 410 can communicate that clearly. Update internal links, ads, and email campaigns so they no longer point to it.
Check the server response. On a site running Apache, review the relevant configuration and redirect rules. On Ubuntu, check the web server and application configuration used by the site. Make changes carefully, then verify the final response code and destination with a browser or HTTP status checker.
Update measurement. If the deleted page was part of a campaign funnel, confirm that ads and conversion triggers still point to live pages and that the replacement does not inflate conversions.

A dead tracking tutorial can also create bad implementations. For example, a dated guide may recommend measuring a form button click rather than a successful submission. When replacing a resource, update the instructions and the conversion definition—not just the URL.

How to evaluate Google Ads specialists and agencies

Tracking quality is a useful test of an agency’s working standards. Ask prospective specialists to explain how they would measure your actual lead outcome, how they would test it, and what they would do if your form does not redirect. A credible answer should be specific to your site and sales process, not a promise to “optimize everything.”

Ask for a measurement plan. It should identify primary and secondary conversions, the event source, deduplication approach, and testing steps.
Ask what changed last week? Before anyone makes changes, they should review recent campaign, website, and tracking changes. Sudden performance shifts often follow a concrete change.
Request dated evidence. Reports should name the account or property, date range, conversion action, and test context. A screenshot without those details is not enough to verify an implementation.
Clarify access and ownership. Your business should retain ownership of its Google Ads account, GA4 property, GTM container, and conversion data.
Get clear pricing and scope. Ask what setup, testing, reporting, and ongoing work are included, and what costs extra. Avoid vague claims about guaranteed leads or results that cannot be controlled.
Check how they handle privacy. They should know not to send form submissions’ sensitive personal details into analytics tools and should account for your consent requirements.

Marketing91, like any marketing publisher or resource, can be one place to encounter marketing guidance. Treat any article as a starting point rather than proof that a setup is correct. Platform interfaces and privacy requirements change; verify advice against your current Google Ads, GA4, and GTM configuration, and test it on your own site.

Keep a conversion-tracking checklist

Before launching a campaign—or after a major website change—run through this short checklist:

Define the lead action that matters to the business.
Choose a thank-you page, GTM form trigger, or confirmed data layer event.
Verify the GA4 event fires once, only after success.
Choose one primary Google Ads conversion source for bidding.
Check consent, redirects, cross-domain behavior, and click-ID preservation.
Test with dated evidence and document what changed.
Fix dead landing pages and resources with an appropriate 301, 404, or 410.

Accurate form tracking is not just a tag-management task. It is a shared definition of what counts as a lead, a tested path from form success to reporting, and a regular check that changes to the website have not broken the signal. Get those basics right, and Google Ads decisions become much more useful than optimizing toward clicks alone.