CONNECTIONS / Salesforce / Salesforce to Meta Custom Audience
Salesforce segments, mirrored into Meta Custom Audiences.
Signals watches the segment you nominate in Salesforce and keeps the matching Meta Custom Audience aligned, hashing identifiers on the way through.
- ● salesforce → meta.custom_audience :: live
- > sync segment won_customers rows=27,340
- hash sha256(email,phone)
- route meta.custom_audience upsert
- ✓ audience refreshed · 21,655 matched
WHAT THIS ENABLES
Salesforce to Meta Custom Audience
Salesforce to Meta Custom Audience keeps Meta's Custom Audiences synced with the customer segments defined in Salesforce, adding and removing members on a schedule you set so suppression, lookalike, and retention campaigns always reflect who your customers actually are.
- CRM-scored cohorts arriving in Meta Ads Manager as ready-to-use audiences.
- Lookalikes seeded from the accounts your sales team actually closed.
- Won customers dropped from prospecting audiences as soon as Salesforce records the change.
WHAT FLOWS WHERE
Salesforce to Custom Audience, mapped.
Segment updates leave Salesforce on a schedule, receive SHA-256 hashing inside Signals, and are applied to the audience through Meta's Custom Audiences API.
Segment updates leave Salesforce on a schedule, receive SHA-256 hashing inside Signals, and are applied to the audience through Meta's Custom Audiences API.
Built for the teams that own the number.
Advertisers rebuilding Meta audiences by CSV every few weeks.
Lifecycle marketers running win-back and cross-sell plays on Meta.
From kickoff to verified events.
-
Connect
Connected App access, read-only, to the Salesforce segment you select.
-
Map
Contact fields hashed into Meta's Custom Audience key schema.
-
Deliver
Audience upserts to Meta on your cadence, with accepted-size reporting.
What ships with this use case.
Prospecting spend that skips the customers Salesforce already counts as won.
Lookalike source audiences refreshed alongside your CRM data.
Cross-sell and retention segments that follow your pipeline closely.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=salesforce.segment
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 27,340 · num_invalid_entries 214
- audience_id "1208…" · session "upsert"
- ✓ accepted match=79%
Adjacent moves on the same stack.
from Salesforce
Salesforce to Google Customer Match
Salesforce to Google Customer Match keeps Google's Customer Match lists synced with the…
Learn more
from Salesforce
Salesforce to TikTok Custom Audience
Salesforce to TikTok Custom Audience keeps TikTok's Custom Audiences synced with the list…
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 Meta audience refresh from Salesforce?
Daily is typical, though anything from hourly to weekly works depending on how often the underlying Salesforce report or list view changes. Each refresh sends the members added and removed since the previous sync rather than re-uploading the whole segment, so a tighter schedule does not mean a heavier one.
What match rate should we expect from a Salesforce-sourced audience?
It depends on identifier coverage in the Salesforce records feeding the segment. Contacts with a clean, current email and phone number typically match well once hashed; records missing both fields will not match regardless of volume. We report the accepted audience size after every sync so match quality is visible, not assumed.
Can the same Salesforce segment sync to more than one Meta ad account?
Yes. One segment defined in Salesforce can push to several ad accounts under the same Business Manager, each with its own refresh schedule and accepted-size reporting, so a single report or list view supports every team running Meta campaigns off the same customer base.
NEXT STEP