ReddRadar
Agent skill
activation
Configures CDP activations for exporting segment/journey audiences to external destinations. Covers connection discovery, activation YAML structure, schedule options (daily/weekly/monthly/cron), column selection with masking, behavior data export, and notifications. Use when setting up destination exports for segments, configuring journey activation steps, or setting up schedules and column mappings. Always run `tdx connection list` and `tdx connection schema` first.
Install this agent skill to your Project
npx add-skill https://github.com/treasure-data/td-skills/tree/main/tdx-skills/activation
SKILL.md
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_configfields per connector type (SFMC, S3, BigQuery, etc.) - segment - Segment rule syntax
- journey - Journey structure and activation steps
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
treasure-data/td-skills
email-campaign
This skill should be used when the user asks to "create an email", "build an email campaign", "design an email template", "generate an email for a segment", "preview an email", or "push an email to Engage". Generates enterprise-grade HTML email templates with live preview in Treasure Studio and natural language editing, then pushes the final version to Treasure Engage.
treasure-data/td-skills
action-report
YAML format reference for action reports rendered via preview_action_report. MUST be read before writing any action report YAML — defines the report structure (title, summary, actions array) and action item fields (as_is, to_be, reason, priority, category, impact) with incremental build workflow. Required by seo-analysis and any skill that produces prioritized recommendations.
treasure-data/td-skills
grid-dashboard
YAML format reference for grid dashboards rendered via preview_grid_dashboard. MUST be read before writing any dashboard YAML — defines the page structure, 6 cell types (kpi, gauge, scores, table, chart, markdown), grid layout rules, cell merging syntax, and incremental build workflow. Required by seo-analysis and any skill that produces visual data dashboards.
treasure-data/td-skills
seo-analysis
Runs SEO and AEO (Answer Engine Optimization) analysis on websites or specific pages. Use when the user mentions SEO, AEO, search rankings, search optimization, or wants to analyze how their pages perform in search engines and AI answers. Produces a data dashboard and action report with before/after recommendations.
treasure-data/td-skills
aps-doc-core
Core documentation generation patterns and framework for Treasure Data pipeline layers. Provides shared templates, quality validation, testing framework, and Confluence integration used by all layer-specific documentation skills.
treasure-data/td-skills
aps-doc-id-unification
Expert documentation generation for ID unification layers. Documents identity resolution algorithms, merge strategies, match rules, entity graphs, and multi-workflow orchestration. Use when documenting ID unification processes.
Didn't find tool you were looking for?