Question 1

Which delivery events reach Segment?

Accepted Answer

Label created, picked up, in transit, out for delivery, delivered, and delivery exception, each with a timestamp and the carrier that reported it. Return events carry the reason code. Events stream as they happen, so post-purchase behavior in Segment lines up with what the customer experienced.

Question 2

How do I use delivery data for segmentation in Segment?

Accepted Answer

Delivery outcome becomes a customer property alongside the behavioral data you already collect. Build segments for customers who had a late delivery, customers who return above a threshold, or customers who consistently choose expedited service, and treat each group differently.

Question 3

Can I trigger campaigns from delivery status?

Accepted Answer

Yes. A delivered event can start a review request, an exception can start a proactive apology before the customer writes in, and a return can start a win-back sequence. The trigger fires from the shipment event itself, so timing matches the delivery.

Question 4

How does returns data appear in Segment?

Accepted Answer

Returns arrive with reason code, product, channel, and the original order, so return rate breaks down by any of those dimensions. Pairing return reasons with delivery outcomes separates a product problem from a fulfillment problem.

Question 5

Why send delivery events through Segment?

Accepted Answer

One connection. Segment already routes events to the tools your team uses, so delivery events reach all of them the moment they are sent, and adding a destination later is a change in Segment.

Question 6

What identifies the customer on each event?

Accepted Answer

Its order and customer travel with the event, using the identifiers Segment already has for them, so the event reaches the right profile downstream.

Question 7

What access does CommerceShip need to Segment?

Accepted Answer

The connection uses scoped credentials limited to the record types the integration works with, and you choose which fields are included. Credentials are encrypted at rest and stored separately from your operational data. Revoke the connection from either side at any time and the access ends with it.

Question 8

How is my data protected?

Accepted Answer

TLS in transit and AES-256 at rest, with tenant isolation enforced by row-level security in the database. Role-based permissions control who on your team can see cost data or change carrier settings, and automated actions are written to an audit log. CommerceShip is pursuing SOC 2 Type II certification. The security page carries the full detail.

Event	Order #	Tracking #	Status
order.shipped	#1052	1Z 999 AA1 01	Pending
shipment.delivered	#1049	9400 1000 0000	Pending
shipment.exception	#1047	7489 1234 5678	Pending

Event	Order #	Tracking #	Status
order.shipped	#1052	1Z 999 AA1 01	Pending
shipment.delivered	#1049	9400 1000 0000	Pending
shipment.exception	#1047	7489 1234 5678	Pending

Send delivery events to Segment

Segment Integration Capabilities

How the Segment integration works

Connect Segment

Choose events and properties

Stream as it happens

Segment Integration FAQs

Route delivery events through Segment

Other Customer Data Tools