The short answer

Have your website push one event, generate_lead, to the data layer each time your server confirms an enquiry. In Google Tag Manager, a Custom Event trigger listens for it and fires a GA4 event tag. In GA4 you mark generate_lead as a key event, and Google Ads receives the lead in one of two ways: you import the key event, or you fire a Google Ads conversion tag on the same trigger. Bid on one of them, not both, and test the whole chain in Tag Assistant and DebugView before you trust the numbers.

generate_lead is one of GA4’s recommended events, meant for when someone submits a form or a request for information, so you don’t need to invent a name. GA4 also has events for later stages, such as qualify_lead and close_convert_lead, which become useful once you record what happens to each lead.

This is the setup we designed for our own site, 2rar.agency: the website side is live, and the Tag Manager part follows the steps below.

Why thank-you page views overcount

The quickest setup is a goal on visits to /thank-you. It works, but it counts every time the page opens: a reload, a return with the Back button, a bookmark, a forwarded link. It also can’t tell whether your server accepted the enquiry or the message went nowhere.

Google Ads bids on primary conversions. If one enquiry shows up as three conversions, a campaign looks better than it is, and bidding is built on that picture.

GA4’s automatic form events have a similar gap. With Form interactions switched on in Enhanced measurement, GA4 records form_start and form_submit by itself. form_submit fires when the browser submits a form; it can’t know whether the enquiry was accepted. Don’t mark either as a key event. We recommend switching Form interactions off so these events can’t be mistaken for leads.

Step 1: send one event per confirmed enquiry

Push the event from your website’s code only after the server answers that the enquiry was received, and only once per submission. A simple version looks like this: dataLayer.push({event: 'generate_lead', service: 'google-ads', form_page_path: '/dallas/google-ads'}).

On our site the form shows a confirmation and then opens a thank-you page. The event fires there only if the page receives a one-time handoff from the form for that submission; the handoff must be less than 30 minutes old and is deleted as soon as it’s read. A reload, a second tab, the Back button or a direct visit to the address sends nothing. If the browser can’t store the handoff, the form sends the event itself before it opens the page.

Decide the parameters before you build anything. Ours are the site language, the market chosen in the form, the service, the page the form was sent from, the contact type and whether the enquiry is a test. Nothing a visitor types into the form goes into them.

  • Use fixed values you control: service slugs, city names, page paths without query strings.
  • Never send a name, email address, phone number or message text, including inside a URL.
  • Give every submission an ID in your code so the same enquiry can’t fire twice, and keep that ID out of analytics as well.
  • Push the event after a successful server response, never on the button click.

Step 2: build the trigger and GA4 tag in Tag Manager

Google Tag Manager needs variables that read the event’s parameters, a trigger for the event and a tag that sends it to GA4. First, two naming details from our own setup.

GA4 uses the traffic_type parameter for its internal-traffic filters, so our test-or-production flag goes to GA4 as lead_environment instead. And because the event fires on the thank-you page, the page path GA4 records for it is /thank-you. The page where the form was sent travels separately as form_page_path: use it to compare your Los Angeles, Dallas and Dubai pages.

Lead tags for other ad platforms can share the same trigger, so every tool counts the same thing. The build takes four steps:

  • Variables → New → Data Layer Variable for each parameter, for example service and form_page_path.
  • Triggers → New → Custom Event, event name generate_lead. Add the condition Page Hostname equals your domain, so a copy of the site on another address can’t send leads.
  • Tags → New → Google Analytics: GA4 Event. Enter your Measurement ID (G-…), the event name generate_lead and the parameters from your variables, then choose the generate_lead trigger.
  • Preview the container, run the checks in Step 5, and only then submit and publish.

Step 3: make generate_lead a key event in GA4

In current GA4, the actions that matter most are called key events; Google Ads keeps the word “conversions”. In Admin → Data display → Events, find generate_lead and click the star next to it. A new event may not appear in that list straight away, but you can mark it as a key event in advance.

Marking isn’t retroactive: reports count the key event from the moment you mark it. If you plan to test with a simulated event (Step 5), do that first and mark the event afterwards, so the test doesn’t become your first conversion.

Register the parameters you want in reports as event-scoped custom dimensions. Google says you can start reporting on a new custom dimension after 24–48 hours, so do it before the first real enquiries arrive.

Step 4: send the lead to Google Ads once

Google Ads can receive the same enquiry in two ways. Import the GA4 key event: link GA4 and Google Ads, enable auto-tagging, then in GA4 go to Advertising → Conversion management → New conversion. Or tag it: create a conversion action in Google Ads, copy its Conversion ID and Conversion label into a Google Ads Conversion Tracking tag in GTM and fire it on the generate_lead trigger, with a Conversion Linker tag storing the ad-click information in first-party cookies.

Imported conversions start as secondary; to bid on one, change it to primary in Google Ads. Google also notes that imported conversions don’t show view-through conversions, and that Google Ads and Analytics totals can differ.

Primary conversions appear in the Conversions column and are used for bidding; secondary ones only show in All conversions. If you import generate_lead and also tag it, and both are primary, every enquiry counts twice. The same happens with an old thank-you page goal left over from a previous website: make it secondary or remove it.

For lead forms, set Count to One: Google then counts one conversion per ad click, since one unique lead per click is what usually matters. Every suits purchases. If you’re unsure which route to take, start with the import: one definition of a lead in both tools. Move to the tag when you need features built on Google Ads’ own tracking, such as enhanced conversions for leads.

Import the GA4 key eventGoogle Ads conversion tag
Set up inGA4: Advertising → Conversion managementGoogle Ads conversion action plus a GTM tag on the same trigger
Starts asSecondary until you make it primaryPrimary or secondary, as you set it
Worth knowingSame lead definition as GA4; no view-through conversionsNeeds a Conversion Linker tag; totals can differ from GA4

Enhanced conversions for leads: only with a CRM

Google describes enhanced conversions for leads as an upgraded version of offline conversion import. The Google tag captures data the visitor entered in your lead form, such as an email address or phone number, and sends it hashed: raw data is hashed by the tag with SHA256. You keep the lead in your CRM, and when it becomes a customer you import that conversion; Google matches it to the ad interaction.

Google’s requirements include accepting the customer data terms in Google Ads, enabling auto-tagging, a Conversion Linker tag on pages where people land after clicking an ad, an email or phone field on the form, and an automated import of offline conversions through Google Ads Data Manager or the Data Manager API. Since April 2026, enhanced conversions for web and for leads share a single setting.

It pays off when sales close later, by phone or in person, and you record the outcome. It does send hashed personal data to Google, so check that your privacy policy covers it. Ours says enquiry details aren’t passed to analytics, so we don’t use it on 2rar.agency.

Step 5: test before you trust the numbers

In GTM, click Preview, enter your site’s address and connect. Tag Assistant shows which tags fired on each event and which trigger fired them. Then open GA4 Admin → DebugView to watch events arrive in real time.

  • Before marking the key event, push a test event from the browser console: the GA4 tag should fire and DebugView should show the parameters.
  • Submit an empty form: there should be no generate_lead.
  • Send one real test enquiry: exactly one generate_lead, with the right service and page.
  • Reload the thank-you page and open its address in a new tab: no second event.
  • Read the parameters in DebugView: no name, email, phone number or message text.
  • Block googletagmanager.com in your browser and send again: the enquiry must still arrive. Analytics should never be able to stop a form.
  • Delete test enquiries and note the test dates to exclude them from reports.

Keep personal data out and count leads where they arrive

Google Analytics doesn’t allow data that Google could use or recognise as personally identifiable information, such as email addresses, phone numbers and names. It often leaks through URLs and page titles, so never put an email in a thank-you page address like ?email=…, and don’t copy form fields into event parameters.

Browser analytics will always miss some enquiries, because of blockers or tabs closed too early. The real count is where enquiries arrive, your inbox or CRM: compare it with GA4 and Google Ads every month. And an accepted enquiry is still not a qualified lead or a sale, so record those separately as they happen.

For a second opinion on what your account counts as a conversion, our Google Ads audit reviews enquiry tracking along with campaigns and landing pages. Conversion tracking is also part of every Google Ads launch we run for Los Angeles, Dallas and Dubai.

Let’s look at your business

Send your website and tell us what you want to change. We’ll discuss where to start.

Discuss your project