CONNECTIONS / Copper / Copper to LinkedIn Offline CAPI
From Copper account pipelines to LinkedIn account-revenue reporting.
Connect Copper and point Signals at your Copper account pipelines; it reports closed B2B deals so LinkedIn optimizes on account revenue as records change, hashed and consent-checked for LinkedIn.
- ● copper → linkedin.capi :: live
- > read closed_deals rows=21,172
- hash sha256(email,phone) consent=filtered
- route linkedin deliver
- ✓ delivered · 17,996 matched
WHAT THIS ENABLES
Copper to LinkedIn Offline CAPI
Copper to LinkedIn Offline CAPI: your Copper account pipelines, hashed and consent-checked, feed LinkedIn as Signals reports closed B2B deals so LinkedIn optimizes on account revenue as records change.
- Offline and in-store sales from your Copper account pipelines activated for LinkedIn, as Signals reports closed B2B deals so LinkedIn optimizes on account revenue.
- Pipeline revenue tied to the LinkedIn campaigns that sourced it, drawn from your Copper account pipelines by Google Workspace sales teams on Copper.
The click, the conversion, and the credit.
The conversion happens off LinkedIn, 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 LinkedIn account-revenue reporting straight from Copper account pipelines.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Copper, reading only your Copper account pipelines to feed LinkedIn's Conversions API, sized for long B2B attribution windows.
-
Map
Signals reads your Copper account pipelines, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.
-
Deliver
On each run, Signals pulls your Copper account pipelines, reports closed B2B deals so LinkedIn optimizes on account revenue, and sends only the records that changed, with long B2B attribution windows 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 /conversionEvents source=copper.closed_deals
- conversion "urn:lla:llaPartnerConversion:78619"
- conversionHappenedAt 1784674619000
- user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
- ✓ accepted · conversionValue 45327 USD
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 LinkedIn Offline CAPI
ActiveCampaign to LinkedIn Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
LinkedIn Offline CAPI
Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…
Learn moreAsked on almost every call.
How often does the Copper LinkedIn Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly Copper sync of your Copper account pipelines into LinkedIn. Since Signals sends only the records that changed, pipeline revenue tied to the LinkedIn campaigns that sourced it keeps pace and Google Workspace sales teams on Copper watch long B2B attribution windows. One scoped connection sets it up, cadence adjustable later.
What match rate should a Copper-sourced LinkedIn Offline CAPI batch expect?
In Copper, match rate tracks the email and phone quality your Copper account pipelines carry. Clean identifiers land for LinkedIn; blank ones never will. The first Conversions API report shows Google Workspace sales teams on Copper where long B2B attribution windows needs work, a data-quality task handled in Copper.
NEXT STEP