CONNECTIONS / Copper / Copper to Snap Offline CAPI
From Copper account pipelines to Snapchat in-store conversions.
Connect Copper and point Signals at your Copper account pipelines; it reports in-store purchases against the Snapchat campaigns that reached the buyer as records change, hashed and consent-checked for Snapchat.
- ● copper → snap.capi :: live
- > read closed_deals rows=58,554
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 50,942 matched
WHAT THIS ENABLES
Copper to Snapchat Offline CAPI
Copper to Snapchat Offline CAPI: your Copper account pipelines, hashed and consent-checked, feed Snapchat as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer as records change.
- Offline and in-store sales from your Copper account pipelines activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
- Physical-world sales counted inside Snapchat performance, drawn from your Copper account pipelines by Google Workspace sales teams on Copper.
The click, the conversion, and the credit.
The conversion happens off Snap, 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 Snapchat in-store conversions straight from Copper account pipelines.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Copper, reading only your Copper account pipelines to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals reads your Copper account pipelines, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.
-
Deliver
On each run, Signals pulls your Copper account pipelines, reports in-store purchases against the Snapchat campaigns that reached the buyer, and sends only the records that changed, with offline event timing 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 Offline CAPI 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 Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=copper.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784432329 · price 32041 · currency USD
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Copper
Copper to Google OCI
Copper to Google Offline Conversions: your Copper account pipelines, hashed and…
Learn morefrom Copper
Copper to Google Store Sales
Copper to Google Store Sales: your Copper account pipelines, hashed and consent-checked,…
Learn more
same use case
ActiveCampaign to Snap Offline CAPI
ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreAsked on almost every call.
How often does the Copper Snap Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly Copper sync of your Copper account pipelines into Snapchat. Since Signals sends only the records that changed, physical-world sales counted inside Snapchat performance keeps pace and Google Workspace sales teams on Copper watch offline event timing. One scoped connection sets it up, cadence adjustable later.
What match rate should a Copper-sourced Snap Offline CAPI batch expect?
In Copper, match rate tracks the email and phone quality your Copper account pipelines carry. Clean identifiers land for Snapchat; blank ones never will. The first Conversions API report shows Google Workspace sales teams on Copper where offline event timing needs work, a data-quality task handled in Copper.
NEXT STEP