rt-setup-triggers

RT 2.0 Triggers Setup - Complete Workflow

Orchestrates the complete RT triggers/journey setup: parent segment validation → use case discovery → data exploration → RT config → journey creation → activation deployment.

Prerequisites

• TD CLI installed: tdx
• Authenticated: tdx auth setup
• Parent segment created in Data Workbench
• Master API key with full permissions: export TD_API_KEY=your_key
• Webhook endpoint or integration configured (optional)

Workflow Overview

Complete workflow with checkpoints at each step.

Step 1-7: RT Infrastructure Configuration ✓ (SHARED with rt-setup-personalization)
Step 8: Create RT Journey ✓
Step 9: Create Activation ✓
Step 10: Configure Journey Stage & Entry Criteria ✓
Step 11: Wait for RT Infrastructure Ready ✓
Step 12: Launch Journey ✓
Step 13: Verify & Test ✓

---

Steps 1-7: RT Infrastructure Configuration

SHARED STEPS - See steps/01-07-shared-rt-config.md which references:

• rt-setup-personalization/steps/01-02-validate-discovery.md
• rt-setup-personalization/steps/03-06-data-exploration.md
• rt-setup-personalization/steps/07-rt-config.md

Quick Summary

Step 1: Validate parent segment RT status

tdx ps rt list --json | jq '.[] | select(.id=="<ps_id>") | {id, name, rt_status: .status}'

Step 2: Use case discovery (Welcome Journey, Cart Abandonment, High-Value Purchase, etc.)

Steps 3-6: Data exploration (batch attributes, event tables, ID stitching, RT attributes)

Step 7: Configure RT infrastructure

# Configure event tables, key events, RT attributes, ID stitching
# Wait for RT status "ok"
while [ "$(tdx ps rt list --json | jq -r --arg ps '<ps_id>' '.[] | select(.id==$ps) | .status')" != "ok" ]; do
  sleep 10
done

Checkpoints:

• ✓ Parent segment validated
• ✓ Use case selected (journey trigger)
• ✓ Event tables configured
• ✓ RT attributes created
• ✓ ID stitching configured
• ✓ RT status is "ok"