Conversion Tracking Fundamentals — the layer every audit and every bid strategy depends on

Every number a Google Ads account reports — and every automated bid Smart Bidding places — depends on what counts as a conversion, where the tag fires, and whether the same action gets counted once or twice. Get this wrong and everything downstream (Quality signals aside) is built on bad data: What Does NOT Work: Broad Match and Smart Bidding Without Guardrails — where automation burns budget instead of saving it calls this "garbage in, garbage out" for a reason.

Conversion sources

Google Ads recognizes four primary conversion sources: website conversions (purchases, signups, clicks), app conversions (installs or in-app purchases), phone call conversions (inbound calls), and offline conversions (store visits, imported data) — support.google.com/google-ads/answer/1722054.

For websites, the recommended method is the Global Site Tag (gtag.js): it sets first-party cookies on the advertiser's domain that store a unique identifier for the user or the ad click. Google Ads stores cookie data about ad interactions, and the GCLID (Google Click Identifier) is what links a later conversion back to the ad click that produced it — support.google.com/google-ads/answer/7521212.

GA4 imported goals are not a separate source but a way of importing website conversions: conversions created from Google Analytics key events and imported into Google Ads are automatically marked secondary on import, specifically to prevent double-counting against a native website tag tracking the same event — support.google.com/google-ads/answer/13735417.

Fires here

the confirmation/completion page or event — e.g. the purchase confirmation page, or the thank-you page after a form submit — because that is where the conversion is actually confirmed and where conversion data (purchase value, transaction ID, customer info) is accessible in the page code — support.google.com/google-ads/answer/16560108.

Must not fire here

any page load that isn't the confirmation event. Tags should use URL-based targeting rules ("URL is," "URL contains," "URL starts with") to restrict firing to the intended page — support.google.com/google-ads/answer/16560108. A tag placed on a template that loads on every page (a shared footer, for instance) will overcount.

Cookie dependency

opting out of first-party cookies degrades measurement accuracy, since Google Ads' website tracking relies on the cookies set by the tag — support.google.com/google-ads/answer/7521212.

Enhanced conversions and consent mode for EU traffic

Enhanced conversions supplement standard tracking by sending hashed first-party customer data (email, address, phone) to Google using SHA256, a one-way hashing algorithm; the hash can be generated automatically by Google's tag from unhashed input, or supplied pre-hashed by the advertiser — support.google.com/google-ads/answer/9888656 and support.google.com/google-ads/answer/13258081. For web, at least one of the following is required: email (preferred), full address (first name, last name, postal code, country), or phone number (paired with email or address) — support.google.com/google-ads/answer/13258081.

Consent mode v2 adds two parameters: ad_user_data (consent to send user data to Google for advertising) and ad_personalization (consent for personalized ads) — support.google.com/google-ads/answer/13695607. For EEA traffic this is not optional: advertisers must implement consent mode and collect explicit user consent before firing applicable tags/SDKs for measurement, personalization and remarketing, per Google's EU User Consent Policy — same source. A Google-certified CMP updates consent mode automatically; a custom consent banner requires implementing consent mode v2 manually.

Primary vs secondary conversion actions — why it matters for bidding

Primary actions feed the "Conversions" column and are what Smart Bidding strategies optimize against in campaigns where that goal is active — support.google.com/google-ads/answer/11461796.

Secondary actions are observation-only: they show up in "All conversions" but do not influence bidding, unless explicitly folded into a custom goal — same source. GA4-based conversion actions default to secondary specifically so an event already tracked by a native tag doesn't also get bid on as if it were a second, independent action.

Practical implication

an account bidding toward Target CPA/ROAS (Bidding Strategies: Manual, Smart Bidding, and When Each Applies — matching the strategy to the conversion data you actually have) is only as good as its primary conversion set. A misclassified or duplicated primary action feeds bad signal directly into the bid algorithm at auction time.

What does NOT work: counting the same action twice

Firing a native Google Ads tag on a confirmation page and importing the same event from GA4 as a conversion, both left as primary/uncontrolled, double-counts one purchase as two conversions — the exact failure mode support.google.com/google-ads/answer/13735417 addresses by defaulting GA4-imported actions to secondary.

The other common double-count: a purchase confirmation page that reloads (browser refresh, back-button revisit) refires the tag for the same order. The fix Google documents is a transaction ID — a unique value (order ID, confirmation number) attached to each conversion; if two fires share the same transaction ID, Google Ads recognizes the second as a duplicate and drops it — support.google.com/google-ads/answer/6386790. Transaction IDs are the recommended method for purchase tracking specifically because they preserve accurate multi-purchase-per-customer data while eliminating reload-driven recounts; Google's documentation does not describe any other automatic safeguard against a reload refiring the tag, which is why the transaction ID is presented as something the advertiser must set up, not a default protection. Secondary-marking GA4 imports plus transaction IDs on purchases are the two advertiser-side levers that actually prevent double-counting — support.google.com/google-ads/answer/6386790 and support.google.com/google-ads/answer/13735417.

Why this matters for the objective

the wiki's audit method (How to Audit an Existing Google Ads Account (Priority Order) — the sequence that stops you from trusting broken data) puts verifying conversion tracking accuracy as step 1, before any other finding is trusted — a Search Terms report or an Auction Insights read is meaningless if the conversions it's measured against are inflated or missing. Setting this up correctly the first time is the subject of How to Set Up Conversion Tracking Correctly — the five steps that keep Smart Bidding's data honest.

Related

- How to Set Up Conversion Tracking Correctly — the five steps that keep Smart Bidding's data honest — the step-by-step procedure that applies these fundamentals: choose sources, place the tag correctly, dedupe against GA4, verify, then layer in enhanced conversions and consent mode. - Bidding Strategies: Manual, Smart Bidding, and When Each Applies — matching the strategy to the conversion data you actually have — Smart Bidding optimizes toward primary conversion actions at auction time; this page is why "the data feeding the algorithm" is a tracking-setup question, not a bidding-strategy question. - What Does NOT Work: Broad Match and Smart Bidding Without Guardrails — where automation burns budget instead of saving it — the "garbage in, garbage out" failure mode this page's duplicate-counting and mis-tagged-source sections are the concrete cause of. - How to Audit an Existing Google Ads Account (Priority Order) — the sequence that stops you from trusting broken data — treats conversion-tracking verification as the mandatory first step of any account audit, for the reasons laid out in "What does NOT work" above.