Segment
Send events, user identifications, and group data to Segment for customer data routing. Use Zeotap to push warehouse data into your Segment pipeline.
Prerequisites
- A Segment account
- A Segment source Write Key
Authentication
Segment uses Write Key authentication.
- In Segment, go to Connections > Sources
- Create or select a source (e.g., HTTP API source)
- Copy the Write Key from the source settings
- Paste it into the Write Key field in Zeotap
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Data Center | Select | Yes | Segment data center: United States or European Union. Default: US |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Event Type | Select | Yes | Type of Segment API call: Identify (user traits), Track (events), or Group (company/org traits) |
Supported Operations
Sync Modes: Upsert, Insert
Audience Sync Modes: Add, Upsert
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Event Type | Required Fields |
|---|---|
| Identify | user_id |
| Track | user_id, event |
| Group | user_id, group_id |
Default Destination Fields
Identify: user_id, anonymous_id, email, name, phone
Track: user_id, event, properties, timestamp
Group: user_id, group_id, traits
Realtime syncs
A Segment destination can also receive a realtime sync from a realtime audience: one person at a time, within seconds of the event that changed their answer, rather than a list on a schedule. The same destination — data center and write key — serves both.
Each change is one identify call for the person’s userId (the audience’s destination key) that sets one trait you name to true when they join and false when they leave, the way Segment’s own audiences mark people. Every destination, warehouse and Unify profile connected to that Segment source receives it like any other trait. Leaving changes only that trait. Two things to know:
- A leave can create a profile. Segment has no way to update only people it already knows, so a leave for someone Segment has never seen creates a profile holding only the trait set to
false. It is in no audience built on the trait being true. - Some refusals are silent. Segment answers success to every call except an oversized or malformed one, so a refused change can count as sent. The usual cause is a write key from the other region than the destination’s data center: Segment accepts the call and the data never arrives. Check the source’s Debugger in Segment when changes do not show up.
Settings and the full behaviour are under Realtime Syncs → Segment.
Troubleshooting
Invalid Write Key
Ensure the Write Key is from a valid Segment source. The source must be enabled and not archived.
Events not flowing to downstream destinations
Verify that your Segment source has downstream destinations connected and enabled. Check the Segment Debugger for incoming events.
Wrong data center
US and EU workspaces have different endpoints. Ensure you selected the correct data center.