CONNECTIONS / Linode / Linode to Google Store Sales
From Linode objects to Google Store Sales matching.
Connect Linode and point Signals at your Linode objects; it matches in-person transactions to Google accounts as store-sales conversions each time a new file lands, hashed and consent-checked for Google Ads.
- ● linode → google.sales :: live
- > read closed_deals rows=36,759
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 31,980 matched
WHAT THIS ENABLES
Linode to Google Store Sales
Linode to Google Store Sales: your Linode objects, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions each time a new file lands.
- Offline and in-store sales from your Linode objects activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
- Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Linode objects by developers on Linode Object Storage.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Linode closes the loop.
Built for the teams that own the number.
Developers on Linode Object Storage activating Google Store Sales matching straight from Linode objects.
From kickoff to verified events.
-
Connect
A read-only key scoped to the Linode bucket you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals picks up your Linode objects, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.
-
Deliver
On each run, Signals pulls your Linode objects, matches in-person transactions to Google accounts as store-sales conversions, and processes only the newly dropped file, with the store-sales match rate in the debugger.
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 Store Sales 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 Linode records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=linode.closed_deals
- transaction_time 2026-07-22T16:27:49 · transaction_amount_micros 46796000000
- currency_code USD
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=87%
Adjacent moves on the same stack.
from Linode
Linode to Google OCI
Linode to Google Offline Conversions: your Linode objects, hashed and consent-checked, feed…
Learn more
from Linode
Linode to Meta Offline CAPI
Linode to Meta Offline CAPI: your Linode objects, hashed and consent-checked, feed Meta as…
Learn more
same use case
ActiveCampaign to Google Store Sales
ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…
Learn moreAsked on almost every call.
How often does the Linode Google Store Sales sync run?
Delivery tracks Linode, run by developers on Linode Object Storage: a near-real-time or scheduled sync of your Linode objects feeds Google Ads on that cadence. Each run processes only the newly dropped file, so store visits reconciled to campaign spend holds up on the store-sales match rate. The live debugger confirms every delivery inline.
What match rate should a Linode-sourced Google Store Sales batch expect?
Match rate follows identifier coverage in your Linode objects, which developers on Linode Object Storage control, not Linode itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Store Sales Direct API pinpoints the store-sales match rate, the number developers on Linode Object Storage tune against.
NEXT STEP