CONNECTIONS / Freshsales
Freshsales + Datahash: score-qualified deals become ad signals.
Freddy AI scores leads and moves deals across the Freshsales kanban, but that scoring never reaches the campaigns that sourced them. Signals reads deal stage and score changes out of Freshsales into Meta, Google, TikTok, and Snap as conversion events.
- ● freshsales :: signals live
- > read deals stage=won rows=4,927
- > read contacts score>=70 (freddy)
- hash sha256(email,phone) scope=deals.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 82%
The signal Freshsales yields, and receives.
Every kind of signal that moves between Freshsales and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A Deal moving to a later kanban stage in Freshsales posts as a conversion event, so campaigns optimize on real pipeline movement instead of the first lead capture.
- Lead conversions
- Deals marked won leave Freshsales with their value attached, landing on ad platforms as offline conversions with revenue intact rather than a flat conversion count.
- Custom audiences
- Contact and Account identifiers are hashed before they leave Freshsales, so an audience built from a customer list never exposes a raw email or phone number.
- Lead generation inbound
- A Freddy AI lead score or a custom field on a Contact or Deal appears in the visual mapper as soon as it exists, so scoring changes never require a new build.
Pick your platform. Every use case for it, in one place.
Every way Freshsales data moves, grouped by platform and ranked by how many use cases Freshsales 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 Freshsales with a scoped, reversible integration user.
-
Map stages
Map deal stages and Freddy AI score thresholds 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.
Freshsales questions, answered.
Which Freshsales stage changes can fire events?
Any Deal stage or lead status you configure in Freshsales can fire an event. Most teams map the stage where Freddy AI marks a lead as sales-qualified, plus closed-won, and leave earlier kanban stages to build audiences instead of feeding the bidding algorithm on cold pipeline.
Is customer PII stored by Datahash?
No, identifiers are SHA-256 hashed at the moment they are read from Freshsales, and Datahash Cloud stores no raw PII on its servers. A self-hosted Core deployment runs the identical mapping for organizations whose data cannot leave their own infrastructure at all.
How fast do stage changes reach the ad platforms?
Stage changes reach ad platforms in near real time, not on an overnight batch. A Deal update in Freshsales is read, hashed, and routed to every connected destination on that cadence, and the live debugger reports per-platform match feedback so you can confirm delivery instead of waiting to see it in a campaign report.
NEXT STEP
See your Freshsales data working in every ad platform.
Ready to enable a use case, or still mapping what Freshsales data could do? Our team helps you find the right place to start.
