Journey orchestration tips and tricks in Customer Insights — Journeys

Customer Insights — Journeys turns segment membership and event signals into automated, multi-channel customer experiences. The journey designer is approachable, but real-world journeys quickly hit subtleties: timing, suppression, branching, and the inevitable need to extend beyond the built-in primitives.

Journey types.

• Segment-based — runs continuously; new segment members enter, exit when they leave.
• Trigger-based — single event triggers a journey instance per profile.
• Series — sequential set of campaigns or events.

Trigger-based journeys are the modern pattern for behavioural marketing — actions trigger immediate, personalised follow-ups.

Triggers. A trigger is an event:

• System trigger — built-in (email opened, link clicked, form submitted).
• Custom trigger — defined event from any source via API or Power Automate.
• Dataverse trigger — record create/update/delete.

Custom triggers are the power feature — emit "Order Placed" from your e-commerce platform; trigger a confirmation journey.

Branching.

• If/then — split based on profile attributes or event details.
• Channel preference — email vs SMS based on preference.
• A/B test — two variants of the same step, comparison reported.

Deep branching becomes hard to maintain; keep journeys shallow and modular — let sub-journeys handle complex sub-flows.

Wait steps. Insert delays:

• Fixed wait — wait 3 days.
• Wait until — wait until a date, or until a recipient performs an action.
• Wait until time of day — send at 9 AM local time.

Time-of-day waits respect the recipient's time zone if it's captured — invaluable for global campaigns.

Dynamic content. Personalised content via:

• Personalization fields — {{contact.firstname}} in emails.
• Conditional blocks — show different content based on profile attribute.
• Dynamic product recommendations — pulled from connected catalog.
• Loyalty status, recent activity — context-aware references.

For high-volume campaigns, personalised content drives meaningfully better engagement.

Multi-channel. A single journey can mix:

• Email — primary channel.
• SMS — high-engagement, transactional.
• Push notification — mobile app.
• In-app message — within product surface.
• Custom channels — via API integration.

Pattern: try email first; SMS if no open within 24 hours; phone if no SMS response within 48 hours.

Suppression.

• Global suppression — opt-outs, unsubscribes.
• Journey-specific suppression — exclude profiles in other journeys.
• Frequency caps — no more than N messages per week to one profile.

Frequency cap is critical at scale; without it, recipients get bombarded as multiple journeys fire concurrently.

AI suggestions. Built-in Copilot features suggest:

• Next-best-action — given current journey state and profile.
• Subject line variations — for A/B testing.
• Send-time optimisation — when this recipient is most likely to engage.

Use as a starting point; refine with judgment.

Real-time vs scheduled journeys. Real-time journeys process events immediately; scheduled journeys batch. For transactional flows (order confirmation), real-time. For nurture campaigns (weekly newsletter), scheduled is fine.

Goal tracking. Each journey defines a goal — conversion event the journey is designed to drive:

• Goal reached — profile exits successfully.
• Conversion rate — reached / entered.
• Time to goal — average.

Without goals, journeys can't be optimised.

Common patterns.

• Welcome series — new subscriber → 3-email onboarding over 2 weeks.
• Cart abandonment — added to cart → wait → reminder → wait → incentive.
• Birthday / anniversary — date-triggered.
• Re-engagement — inactive 90 days → win-back series.
• Event invitation → reminder → post-event follow-up.

Workarounds for limits.

• Too-complex single journey → split into multiple journeys with hand-off triggers.
• No native loop → use a counter attribute and re-entry logic.
• External data needed → call Power Automate as an action step.

Reporting.

• Funnel analytics — entry, by step, exit.
• Per-step metrics — open, click, conversion per email.
• Audience overlap — how many in multiple journeys.

Common pitfalls.

• No frequency cap. Same profile in 5 active journeys; gets 20 emails a week; unsubscribes en masse.
• Trigger event noisy. Custom trigger firing wrong; journey starts for unintended audiences.
• Suppression incomplete. Customers who complained still receive next journey.
• Goal not defined. Journey can't be evaluated for effectiveness.
• Schedule miscoordinated. Two journeys send conflicting messages on the same day.
• Data dependency missing. Personalisation field empty for some recipients; broken email.

Operational discipline. Production journeys need lifecycle management: build, test with small audience, scale to full, monitor, iterate, retire. A journey shipped without monitoring becomes liability — when something breaks, the inbox tells you, not the analytics. Treat journey orchestration as engineering: testable, observable, version-controlled, retired when no longer adding value.