What Segment is
Segment is a customer data platform: a single collection point that fans events out to every downstream tool.
That makes it the highest-leverage place to get identity right, and the most expensive place to get it wrong.
- Home
- Integrations
- Segment
Segment integration: identity-resolved events and contacts
Send server-side, identity-resolved events to Segment so everything downstream of your CDP inherits one version of the customer.
- Role
- Destination
- Category
- Analytics & CRM
- Plans
- All plans
About Segment
Upstack sends server-side, identity-resolved events into Segment, so everything downstream inherits one version of the customer rather than each tool resolving separately and differently.
Getting resolution right once, upstream of the fan-out, is structurally cheaper than correcting it in every destination.
How Segment works
Segment collects events from your sources and routes them to destinations, applying identity resolution based on the identifiers each event carries. Its output is only as good as its input: an anonymous event fanned out to twelve tools is anonymous in all twelve.
What you can do with it
Three jobs this connector does inside Segment.
01
Send complete conversions
Conversions reach Segment through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.
02
Optimize on the customer you want
Map any order attribute to the conversion Segment receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.
03
Resolve once, upstream of the fan-out
Events arrive already resolved, so every downstream destination inherits the same customer rather than each one guessing separately.
Documentation
Set-up reference.
Set-up, event schema and field mapping for Segment as a destination.
FAQ
Segment integration questions.
What does Upstack send to Segment?
Send server-side, identity-resolved events to Segment so everything downstream of your CDP inherits one version of the customer.
Which plans include the Segment integration?
All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.
Will Upstack slow down my store?
Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.
Similar integrations
Other destinations to send to.
-
HubSpot CRM records that match what actually happened. -
PostHog Analysis on a person, not a session. -
Loops Lifecycle messaging on resolved customers. -
ActiveCampaign Automation and segmentation on resolved contacts. -
Meta Conversions API Conversions API with higher Event Match Quality. -
Google Ads Conversions Enhanced Conversions that actually match. -
TikTok Events API Events API with a resolved customer attached. -
Pinterest Conversions API, deduplicated server-side. -
Snapchat Conversions API with restored identifiers. -
Reddit Conversions API for a community-led audience. -
Microsoft Ads UET conversions with restored identifiers. -
X Conversions API, deduplicated server-side.
Get Segment tracking right.
A 15-minute walkthrough tailored to your stack and channels.