Customer data glossary

Journey orchestration

By Art Kukharenko · Published · Updated

Browse learn glossary resources

Journey orchestration coordinates messages and actions across channels over time for each customer, moving them through defined paths based on their behaviour, data and consent.

Part of the Learn hub and the customer data glossary.

What it means in practice

A journey is a sequence of steps for one person over time: a trigger (opened an account, missed a payment), conditions that test attributes, waits, branches, actions in one or more channels, and exit criteria. Orchestration is the engine that tracks where each person is, evaluates the conditions and fires the actions across email, SMS, push, call-centre tasks and advertising audiences.

It differs from a campaign, which is a single send to a segment, and from next best action, which makes one decision. Journeys keep state per person, and that state is personal data: deletion requests must cover it, and a person who leaves must leave every journey.

The consent problem is the central design issue. Consent and suppression must be checked at each step, not only at entry, because someone who withdraws consent on day two must not receive the day-five marketing message. Keep service messages and marketing messages in separate flows with separate legal bases. Frequency caps across journeys stop one person receiving several welcome sequences from different teams.

Operational risks include duplicates after retries, so actions should be idempotent, and replays that re-trigger old journeys, so replay must not fire live actions.

Example (health insurer): a new-member journey sends a welcome message, waits, then reminds the member about screening eligibility. A member who opts out of marketing leaves the marketing steps immediately while plan notices continue, and the screening message uses only the minimum data needed and does not mention a condition.

Where it matters

Frequently asked questions

How is it different from marketing automation?

Marketing automation often runs per-channel workflows. Orchestration coordinates across channels using a unified profile and shared consent, so one person experiences one plan.

Do journeys need real-time data?

Only for time-critical steps. Many journeys run on batch refreshes, but consent changes should be applied in real time.

Where should journey state live?

With the orchestration engine, but keyed to the person ID so that deletion, suppression and audit can find it.

Back to the customer data glossary or the Learn hub.

Further reading

Published: · Updated:

Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.

Need help?

Ask the PrivyCDP Assistant