Segment HubSpot destination
You already have the eventsZoody is the HubSpot destination.
Your team spent quarters getting identify and track calls right. Stop pouring those events into a black box. Zoody turns your existing Segment spec into HubSpot contact and company properties RevOps can act on.
Quick answer
Zoody is a Segment destination that aggregates your existing track and identify events into HubSpot contact and company properties. Your Segment spec is the source of truth. Zoody handles the HubSpot side: field types, lists, rolling windows, identity resolution, rate limits.
The data flow
Same shape as any other Segment destination, with HubSpot-aware aggregation in the middle.
Segment
Sources, identify, track, group, Personas / Engage audiences.
Zoody (destination)
Aggregates events, resolves identity, maps to HubSpot fields.
HubSpot
Contact + company properties. Lists. Workflows fire instantly.
What you can do once it is wired
The Segment events you already have, finally usable in HubSpot workflows.
Reuse your existing identify and track schema
The traits you set in identify calls become HubSpot contact properties. The events in your spec become aggregated property values. No second taxonomy, no remapping. The naming convention you wrote into your tracking plan is the one HubSpot ends up with.
Group calls become HubSpot company properties
If you fire group() calls for B2B accounts, Zoody routes group traits and group-scoped events onto the matching HubSpot company. Account managers see roll-ups (active users, MRR, key event count) on the company record without leaving HubSpot.
Personas / Engage audiences as HubSpot lists
Audiences computed in Segment Personas sync to HubSpot active lists. Membership stays in lockstep. No more 'why is this person in the Segment audience but not the HubSpot list' drift.
Rolling-window aggregations on contact records
Zoody computes things like zo_logins_7d, zo_value_30d_sum, zo_last_active_at from your Segment events. The math runs on Zoody's side. HubSpot just sees a fresh property value, no warehouse round-trip.
Multi-source routing
If marketing-site, app, and backend each have their own Segment source, Zoody can selectively listen to specific writeKeys. You don't accidentally pollute HubSpot with marketing pageview noise from anonymous traffic.
Lifecycle stage automation
A specific Segment event (Trial Started, Activated, Paid) flips a HubSpot property and Zoody-stamped lifecycle stage. The HubSpot workflow you already have on lifecycle stage transitions takes it from there.
Wiring Segment to HubSpot via Zoody in four steps
- 1
Add Zoody as a Segment destination
Pick Zoody from the Segment destination catalog. Connect it to the source(s) you want to forward. Zoody is added with a write key Zoody generates - copy it from your Zoody dashboard, paste into Segment, save.
- 2
Choose which events Segment sends to Zoody
Use Segment's standard event filtering UI to control which events flow to Zoody. Most teams forward identify, group, and a curated set of business-critical track events. Pageviews from anonymous traffic usually stay off.
- 3
Authorize Zoody on the HubSpot side
OAuth into HubSpot. Zoody requests scopes for contacts, companies, lists, and timeline events. The flow is one click for HubSpot Super Admins. Zoody manages refresh tokens.
- 4
Map traits and events to HubSpot properties
In Zoody's mapping UI, pick a Segment trait or event, pick the destination HubSpot property, pick aggregation. Most teams ship 8-12 mappings in the first sitting. Toggle on, and HubSpot starts updating within 30 seconds of the next event.
What you would do without Zoody
Three patterns Segment customers usually start with. They each break at a different scale.
Segment's native HubSpot destination, alone
Forwards events, writes raw traits, syncs Personas audiences as lists. No aggregations, no rolling windows, no field-type coercion, no group rollups onto company records. PQL scoring and lifecycle automation hit the ceiling within weeks.
Segment Functions writing directly to HubSpot via the API
Possible. You're now maintaining JavaScript in Segment, owning HubSpot rate limits, error handling, idempotency, and identity resolution. Every mapping change is a deploy. RevOps can't change anything without an engineer.
Segment warehouse load to dbt to reverse ETL to HubSpot
The full warehouse stack on top of Segment. Justifiable if HubSpot is one of many destinations. Hard to justify if you only need product data in HubSpot. Latency goes from seconds to tens of minutes, and the bill goes from hundreds to thousands per month.
Frequently asked questions
How is this different from Segment's native HubSpot destination?+
Segment's native HubSpot destination forwards individual events and writes basic profile traits. Zoody handles aggregations (count of event in last 7 days, sum of value, last value, rolling window), HubSpot field-type coercion, list membership, group/account rollups, and a UI for RevOps to manage mappings without touching Segment. The native destination is great for forwarding pageviews. Zoody is what you need for PQL scoring, lifecycle automation, and account-based plays.
Do I need to change my Segment implementation?+
No. Zoody is a Segment destination, same as any other. You add it from the Segment catalog, point it at your existing source, and pick which events flow through. Your identify and track calls don't change. Your spec doesn't change. The events you've been collecting for years are the events Zoody works with.
Does Zoody support Segment Personas / Engage audiences?+
Yes. Personas / Engage audiences sync to HubSpot active lists or contact properties via Zoody. Computed traits sync to HubSpot custom properties. The audience name and definition stays in Segment, the membership shows up in HubSpot.
What about server-side vs client-side events from Segment?+
Both are supported. Zoody receives the events Segment forwards regardless of source - browser, mobile SDK, server library, Functions. We respect the writeKey scope. If you have separate sources for marketing site, app, and backend, you can route different events to Zoody from each.
How does identity resolution work between Segment and HubSpot?+
Zoody honors Segment's userId and anonymousId. Matching to HubSpot is by email primarily, with userId as a fallback when email isn't yet known. Pre-identify events get buffered and replayed once an identify call provides an email. You don't lose anonymous activity that becomes attributable later.
Use the events you already pay Segment for
Beta access while we're tuning the Segment destination on real workloads. Direct line to the engineering team. Free for the duration of the program.