For many advertisers Google Ads is the biggest channel, and at the same time the one where tracking most often breaks silently. The campaign runs, the clicks come in, but the "Conversions" column shows too few, too many or simply the wrong ones. Smart Bidding then optimizes on data that has little to do with your business.
In 2026 Google changed several things at once: enhanced conversions now run on a single toggle, Consent Mode has become the central control for advertising data from GA4, and the Google tag gateway is generally available. This guide explains how Google Ads conversion tracking works today, which setup options exist and which mistakes to avoid.
How conversion tracking in Google Ads works
At its core, Google Ads conversion tracking consists of three building blocks: the click with a click ID, the Google tag on your website and the conversion action in your account.
1. The click: gclid, gbraid and wbraid
When auto-tagging is enabled in your account (the default), Google appends a click ID to every final URL. The best known is the gclid. For clicks from iOS environments where Apple restricts tracking, Google also uses the parameters gbraid and wbraid. These IDs are the thread connecting the ad click to the later conversion.
The Google tag reads the click ID from the URL on the first page view and, if consent is given, stores it in a first-party cookie on your domain. If the conversion only happens three pages or two days later, Google can still attribute it to the original click.
2. The Google tag (gtag.js)
The Google tag is the script that runs on your website. It is loaded with your conversion ID, which always has the format AW- followed by a number. The ID stands for your Google Ads account, not for a single conversion.
3. The conversion action with its label
In Google Ads you create a conversion action under "Goals", for example "Lead contact form" or "Purchase". Each action gets its own conversion label. When a conversion event with ID and label fires on your website, Google knows which action to count. Optionally you pass a value, a currency and a transaction ID.
The transaction ID is Google's mechanism against counting the same conversion twice. For purchases you should always send it, for example the order number. For leads it helps when a form is submitted twice or a thank-you page is reloaded.
Three ways to set it up
There is no single right way. Which option fits depends on how many platforms you advertise on and who maintains your website technically.
| Google tag directly in code | Google Tag Manager | All-in-one tool like LeadSignal | |
|---|---|---|---|
| Setup | Code snippets per conversion | Container, tags, triggers, variables | One script, events by click |
| Who maintains it? | Developer | Someone with GTM experience | Marketing itself |
| More platforms | separate code each | separate tags each | Meta, LinkedIn, TikTok in the same setup |
| Consent | wire up separately with a CMP | wire up separately with a CMP | Cookie banner built in |
| Flexibility | high | very high | optimized for standard cases |
Google tag directly: For a single thank-you page and only Google Ads this is lean. As soon as multiple conversions, values, enhanced conversions and consent come into play, it quickly becomes a developer task.
Google Tag Manager: The classic with maximum flexibility. The price is complexity: triggers, variables, data layer, versions and regular changes by Google that you need to keep an eye on. We summarize what changed in Tag Manager in 2026 in our article on Google Ads tracking changes in 2026.
All-in-one tool: A tool deploys the Google tag for you, connects it to the cookie banner and takes care of the consent signals. That is LeadSignal's approach and our focus on simple tracking: Google Ads, Meta, LinkedIn and TikTok from one script, without Tag Manager.
Step by step: set up Google Ads conversions
Regardless of the method, the steps in your Google Ads account are the same.
1. Plan your conversion actions
Decide in advance what really counts. For lead generation that is usually submitted forms, booked appointments or calls. In e-commerce it is the purchase with cart value. Micro-conversions such as scroll depth or clicks on "Learn more" can be set up as secondary conversions so they do not distort Smart Bidding.
2. Create the conversion action in Google Ads
Under "Goals" and "Conversions" you create a new action of type "Website". You choose category, value, count setting (usually "One" for leads, "Every" for purchases) and the conversion window. Afterwards you get the conversion ID and label.
3. Install the Google tag
The Google tag must load on every page so the click ID is stored on the landing page already. If it only loads on the thank-you page, Google often loses the connection to the click.
4. Fire the conversion event
The event fires where the conversion happens: when the thank-you page loads, when the submit button is clicked, or via code after a successful checkout. Thank-you pages are the most robust because they are only reached after a successful submission.
5. Turn on enhanced conversions
More on this in the next section. In short: you additionally pass the email address or phone number so Google can attribute conversions even when the click ID is missing.
6. Wire up Consent Mode v2 properly
Without correct consent signals Google counts fewer conversions in the EU than you expect, or you process data without consent. You want to avoid both.
7. Test
With Google's Tag Assistant you check whether the tag loads, whether the conversion event fires and which consent values are set. In Google Ads, "Diagnostics" shows per conversion action whether data is arriving. Expect new conversions to show up only after a few hours.
Enhanced conversions in 2026: one toggle for web and leads
Enhanced conversions add user-provided data to classic tracking, typically email address, phone number and name from a form. This data is hashed with SHA-256 before it is sent. Google matches it against signed-in Google accounts and can thereby attribute conversions where the cookie or click ID was lost, for example due to Safari ITP, ad blockers or a device switch.
In 2026 Google simplified the feature considerably. According to the Google Ads help center:
- From April 2026 Google Ads accepts user-provided data simultaneously from the website tag, Data Manager and API connections.
- From June 2026 enhanced conversions for web and for leads are combined into a single on/off setting. Choosing an implementation method (Google tag, Tag Manager or API) is no longer needed.
- Existing users who had already accepted the customer data terms were migrated automatically.
- Since June 15, 2026 offline conversion imports and uploads for enhanced conversions for leads only run through the Data Manager API, no longer through the Google Ads API.
For most advertisers that means: switch it on, accept the terms, and make sure the Google tag actually receives the form data. In practice that is the hard part, because the data has to be available at the moment of conversion.
Offline conversions, meaning leads that only turn into customers in your CRM days later, are a topic of their own. If you want to send closed deals from your CRM back to Google Ads, have a look at our sister product LeadMetrics. LeadSignal focuses on tracking on the website.
Enhanced conversions with LeadSignal
LeadSignal detects form fields for email, phone, first and last name automatically, without you mapping any fields. When a conversion event goes to Google Ads, LeadSignal passes this data as user data to the Google tag, which sends it to Google hashed. You do not need to build a data layer for it.
Consent Mode v2: what really matters in 2026
Google Consent Mode v2 transfers the decision from your cookie banner to the Google tags. Four signals are central:
ad_storage: set and read advertising cookiesad_user_data: send user data to Google for advertising purposesad_personalization: personalized advertising and remarketinganalytics_storage: analytics cookies
For users in the EEA, Google expects the default value to be "denied" before any choice and only to be updated to "granted" after active consent.
The June 2026 change
Until now, the collection of advertising identifiers in Google Analytics was governed both by the Google Signals setting and by the Consent Mode settings. According to the Google Analytics help center, Consent Mode has been the single control for this since around June 15, 2026. Google Signals now only governs whether Analytics data is linked to signed-in users for behavioral reporting. For data that flows to Google Ads through a linked property, the Google Ads settings apply.
Google has announced further steps, but without a date yet: ad_personalization is to exclusively control whether linked data is used for personalization, and automatically collected IP addresses are to be sent encrypted to the linked Google Ads account.
What this means in practice: if you used to rely on "Google Signals off" to hold back advertising data, now check that your Consent Mode default really is "denied" and that the update only comes after consent. A wrong default has had a direct effect since June.
Consent Mode with LeadSignal
As soon as you set up a Google Ads integration in LeadSignal, the script sets the Consent Mode defaults to "denied" and sends an update after consent in the cookie banner. The advertising signals ad_storage, ad_user_data and ad_personalization follow the Marketing category, analytics_storage follows the Statistics category. If you want it stricter, you can enable a restricted consent mode in the project: then the Google tag only loads after marketing consent. The guide on GDPR-compliant tracking explains the legal framework.
Google tag gateway: first-party serving, not a consent shortcut
The Google tag gateway for advertisers (formerly "first-party mode") serves Google tags through your own domain instead of Google domains. According to the Tag Manager release notes it has been generally available on Google Cloud since June 2026, and also via Akamai, Fastly and Amazon CloudFront.
The benefit: requests through your own domain are slowed down less often by ad blockers and browser protections. What matters, though, is what the gateway does not do. It does not change the requirement for consent. Consent Mode signals are evaluated exactly as before. A gateway without a proper cookie banner is not progress, it is a risk.
The gateway requires access to your CDN or cloud infrastructure. For many smaller websites on site builders that is simply not available. Then the regular Google tag with good Consent Mode and enhanced conversions remains the realistic path.
The most common Google Ads tracking mistakes
The gclid gets lost
The click ID disappears more often than you think: redirects that strip URL parameters, cookie banners that reload the page, forms on another domain, or a Google tag that only loads on the thank-you page. Use a test click (the parameter ?gclid=test is enough for a first check) to see whether the parameter arrives on the landing page and is stored after consent. LeadSignal captures gclid, gbraid and wbraid together with the UTM parameters per session, so you can trace in the event log which click a lead came from.
Duplicate conversions from GA4 import and tag
Very common: a conversion is measured via the Google Ads tag and also counted as an imported GA4 event. Both are set as primary conversions in the account, and Smart Bidding suddenly sees twice as many leads. Pick one source per conversion and set the other to "secondary".
The consent update is missing or late
The banner stores the consent, but the update command never reaches the Google tag because banner and tag are not wired together. The result: consenting users are treated like refusing ones. Tag Assistant shows which consent values were actually set when the conversion event fired.
Wrong count setting
Counting "Every" instead of "One" for leads inflates the numbers as soon as someone submits a form twice. For purchases it is the other way round: "One" would swallow repeat purchases in the same session.
Conversion on click instead of success
A click on "Submit" is not a lead yet if the form shows an error message afterwards. Where possible, measure success: the thank-you page or a confirmation. Click events make sense for buttons that lead directly to the goal, such as "Call now" or a calendar link.
Enhanced conversions without data
The toggle is on, but diagnostics say hardly any user data arrives. Usually that is because the form data is no longer available at the time of conversion, for example because the form redirects to a thank-you page. A setup that captures the fields while they are filled in and passes them with the conversion event solves exactly this problem.
Checklist: Google Ads conversion tracking 2026
- Auto-tagging is enabled in Google Ads.
- The Google tag loads on all pages, not only on the thank-you page.
- Each conversion action has the correct label, a value and the right count setting.
- Each conversion has exactly one primary source (tag or GA4 import, not both).
- Enhanced conversions are switched on and diagnostics show incoming user data.
- Consent Mode v2: default "denied", update only after active consent.
- Cookie banner with an equally prominent reject option on the first layer.
- Click IDs (gclid, gbraid, wbraid) arrive on the landing page and are stored after consent.
- Test conversion checked with Tag Assistant.
- Other platforms such as Meta, LinkedIn or TikTok run through the same consent setup.
Conclusion
Google Ads conversion tracking has become simpler in a few places in 2026: enhanced conversions only need one toggle, and Consent Mode is the one central control for advertising data. At the same time the margin for error has shrunk. A wrong consent default or missing form data directly costs you conversions in Smart Bidding.
If you run Google Ads together with Meta, LinkedIn or TikTok and do not want to maintain a tag manager, a setup with one script and a built-in banner helps. See how LeadSignal's Google Ads integration works on the integration page.