Skip to main content
TrackingConsultingFree audit
Google Ads · Checkout → purchaseUse-case guide

How to track checkout to purchase for Google Ads

Everything between checkout starting and the order existing is where ecommerce tracking actually fails, and it fails differently depending on how your checkout is built. A hosted payment page is a different domain. A wallet payment can complete without the customer ever seeing the confirmation. Both produce orders in your store that no platform ever hears about. On Google Ads the specifics that matter are the click identifier (gclid, gbraid and wbraid), the import mechanism (Google's offline conversion import), and conversion actions deduplicate on their own counting setting rather than an event ID, so the setting matters more here than the payload. The chain only works end to end if the identifier is captured on landing and stored on the order record in your store — no cookie survives the gap between checkout started and purchase sent with the order id.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamGoogle Ads · Checkout → purchase, in short ↓

Specific to Google Ads × Checkout → purchase

Google Ads: purchases that skip the thank-you page via wallets

On Google Ads, send the purchase as the primary conversion action from the order webhook, through offline conversion import against the gclid, gbraid or wbraid saved on the order at checkout start, with Enhanced Conversions as backup. Keep begin_checkout as a secondary action, and use conversion adjustments to retract refunds.

Most Google Ads purchase tags are still a gtag event on the order confirmation page, and that's exactly where checkout-to-purchase breaks. A Google Pay or PayPal buyer can finish payment and close the tab before the confirmation loads, and Google Ads never hears about the order. The fix is to save the click identifier onto the cart or order at checkout start, so the order webhook can send the purchase through offline conversion import regardless of what happened in the browser.

If you run both, the browser tag and the server upload, decide which one the conversion action counts. Google Ads doesn't pair events by ID across a tag and an import the way Meta does, so two sources feeding one action double-count. The clean pattern is one action fed from the order record, with begin_checkout as a secondary action for diagnosis.

Google's conversion adjustments let you retract a refunded order or restate its value, which matters for checkout-to-purchase because failed payments, chargebacks and fraud cancellations happen after the order exists. Enhanced Conversions, sending the order's hashed email, is the fallback for iPhone orders whose identifier was lost on the hop to a hosted payment page. Read the match rate after each upload, not the success message.

Google Ads · Checkout → purchase · what breaks

Where this funnel usually breaks — Google Ads · Checkout → purchase

  1. 01

    Wallet payments skip the confirmation page

    Shop Pay and PayPal can be abandoned after the money moves. The order is real; the page view never happened.

  2. 02

    A hosted payment page on another domain

    Session splits, the click identifier doesn't cross, and the purchase gets credited to your own site as a referral.

  3. 03

    Every payment method assumed to behave the same

    Card, wallet and redirect gateways each return differently, and the untested one is where the missing conversions are.

Google Ads · Checkout → purchase · the fix

What working looks like — Google Ads · Checkout → purchase

  • Purchase sent with the order ID attributed to the click

    Weeks later if necessary, because the identifier lives on the order record in your store rather than in a cookie.

  • Google Ads bidding fed the real outcome

    Via offline conversion import, so it optimizes toward completed orders rather than toward checkout starts.

  • A reconciliation that closes

    Your store's order records, web orders only matched per record against what Google Ads reports, over a fully closed window.

Google Ads · Checkout → purchase · architecture

The exact event sequence — Google Ads · Checkout → purchase

Stage three is the one you often can't instrument, which is precisely why stage four has to be the source.

  1. 1

    Checkout started

    Browser-side, with value. The last point you reliably control the page.

  2. 2

    Payment info submitted

    Worth splitting out — it turns one opaque step into a diagnosable one.

  3. 3

    Payment authorised

    Often on someone else's domain, and frequently invisible to your tags entirely.

  4. 4

    Order created

    From the order webhook. This is the only step that sees every order regardless of how payment happened.

  5. 5

    Purchase sent with the order ID

    Deduplicated on that ID, with refunds wired to reverse.

Google Ads · Checkout → purchase · diagnose

What's specific to Google Ads

  1. 01

    Click identifier: gclid, gbraid and wbraid

    Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.

  2. 02

    Import mechanism: offline conversion import

    Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.

  3. 03

    Deduplication

    There's no shared event ID mechanism like Meta's. What matters instead is the counting setting on each conversion action — 'one' for lead-type conversions so a repeat submitter doesn't count three times, 'every' for ecommerce where a second purchase is a second sale. This is the single most common misconfiguration we find in Google Ads accounts.

  4. 04

    Window and timing

    Google's offline import window is 90 days from the click. Anything older can't be matched, and rows outside it fail as unmatched without much explanation. Measure your median click-to-outcome time against that before designing anything.

  5. 05

    The Google Ads gotcha

    A conversion action that stops receiving hits is flagged as inactive 30 days later — by which point a month of budget has already run against a missing signal. Check the last-received date on every action monthly; it takes two minutes and it's the cheapest monitoring available.

Google Ads · Checkout → purchase · prove

How to prove the chain works — Google Ads · Checkout → purchase

Source of truth

your store's order records, web orders only

  • The same identifier confirmed on the order record in your store after a full real journey through every step.
  • Purchase sent with the order ID confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
  • Your store's order records, web orders only reconciled against Google Ads per record over a fully closed window.

Google Ads · Checkout → purchase · free audit

What we check in the free audit

  • Click identifier: gclid, gbraid and wbraid
  • Import mechanism: offline conversion import
  • Deduplication
  • Window and timing
  • The Google Ads gotcha

Checked against

your store's order records, web orders only

Get my free conversion tracking audit

Free30 minutesNo obligation

Google Ads · Checkout → purchase · when not to buy

When this doesn't apply to you — Google Ads · Checkout → purchase

  • If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
  • If you're running Performance Max exclusively and haven't separated your conversion actions, the import will work and the reporting won't tell you much. Worth sorting the account structure first.
  • If your cycle from click to purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
  • If almost none of your orders carry a click identifier today, that's the whole project.

Google Ads · Checkout → purchase · what we deliver

The implementation, on Google Ads

  • Capture gclid, gbraid and wbraid on landing

    Auto-tagging appends the identifier. Confirm it's enabled in every account — it gets switched off for cleaner analytics URLs more often than you'd expect, and that single setting removes conversion attribution, Enhanced Conversions and offline import in one go.

  • Persist it to the order record in your store

    Set a first-party cookie server-side before the hop, and pass the identifier into the payment domain where the provider supports it — where it doesn't, the order record is the only path.

  • Send purchase sent with the order id from the record

    The order webhook fires once per order, independent of which payment path the customer took or whether they ever saw a confirmation page. Dispatched to Google Ads through Google's offline conversion import.

  • Deduplicate and reverse

    Conversion actions deduplicate on their own counting setting rather than an event id, so the setting matters more here than the payload. Refunds reverse from the refund webhook; failed and cancelled orders should never have counted in the first place.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Google Ads · Checkout → purchase questions, answered

The purchase tag sits on the confirmation page, and wallet buyers often never load it. Send the purchase from the order record against the click identifier saved at checkout.

More on Google Ads · Checkout → purchase

RELATED GUIDES

Funnels next to checkout to purchase, and the checks that close it

Free · 30 min

Get checkout to purchase tracked properly on Google Ads

Book the free call WhatsApp

Free30 minutesNo obligation