Google Ads conversion tracking,
from the inquiry to the sale

Conversion tracking records what people do after they interact with a Google ad. You choose which actions count, and Smart Bidding strategies such as Target CPA optimize toward them (Google Ads Help).

For a business that sells through inquiries, tracking first sees a form or a call. The revenue arrives later, in a CRM that Google Ads cannot see. A working setup counts each real inquiry once and sends the CRM’s verdict back, so bidding can learn which inquiries were worth having.

Google changed much of this in 2026. Everything described here is live as of September 2026 unless the text says otherwise.

How Google Ads knows a conversion happened

With auto-tagging on, the default for new accounts, Google Ads adds a GCLID parameter to the landing page URL. The Google tag (formerly the global site tag) stores that click ID in a first-party cookie, such as _gcl_aw, on your own domain. When the visitor completes the action, the tag matches it to the stored click and records a conversion (how Google Ads tracks website conversions).

Because the click ID sits in a first-party cookie, Digital Traction’s reading is that Chrome’s third-party cookie policy is not what decides whether a click-based inquiry gets counted. Where a browser blocks third-party cookies or shortens how long first-party cookies last, Google models the conversions it cannot observe (conversion modeling). View-through conversions from browsers that block cross-site cookies cannot be reported (conversion tracking data).

Decide what counts before you tag anything

Write down the stages a lead passes through, usually an inquiry, a qualified lead and a converted lead. Google’s Lead Journey Mapping tool, live as of September 2026, asks for the same map, including steps you do not track yet. Google does not say every account has it.

Smart Bidding optimizes toward the conversions in the goal a campaign bids on. Count only form submissions and it bids for more form submissions, whether or not they become business. A separate note on feeding real outcomes back to the platform makes the case for sending CRM outcomes to Google Ads, and the CRM section below covers how.

Google’s lead-gen best practices set out guidance for the stage you bid toward:

• At least 15 conversions in the last 30 days, at the account level
• Ideally completed within 7 days of the ad interaction
• If imported, uploaded regularly, ideally daily
• One stage, not goals from several stages of the journey at once

Google says the categories “Qualified lead”, “Converted lead”, “Book appointment” and “Request quote” switch on invalid-traffic protections built for lead generation.

Which settings decide what bidding learns

Primary or secondary

Actions sit in goals by category, such as “Submit lead forms”. Primary actions fill the Conversions column and drive bidding when the campaign uses their goal. Secondary actions appear only in All conversions and drive bidding only inside a custom goal, an advanced option Google says is not recommended in most cases (primary and secondary actions). Google adds that unused primary actions may still inform predictions, so keep actions you only want to watch secondary.

Count one or every

Every counts every conversion after an ad interaction, and Google suggests it for sales. One counts one conversion per ad click, and Google suggests it for leads (counting options). Someone who sends the same form twice after one click is one lead.

How long the window runs

The click-through window defaults to 30 days and can run from 1 day to 30, 60 or 90 depending on the source. Google recommends at least 7, and conversions after the window are not recorded (conversion windows). Check the time lag report under Attribution, and give an imported Converted lead action a window that covers your sales cycle. If the cycle runs longer than the window allows, see long sales cycles.

Data-driven or last click

Data-driven attribution is the default for most actions, and Google has retired every rule-based model except last click (attribution models). Google recommends 200 conversions and 2,000 ad interactions in 30 days for data-driven attribution. It still runs with less, though with little data the result can match last click (data-driven attribution). Split credit is why a keyword can show 0.5 conversions (conversion tracking data).

One value or several

A value can be fixed or passed per conversion by the tag, and value-based strategies use it. One fixed value fits inquiries that are worth about the same on arrival.

Set it up in this order

The sequence is Digital Traction’s recommendation. The facts behind each step come from Google’s documentation.

1. Map the stages and pick the one bidding will chase first, usually the inquiry
2. Confirm auto-tagging is on, redirects keep the GCLID, the gtag linker covers any second domain, and no tag fires inside an iframe (Google’s prerequisites)
3. Install the Google tag on every page, directly or through Google Tag Manager. In GTM, a Google tag on every page makes a separate Conversion Linker tag unnecessary
4. Create one primary inquiry action: the right category, Count set to One, a window from the time lag report. Set it up with code, through the Google tag or GTM, because Google’s no-code URL method is for actions that do not need transaction IDs (web conversions). In GTM, the conversion tag takes the Conversion ID and Label from the action’s Tag setup (Tag Manager Help)
5. Send a unique transaction ID with each inquiry (Google also calls it an order ID). Google can adjust or retract a website conversion only if it carried one (conversion adjustments)
6. Turn on enhanced conversions, and add consent mode wherever you show a banner
7. Test the inquiry action end to end, then decide how phone calls count
8. Create the CRM stages as secondary import actions and upload daily
9. Move the bid goal once an imported stage is reliable and has the volume

How to turn on enhanced conversions

The tag hashes what the visitor typed into the form (email, name, address, phone) and sends it to Google, which matches it to signed-in accounts that engaged with an ad (enhanced conversions for web). For leads, the same hashed details come back later with the CRM outcome (enhanced conversions for leads).

Google merged the two in 2026. Since April 2026, Google Ads has accepted user-provided data from tags, Data Manager and API connections at once. Since June 2026, web and leads have shared one on/off switch. Existing users who had accepted the customer data terms moved over automatically, and each action can still opt out (settings update).

Switch it on under Goals, Settings, Customer data use, confirming that the Google Ads Data Processing Terms apply. Then let the tag read the form, with form-interaction detection in the Google tag’s automatic event detection (configure the Google tag for leads) or the Google Ads User-Provided Data Event tag in GTM. A form inside an iframe has to pass its data to the parent page, for example with postMessage (implementation checklist).

Google recommends email as the match key, because a CRM is unlikely to reformat it, and phone with a country code as well, to improve match rates (match keys). It says enhanced conversions help most at 20 or more conversions a week, organic ones included (enhanced conversions for leads report).

How to send qualified leads back from the CRM

Google calls enhanced conversions for leads an upgraded offline conversion import and recommends it to anyone not yet importing (offline conversion imports). Google’s file-import Help page is now labeled legacy.

Google recommends Data Manager (under Tools), which connects a source once for jobs such as conversion import and Customer Match. Google’s implementation checklist also lists direct CRM connections such as HubSpot, and Zapier is supported too (enhanced conversions for leads).

Since June 15, 2026, the Google Ads API has accepted no new adopters of offline conversion imports, enhanced conversions for leads included (Google Ads Developer Blog; deprecations page). Google’s advertiser Help pages carry the same notice (offline conversion imports). Existing users can continue while they migrate, and new builds belong on the Data Manager API. Google’s notices are written about the API itself, which suggests they also reach a CRM vendor’s connector built on it. If a connector runs your import, ask which API it uses.

The steps, mostly from Google’s implementation checklist:

1. Store the GCLID and email with every lead in the CRM, plus phone with a country code. Google says to include GCLIDs whenever possible
2. Create one action per stage, such as “Qualified lead” and “Converted lead”, with the source “Import from clicks”. Keep each new action secondary for its first 2 to 3 weeks
3. Wait 4 to 6 hours after creating an action before uploading to it (file import page)
4. Upload every lead that reached the stage, including those not from Google Ads, as Google requires for enhanced conversions for leads
5. Include an order ID, the time the stage actually happened and a consent value. Skip zero-value conversions unless you are using adjustments
6. For scheduled uploads, normalize and SHA-256 hash first: emails lowercased and trimmed, with periods before the @ removed for gmail.com and googlemail.com, and phones in E.164, such as +16505551234
7. Upload daily, with an extra day of overlap each time. Click IDs must be within 90 days, enhanced conversions for leads uploads must arrive within 63 days of the last click, and processing takes 24 to 48 hours (conversion measurement; import guidelines)
8. Check data quality in the diagnostics report, graded Excellent, Good, Needs attention or Urgent

Imported conversions report on the original click date, not the upload date, and a successful API response does not mean the conversion was attributed (Google Ads API docs). To take back a junk lead, retract it, which removes it from the counts and sets its value to 0.

Lead form assets collect the inquiry inside the ad, where your site’s tag cannot see it. Google keeps those leads for 60 days, and a webhook can send them to the CRM for grading.

When the sale outlasts the upload window

The import limits in the CRM steps above count from the last ad click to the upload, not to the sale. Google does not import an offline conversion uploaded more than 90 days after the last click, and for enhanced conversions for leads the limit is 63 days (import guidelines). A sale that closes later than that, or closes in time but is sent late, is not imported and does not appear in Google Ads conversion statistics.

Google’s answer is a stage that happens sooner. For a conversion that happens after 90 days, it says to “upload a different offline conversion event that happens within 90 days” (import errors). Its value-based bidding page grants that the final purchase might have the most accurate values, then adds: “If the delay is too long for you to manage, consider selecting a goal earlier in the consumer journey, like a qualified lead” (value-based bidding).

The setup Digital Traction recommends when the sales cycle runs longer than the window:

• Bid toward the latest stage that reliably happens, and gets uploaded, well inside the window, such as a qualified lead or a first meeting held. The guidance above on volume and delay for the stage you bid toward still applies
• Keep the sale as its own action, set to secondary, with the longest click-through window its source allows. Google recommends a separate action for each stage so that bidding can target one of them (offline import FAQs). The sales uploaded in time then show in All conversions, and bidding does not target them unless the action sits in a custom goal (primary and secondary actions)
• If bidding will move to value, set the earlier stage’s values from what the CRM shows comparable leads at that stage have been worth in closed revenue, for example by service line, so the stage carries at least two different values as Google requires. Google accepts proxy values, as the next section notes, so the stage does not have to wait for the sale to carry one
• Do not plan on restating those values when the deal closes. Autobidding reads a restatement or retraction for up to 7 days after the conversion is first recorded, and Google’s pages put the limit for any adjustment at 54 days (adjust your conversions) or 55 (offline import FAQs). Digital Traction’s reading of that limit is that a restatement after the first week changes the reports, not what bidding learned. Google’s value-based bidding page also cautions against backfilling value data with delayed offline uploads, because delays in uploading affect Smart Bidding performance (value-based bidding)
• Check how far back your connection reads. Google says Data Manager reads the last 90 days on every run from file and storage sources such as SFTP, only the last 14 days on every run from databases such as BigQuery, and from Salesforce and HubSpot the last 14 days on the first run, then the changes since the last run (GCLID setup). The same page lists a click-to-conversion cycle under 14 or 90 days, depending on the source, as a prerequisite

Journey-aware bidding, covered in the next section, is Google’s beta for letting Search campaigns on Target CPA or Maximize conversions learn from goals they do not bid on, once enough conversion actions are imported to show the lead journey (beta page). A sale uploaded past the window is not imported, so Digital Traction’s reading is that the earlier stage still does the teaching.

Past the window, Google Ads does not count the sale, so the check belongs in the CRM. Check there, by the month each lead arrived, what share of qualified leads from Google Ads goes on to close. If that share moves, the stage bidding chases no longer means what it did, and its value needs revisiting.

When to move bidding to qualified leads

Move the bid goal once the imported stage has run as secondary for a few weeks, matches the CRM and meets Google’s volume guidance. To go from Target CPA on form submissions to Target ROAS on qualified leads, Google’s order is qualified leads on Target CPA first, then value (value-based bidding). Value bidding needs at least two different values, from revenue or a proxy such as a lead score. Without them, Google recommends Target CPA on qualified or converted leads. Smart Bidding for lead generation covers the move step by step.

Set the new target deliberately, for the reasons in the note on why campaigns stopped beating their target. Expect a learning period after the switch (Google Ads Help); how long it runs, and which changes reset it, is covered in Smart Bidding for lead generation. Judge results over periods with at least 30 conversions, or 50 for Target ROAS (About Smart Bidding).

Conversion value rules adjust values by audience, location or device. Google notes that Smart Bidding already uses location and device, so base a rule on a difference your CRM shows.

Journey-aware bidding is in beta as of September 2026, which means Google is still testing it. As announced on May 7, 2026, it lets Search campaigns on Target CPA learn from biddable and non-biddable goals when the full lead-to-sale journey is tracked (announcement). The beta page, updated September 16, 2026, adds Maximize conversions and asks for enough imported conversion actions to show the lead journey, without saying how many. Treat it as a pilot.

How phone calls count

Google Ads counts calls from ads, calls to a Google forwarding number on your site, clicks on a phone number on your mobile site and imported calls. With call reporting on, new calls count under a default “Calls from ads” action included in Conversions (measure calls from ads).

AI-qualified call leads are live as of September 2026. With call recording on, Google’s AI evaluates each recording and counts only calls it judges qualified. A call that cannot be recorded counts if it lasts longer than a minimum length you set (AI-qualified call leads). Recording is on by default, except where an advertiser turned it off or Google identified the business as healthcare or financial services. It works only when both numbers are in the US or Canada, callers hear a recording notice, and calls from location assets are not recorded (call recording settings).

Decide whether calls should drive bidding alongside forms. If they should not, set the call action to secondary.

When you need consent mode

Consent mode passes the visitor’s choice to Google tags. It is not a banner. Basic mode holds tags until the visitor responds. Advanced mode loads them and sends cookieless pings when consent is denied.

Version 2 added ad_user_data and ad_personalization. For users in the EEA, Google requires advertisers to collect consent and pass it on to keep using tags for measurement, personalization and remarketing (EEA update). Google recommends scoping the default state to the regions where a banner shows (developer guide). CRM uploads need a consent value too, or the conversions may not be attributable.

Digital Traction’s position is to accept a conversion lost to a declined choice. Which regions need a banner is a question for your counsel.

GA4 import or the Google tag

Both can feed Google Ads, and you choose the source per action (GA4 conversions in Google Ads). The differences:

• Google Ads counts conversions from Google Ads only, while GA4 key events can include other sources
• Only key events import, and nothing from before the import comes across
• GA4 imports start as secondary, settings such as window and counting may not be editable, and view-through conversions are unavailable
• Google recommends the Google tag if you do not use Google Analytics or need Ads-specific features such as enhanced conversions (conversion measurement)

With enhanced measurement on, GA4 also sends form_submit for forms across the site, not only the inquiry form, so unfiltered it counts more than inquiries. For visits from AI tools, see the note on where AI traffic actually lands in GA4.

How to test before you trust the numbers

1. In Goals, Conversions, Summary, launch Tag Assistant on any action marked Unverified, Tag inactive or Needs attention. Start from a landing page, not the thank-you page (Tag Assistant)
2. Submit the inquiry form yourself and confirm in Tag Assistant or Chrome DevTools that one request fires, on submission, with the right value and transaction ID (transaction IDs)
3. Check that the _gcl_aw cookie is present on the form page, especially after a redirect or a change of domain
4. Allow about 30 minutes. Verified actions read “no recent conversions”, then “Recording” once real ones arrive. After a fix, status can take up to 48 hours to update
5. Read the overview status: Active, Needs attention (still recording), Misconfigured (stopped) or Awaiting conversions (none in 7 days). As of September 2026 Google says some are still rolling out, so you may see the older labels instead (tracking status)
6. For imports, segment campaigns by the new action using All conv. (by conv. time)
7. Reconcile a week of inquiries against the CRM by hand before you trust either

Why Google Ads and the CRM disagree

Some gap is built in. Standard columns date a conversion by the ad click while the CRM dates the lead, and Google says All conv. (by conv. time) may compare better with your own systems (conversion tracking data). Data-driven attribution splits credit, One counts once per click, the window drops late conversions, Google Ads counts only its own, and modeled conversions fill in what Google could not observe, only when it has high confidence the ad caused them.

Treat any gap beyond these as a setup error until you find otherwise, starting with the next section. Reported conversions measure what Google attributes to its own ads, and the note on campaign-level lift covers the limits of that.

Which failures are easy to miss

Most of these never show in the campaign view, and the rest surface only in diagnostics or as upload errors. Each changes what bidding learns:

• The default “Calls from ads” action counting in Conversions beside the form action
• An empty value field in a GTM conversion tag, which sends a value of 0
• A CMS plugin tagging the site a second time and duplicating conversions
• A hardcoded transaction ID, so Google may process only the first conversion that carries it
• A redirect or click tracker that strips the GCLID
• A native tag and a GA4 import on the same form, both primary
• Only leads with a GCLID uploaded for enhanced conversions for leads, which the diagnostics report flags
• Click IDs older than 90 days, which show as upload errors in Diagnostics (conversion measurement)
• Enhanced conversions for leads uploaded more than 63 days after the last click, which Google does not import (import guidelines)
• Uploads with no consent value, which may not be attributable

Agreeing on what a qualified lead is, and keeping that answer flowing back from the CRM as the business changes, is work that continues after the tag is installed. It is the measurement side of Digital Traction’s Search & acquisition work.