sales-treasuredata

name	sales-treasuredata
description	Treasure Data platform help — enterprise AI-native CDP with profile unification, audience segmentation, journey orchestration, 400+ connectors, AI Marketing Cloud suites. Use when setting up Treasure Data CDP, unifying customer profiles across channels, building audience segments in Treasure Data, activating audiences to ad platforms or CRMs, configuring Treasure Data connectors or integrations, writing SQL queries in Treasure Data, troubleshooting Treasure Data workflows or jobs, or working with the TD API. Do NOT use for general CRM data quality without Treasure Data context — use /sales-data-hygiene instead.
argument-hint	[describe what you need help with in Treasure Data]
license	MIT
version	1.0.0
tags	["sales","cdp","enterprise","platform"]
github	https://github.com/treasure-data

Treasure Data Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

What do you need help with?

• A. Initial setup — implementation, onboarding, connecting first data sources
• B. Profile unification — identity resolution, merging customer records, parent/child tables
• C. Audience segmentation — building segments, no-code Audience Studio, SQL-based segments
• D. Connectors & integrations — configuring import/export connectors, Integration Hub, 400+ sources
• E. Journey orchestration — customer journeys, triggered campaigns, activation workflows
• F. AI Marketing Cloud — AI Suites (Engagement, Personalization, Creative, Paid Media, Service)
• G. Agent Hub & Treasure Code — AI agents, Marketing Super Agent, agent development
• H. API & SDK — TD API, Audience API, Postback API, LLM API, client SDKs
• I. SQL & queries — Presto/Trino queries, job management, query optimization
• J. Workflow scheduling — Treasure Workflows, DAGs, scheduling jobs, CI/CD
• K. Pricing & plans — Intelligent CDP vs AI Marketing Cloud, "No Compute" pricing, Trade-Up Program
• L. Choosing vs competitors — Treasure Data vs Segment, Tealium, Amperity, Hightouch, RudderStack
• M. Other

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

Step 2 — Route or answer directly

If the question is about...	Route to...
CRM data deduplication or quality outside TD	/sales-data-hygiene [question]
Retargeting/remarketing strategy	/sales-retargeting [question]
Connecting TD to other tools (general integration strategy)	/sales-integration [question]
Contact/company enrichment	/sales-enrich [question]
Lead scoring models	/sales-lead-score [question]
Buying intent signals	/sales-intent [question]