journey

Create CDP journey definitions in YAML using tdx journey commands.

21|24|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/treasure-data/td-skills --skill journey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/treasure-data/td-skills/tree/main/tdx-skills/journey
Command: npx skills add https://github.com/treasure-data/td-skills --skill journey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables defining and managing CDP journeys with stages, steps, activations, and versioning, all in YAML for reproducible deployment.

Core Features & Use Cases

  • Journey stages and steps with various types (wait, activation, decision_point, ab_test, merge, jump, end)
  • Embedded segments and versioning support
  • Activation integration and scheduling patterns

Quick Start

Pull journeys to YAML with tdx journey pull, then push with tdx journey push --dry-run.

Frequently Asked Questions about journey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define and orchestrate customer journeys in YAML?

CDP journey orchestration in YAML uses tdx journey commands to define stages, steps, activations, and segments. Pull existing journeys with `tdx journey pull`, edit the YAML schema (type, name, reentry, goal, journeys, stages, steps with next), then push with `tdx journey push --dry-run` to validate before deployment.

What step types are supported in CDP journey workflows?

Journey step types include wait, activation, decision_point, ab_test, merge, jump, and end. Each step routes to the next stage based on conditions, segment membership, or explicit transitions, enabling onboarding, activation, re-engagement, and retention scenarios.

Can I use embedded segments and versioning in customer journey definitions?

Yes, journey definitions support both embedded segments defined inline and external segment references, with full versioning control. This enables reproducible deployment, testing via simulation guidance, and safe rollout across customer segments.

How do activation connectors work in journey step definitions?

Activation steps execute connectors that send customers to downstream systems or channels. Step definitions include connector configuration, scheduling patterns, and segment targeting to trigger communications at the right journey stage.

What are the technical requirements for managing journey YAML schemas?

Journey YAML schemas require mandatory fields (type, name, reentry, goal, journeys, stages, steps with next) and support optional features like embedded segments, activation connectors, simulation guidance, and defined limits for scale and performance.