CONNECTIONS / Copper / Copper to Google Store Sales
From Copper account pipelines to Google Store Sales matching.
Connect Copper and point Signals at your Copper account pipelines; it matches in-person transactions to Google accounts as store-sales conversions as records change, hashed and consent-checked for Google Ads.
- ● copper → google.sales :: live
- > read closed_deals rows=35,986
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 30,588 matched
WHAT THIS ENABLES
Copper to Google Store Sales
Copper to Google Store Sales: your Copper account pipelines, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions as records change.
- Offline and in-store sales from your Copper account pipelines 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 Copper account pipelines by Google Workspace sales teams on Copper.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how Copper closes the loop.
Built for the teams that own the number.
Google Workspace sales teams on Copper activating Google Store Sales matching straight from Copper account pipelines.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Copper, reading only your Copper account pipelines to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals reads your Copper account pipelines, 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 Copper account pipelines, matches in-person transactions to Google accounts as store-sales conversions, and sends only the records that changed, 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 Copper records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=copper.closed_deals
- transaction_time 2026-07-13T06:21:47 · transaction_amount_micros 12763000000
- currency_code SAR
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=85%
Adjacent moves on the same stack.
from Copper
Copper to Google OCI
Copper to Google Offline Conversions: your Copper account pipelines, hashed and…
Learn more
from Copper
Copper to Meta Offline CAPI
Copper to Meta Offline CAPI: your Copper account pipelines, hashed and consent-checked,…
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 Copper Google Store Sales sync run?
You set the cadence, from near-real-time to a nightly Copper sync of your Copper account pipelines into Google Ads. Since Signals sends only the records that changed, counter and showroom revenue inside the same ROAS view as online orders keeps pace and Google Workspace sales teams on Copper watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.
What match rate should a Copper-sourced Google Store Sales batch expect?
In Copper, match rate tracks the email and phone quality your Copper account pipelines carry. Clean identifiers land for Google Ads; blank ones never will. The first Store Sales Direct API report shows Google Workspace sales teams on Copper where the store-sales match rate needs work, a data-quality task handled in Copper.
NEXT STEP