CONNECTIONS / HubSpot
Make HubSpot pipeline data count on every ad platform.
Ad platforms see the form fill and stop there. The rest of the story, lifecycle stages, deal stages, closed-won revenue, lives in HubSpot. Signals reads it there and returns qualified stages, offline revenue, and audiences to Meta, Google, TikTok, Snap, and LinkedIn.
- ● hubspot :: signals live
- > Deal stage change SQL→Closed Won
- > Lifecycle stage change Lead→MQL
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · snap · linkedin
- ✓ 5 destinations synced · match 88%
The signal HubSpot yields, and receives.
Every kind of signal that moves between HubSpot and the platforms, through one hashed, deduplicated route.
- Offline conversions
- When a deal hits closed-won, the revenue goes out hashed and lands as campaign credit wherever the first click or form fill happened.
- Lead conversions
- Stage mapping is event-driven: HubSpot saves the change, the platform event fires, and no batch window sits in between.
- Custom audiences
- Audiences inherit their membership from active lists directly; the concept of an export file simply stops existing.
- Lead generation inbound
- Platform lead forms feed straight into HubSpot, where each submission checks for an existing contact before creating one.
Pick your platform. Every use case for it, in one place.
Every way HubSpot data moves, grouped by platform and ranked by how many use cases HubSpot 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.
-
Authorize
One private app token covers contacts, deals, and lists; revoking it in HubSpot settings ends the connection instantly.
-
Map stages
The visual mapper pairs each lifecycle or deal stage, custom pipelines included, with the platform event it should become.
-
Hash and consent
SHA-256 hashing and a consent check happen first; only then does data leave HubSpot.
-
Deliver
Every mapped destination receives its events, and match rates report back per stage.
HubSpot questions, answered.
Does Datahash need super admin access to our HubSpot account?
No. A scoped private app token is the whole footprint, and a workspace decides which objects it can see, contacts, deals, and lists being the usual set. Reads dominate; the only writes happen when a use case creates records, platform lead ads for example. Kill switch included: revoke the token in HubSpot settings and the connection is dead that second.
Can the mapper handle our custom HubSpot pipelines and deal stages?
It has to, since almost no two HubSpot portals run the same pipeline shape. What the mapper shows you is your portal: every pipeline, every stage, renamed properties and all. A workspace decides which stage in which pipeline becomes which platform event, and mapping decisions stay editable indefinitely, so renaming a stage in HubSpot next month means updating a dropdown, not calling us.
How fast do HubSpot lifecycle and deal stage changes reach the ad platforms?
Webhooks make it event-driven: HubSpot saves the stage change, the delivery fires, and the ad platform usually knows before the rep has moved on to the next record. Batching is available for teams that want it, on any schedule from hourly to daily, and switching between the two modes later takes a settings change, nothing more.
We're mid-migration onto HubSpot from another CRM. Can Signals cover both systems at once?
It can, and migrations are a common reason teams arrive here. Both CRMs feed Signals in parallel, with external-ID dedupe deciding that a contact present in each counts once, not twice, downstream. There is no fixed cutover date required either; the second source stays live until your team declares the legacy system done, typically a few weeks in.
NEXT STEP
See your HubSpot data working in every ad platform.
Ready to enable a use case, or still mapping what HubSpot data could do? Our team helps you find the right place to start.
