Google Ads Conversion Tracking: Setup Guide (2026)

What is Google Ads conversion tracking?

Google Ads conversion tracking records what happens after someone clicks your ad, such as a purchase, a lead form or a phone call, and reports it back against the campaign, ad group and keyword that earned the click. Smart Bidding strategies like Target CPA and Target ROAS then use those conversions to decide how much each future auction is worth.

That last part is why this setup matters more than a reporting nicety. If your conversion data is wrong, Google's bidding learns from the wrong signal. Undercounting makes good campaigns look bad, and double counting makes weak ones look great.

This guide covers the whole path: how Google connects a sale to a click, how to create and install a conversion action, which settings to change from the defaults, how to read the status column, and what to do when Google Ads reports fewer conversions than your store.

How Google Ads connects a sale to an ad click

When someone clicks your ad, Google can add a GCLID (Google click identifier) to the landing page URL. This only happens if auto-tagging is on in your account settings. The Google tag on your site reads the GCLID and stores it in a cookie on your own domain. Google says Google Ads cookies expire 90 days after the click.

When the visitor later reaches your confirmation page, the conversion event fires, the tag reads the stored click identifier and sends both to Google. Google matches the sale to the click, and the conversion appears in your reports, dated to the click rather than to the purchase.

Three things have to be true for that chain to work:

Auto-tagging is on, so the GCLID exists
The GCLID survives your site (a redirect that strips URL parameters breaks it)
The Google tag, plus a conversion event, runs on the pages that matter

If you use Google Tag Manager, the piece that handles step 2 and 3 is the Conversion Linker tag, which Google says should fire on All Pages.

Three ways to feed conversions into Google Ads

You can collect conversions in more than one way. Most mature accounts use a mix.

Method	How it works	Good for	Weak spot
Google tag or Google Tag Manager	A browser tag fires an event snippet on the conversion page	Fast setup, any website	Blocked by ad blockers, affected by consent choices and page changes
Google Analytics key event import	You mark a GA4 event as a key event and import it as a conversion	One source of truth across channels	Data can take up to 24 hours to arrive, and GA4 only knows what its own tag saw
Server-side upload	Your server sends the conversion with the click ID, value and order ID	Conversions the browser missed, and offline sales	Needs the click ID to reach your server, and a careful duplicate strategy

If a site uses more than one tracking method at once, such as gtag.js and Google Tag Manager together, Google advises checking for conflicts and consolidating to a single method, preferably Google Tag Manager.

How to set up conversion tracking in Google Ads (step by step)

These steps cover a standard website purchase or lead conversion.

Step 1: Turn on auto-tagging

Open your account settings and make sure auto-tagging is enabled. Without it Google Ads cannot attach a GCLID to your ad URLs, so there is nothing for the tag to store. If you import GA4 conversions, the Google Ads and GA4 properties also need to be linked.

Step 2: Create the conversion action

In Google Ads, open Goals, then Conversions, then Summary
Click + Create conversion action
Choose Website and enter your domain. Google scans it and detects an existing Google tag or Google Analytics property if you have one
Choose how to define the conversion:
- Set up with a URL if a page load is the conversion and you don't need transaction details. It is the fastest route and needs no extra code once your tags are in place
- Set up with code if you need to track a button click, a dynamic value such as the order total, or a transaction ID

For ecommerce purchases, use code, because you need the value and the transaction ID.

Step 3: Install the Google tag and the event snippet

The Google tag goes on every page of your website. The event snippet goes on the conversion page itself, after the Google tag. The two work together.

A purchase event snippet looks like this, with your own IDs and the real order values filled in dynamically:

<script>
  gtag('event', 'conversion', {
    'send_to': 'AW-123456789/AbC-D_efG-h12_34-567',
    'value': 59.00,
    'currency': 'USD',
    'transaction_id': 'ORDER-10482'
  });
</script>

The send_to value combines your Google Ads conversion ID with the conversion label for this specific action. If either is wrong, the conversion goes nowhere.

If you use Google Tag Manager instead, create a Conversion Linker tag that fires on All Pages, then a Google Ads Conversion Tracking tag with the same conversion ID and label, triggered on your purchase event. Pull the value, currency and transaction ID from your data layer.

If your site runs on a platform such as Shopify, a theme, app or plugin may already install a Google tag. Google warns that double-tagging a site causes duplicate conversion reporting, so check what is already installed before you add anything.

Step 4: Pass a value and a unique transaction ID

For purchases, send the order total and currency so Google can calculate conversion value and ROAS. Also send a transaction ID, usually your order number.

Google treats a transaction ID as the key for removing duplicates. If two conversions arrive for the same conversion action with the same ID, the second is flagged as a duplicate and not counted. That protects you when a customer reloads the thank-you page or the browser and a server both report the same order.

Google's rules for the ID are specific:

It must be dynamic and unique for every transaction. A hard-coded or reused ID causes undercounting, because Google may process only the first instance
It can contain letters, numbers, dashes and spaces, up to 64 characters
It should not contain personal information

Step 5: Test it with Tag Assistant

Open your conversion page with Tag Assistant and complete a test purchase. Check that the conversion tag fires once, with the right ID, label, value and transaction ID. Then check the status in Google Ads. Google notes the tag status can take up to 48 hours to update after you fix something.

A test conversion proves the tag fires. Only a conversion from a real ad click proves attribution works end to end, so check again after a real click comes through.

The settings that matter (and the defaults to change)

Once the action exists, open its settings. Four of them have the biggest effect on your data.

Primary vs Secondary

Each conversion action in a goal is Primary or Secondary:

Primary actions appear in the Conversions column and are used for bidding, provided the goal they belong to is used for bidding
Secondary actions are observation only. They appear in All conversions, but they do not influence bidding

There is one exception: any action inside a custom goal is used for reporting and bidding whatever its Primary or Secondary label. Google also warns that a wrong setup here stops Smart Bidding from optimizing properly.

A good starting point for an online store: Purchase as Primary, and softer steps such as add to cart or begin checkout as Secondary, so you can watch them without bidding on them. For a lead-generation business, qualified leads should be Primary and raw form fills Secondary if you can tell them apart.

Account-default goals and campaign goals

Conversion goals are groups of actions. A goal marked account-default feeds the primary actions inside it into the Conversions column and into bidding for every campaign, unless that campaign has its own goals selected. When you create a new campaign, all account-default goals are selected by default, so keep the default list short and meaningful.

Count: Every or One

The Count setting decides how many conversions Google records after one ad click:

Setting	Meaning	Use for
Every	Every conversion after an interaction is counted	Purchases, because every sale has value
One	Only one conversion per ad click is counted	Leads, where a second form fill from the same person is not a second lead

Google's defaults: Every for website actions, in-app actions, Analytics transactions and imported actions, and One for calls from ads, Analytics goals, calls to a number on your website and app installs. Changing the setting later only applies to future conversions.

If you take payment, remember that "Every" combined with a transaction ID is Google's recommended pattern for purchases: you count every sale but never the same sale twice.

Conversion window

The conversion window is how long after an ad interaction a conversion can still be recorded:

Window	Default	Range
Click-through	30 days	1 to 90 days, depending on the conversion source
Engaged-view	3 days	1 to 30 days
View-through	1 day	1 to 30 days

Google recommends windows of at least 7 days. To pick one, open the time lag report in your attribution reports and see how long your customers actually take to convert. A promotion that only runs for a week might justify 7 days; furniture or software with a long buying cycle might need 60 or 90. Like the Count setting, a changed window only applies to conversions from that day forward.

Attribution model

Google Ads now supports two attribution models: data-driven and last click. The first-click, linear, time-decay and position-based models were removed, and conversion actions that used them were moved to data-driven. Data-driven attribution is the default for most conversion actions, and it spreads credit across the ad interactions on the path.

If you switch models, expect your Conversions column to show decimals, because credit is split between interactions. Update bids and targets after a switch, since the same campaign will report different numbers. For a wider view of how these models compare, see marketing attribution models explained.

How to read the conversion status column

Open Goals, then Conversions, then Summary and look at the status of each action. Google renamed the statuses in 2026, so many guides, and some of Google's own older screenshots, still show the old wording.

Current status	Old wording	What it means	First thing to check
Active	Active	Working as intended	If numbers look low compared with your store, see the next section
Needs attention	Needs attention	There are issues to fix, but conversions are still recording	Hover over the status for Google's suggested fix
Misconfigured	Inactive	Conversions have stopped recording because of a setup error or broken tag	Is the tag still on your confirmation page? Test with Tag Assistant
Awaiting conversions	No recent conversions	Nothing recorded in the last 7 days. The action may be under 48 hours old, campaigns paused, or traffic too low	Compare with your own order data for the same 7 days. Real orders with no conversions points to a tag fault
Removed	Other	The action was deleted or archived	Confirm no goal still depends on it

Older help pages also mention tracking-status labels such as Unverified, Tag inactive and Recording conversions. When a status shows a problem, hover over it to see Google's steps. For tag problems, Google also offers a Troubleshoot link that opens Tag Assistant for that conversion action.

Why Google Ads shows fewer conversions than your store

Almost every account sees a gap between Google Ads, GA4 and the orders in its store admin. Some of it is by design and some of it is lost data.

Differences that are not errors:

Click date vs purchase date. Google Ads reports a conversion on the date of the click, not the date of the sale. A click on the 19th and a purchase on the 20th shows under the 19th
Conversions vs All conversions. The Conversions column only counts Primary actions. All conversions also includes Secondary actions and view-through conversions, which is a common reason for mismatches
Count setting. A lead form filled in twice shows as two events in GA4 but one conversion in Google Ads if the action counts One
Invalid clicks. Google filters conversions that come from clicks it treats as invalid
Cookie lifetime. Google Ads cookies last 90 days after a click, while Analytics cookies can last up to two years, so late conversions can appear in GA4 but not in Google Ads
Only Google Ads clicks count. Your store records every order, including organic and email

Differences that are lost data:

Ad blockers and browser protections that stop the Google tag from firing
Visitors who deny consent, so the full tag data is never sent
A GCLID that gets dropped by redirects, payment pages or checkout steps on another domain
A conversion event that does not fire on every checkout path, for example a payment step that returns customers to a different confirmation page
Fake leads and bot orders that inflate your count rather than shrink it. See how to audit your Google Ads for bot traffic

The second group is where server-side tracking helps. For a wider view of why platforms disagree with each other, see why your Facebook and Google Ads numbers never match.

How to close the gaps

A browser tag is the baseline. Four additions recover most of what it misses.

1. Enhanced conversions

Enhanced conversions send hashed first-party data, such as an email address or phone number, along with the conversion so Google can match more sales back to signed-in users. Google has been merging the web and leads versions into a single on/off setting in 2026, with Google Ads accepting user data from website tags, Data Manager and API connections together.

If you send them through an API, you still need a regular conversion tag on your site, and you should use the same transaction ID in both so Google can match and de-duplicate. Our enhanced conversions setup guide walks through each method, and the best Google enhanced conversions tools compares the options.

For visitors in the European Economic Area, you need to collect consent and pass the choice to Google with consent mode v2. The ad_user_data signal covers sending user data to Google for advertising and is required for measurement use cases such as enhanced conversions and tag-based conversion tracking. ad_storage controls advertising cookies.

When consent is denied, tags can send cookieless pings that Google uses for conversion modeling. Modeled conversions then appear in your Conversions column. Google sets conditions for this: consent mode must be implemented correctly, and your account needs at least 700 ad clicks over seven days per country and domain grouping. Advanced consent mode, where tags load and send cookieless pings, gives advertiser-specific modeling. Basic mode, which blocks tags until consent, only supports a general model. See our guide to consent mode v2.

3. Server-side delivery

A server can send the conversion after the order is created, so a blocked browser tag does not mean a lost conversion. For this to attribute correctly, the click ID has to reach your server: capture the GCLID (and the GBRAID and WBRAID parameters Google uses for some iOS traffic) when the visitor lands, store it with the session, and attach it to the purchase.

Read what server-side tracking is for the concept and why your pixel is losing conversions to ad blockers for the scale of the problem.

4. Offline conversions

If the sale closes later, by phone or in a CRM, you can import it against the original click. Two time limits apply: Google keeps a GCLID for 90 days, so conversions uploaded more than 90 days after the last click are not imported, and conversions matched on user-provided data must be uploaded within 63 days. The conversion time must also be after the click time, or Google rejects it.

If you build uploads yourself, note that Google's help center says offline conversion imports and enhanced conversions for leads uploads moved to the Data Manager API from June 15, 2026, and are blocked in the Google Ads API for developer tokens that had not used legacy access. Our offline conversion tracking guide covers the full process.

Avoid double counting when you add server-side conversions

The most common mistake after adding a second data source is counting one sale twice. Google removes duplicates inside a single conversion action when they share a transaction ID, but it does not remove duplicates across two different conversion actions.

That leads to a simple rule: if you have one conversion action fed by your Google tag and another fed by a server-side upload for the same purchase, only one of them should be Primary. Make the other Secondary so you can compare them without bidding on both. If both are Primary and sit in the same campaign goal, one order can count twice.

The same warning applies if you import a GA4 key event and also fire a Google Ads tag for the same purchase. Pick one source per business event. Keep the others as Secondary for comparison.

How SignalBridge works with Google Ads conversion tracking

SignalBridge does not replace your Google tag. It adds the server-side layer that catches what the tag misses.

You connect your Google Ads account and map SignalBridge events, such as a purchase, to a Google Ads conversion action
SignalBridge sends each conversion with the click identifier (GCLID, or GBRAID and WBRAID where they apply), the conversion time, value and currency, the order ID as the transaction ID, and the visitor's consent state
When the visitor has consented and provided them, it can include hashed email and phone number to help Google match the conversion
The conversion action needs to be an import type that accepts click conversions, and to accept GBRAID and WBRAID it has to count Every conversion per click
Click identifiers need to reach SignalBridge, so ad traffic must arrive with auto-tagging on and the GCLID in the URL

Because a server-side action is separate from your Google tag action, follow the rule above and keep one of them Primary. You can see how events are delivered to each platform in the server-side tracking feature overview, and check Performance Max data quality if you run PMax.

Common Google Ads conversion tracking mistakes

Mistake	What happens	Fix
Auto-tagging is off	No GCLID, so sales cannot be matched to clicks	Turn it on in account settings
A static or reused transaction ID	Google counts only the first order	Pass the real order number, dynamically
Tag and GA4 import both Primary for one event	Each purchase counts twice	Make one Primary, the other Secondary
Count set to Every on a lead form	One person can create several conversions per click	Set lead actions to One
Add to cart set as Primary	Smart Bidding optimizes for cart adds, not sales	Make it Secondary
Conversion Linker missing in Google Tag Manager	The click ID is not stored	Fire it on All Pages
Redirects that strip URL parameters	The GCLID is lost before the tag can store it	Pass parameters through each redirect
Judging a new action after one day	Status shows Awaiting conversions	Wait up to 48 hours, then test with a real click

Frequently Asked Questions

How does Google Ads conversion tracking work?

You create a conversion action in Google Ads and install the Google tag on your site, with an event snippet on the page that confirms a sale or lead. Auto-tagging adds a GCLID to your ad URLs, the tag stores it in a cookie on your domain, and when the conversion fires the tag sends the click ID to Google so the conversion can be tied to the ad click.

How long does it take for Google Ads conversion tracking to start working?

The tag status in Google Ads can take up to 48 hours to update after you install or fix a tag. A new action can show as Awaiting conversions until it records its first one. Imported GA4 conversions can take up to 24 hours to arrive in Google Ads.

Do I need Google Tag Manager to track conversions?

No. You can paste the Google tag and event snippet straight into your site. Google Tag Manager is easier to maintain when you have several tags, and Google prefers a single method if you find overlapping tags. Whichever you use, pick one to avoid duplicate conversions.

What is the difference between Primary and Secondary conversions?

Primary conversion actions show in the Conversions column and are used for bidding. Secondary actions are observation only and show in All conversions. An action inside a custom goal is used for bidding regardless of its label.

Why do my Google Ads conversions have decimals?

Decimals appear when an attribution model splits credit for one conversion across several ad interactions. Data-driven attribution does this, so a conversion may be counted as 0.5 or 0.33 for a single campaign.

Should I use Every or One for conversion counting?

Use Every for purchases, with a transaction ID so you never count the same order twice. Use One for leads, where a second form submission from the same person is not a second lead.

What conversion window should I use?

The default click-through window is 30 days. Use the time lag report in your attribution reports to see how long customers really take to convert, then set the window to cover most of them. Google recommends at least 7 days. Remember that a changed window only applies to future conversions.

Is it better to use the Google tag or to import GA4 conversions?

Both work. The Google tag measures conversions from Google Ads clicks only. GA4 imports let you manage conversions from one place and include data from other channels, but they depend on GA4's own tag and can arrive up to 24 hours later. Whichever you choose, avoid counting the same event through both in Primary actions.

Why is Google Ads reporting fewer conversions than my store?

Part of it is by design: conversions are dated to the click, only Primary actions appear in the Conversions column, and your store also records organic, email and direct orders. The rest is lost data from ad blockers, denied consent and dropped click IDs. Enhanced conversions, consent mode and server-side delivery recover much of it.

Can I track conversions without cookies?

Partly. With consent mode, tags can send cookieless pings when cookie consent is denied, and Google uses them to model conversions. Enhanced conversions use hashed first-party data such as email to match sales without relying on a browser cookie. Server-side delivery sends the conversion from your server with the stored click ID.

Key Takeaways