userId locates the recipient, and its properties become the journey’s data.
What you will build
Prerequisites
- A Segment workspace sending Track, Identify, or Group events
Set it up
1
Connect Courier as a Segment destination
In Segment, add Courier as a destination and point it at your workspace. See the for the connection details.
2
Create a journey with a Segment trigger
In the console, and choose the Segment trigger. Select the source event (for example
Order Completed). No schema is required. Courier receives whatever Segment sends.3
Narrow with conditions (optional)
Add trigger conditions to run only for the events you want, for example
properties.total > 100. Only events that pass all conditions start the journey.4
Design the flow and publish
Add send nodes and any delays or branches, referencing the event data as variables, then publish. See for the runtime model.
Verify
1
Fire the event
Trigger the event in your app, or replay it from Segment, and confirm a run appears in the journey’s Logs tab.
2
Check the data came through
Open the run and confirm the event’s properties arrived as its
data. A send node rendering empty variables usually means the property names differ from what the template expects.3
Confirm the message delivered
Step through the run to the send node, then find the message in .
A Segment
track event’s userId must be a valid Courier user for the journey to run. Identify users to Courier first, or make sure the userId matches a stored profile.