CONNECTIONS / Copper
Copper + Datahash: turn Gmail-native pipeline into ad signals.
Copper logs a deal's whole history straight out of Gmail, but ad platforms never see any of it. Signals reads Opportunity stage changes and closed-won value out of Copper into Meta, Google, and LinkedIn as conversion events.
- ● copper :: signals live
- > read opportunities pipeline=sales stage=won rows=1,734
- > read people list=customers
- hash sha256(email,phone) scope=leads.read
- route meta · google · linkedin
- ✓ 3 destinations synced · match 83%
The signal Copper yields, and receives.
Every kind of signal that moves between Copper and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A Copper Opportunity moving to a later pipeline stage posts as a conversion event, so campaigns optimize on real sales movement instead of the Gmail thread that started it.
- Lead conversions
- Opportunities marked won leave Copper with their value attached, arriving on ad platforms as offline conversions rather than a generic lead event.
- Custom audiences
- People and Company records are hashed before they leave Copper, so a customer list becomes an audience without a raw email ever crossing the wire.
- Lead generation inbound
- A custom field on a Lead or Opportunity in Copper appears in the visual mapper without a rebuild, so a change to your pipeline never breaks the feed.
Pick your platform. Every use case for it, in one place.
Every way Copper data moves, grouped by platform and ranked by how many use cases Copper supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Copper with a scoped, reversible integration user.
-
Map pipelines
Map Opportunity pipeline stages to events in the visual mapper.
-
Hash and consent
Hashing and consent flags are applied the moment a record is read.
-
Deliver
Go live with per-destination delivery status and match rate reporting.
Copper questions, answered.
Which Copper stage changes can fire events?
Any Opportunity pipeline stage you choose can fire an event, including custom pipelines built around Projects or non-sales Items. Most Copper users map the stage where a deal turns real, not the moment a Lead first appears, so ad platforms optimize on qualified pipeline instead of every inbox reply logged from Gmail.
Does Datahash read our Gmail data through Copper?
No, Datahash only reads the Copper records granted through a scoped integration user, such as People, Companies, and Opportunities. Gmail messages that Copper logs against a contact stay inside Copper, and Datahash never touches the mail API directly. Access can be revoked from Copper at any time without contacting support.
How fast do stage changes reach the ad platforms?
Stage changes reach ad platforms in near real time where the destination accepts event triggers, and on a short schedule where it does not. A Copper Opportunity update is read, hashed, and routed on that cadence, and the live debugger shows per-destination match feedback so a stalled sync is visible right away.
NEXT STEP
See your Copper data working in every ad platform.
Ready to enable a use case, or still mapping what Copper data could do? Our team helps you find the right place to start.
