Skip to content

How to Set Up GA4 Form Conversion Tracking for Lead Forms

Step-by-step GA4 form conversion tracking for lead forms: send generate_lead via GTM or thank-you pages, test in DebugView and import into Google Ads.

By Devma Team · · 10 min read

A sunlit office desk with a laptop, coffee mug, sticky notes and a notepad showing a hand-drawn funnel diagram.

To set up GA4 form conversion tracking for lead forms, send a generate_lead event only when a form submits successfully (ideally through Google Tag Manager or a protected thank-you page), confirm it in DebugView, and then mark it as a key event. After that, link GA4 to Google Ads and import that key event so your campaigns bid toward real leads instead of pageviews or button clicks.

Key takeaways

  • GA4 now calls conversions "key events." The word "conversion" refers to Google Ads conversion actions, which are created from key events. Older guides that say "Mark as conversion" describe the same setting.
  • Enhanced measurement's form_submit event can fire on search boxes, newsletter widgets and cookie banners, so treat it as a diagnostic signal, not as your lead conversion.
  • The most reliable trigger is your form tool's success event, caught in Google Tag Manager and sent to GA4 as Google's recommended generate_lead event.
  • Marking an event as a key event is not retroactive, and it does not send anything to Google Ads. You have to import it separately.
  • In Google Ads, keep exactly one primary conversion per lead (either the GA4 import or a native Ads tag) and set the other to secondary to avoid double counting.

Key events vs. conversions: what changed in GA4

In March 2024, Google renamed GA4 "conversions" to key events. Today, "conversion" means a Google Ads conversion action, which you create from a key event (MeasureU, Relevant Audience).

This matters for two reasons. First, many tutorials and screenshots still say "Mark as conversion," which is the same toggle you now see as "Mark as key event" (Notfair). Second, marking something as a key event in GA4 does not send it to Google Ads on its own (LinkUTM). The two systems are connected only after you link them and import the event.

Which GA4 form conversion tracking method should you use?

There are three common ways to detect a lead form submission. They are not equally trustworthy.

Method How it works Reliability Best for
Enhanced measurement form interactions GA4 automatically sends form_start and form_submit Low: fires on non-lead forms and can miss or double-count JavaScript forms Diagnostics only
Thank-you page view Trigger on a page view of the confirmation URL Medium: reloads, bookmarks and direct visits inflate counts Simple forms that redirect after submit
Google Tag Manager success event Custom Event trigger on the form tool's success event, sending generate_lead High, as long as the form tool confirms a real submission AJAX forms and most business websites

For most small and mid-size businesses, the GTM success event is the right default. A thank-you page is a reasonable fallback if your form already redirects and you protect the page properly.

Step 1: Audit what your site tracks today

Before you add anything, find out what is currently counting as a lead. It is usually one of four things: a button click, the enhanced measurement form_submit event, a thank-you page view, or a success event from the form tool (Vow Design).

A click on the submit button is not the same as a successful submission. People click and then hit a validation error, or the form fails to send. If your current setup counts clicks, your lead numbers are inflated and your ad bidding is learning from bad data.

Write down every form on the site (contact, quote request, demo booking, newsletter) and decide which ones are actual leads. Newsletter signups are useful, but they should rarely sit next to quote requests as a primary conversion.

Step 2: Choose and set up your trigger

Option A: Enhanced measurement form interactions (use with caution)

Google added "Form interactions" to enhanced measurement in September 2022 (MoreVisibility). When it is on, GA4 sends form_start on the first interaction with a form and form_submit when a form is submitted, with parameters such as form_id, form_name and form_destination (Optimize Smart).

You can find the toggle under Admin › Data streams › your web stream › Enhanced measurement (gear icon) › Form interactions.

The problem is accuracy. Analytics practitioners report that it fires on search boxes, newsletter widgets and cookie banners, and that forms submitting through JavaScript can be missed or counted twice (Measurebase). Third-party scripts can also cause one submission to be sent several times, and Google has not published detailed documentation of exactly when these events fire (ezSegment).

If you must work with it, you can go to Admin › Events › Create event and create a generate_lead event whenever form_submit arrives with a specific form_id. It is better than marking every form_submit, but a GTM trigger on a true success event is still more reliable.

Option B: Thank-you page view

If your form redirects to a confirmation page, you can trigger on a page view of that URL. The risks are reloads and visitors who bookmark or land directly on the thank-you page, all of which inflate counts (ProGeek Tech).

To reduce that noise:

  1. Use a unique thank-you URL per form (for example /thank-you-quote/), so you can tell leads apart.
  2. Keep the page out of navigation and set it to noindex so search visitors do not land on it.
  3. In GTM, add a condition that the referrer contains the form page, so direct visits do not fire the tag.
  4. Consider the "once per session" counting method (covered in Step 5) if reloads are common.

Many modern forms submit without leaving the page (AJAX). In that case, use a GTM Custom Event trigger that listens for the form tool's success event in the data layer, then fire a GA4 Event tag that sends generate_lead (ProGeek Tech).

GTM also has a built-in Form Submission trigger, but it may not detect forms that submit through JavaScript. If you consider it, check Google's Tag Manager help for its current options and test it carefully before relying on it.

Here is the process for the success event approach:

  1. Open GTM Preview mode, submit your form, and look at the data layer for a success event. Many form plugins and hosted form tools push one. Check your form tool's documentation too.
  2. If there is no success event, ask your developer to push one only after the server confirms the submission:
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: 'lead_form_success',
  form_id: 'contact_main',
  lead_type: 'quote_request'
});
  1. In GTM, create a Custom Event trigger with the event name lead_form_success (it must match exactly).
  2. Create Data Layer Variables for form_id and lead_type.
  3. Create a Google Analytics: GA4 Event tag with the event name generate_lead, add the parameters, and attach the trigger.
  4. Turn off enhanced measurement Form interactions, or at least never mark form_submit as a key event, so the same lead is not counted twice.

If your site uses gtag.js directly instead of GTM, the equivalent call looks like this:

gtag('event', 'generate_lead', {
  form_id: 'contact_main',
  lead_type: 'quote_request'
});

If you run WordPress, your form plugin choice affects how easy this is. Pick a form tool that exposes a clear success event, and if you need help with plugins or custom form handling, see our WordPress development services.

Step 3: Send generate_lead with useful parameters

generate_lead is one of Google's recommended events, meant for when a user "submits a form or a request for information." Recommended events are not sent automatically; you have to implement them yourself (Google Analytics Help).

No parameter is strictly required. value is recommended, lead_source is optional, and you should send currency whenever you send value (ClickyOwl). If you assign a value, use an honest estimate tied to what a lead is typically worth to you, not a placeholder.

The most useful habit: keep one event name and use parameters like form_id or lead_type to separate forms. Creating contact_lead, quote_lead and demo_lead as separate event names makes reporting messier and uses up key event slots. To see custom parameters such as form_id in standard reports, register them as custom dimensions in GA4.

If you also run email, social or partner campaigns, tag those links consistently with our UTM Campaign URL Builder so lead sources stay clean in GA4.

Step 4: Test your form tracking in DebugView

Never mark an event as a key event until you have watched it arrive correctly. Use two tools together:

  • GTM Preview shows whether your tag fired.
  • DebugView shows what GA4 actually received.

DebugView streams events live from a single device that has debug mode turned on. It does not show all users; the Realtime report covers everyone over the last 30 minutes (Relevant Audience). You will find it under Admin › Data display › DebugView, and your device can take 10 to 30 seconds to appear (Stackmatix). GTM Preview turns on debug mode automatically, or a tag can send debug_mode: true (Native Ore Analytics).

Run through this checklist:

  1. Submit a valid test form. Confirm generate_lead appears exactly once.
  2. Click the event and confirm form_id, lead_type and any value parameters arrived.
  3. Submit a deliberately invalid entry (missing required field). No event should fire.
  4. Browse other pages and submit other forms, such as site search. generate_lead should not fire.
  5. If you used a thank-you page, reload it and visit it directly. Neither should count.

If the tag fires in GTM Preview but nothing appears in DebugView, consent settings or browser privacy controls are the usual suspects (Relevant Audience). Test in a clean browser profile with consent accepted.

Step 5: Mark generate_lead as a key event

Once the event is arriving cleanly, go to Admin › Data display › Events and toggle or star generate_lead as a key event. You can also use Create event with the "Mark as key event" option. Event names are case-sensitive, so Generate_Lead and generate_lead are different events (Relevant Audience).

A few practical details:

  • Permissions: you need at least the Editor role to mark an existing event, and at least the Marketer role to create a new key event (Relevant Audience).
  • It must exist first: an event appears in the list only after GA4 has received it once, which your Step 4 test takes care of (LeadSource).
  • Not retroactive: counting starts from the day you mark it. Past submissions will not be reclassified.
  • Counting method: choose "once per event" (the default) or "once per session."
  • Limits: standard properties have a cap on key events. Third-party guides cite 30 (Loves Data), but check Google's help center for the current figure.
  • Patience: standard reports can take about 24 hours to show new data.

Step 6: Import the GA4 key event into Google Ads

This is where tracking starts paying for itself. Without the import, Google Ads may be optimizing for pageviews, clicks or nothing useful at all.

  1. Link the accounts: in GA4, go to Admin › Product links › Google Ads links and link your Ads account.
  2. Turn on auto-tagging in Google Ads (Walker Sands).
  3. In Google Ads, go to Goals › Conversions › Summary › + New conversion action › Import › Google Analytics 4 properties (Graphed).
  4. Select generate_lead. Only key events appear here, and a newly marked one can take up to 24 hours to show up.
  5. Set it as a primary action if you want bidding to optimize for it, and review its value and attribution settings.

Google changes these menus fairly often, so labels may differ slightly in your account. We covered one recent shift in GA4 and Google Ads Data Change June 2026.

Avoid double counting leads

If a native Google Ads conversion tag and a GA4 import both track the same form and both are primary, each lead counts twice (Notfair). Pick one as primary and set the other to secondary. Inflated conversion data is one of the quieter Google Ads mistakes that kill ROAS, because Smart Bidding happily optimizes toward numbers that are not real.

Native Ads tag or GA4 import as primary?

Experts disagree. Adswerve recommends native Google Ads conversion tags as primary, with GA4 imports as secondary for comparing attribution. Many other guides present the GA4 import as the main method.

A reasonable rule: if you have a clean GTM setup and someone to maintain it, a native Ads tag firing on the same success trigger is a solid primary. If you want one source of truth and less tag maintenance, the GA4 import works. Either way, never let both count as primary.

Common lead tracking mistakes to check for

  • Marking enhanced measurement form_submit, or every page view, as the key event.
  • Firing on button clicks instead of successful submissions.
  • Counting thank-you page reloads and direct visits.
  • Running enhanced measurement form tracking alongside a GTM generate_lead tag that both get marked.
  • Spelling or capitalization mismatches between the tag and the key event.
  • Expecting historical data after marking an event.
  • Importing low-intent micro-events (scroll depth, video plays) as primary conversions, which trains bidding on the wrong goal.
  • Forgetting that consent choices and ad blockers hide some events.

Going further: from form fills to qualified leads

A form submission is not a sale. Google's lead funnel includes qualify_lead, disqualify_lead, working_lead, close_convert_lead and close_unconvert_lead alongside generate_lead. Sending them populates GA4's Lead acquisition report and suits businesses with offline or B2B sales cycles (Google Analytics Help).

Google Ads also offers enhanced conversions for leads and offline conversion imports, which let you feed CRM outcomes back into bidding. Requirements and setup details change, so check Google's current documentation before implementing. The same goes for consent requirements if you have visitors in Europe.

Once your numbers are trustworthy, improving them becomes a design question. Clear landing pages and funnels and ongoing conversion rate optimization only work when the lead count you are testing against is accurate.

Make your ad spend learn from real leads

Accurate GA4 form conversion tracking is the foundation every paid campaign stands on. If you would like a second set of eyes on your key events, Google Ads imports or primary conversion settings, Devma Agency's PPC management team can review your setup and help your campaigns optimize for the leads that actually matter.

Frequently asked questions

Why does GA4 show more or fewer form submissions than my inbox or CRM?

More usually means the trigger is too broad: enhanced measurement form_submit firing on search boxes or newsletter widgets, thank-you page reloads, or two tags counting the same lead. Fewer usually means consent choices, ad blockers or privacy settings stopped the event from reaching GA4. Your CRM will always be the record of truth for actual leads, so use GA4 for trends and attribution rather than an exact head count.

Why don't my GA4 and Google Ads lead numbers match?

GA4 counts key events from every channel, while Google Ads only counts conversions it can attribute to ad interactions. The two tools also use different attribution settings and reporting dates. Expect a gap and investigate only if it grows suddenly or changes direction.

How long does it take for a new key event to show up?

In DebugView, your device can take about 10 to 30 seconds to appear, and test events show up live after that. Standard GA4 reports can take about 24 hours to reflect new data, and a newly marked key event can take up to a day to appear in Google Ads as an import option.

Do I need a developer to track a form that has no thank-you page?

Not always. Many form plugins and hosted form tools already push a success event to the data layer, which you can catch in Google Tag Manager without code changes. If your form does not, a developer can add a few lines that push a success event after the submission is confirmed, which usually takes little time.

Abstract blue swirling shapes with light reflections

Let’s build something great together.

Contact us to discuss how we can elevate your business through expert web development, SEO, and digital marketing.

Get a free proposal

Fill out the form and our team will get back to you within 24 hours.

Devma

AI assistant · replies in seconds

Hi there.
How can we help?

Ask about websites, SEO, ads, AI search or our care plans. Answers come from our own guides, and a person is one tap away.

  • Message us on WhatsApp