Yes. Twilio Segment has a HubSpot destination in its Catalog that accepts Page, Group, Identify and Track calls. You authenticate with a HubSpot Private App Token and enter your Hub ID. Segment also points to newer HubSpot Cloud Mode (Actions) and HubSpot Web (Actions) destinations.
Segment the data platform, not audience segments
This is about Twilio Segment, the customer data platform that collects events from your site and apps and sends them on to other tools. If you meant splitting your audience into groups, my guide to customer segmentation tools is the one you want.
Which HubSpot destination to pick
| Destination | What Segment says | Modes |
|---|---|---|
| HubSpot (Classic) | Accepts Page, Group, Identify and Track calls; newer versions available | Device-mode on web and mobile, Cloud-mode on server sources |
| HubSpot Cloud Mode (Actions) | A newer version Segment points to | Cloud mode |
| HubSpot Web (Actions) | A newer version Segment points to | Web |
The Classic destination is called HubSpot in the Integrations object, and its Analytics.js version is open source. Because Segment flags newer versions on the Classic page, check the Actions destinations first if you're starting fresh.
Setting up the connection
- In HubSpot, create a Private App and give it the scopes Segment needs.
- In Segment's Catalog, search for HubSpot and choose your sources.
- Paste the Private App Token and enter your Hub ID.
- Activate the destination, and allow time for the change to reach the Segment CDN.
HubSpot no longer allows new connections to authenticate with an API Key, so new set-ups must use a Private App Token. Segment lists the scopes: business-intelligence, crm.objects.contacts.read and write, crm.schemas.contacts.read, crm.objects.companies.read and write, and crm.schemas.companies.read.
After activation, changes take about 45 minutes to reach the Segment CDN before Analytics.js starts loading the HubSpot snippet. If nothing happens in the first few minutes, that's normal. Don't keep toggling the destination off and on while you wait, since each change has to make the same trip.
Why your contact wasn't created
Device mode has a rule that trips people up. An Identify call must include traits.email, and it must be followed by a Page or Track call, before HubSpot creates or updates the contact. An Identify on its own does nothing. Cloud mode is different: it updates records without needing a follow-up call.
Traits cause the second set of problems. HubSpot doesn't accept trait keys with upper case letters or spaces, so Segment lowercases custom traits and replaces spaces with underscores. A trait called Plan Type arrives as plan_type. And HubSpot removes any traits that aren't contact fields in HubSpot, so create the matching contact property first or the data's dropped.
Testing without the Event Tester
Segment Docs, on the HubSpot (Classic) destination, flag the gap. This destination isn't compatible with the Segment Event Tester, so you'll need other tools to troubleshoot. Combine that with device mode's email-plus-follow-up rule and the newer Actions versions, and it's easy to lose an afternoon wondering why a test user never appeared.
A practical check: identify one test user with an email, fire a Page call straight after, wait, then search for that email in HubSpot. If the contact's there but a trait isn't, look at the property name and whether it exists in HubSpot. My HubSpot setup checklist covers creating properties before data arrives.
RudderStack and PostHog as other routes
RudderStack has a HubSpot destination that sends events in cloud mode or device mode, and can connect a Reverse ETL source to HubSpot. PostHog lists HubSpot among its data pipeline destinations for sending event data onward. If you're still choosing where customer data should live, see my guide to customer database software.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My take for marketing and data teams
Yes, Segment connects to HubSpot, but start with the Actions destinations and use a Private App Token with the listed scopes. In device mode, always send an email on Identify followed by a Page or Track call. Create HubSpot contact properties for every trait you send, in lowercase with underscores.
A quick example: a software company sends a Track call called Trial Started with a trait called Plan Name. In HubSpot, they first create a contact property named plan_name. Then every trial user who's identified with an email lands as a contact with their plan attached, ready for a sales follow-up list. Skip the property and the plan quietly disappears, even though the contact arrives.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Segment connect to HubSpot?
Yes, through a HubSpot destination in the Catalog.
How do I authenticate?
With a HubSpot Private App Token plus your Hub ID; new API keys aren't allowed.
Which calls does it accept?
Page, Group, Identify and Track.
Why isn't my contact created?
In device mode, Identify needs an email and a following Page or Track call.
Is there a newer destination?
Segment points to HubSpot Cloud Mode (Actions) and HubSpot Web (Actions).
