Say Google Ads shows 30 conversions a month, but only 10 enquiries reach your inbox. A common reason is that the conversion is recorded when someone clicks the button, not when the enquiry actually arrives. Below are four steps to track form submissions with Tag Manager so that GA4 and Google Ads count only the enquiries that went through.
In short
Track success
The conversion is recorded after a successful submission, not when someone clicks the button.
Pick the trigger to match the form
The right trigger depends on what the form does after it is sent. The options are a thank-you page, the form submission trigger and a dataLayer event.
Test with a real submission
Check in Preview, GA4 and Google Ads that one enquiry gives you one conversion.
What counts as a conversion for a form?
For an enquiry form, the conversion is the moment the enquiry has actually arrived. The data has been sent and the visitor sees a thank-you message or a thank-you page. A button click is not enough. If a required field is left empty or the email address is invalid, the visitor still clicks the button, but no enquiry comes in.
I track only the actions that actually succeeded, not as many events as possible. So before I open Tag Manager, I think through what a successful enquiry is on that page and what result the ads should bring in. If the page has several forms, such as a contact form and a newsletter sign-up, decide straight away which one is the enquiry. How GA4, Tag Manager and Google Ads share data is covered in more detail in how GA4, Google Tag Manager and Google Ads work together.
1. See what the form does after it is sent
In Tag Manager, the trigger tells a tag when to fire. The right trigger depends on what happens after the button is clicked. Send the form yourself and see which of these happens:
- a new page opens, such as
/thank-you/, which means you have a thank-you page; - a message such as “Thank you, your message has been sent” appears on the same page and the address does not change, which means the form sends the data in the background.
In the second case, also check in Tag Manager’s Preview mode whether the form plugin pushes its own event to the dataLayer after a successful submission. If it does, you already have the most reliable option.
2. Choose the trigger
Thank-you page
The simplest option is a Page View trigger that fires only on the thank-you page URL. It works only if nobody can reach the thank-you page any other way: the page is not in the menu, no links point to it and it cannot be found in Google Search. Otherwise a conversion is also recorded when someone opens the thank-you page directly or reloads it.
Message on the same page
Tag Manager’s Form Submission trigger reacts when the browser submits the form in the standard way. It has two settings worth using. With Check Validation switched on, the trigger fires only if the form was submitted successfully. Otherwise it fires on every attempt. With Wait for Tags switched on, the browser waits to open the next page until the tags have fired or the timeout runs out. That way a slow tag is not cut off.
In the trigger settings, choose Some Forms and limit the trigger to one form, for example by Form ID. That way you do not count a newsletter sign-up as an enquiry. Many forms, however, send the data in the background and the browser never submits the form in the standard way. For a form like that you need a custom event.
dataLayer event
The most reliable option is when the form itself reports that the enquiry went through. To do that, the form plugin or code added by a developer pushes an event to the dataLayer (the layer that passes data from the page to Tag Manager). The event needs an event key, because that is what Tag Manager uses to fire a trigger:
window.dataLayer = window.dataLayer || [];
dataLayer.push({'event': 'form_success', 'form_name': 'contact'});
In Tag Manager, create a Custom Event trigger whose Event name is exactly form_success. Do not use the pattern .* in the event name, because the trigger would then also fire on all of Tag Manager’s own events.
I prefer an event that does not depend on the page’s HTML structure, because then a design change does not break the tracking. If the form does not send such an event itself, I write the developer a short requirement: when to send the event, what to call it and what data to include.
Is GA4’s automatic form event enough?
GA4 Enhanced measurement has a Form interactions option. It collects a form_start event when someone starts filling in a form and a form_submit event when they submit it. The form ID, name and submit button text come with it, but you only see them in reports once you create custom dimensions for them.
For an enquiry conversion, your own event is usually the better choice. GA4 cannot tell by itself which form is the enquiry for you. If you still want to use the automatic event, test first whether it fires only on a successful submission.
3. Send the enquiry to GA4 and Google Ads
Once you have the trigger, create two tags: a GA4 event and a Google Ads conversion. If both use the same trigger, both systems record the same moment.
GA4: event and key event
Create a GA4 event tag (Google Analytics: GA4 Event) and name the event generate_lead. This is Google’s recommended event for an enquiry. If you add a value, you also need to add the currency, for example EUR.
Then mark the event as a key event in GA4: open Admin → Events → Recent events and click the star next to the event. The change applies from then on and does not alter historical data. It can take up to 24 hours to show up in standard reports. For counting, Google recommends the default Once per event option. Analytics Mania prefers Once per session for forms, so that repeat submissions do not inflate the numbers, but Google labels that option as Legacy.
Google Ads: conversion action and tag
In Google Ads, create a website conversion action for the enquiry. In Tag Manager, create a Google Ads Conversion Tracking tag and add the Conversion ID and Conversion Label. The ID is the same across the account, while each conversion action has its own Conversion Label. If you leave the value empty, Tag Manager sends 0 as the value.
For an enquiry, the sensible Count setting is One. That way one ad click gives you one conversion, even if the visitor submits the form twice. Every suits sales, where each purchase brings in money. Also check that the Google tag or the Conversion Linker fires on every page in Tag Manager. It stores the ad click details that Google Ads uses to match the enquiry to the right click.
When I set up a conversion, I always think about what Google Ads will do with that data. If the campaign uses automated bidding, Google learns from exactly this conversion, so it has to be a real enquiry. There is more on this in when to trust Smart Bidding.
One enquiry, one conversion
Google Ads can also get the enquiry through GA4 if you import the key event. Pick one route. If both the conversion imported from GA4 and the Google Ads tag are primary conversions, Google Ads counts the same enquiry twice.
I look for double counting in Preview mode, in the browser’s network requests and in plugins, and keep one verified data stream. One client had changed ad managers and removed the Site Kit plugin from WordPress, but the previous manager’s Google Ads code was still on the site. That is why I check Tag Manager, the plugins and the page code.
4. Test with a real submission
Publish your Tag Manager changes only after testing. Preview mode opens your site with Tag Assistant, where you can see which tags fired and in what order, and why a tag fired or did not.
- In Tag Manager, click Preview, enter your site’s URL and click Connect.
- Send the form with an error, for example leave a required field empty. No conversion tag should fire.
- Send the form correctly. Tag Assistant should show your event with both tags under it, each firing once.
- Check in GA4 DebugView that
generate_leadarrived. - Check that the enquiry also reached the inbox. A conversion without an enquiry means something is being counted wrongly.
- After a few days, check in Google Ads that the conversion action status is fine and the enquiries appear in the conversions column.
I always test with a real form submission and check exactly when the trigger and the conversion tag fire. If something does not arrive, I do not start from the GA4 report. I start where the event happens and work forward step by step until I see where the data gets lost.
Test both with and without consent. If someone declines cookies, Google’s tags send data differently and GA4 shows fewer enquiries than you actually received. To see how consent changes tracking, read Cookie Consent and Consent Mode.
Practical tip
Before testing, tell whoever receives the form enquiries that a test message is coming, and write “TEST” in the message. That way nobody replies to the test enquiry, and later it is easy to tell test enquiries apart from real ones.
Where to start
Send your form once and see what happens after the button is clicked, because that decides which trigger you choose. If you want to review your whole GA4 and Tag Manager setup, use the GA4 and GTM checklist. If you would like someone to review the conversions, tags and page together, see how conversion tracking setup works and what the Google Tag Manager service includes.
Sources
- Google Analytics Help: Enhanced measurement events
- Tag Manager Help: Form submission trigger
- Tag Manager Help: Custom event trigger
- Google Tag Platform: The data layer
- Google Analytics: Recommended events (generate_lead)
- Google Analytics Help: Mark events as key events
- Google Analytics Help: Change the counting method
- Tag Manager Help: Google Ads conversions
- Google Ads Help: About conversion counting options
- Tag Manager Help: Conversion linker
- Tag Manager Help: Preview and debug containers
- Analytics Mania: Track Key Events with Google Analytics 4
Facts checked against official documentation on 18 November 2026.
Richard Pikmets