CONNECTIONS / Shopify / Shopify to Google OCI
Shopify pickup orders, still credited to the click.
A shopper clicks a Google ad, reserves online, and pays at the counter days later. The GCLID from that first click would normally expire with the session. Signals persists it through to the POS transaction and uploads the match to Google Ads.
- ● shopify → google.oci :: live
- > event Order reserved gclid=Cj0KCQjw…
- > event POS order placed value=340.00 AED
- hash sha256(email,phone) gclid=carried
- route google.oci upload batch=nightly
- ✓ delivered · click conversion recorded
WHAT THIS ENABLES
Shopify to Google Offline Conversion Import
Shopify to Google Offline Conversion Import carries the GCLID captured on a storefront session through to the POS transaction that completes it, so a buy-online-pickup-in-store order still uploads to Google Ads as a click-based conversion.
- Buy-online-pickup-in-store orders attributed back to the exact Google ad click that started them.
- Smart Bidding trained on completed POS transactions, including the in-store sales that online reservations miss.
- A GCLID that survives the gap between an online reservation and a counter payment.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Shopify closes the loop.
Built for the teams that own the number.
Retailers whose Google-driven traffic completes purchase at a physical till, not the storefront.
From kickoff to verified events.
-
Connect
App-scoped access to Shopify order and POS webhooks, plus the storefront session data carrying the GCLID.
-
Map
GCLID field and the POS event that counts as the completed conversion agreed in the visual mapper.
-
Deliver
Nightly or hourly delivery through the Google Ads API, with an accepted-row count on every run.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same OCI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment Shopify records the event. |
What OCI actually receives.
- ● signals :: event payload
- > POST /offline_conversion_import source=shopify.pos_order
- gclid "Cj0KCQjw…" · conversion_action "pos_pickup_complete"
- conversion_date_time "2026-07-20 14:12:00+04:00"
- conversion_value 340.00 · currency_code AED
- ✓ accepted · batch=nightly
Adjacent moves on the same stack.
from Shopify
Shopify to Google Store Sales
Shopify to Google Store Sales hashes customer and order data from both the online…
Learn morefrom Shopify
Shopify POS to Meta Offline CAPI
Shopify POS to Meta Offline CAPI captures in-store transactions the moment a Shopify POS…
Learn moresame use case
ActiveCampaign to Google OCI
ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…
Learn moregeneric
Google Offline Conversion Import
Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…
Learn moreAsked on almost every call.
What happens if the GCLID is lost between the online reservation and the pickup?
That order cannot be imported through OCI, which matches on the click ID alone. We reduce the loss by writing the GCLID to the order record the moment it is reserved online, and for stores where a lot of traffic never reserves online first, Google Store Sales is usually the better fit alongside OCI.
How long after a POS order does the conversion show up in Google Ads?
Uploads run on the schedule you choose, from hourly to nightly, and Google typically processes an OCI batch within a few hours of receiving it. A pickup completed today is usually visible in Google Ads reporting by the next business day.
NEXT STEP