How-to guideSourcesAvailable
Shopify to Segment
Route Shopify events and customer identities through Segment using Vendo's canonical Shopify event model and Segment destination.
Last reviewed July 13, 2026
Use this workflow when Segment should receive normalized Shopify events for downstream routing. Vendo emits Segment track and identify calls while preserving stable event and customer identifiers.
Before you start
- Connect Shopify and verify storefront tracking.
- Create or choose a Segment HTTP API source.
- Copy its write key and confirm the target Segment workspace.
- Decide how Shopify customer and anonymous IDs should map into Segment.
Data sent to Segment
| Segment call | Shopify data |
|---|---|
track | Storefront, checkout, order, fulfillment, cancellation, and refund events |
identify | Known customer profile traits and commerce totals |
| Context | Event time, source, UTM values, click IDs, and stable message ID |
Use Shopify data model for canonical event semantics and Segment events and properties for the destination mapping.
Configure the destination
- Open Data → Integrations → Destinations and add Segment.
- Enter the Segment write key and test the connection.
- Create or update the Shopify integration.
- Select Segment as the destination and choose the required data types.
- Save and run a small recent window.
Verify
- Open the Segment source debugger.
- Trigger a Shopify storefront event and a test order.
- Confirm both events arrive with the expected
messageId,anonymousIdoruserId, timestamp, and commerce properties. - Confirm the events continue to the Segment destinations you expect.
Troubleshooting
| Symptom | Check |
|---|---|
| No events in Segment | Write key, target source, Shopify tracking, and Vendo job state |
| Events arrive but do not route | Segment destination filters and protocols |
| Duplicate events | Stable message ID and overlapping backfill windows |
| User history is split | Anonymous-to-known identity mapping |
Related
Last updated on