CONNECTIONS / Copper / Copper to Meta Custom Audience
From Copper account pipelines to Meta lookalike and suppression seeds.
Connect Copper and point Signals at your Copper account pipelines; it keeps Meta audiences synced as adds and removals so lists never drift as records change, hashed and consent-checked for Meta.
- ● copper → meta.audience :: live
- > read segments rows=62,372
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 48,650 matched
WHAT THIS ENABLES
Copper to Meta Custom Audience
Copper to Meta Custom Audience: your Copper account pipelines, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.
- Customer segments from your Copper account pipelines activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
- Lookalike seeds and suppression lists that track your live customer base, drawn from your Copper account pipelines by Google Workspace sales teams on Copper.
WHAT FLOWS WHERE
Copper to Custom Audience, mapped.
Signals reads the customer segments from your Copper account pipelines as records change, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Signals reads the customer segments from your Copper account pipelines as records change, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Built for the teams that own the number.
Google Workspace sales teams on Copper activating Meta lookalike and suppression seeds 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 Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals reads your Copper account pipelines, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.
-
Deliver
On each run, Signals pulls your Copper account pipelines, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the records that changed, with audience refresh cadence in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Copper account pipelines and sends only the records that changed.
Always-current lookalike seeds and exclusions from your Copper account pipelines, with API call volume steady because Signals sends only the records that changed.
A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Copper account pipelines.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=copper.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 62,372 · num_invalid_entries 146
- audience_id "1656133" · session "upsert"
- ✓ accepted match=78%
Adjacent moves on the same stack.
from Copper
Copper to Google Customer Match
Copper to Google Customer Match: your Copper account pipelines, hashed and consent-checked,…
Learn more
from Copper
Copper to TikTok Custom Audience
Copper to TikTok Custom Audience: your Copper account pipelines, hashed and…
Learn more
same use case
ActiveCampaign to Meta Custom Audience
ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Custom Audience
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…
Learn moreAsked on almost every call.
How often does the Copper Meta Custom Audience 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, lookalike seeds and suppression lists that track your live customer base keeps pace and Google Workspace sales teams on Copper watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.
What match rate should a Copper-sourced Meta Custom Audience 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 Custom Audiences API report shows Google Workspace sales teams on Copper where audience refresh cadence needs work, a data-quality task handled in Copper.
NEXT STEP