tdx Activation - CDP Activation Configuration

Discovery Commands (MUST run first)

tdx connection list                    # List available connections (name + type)
tdx connection show "Connection Name"  # Show connection details
tdx connection schema "Connection Name"  # Discover connector_config fields
tdx connection settings <type>         # Show connection-level credential fields
tdx connection types                   # List all connector types

CRITICAL: Always run tdx connection list before writing activations. Do NOT guess connection names or connector_config fields.

Segment Activations

Activations are a list under activations: in segment YAML (vs. journey activations which use a key map).

activations:
  - name: SFMC Contact Sync
    connection: salesforce-marketing       # Exact name from `tdx connection list`
    columns:
      - email
      - first_name
      - last_name
    schedule:
      type: daily                          # none | hourly | daily | weekly | monthly | cron
      timezone: America/Los_Angeles
    connector_config:                      # Fields from `tdx connection schema`
      de_name: ContactSync
      data_operation: upsert
    notification:
      notify_on: [onSuccess, onFailure]
      email_recipients: [team@company.com]

Journey Activations

Activations are a key map (not a list). Steps reference keys via with.activation.

activations:
  welcome-email:                           # Key — referenced in step's with.activation
    name: Welcome Email Campaign
    connection: My SFMC Connection
    all_columns: true
    run_after_journey_refresh: true         # Common for journeys
    connector_config:
      de_name: WelcomeEmails
      data_operation: upsert

  sms-reminder:
    name: SMS Reminder
    connection: Twilio SMS Connection
    all_columns: true
    run_after_journey_refresh: true
    connector_config:
      message_template: welcome_reminder

Journey steps reference activations by key:

steps:
  send-welcome:
    type: activation
    with:
      activation: welcome-email            # Key from activations map

Column Selection

all_columns: true                # Export all columns
# OR specific columns:
columns:
  - email
  - first_name
  - name: ssn                    # With visibility control
    visibility: masked           # clear | masked

Schedule Options

Use either schedule or run_after_journey_refresh (mutually exclusive).

schedule:
  type: daily                    # none | hourly | daily | weekly | monthly | cron
  timezone: America/Los_Angeles  # none = manual trigger only
  # Advanced (optional):
  repeat_unit: week              # minute | hour | day | week | month | once | none
  repeat_frequency: 2            # Every 2 weeks
  repeat_sub_frequency: [1, 3]   # Monday and Wednesday (0=Sun, 1=Mon, ...)
  start_at: "2025-04-01T09:00:00Z"
  end_on: "2025-12-31"

# Journey alternative (instead of schedule):
run_after_journey_refresh: true

Notifications

notification:
  notify_on: [onSuccess, onFailure]    # onSuccess | onFailure
  email_recipients: [team@company.com]

Behavior Data Export

behavior:
  behavior_table: purchase_history
  join_strategy: Last              # All | First | Last | Top-N
  join_row: 10                     # Rows for Top-N
  formatting: rows                 # rows | cols
  order_by:
    - key: timestamp
      order: desc
  columns:
    - name: product_name
    - name: order_total

Common Issues

Issue	Solution
Connection name wrong	tdx connection list to verify exact name
connector_config fields unknown	tdx connection schema "Connection Name"
Activation not running	Check schedule type and parent segment refresh status

Related Skills

• connector-config - connector_config fields per connector type (SFMC, S3, BigQuery, etc.)
• segment - Segment rule syntax
• journey - Journey structure and activation steps