Digital Marketing

Form Tracking: Which Event Goes Where? Start, Submit, Lead

Talha Aslan 20 min read 3 views

Short answer

What is form tracking and which events does it cover?

Form tracking means measuring every step from a visitor first seeing a form to becoming a lead, with one event for each step. Three events matter most: the first interaction with the form (start), the submission, and the qualified lead. Each event does a different job, so you name each one separately and send it to a different place.

Keep reading for the full details and examples

In practice, most businesses look only at "forms submitted". However, the gap between start and submit shows why a form fails to convert. Likewise, the gap between submit and lead shows whether your ads bring real business.

In this guide, we explain the name, the trigger moment, and the destination of each event, step by step. For the facts, we rely on the official Google Analytics and Google Ads help pages. To keep your campaign links tidy, also keep a utm builder open while you read.

For example, a thousand visitors see a page. Two hundred click into the form, sixty press submit, and forty become qualified leads. So if you watched only one "submission" count, you would miss the lost steps. With three events, however, you see that most people never start the form and that a third of the senders drop out later.

Of course, these numbers are only an example, and your site will differ. Still, the method stays the same. Measure each step on its own, and read the loss at each step separately. Then you spend your improvement effort on the right step.

Which event serves which purpose?

Sort your events by three questions: did the person show interest, did the person finish, and is the person valuable? So each question gets its own event. As a result, whoever reads your report does not pull three different meanings from one number.

First, form start measures interest. The visitor touched the fields, but we do not know whether they sent anything. Therefore, this event is ideal for spotting friction in the form.

Second, form submit measures completion. Here the visitor pressed the submit button. However, this event alone does not guarantee that the submission arrived.

Finally, the lead event measures value. The submission is valid, and the person is a real prospect. In most accounts, the conversion you send to your ad platform is this event. So first separate the layers of measurement, and then decide which layer goes to advertising.

Also, put these three questions at the top of your weekly report. Then the reader sees at a glance where you lose people. For example, if starts are high and submits are low, the problem sits in the form. If submits are high and leads are low, the problem sits in traffic intent or in your filtering rules.

Where should each form tracking event go?

Still, not every event goes everywhere. Your analytics tool wants the broad picture. Your ad platform, in contrast, wants one clear target to optimize. So spread the events across three destinations: analytics reports, ad optimization, and your sales record.

So start and submit events stay in analytics. Do not tie your bidding strategy to them, because the signal is weak. The qualified lead event becomes a key event in analytics and also goes to your ad account as a conversion. Then your CRM keeps the sales record.

In addition, there is another reason for this split. An ad system learns from the conversion you give it. If you feed it a weak signal, it starts looking for weakly qualified people. So give your ad account only the event that carries real business value.

Things get tangled when tag publishing and the ad account depend on each other. Which event feeds which conversion, and which one counts twice? Because sorting that out takes experience, outside help can pay off. In such cases, a team with google ads management experience can read the event map and the account together and find the fault faster.

If you wonder why the numbers differ between tools, our sibling guide why GA4 and Google Ads numbers don't match covers the topic in depth.

When do the automatic GA4 form events do the job?

Enhanced measurement in Google Analytics can track form interactions on its own. According to the official help page, there are two events: form_start fires the first time a user interacts with a form in a session, and form_submit fires when the user submits a form. Read the enhanced measurement help page for the source.

First, these two events give you a fast start. However, do not assume they work on every form. If a plugin loads the form, or if the submission happens without a page reload, the event may not fire, or it may fire at the wrong moment.

Here is a practical rule: keep the automatic events on, but compare the result with your real form records. So if the numbers match, the automatic events do the job. If they do not, define your own event. Otherwise you make decisions on a wrong number.

Consider your own event in these cases:

  • The form submits without a page reload, and the automatic event never fires.
  • The page has several forms, and you cannot tell which one works.
  • The automatic event also counts failed attempts, so the number runs higher than real records.
  • A third-party tool loads the form, and no event arrives at all.
  • You use a multi-step form and want to see the middle steps.

What information do form_start and form_submit carry?

The help page says these events carry parameters such as form ID, form name, and form destination. In addition, form_submit can carry the text of the submit button. These parameters let you tell which form worked when you have more than one.

However, two points need care. First, to use these parameters in your reports, you must create custom dimensions for them. Without that step, the data arrives but does not show in reports. Second, never collect personal information. Do not write a name, an email, or a phone number into a parameter.

Also, give your forms meaningful names. Names like "form1" and "form2" become a puzzle six months later. Clear names such as "contact_form" or "quote_form" carry the same meaning for everyone who reads the report.

Then write the naming rule down and share it with your team. Simple rules, such as lowercase letters and underscores, keep reports consistent even months later. Also, when you add a new form, you can reuse the same naming pattern with no effort.

Why does the submit event sometimes count wrongly?

The form_submit event catches the moment a visitor presses the submit button. However, that moment does not mean the form went through. A required field may be empty, the server may return an error, or the visitor may type a wrong verification code.

So the submit count often runs higher than the real record count. For example, a visitor tries three times with a missing field. The event fires three times, but only one record exists. If you tie your conversion goal to this event, you optimize an inflated number.

The fix is a signal that marks the moment of success: a success message, or a thank-you page that opens only after a successful submission. That way, the event fires at the moment the system truly accepts the form. Then the next section compares the two approaches.

Also, do not forget spam submissions either. Bots can fill and send the form, which inflates your count. A hidden validation field or a security question reduces this noise. Then tie the lead event only to submissions that pass validation. For deeper protection, read how to stop contact form spam.

What is the right success signal: a thank-you page or an event?

In practice, two common methods exist, and both work. The thank-you page method is simple: after a successful submission, the visitor lands on a separate page, and viewing that page counts as the conversion. The event method instead sends an event the moment the success message shows on a form that does not reload the page.

Its main strength is robustness. If the page opens only after success, the risk of wrong counting drops. Its weakness is that a visitor who reloads the page, or who saves the address and opens it again, triggers the conversion a second time.

The event method, instead, offers flexibility. However, it needs a change in your site code. Whichever you choose, the rule stays the same: the trigger must run only on a successful submission. Then compare the result with real records.

When should you use the generate_lead event?

generate_lead is one of Google's recommended events. According to the developer documentation, it measures when a lead has been generated, for example through a form. It can carry optional parameters such as value, currency, and lead source. For the details, read the GA4 events reference.

Place this event on top of the submit event, not in its place. form_submit says "the button was pressed", while generate_lead says "this became a lead". So you fire the second one only on a valid, successful submission.

If you use the value parameter, also send the currency. The documentation says currency is required when you set a value. Set the value as an estimated lead value, and update it later with real sales. Instead, do not write a made-up value with no basis.

In fact, you do not have to give a value at all. If you do not know the value, first just count the event. A few months later, look at your sales data and set a reasonable value. A wrong value misleads your bidding strategy, while an empty value only counts.

Which event should you mark as a key event?

Any event you collect in Google Analytics can become a key event. However, that flexibility is a trap. So if you mark every event, your conversion count loses its meaning. Mark only the one or two events that truly represent your business goal.

Here is a common recommendation: make the lead event a key event, and keep the start and submit events as plain tracking. After all, a start shows interest but brings no business. Your key event choice shapes both your reports and the conversions you pass to your ad account.

If you struggle to set the goal, read how to set website conversion goals. To track the smaller steps, our guide on micro conversions shows the way.

How do you connect a key event to a Google Ads conversion?

The Google Ads help page explains how to create conversions from Analytics key events. The prerequisites are linking Analytics and Google Ads, turning on auto-tagging, and having enough access on the property. For the official steps, see create Google Ads conversions based on Google Analytics key events.

The flow, roughly, is this: in Analytics you open conversion management, create a new conversion, pick the Google Ads account, and select the events to import. Menu names can change over time, so look for the matching section on screen and follow the current steps on the help page.

Always check on the Google Ads side whether the imported conversion is primary or secondary. Remember that bidding optimizes only for primary conversions. A conversion with the wrong status teaches the campaign toward the wrong goal.

Also review the conversion category and the counting method. For a form lead, counting every single submission as its own conversion is often unnecessary, because the same person can submit twice after one click. Then decide which option fits your sales process.

How do you avoid counting the same conversion twice?

In practice, double counting is the most frequent problem in form tracking. It comes from two paths: importing the same event while also sending it with a direct tag, or tying both the submit and the lead event to the same goal. In both cases, conversions double and cost per conversion looks half as high.

To prevent it, set one rule: every real lead counts as one conversion action in the ad account. First, before you add a new conversion, list the existing conversion actions. If two actions do the same job, make one of them secondary or remove it.

The help page also notes that managing settings in one interface reduces the risk of data discrepancies. Also, if two places manage the system, chaos follows. So name an owner for conversion management, and record every change in a written log.

Finally, a quick check helps you catch double counting. For the same day, put three numbers side by side: real form records, the lead count in analytics, and the conversion count in the ad account. If the ad account shows nearly twice as many, double counting is likely. Different counting methods cause small gaps, but a twofold gap is a warning sign.

How do you carry the campaign source into the form?

If you do not know which ad produced a lead, form tracking stays half done. UTM parameters carry the source, and you can write them into hidden form fields. Then your sales team sees at the moment of entry which campaign sent each request.

In practice, here is how you apply it. First, open the UTM link builder, enter the source, medium, and campaign name, and use the generated link in your ad. Write names consistently, because "Google" and "google" count as different sources. We explain what the parameters do in what UTM parameters are.

Also, do not carry personal data in hidden fields. Instead, write only campaign information. In addition, if auto-tagging is on for your ad links, check the setting so your UTMs do not clash. That way, the source data stays consistent in both analytics and your CRM.

Give campaign names a pattern: source, medium, campaign, and optionally content. For example, use readable names like "google", "cpc", and "quote_form_search". Six months later, you do not guess what each campaign was.

What should hidden fields and CRM links carry?

The last link in form tracking is seeing whether a lead became a sale. For that, you connect the form record to your CRM. The record holds source, campaign, and submission time, so you can feed the sales result back to advertising.

Also, mind personal data here. Name, email, and phone belong only in the CRM, and they should not go to analytics tools. The help pages also stress that you should not collect personally identifiable information in analytics. This is not legal advice, so ask your specialist about your data processing duties.

To set up the CRM link in detail, read website CRM integration and lead tracking. The setup may look complex, but the logic is simple: every lead carries one identifier in both systems.

How does cookie consent affect form tracking?

First, consent management decides which visitors you can measure. So if a visitor does not give consent, some tags may not run. As a result, form events arrive incomplete, and a gap opens between real records and the panel.

That gap is not a bug. It is the natural result of your consent setup. What matters is knowing the size of the gap and comparing numbers with that knowledge. Real form records can always run higher than the measured event count.

Also, after you refresh the consent banner, test your form events again. When the banner changes, the order in which tags fire can change. The rule is simple: after every update that touches the banner, test form tracking from scratch. For background, read is Google Consent Mode v2 mandatory.

How does tracking work on multi-step and pop-up forms?

For multi-step forms, think of a separate event per step. For example, the first step becomes "start" and the last step becomes "submit". Tracking the middle steps shows at which step people give up.

However, pop-up forms create a different problem. The form does not change the page address, and automatic detection may struggle. Here you fire the events yourself, from the submit button in the pop-up or from its success message.

Use the same form ID for every step, and keep the step number as a separate parameter. Then one form reads as one story across the steps. To simplify the form itself, see lead form design for bookings, quotes, and demos.

Read the middle-step events only when you hunt for a problem. Because sending many events can clutter the report, start small. So at first, track the first step, the last step, and the drop-off point. Then, if the need arises, add the middle steps later.

Should you track phone and chat clicks like a form?

Not every visitor fills in a form. Instead, some call directly or send a message. Those actions can count as leads too, but you should measure them as separate events. Otherwise, leads outside the form stay invisible, and your advertising looks weaker than it is.

Give each channel its own event name: phone click, message click, form submit. Then tie all of them to the same lead logic. Still, a click does not guarantee a real conversation, so keep the click and the qualified lead apart.

We have a detailed guide on phone calls: how to track phone calls from Google Ads. There you find the logic of conversions based on call duration.

How do you test form tracking before you go live?

In short, testing is half the setup. Then behave like a real visitor and check that each event fires. Keep the debug view of your analytics tool open, and you can watch events arrive in real time.

Follow this order:

  1. Open the debug view before you touch the form.
  2. Click into the form and confirm that the start event arrives.
  3. Try to submit with a missing field and see that the lead event does not fire.
  4. Submit with valid details and check that the submit and lead events each arrive once.
  5. Repeat the same test on mobile and in a second browser.
  6. Confirm that the real form record and the notification email exist.

Use your own details in the test, and delete the records afterward. Also, never enter someone else's information as a test.

After the test, wait a day and check that the events show in your reports. Real-time views show events at once, but standard reports can fill with a delay. So do not panic over the first day's numbers. According to the help pages, data processing can take time.

Which event fires when, and where does it go?

The table below summarizes the core form tracking events at a glance. Names may differ in your setup, but the logic stays the same. Use the table as the first draft of your event map.

EventWhen it firesWhere it goesKey event?
form_startThe visitor first interacts with the formAnalytics reports onlyNo
form_submitThe visitor presses the submit buttonAnalytics reports, error diagnosisUsually no
generate_leadThe system accepts the submission as validAnalytics and Google Ads conversionYes
Phone or message clickThe visitor taps a call or message linkAnalytics, ad conversion if neededDepends on goal
Sales confirmationThe lead becomes a real customerCRM, offline conversion importDepends on goal

What are the most common form tracking mistakes?

In practice, the same mistakes repeat on different sites. So knowing them lets you build a sound setup from the start. The list below comes from our observations, and your setup may differ.

  • Treating a button click as a successful submission and counting failed attempts.
  • Counting the same lead twice, once through an imported event and once through a direct tag.
  • Marking every event as a key event and making the conversion count meaningless.
  • Counting the visitor who reloads the thank-you page again.
  • Writing personal information into parameters.
  • Skipping the retest after a consent banner update.
  • Leaving form names vague so nobody can read the report.

However, if several of these apply to you, do not panic. You can fix each one on its own, but fix them in order. Handle double counting first, then the trigger, and naming last.

In fact, most of these mistakes come from setting things up once and walking away. The site changes, the form tool ships a new version, and campaigns shift, while the measurement stays the same. So treat form tracking as a living system.

How do you diagnose missing or extra counts?

If the number in the panel does not match real form records, find the direction first. If the panel runs higher, suspect double counting or counting of failed submissions. Otherwise, if it runs lower, a trigger may not fire, consent may block it, or the tag may not load.

Therefore, the direction changes the checklist. For extra counts, inspect the trigger condition and duplicate tags. For missing counts, confirm that the tag runs on the page, that the thank-you page address is right, and that the consent banner does not block the tag.

Moreover, for a detailed checklist on missing conversions, read GA4 conversions missing: causes and fixes. If your rate suddenly dropped, our article on conversion rate drop gives the diagnosis order. You can also calculate the rate yourself with the conversion rate calculator.

How can enhanced conversions strengthen form tracking?

Enhanced conversions send hashed details from a form submission to Google, aiming to improve how well conversions match. However, this needs extra care with personal data. First make sure your consent and privacy text support it.

We have a detailed guide on the setup: Google Ads enhanced conversions setup. There you find which fields you can use and what to watch. This is not legal advice, so consult your specialist before you apply it.

Add enhanced conversions only when your basic form tracking works soundly. If the base has errors, a layer on top makes the problem bigger. The order stays the same: base first, layer second.

Before you add layers, ask yourself: is my current conversion count correct? If it is, enhanced conversions only improve matching. If it is not, sending more data spreads the wrong number further.

What does a monthly form tracking check look like?

You do not set up form tracking once and forget it. A theme update, a form tool change, or a new banner can break events silently. So build a short monthly check routine.

Each month, look at these points: do real record counts and panel counts sit close, does the lead event fire once, and do form names and campaign names stay consistent? Also, if you use Google Tag Manager, review the latest publishes.

This routine takes less than half an hour. Even so, it catches a problem within a week instead of a month. In return, you avoid wrong budget decisions that broken tracking causes.

Tie the routine to a calendar reminder and save the results as a short note. Then, when your team changes or you start working with a specialist, the past checks stay at hand.

When should you ask for help with form tracking?

You can do a lot yourself: draw an event map, run the test list, and compare against real records. However, complexity rises fast once events connect to the ad account, the CRM, and the consent system.

At Talha Aslan and team, we handle the event map, the conversion actions, and the bidding strategy together. The process runs like this: first we audit the current measurement, then we remove double counts and gaps, and then we simplify the conversions in the ad account. For the advertising side, you can read about our google ads agency services.

We give no guarantee of results, because lead volume depends on the offer and the page, not only on measurement. Still, a form you measure correctly shows clearly which budget works.

Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.

Frequently Asked Questions

Which form tracking events should I measure separately?
Separate at least three events: form start, form submit, and lead. Start shows interest, submit shows completion, and the lead shows real value. In most accounts, you pass only the lead event to your ad platform as a conversion. The other two stay in analytics so you can see why a form does not convert.
Is the GA4 form_submit event enough on its own?
Often it is not. form_submit catches the moment someone presses the submit button, but it does not guarantee that the submission succeeded. Failed attempts can count too. So set up a lead event that fires only after a successful submission, and compare your numbers with real form records.
Which event should I import into Google Ads as a conversion?
Usually import only the qualified lead event. First mark the event as a key event in Google Analytics, then link the accounts and import it. If you import start and submit events, your bidding strategy learns from a weak signal. Always check whether the imported conversion is primary or secondary.
Why do my form conversions count twice?
The most common cause is the same event arriving twice: once through an import and once through a direct tag. Sometimes the submit and lead events also feed the same goal. List your conversion actions, then make one of the duplicates secondary or remove it. Every lead should count through a single action.
Does cookie consent affect form tracking?
Yes, it can. If a visitor gives no consent, some tags may not run, so the panel shows fewer events than real form records. That gap is not a bug but a result of the consent setup. Retest your form events every time you update the consent banner.
Can I set up form tracking myself?
For a simple contact form, you can set it up yourself with automatic events and a thank-you page. You must run the test list and compare with real records. If you have a multi-step form, an ad account link, or a CRM, expert help saves time. No setup guarantees results.
  • form tracking
  • ga4 form tracking
  • generate_lead
  • form_submit
  • google ads conversion
  • key event
  • lead tracking
  • event map
Share:
Talha Aslan

Google Partner digital marketing expert. Hands-on with SEO, Google Ads, web design and e-commerce projects since 2012; every post here comes from that experience.

Next project

Get a quote for your project.

Your brief goes straight to Talha Aslan and team: strategy led by Talha, delivery by an experienced team. We reply the same day and send the scope, timeline and price as a written quote within 1 business day.