CONNECTIONS / Copper / Copper to Meta Offline CAPI
From Copper account pipelines to Meta's offline optimization.
Connect Copper and point Signals at your Copper account pipelines; it credits dealer, branch, and phone sales to the Meta campaigns behind them as records change, hashed and consent-checked for Meta.
- ● copper → meta.capi :: live
- > read closed_deals rows=16,527
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 13,883 matched
WHAT THIS ENABLES
Copper to Meta Offline CAPI
Copper to Meta Offline CAPI: your Copper account pipelines, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them as records change.
- Offline and in-store sales from your Copper account pipelines activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
- In-store and phone revenue joining Meta's optimization loop, drawn from your Copper account pipelines by Google Workspace sales teams on Copper.
The click, the conversion, and the credit.
The conversion happens off Meta, 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 Meta's offline optimization straight from Copper account pipelines.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Copper, reading only your Copper account pipelines to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.
-
Map
Signals reads your Copper account pipelines, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.
-
Deliver
On each run, Signals pulls your Copper account pipelines, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the records that changed, with Meta's 62-day event window 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 /offline_conversions source=copper.closed_deals
- event_name "Purchase" · event_time 2026-07-16T08:54:46
- value 40298.00 · currency GBP
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-91086"
- ✓ accepted match=84%
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 Meta Offline CAPI
ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…
Learn moreAsked on almost every call.
How often does the Copper Meta Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly Copper sync of your Copper account pipelines into Meta. Since Signals sends only the records that changed, in-store and phone revenue joining Meta's optimization loop keeps pace and Google Workspace sales teams on Copper watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.
What match rate should a Copper-sourced Meta Offline CAPI batch expect?
In Copper, match rate tracks the email and phone quality your Copper account pipelines carry. Clean identifiers land for Meta; blank ones never will. The first Offline Conversions API report shows Google Workspace sales teams on Copper where Meta's 62-day event window needs work, a data-quality task handled in Copper.
NEXT STEP