How to track online research to in-store purchase for Google Ads

Architecture

The exact event sequence

Five stages. The break is a physical one. No click identifier survives a walk into a shop, so the entire funnel depends on a bridge — an appointment, a reservation, a loyalty account or an email given at the till — and the honest deliverable includes the share of revenue that has no bridge at all. The identifier has to survive all of them.

1. Step 1

   Online research

   Product views and store locator use. The intent signal.

2. Step 2

   Appointment booked or reservation made

   The practical bridge. It captures an identity and a click identifier.

3. Step 3

   Store visit

   Modeled by ad platforms rather than measured. Treat it as directional.

4. Step 4

   In-store transaction

   The money event, from the point of sale.

5. Step 5

   Join to an online identity

   Through the appointment, a loyalty ID or an email captured at the counter.

Diagnostic sequence

What's specific to Google Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Google Ads.

1. 1

   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. 2

   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. 3

   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. 4

   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. 5

   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.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Google Ads ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the point-of-sale transaction, joined to an online identity where one exists after a full real journey through every step.
• Join to an online identity confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
• Your point-of-sale transactions by date, with the share joined to an online identity stated as a number reconciled against Google Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If you have no appointments, no loyalty scheme and no identity capture at the counter, there is no bridge to build. That is a real finding and it should be said before anyone is billed for a project.
• 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 join to an online identity regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward appointments and reservations, valued at your own average in-store transaction instead and use the later data for budget decisions rather than for bidding.
• If almost none of your transaction records carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.