A journey that starts "when a contact enters this segment" only works if the data layer and the execution layer agree on who just entered. On Orbit they are the same system: dynamic segments recompute on the CDP continuously, and the journeys bound to a segment pick up every new entrant on the next refresh tick — no webhook to an external data layer, no nightly audience export, no polling job you have to babysit.
This post covers what shipped, how enrollment behaves once the contact is in, and the three-step setup for your first segment-triggered journey.
What shipped
Pick a segment as your journey's entry audience. In the journey builder, the Audience Entry trigger accepts a dynamic segment the same way it accepts a list or all contacts. Once the journey is running, every contact who newly qualifies for that segment is enrolled automatically from then on.
One click from a segment to a journey. On the Segments page under Audience, each segment carries an "Enroll in journey" action that opens the journey builder with that segment already wired as the entry audience. The Segments page also shows which journeys a segment already drives, so you can tell at a glance whether a segment is powering automation or sitting idle.
Live enrollment on every refresh tick. Segment membership recomputes on the cadence you set per segment — as often as every minute for a high-velocity segment like "signed up today," or hourly, daily, weekly, or monthly for slower-moving ones. Each tick compares membership against the previous snapshot and enrolls only the contacts who newly entered, so the journey sees entrants as the segment sees them, as close to real time as your cadence allows.
How enrollment behaves once the journey is running
Three mechanics keep the trigger safe to leave on:
- A contact mid-journey is not re-enrolled. If the same contact re-qualifies for the segment later while an earlier enrollment is still active, the duplicate is dropped — one live pass per contact per journey. Concurrent refresh ticks racing the same contact settle into a single enrollment, not two copies of the same flow.
- Entry pacing is yours. Journeys carry an entry rate limit, so a segment that gains 10,000 contacts after a backfill or a filter change feeds the journey at the hourly pace you set instead of firing all at once.
- Consent gates at send time. Every message step still passes the contact's consent checks before anything leaves — the trigger decides who enters, not whether channel rules apply.
Wire your first segment-triggered journey in three steps
- Build or pick the segment. Under Audience → Segments, define the segment with the rule builder — for example, contacts whose first signup event landed in the last day, or engaged contacts gone quiet for 30 days. Set its auto-refresh cadence to match how fast the journey should react.
- Enroll it in a journey. Use the segment's "Enroll in journey" action to land in the journey builder with the segment pre-selected as the Audience Entry trigger, then lay out the steps — messages across SMS, email, WhatsApp, or voice, with waits and branches between them.
- Launch and watch the segment page. Save and launch. The Segments page shows the segment's journey binding, and the journey's enrollment analytics report entrants as refresh ticks pick them up.
Existing journeys do not change: journeys triggered by CDP events or manual enrollment behave exactly as before, and the same canvas and steps apply to the segment trigger.
Where this fits in the stack
The segment-to-journey path closes the loop the native CDP started: identity resolution, the unified profile, and dynamic segments now feed execution without a reverse-ETL hop or a second marketing-automation product. "Send this flow to whoever qualifies today" reads the segment's live membership, evaluated where the events already land. For the wider data-layer decision — when a standalone CDP still earns its place — see the CDP vs CRM vs warehouse vs lake decision tree and the native CDP launch post; the journey builder comparison shows where an embedded CDP sits against CRM-first stacks on this exact trigger.