CONNECTIONS / Salesforce
Salesforce data, synced to every ad platform you buy on.
Lead status, opportunity stage, and closed-won revenue sit in Salesforce while ad platforms optimize on form fills. Signals reads your Salesforce object model and syncs qualified stages, offline purchases, and audiences back to Meta, Google, TikTok, Snap, and LinkedIn.
- ● salesforce :: signals live
- > Opportunity closed-won value=48,500 AED
- > Lead status change MQL→SQL
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · snap · linkedin
- ✓ 5 destinations synced · match 91%
The signal Salesforce yields, and receives.
Every kind of signal that moves between Salesforce and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Closed-won Opportunity revenue and offline purchase records leave Salesforce hashed and matched back to the campaign that sourced the deal.
- Lead conversions
- Lead status changes and Opportunity stage moves become conversion events the moment a record updates, not a nightly export.
- Custom audiences
- Saved reports and list views become hashed, scheduled audiences without a CSV touching anyone's desktop.
- Lead generation inbound
- Campaign lead submissions land as Salesforce Leads in real time, deduped against existing records before creation.
Pick your platform. Every use case for it, in one place.
Every way Salesforce data moves, grouped by platform and ranked by how many use cases Salesforce supports.
- 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.
-
Authorize
Connected App authorization scoped to Lead, Opportunity, and Campaign Member objects, revocable from Salesforce at any time.
-
Map stages
Lead status and Opportunity stage values mapped to platform events in the visual mapper, including custom stages.
-
Hash and consent
Identifiers hashed with SHA-256 and consent status applied before anything leaves Salesforce.
-
Deliver
Delivery to every mapped destination with per-stage match reporting.
Salesforce questions, answered.
Does Datahash need admin access to our Salesforce org?
No. Datahash connects through a Connected App scoped to the objects you choose, typically Lead, Opportunity, and Campaign Member, and nothing else. Access is read-only unless a use case specifically requires writes, and the connection can be revoked from Salesforce at any time without waiting on us.
Can the mapper handle our custom Salesforce fields and stages?
Yes. Most Salesforce orgs run custom picklists, multi-step approval stages, or renamed fields, and the visual mapper reads your actual schema instead of assuming a standard one. You choose which custom stage or field maps to which platform event during setup, and the mapping can change later without a new integration project.
How fast do Salesforce updates reach the ad platforms?
Most updates arrive in near real time, picked up as platform events as soon as a Lead status or Opportunity stage changes in Salesforce. Teams that prefer a lighter footprint can run scheduled syncs instead, anywhere from hourly to daily, and the cadence is a setting you choose, not a rebuild.
We are migrating onto Salesforce from another CRM. Can Signals run on both during the transition?
Yes. Signals can read from Salesforce and a second CRM in parallel and dedupes on external ID, so a lead or opportunity tracked in both systems counts once at the ad platform, not twice. Most migrations run this way for a few weeks until the old system is retired and Salesforce becomes the only source.
NEXT STEP
See your Salesforce data working in every ad platform.
Ready to enable a use case, or still mapping what Salesforce data could do? Our team helps you find the right place to start.