Treasure AI (formerly Treasure Data) is an agentic experience platform that unifies customer data from any source, resolves identities across channels, and deploys AI agents to run personalization, messaging, and decisioning autonomously — harnessed by human creativity and strategic judgment. The platform evolved from one of the original customer data platforms into a bundled CDP, omni-channel messaging, and AI system designed to run the Customer Intelligence Loop continuously.
Disclosure: cdp.com is managed by Treasure Data (now Treasure AI). This overview follows the same editorial standards as our other vendor profiles — documented in our Editorial Policy — but readers should be aware of the relationship. For a side-by-side comparison of all CDP vendors, see the CDP Vendor Comparison Guide.
Treasure AI at a Glance
| Dimension | Treasure AI |
|---|---|
| Best for | Global, multi-brand enterprises — both B2C and B2B — with large-scale data environments, especially those needing APAC coverage and multi-region data residency |
| Typical buyer size | Mid-market and enterprise — 39.9% of the 163 G2 reviews classified by company size come from organizations above 1,000 employees, 36.8% from 51–1,000, and 23.3% from 50 or fewer |
| Pricing model | Per-profile plus per-event, quote-based; no separate compute charge for queries and segmentation in Complete CDP mode, while Composable mode queries run on (and bill to) the customer’s own warehouse compute |
| Typical implementation | 4-8 weeks initial; 3-6 months for full enterprise rollout |
| Key differentiator | The widest capability span among the packaged CDPs covered on cdp.com: packaged or composable deployment, native predictive and agentic AI, and native email/SMS/push inside one platform boundary — with APAC-native connectors (LINE, Yahoo! JAPAN Ads) as an added fit for the region |
| Skip if | You need an SMB-sized budget |
Reviewer mix is not a customer base: where a G2 split is quoted above, it describes who reviews the vendor, not who buys it — reviewers self-select and vendors run review-solicitation campaigns. Those counts are G2’s company-size-classified subset, which is smaller than the headline review count quoted elsewhere on a page; where a page names no split, the row rests on the structural fact stated in it rather than on reviewer data. The cross-vendor comparison and the methodology behind these splits are in CDP vendors.
Company History
Treasure Data was founded in 2011 in Mountain View, California, originally as a cloud-based data management platform for log data and big data analytics. Over the following years, the company shifted focus toward customer data, building the infrastructure for large-scale data ingestion, identity resolution, and audience activation that became its customer data platform.
Key milestones:
| Year | Milestone |
|---|---|
| 2011 | Founded in Mountain View, CA as a big data management platform |
| 2018 | Acquired by Arm Holdings (SoftBank Group) for approximately $600 million, accelerating enterprise go-to-market |
| 2020–2024 | Forrester Wave placements: Leader in Customer Analytics Technologies (2020), Strong Performer in CDPs (2022), and Leader in the 2024 Forrester Wave for CDPs, recognized for data foundation strength and enterprise scalability |
| 2026 | Rebranded from Treasure Data to Treasure AI, launched Agentic Experience Platform |
| 2026 | Named a Leader in both IDC MarketScape for Worldwide AI-Enabled Customer Data Platforms cuts, B2C Users (Doc #US53952526) and B2B Users (Doc #US53952326), a distinction shared with Salesforce |
As of 2026, Treasure AI serves over 400 enterprise customers across retail, financial services, healthcare, automotive, CPG, and media. The platform processes billions of unified customer profiles globally.
The Rebrand: Treasure Data to Treasure AI
On April 20, 2026, Treasure Data officially became Treasure AI. The company’s domain changed from treasuredata.com to treasure.ai, and the product category shifted from “Customer Data Platform” to “Agentic Experience Platform.”
The rebrand reflects a structural shift in what the platform does. Treasure Data began as a system where humans accessed unified customer data to make marketing decisions. Treasure AI is designed as a system where AI agents access unified customer data to make and execute decisions autonomously — with humans providing strategy, creativity, and guardrails.
Three changes define the transition:
-
From human-first to agent-first architecture. The platform’s primary interface is shifting from dashboards and query builders to AI agents that operate through MCP (Model Context Protocol), CLI, APIs, and pre-built agent skills. Humans still direct strategy, but AI agents handle execution at scale. Headless access and Digital Workers are described under Core Products below.
-
From data platform to experience platform. The original CDP handled data ingestion, unification, and audience activation. The new platform adds native omni-channel messaging (email, SMS, mobile push, in-app, LINE), AI decisioning, and real-time personalization — eliminating the need to stitch together separate vendors for each stage of the Customer Intelligence Loop.
-
From batch cycles to continuous loops. Where the CDP ran customer segmentation in batch cycles (daily, weekly), the Agentic Experience Platform runs the Customer Intelligence Loop continuously — COLLECT, UNIFY, UNDERSTAND, DECIDE, and ENGAGE in minutes, with engagement outcomes feeding back to inform the next cycle.
All existing APIs, SDKs, and workflows remain backward-compatible. The rebrand is a product evolution, not a migration that breaks existing integrations.
Platform Architecture
Treasure AI is a stack with people at the top and governed customer data at the base. The diagram shows the layers from Treasure AI’s Digital Worker page; each is described under Core Products below.
- Human direction and Digital Workers: The team sets goals, constraints, and approvals. Digital Workers, with example roles of Marketing Analyst, Channel Marketer, and Web Marketer co-designed with a forward-deployed engineer (FDE), do the assigned work on top of the platform.
- Treasure AI Studio and Headless access: Studio is the native AI workspace. The Agent Gateway, APIs, MCP, and Skills expose the same capabilities headlessly, so a team can operate them from Studio or from its preferred tools.
- Governed Customer Context: The CDP layer. It holds identity and profiles, behavior and transactions, consent and data quality, content and voice, the data catalog and permitted data, and the business ontology with agreed definitions.
- AI Real-Time Signals and the AI Decision Engine: Signals predict churn risk, purchase propensity, offer affinity, and lifetime value. The decision engine combines those predictive signals with customer context and reasoning to choose the next best action.
- Personalization and Engagement: Email, SMS, push and in-app messages, web personalization, and LINE and other connected channels, delivered through Treasure AI Engage and Personalization Studio or an existing MarTech stack.
- Feedback, FDE, and guardrails: Customer responses and outcomes return to the governed context. FDEs connect and govern the platform, define roles and review them, and evaluate and improve results. Guardrails cover consent, permissions, evaluation, monitoring, and auditability throughout.
Beneath the layers, the architecture is hybrid: it separates the control plane from the data plane.
-
Control plane (Treasure AI): Identity resolution, audience segmentation, AI decisioning, messaging orchestration, and the AI agent runtime. This is the managed platform layer where the Customer Intelligence Loop executes.
-
Data plane (customer’s infrastructure): Customer data can reside in the customer’s own data warehouse — Snowflake, Databricks, BigQuery. Treasure AI queries those tables in place without requiring data to be moved into proprietary storage. In the other direction, the same warehouses can query tables that Treasure AI manages, published in Apache Iceberg format as read-only tables, without a second copy.
This hybrid deployment model addresses a core tension in the CDP market: composable CDPs keep data in the warehouse, which is tuned for analytical queries rather than sub-second profile lookups; packaged CDPs serve profiles quickly but store the data in their own platform. Treasure AI’s architecture aims to deliver both — warehouse-resident data with a managed control plane designed for low-latency profile access and real-time activation.
Core Products
Treasure AI Studio
Treasure AI Studio is the platform’s primary interface: a workspace where you describe what you want in plain English and an AI agent does the work on your customer data, with no SQL and no engineering ticket.
An interactive walkthrough of Treasure AI Studio: a plain-English question answered from unified profiles, then the segment, email, and journey that follow, with no SQL or IT ticket.
What you can do in Studio
- Ask questions of your customer data. Ask why a discount code spiked or which customers are lapsing, and get a report with charts built from unified profiles.
- Build audiences. Describe a segment in words, get a working segment, and refine it in conversation.
- Create campaigns and journeys. Draft the email, map the journey, and manage the campaign from the same chat.
- Work with data where it already lives. Connections let an agent explore and chart data in a Snowflake warehouse or a Databricks lakehouse, and run Treasure Data CDP queries, workflows, and segment operations. Each person authorizes their own connection, and the agent sees only what that person’s role can see. Snowflake connections authorize as the
PUBLICrole, so a table granted for agent use is visible to every other Snowflake user; grant accordingly. - Keep team knowledge in shared folders. A work folder holds instructions, reference files, skills, and saved actions that the AI reads at the start of every chat (In-Session Memory). In a shared folder, a colleague’s agent starts from the context a marketer has already taught it. Conversations and each member’s
my/directory stay private, and access control limits where each member’s agent may write. - Put recurring work on a schedule. Save a workflow as an action and run it daily, on weekdays, weekly, monthly, or on a custom cron schedule without anyone clicking Run. Schedules are time-based, not event-triggered; reacting to customer behavior in the moment depends on the real-time layer.
- Reach it from where you already work. A shared folder can be exposed to MCP clients and to a Slack bot that takes requests by direct message or channel mention and replies in the thread. Each request runs with the sender’s own permissions, connections, and credits. Chats also have an Ask or Auto setting for
tdxcommands: Ask keeps an approval card on every command, so a team that wants a human check should leave its chats on Ask.
Studio runs on the web, as a desktop app for macOS and Windows, and on iOS and Android for monitoring and approvals. Engineers can use it from the terminal through Treasure Code, built on Claude Code, and anyone can query or capture notes hands-free with Treasure AI Voice.
Treasure AI Studio (mobile). The same conversational interface available on iOS and Android for on-the-go campaign monitoring and approvals.
Headless: Treasure AI from Your Own AI Tools
Headless lets a team direct an AI assistant or coding agent it already uses to work with Treasure AI’s customer data and marketing tools, instead of opening Studio. The agent can prepare audiences and journeys for review; customer-facing actions stay subject to human approval. Treasure AI states that Studio remains the interface for reviewing and refining the work and that Headless is “another way in to the same data, with the same permissions and the same audit trail.”
Treasure AI Headless. Outside clients reach the same governed customer context through the Agent Gateway or the tdx CLI and MCP, under shared permissions and audit trail.
| Route | What it connects |
|---|---|
| Agent Gateway | Team workspaces such as Slack and Microsoft Teams, and agent-based connections |
| Remote MCP | Claude and ChatGPT Enterprise; Snowflake Cortex Code and Databricks Genie Code through MCP |
CLI (tdx, Treasure Code) | Setup guides for Claude Code, OpenAI Codex, GitHub Copilot in VS Code, and Cursor |
| SDKs | The Agent SDK and the Vercel AI SDK for custom applications |
| Skills | Reusable SKILL.md folders with instructions, examples, and reference material; Treasure AI cites 50+ skills drawn from 400+ CDP implementations |
For an agentic CDP evaluation, Headless moves the integration question from “which interface does the platform ship” to “which assistants can operate it under which permissions.” Teams should check that each assistant authenticates as an individual user rather than a shared token, so audit records name a person. The MCP endpoints in Studio’s Agent Channels, described above, support per-member OAuth.
Digital Workers
Digital Workers are Treasure AI’s step from agents a marketer prompts to roles that are assigned work. A Digital Worker is an AI teammate with a defined role, goals, skills, and boundaries. It takes on tasks using your customer data and business context and returns results for your team to review. The product page names three example roles: Marketing Analyst, Channel Marketer, and Web Marketer. Once a task meets agreed quality criteria, a team sets a schedule and a review owner so it recurs.
The governance model is the part a buyer should read closely. Workers run in isolated containers with network activity and file access traced. They read data, investigate changes, draft work, and request human review; customer-facing sends and sensitive operations such as large exports require explicit approval, and every run is logged. Treasure AI also describes forward-deployed engineers who help customers design roles, connect workflows, and deploy workers, so the first roles are a services-assisted project rather than a self-serve switch.
Omni-Channel Messaging & Personalization
The platform includes native messaging and web personalization across:
- Email — Personalized content with AI-driven send-time optimization (Email Marketing)
- SMS — Transactional and promotional messaging, with per-recipient short links and native click tracking (SMS Marketing)
- Mobile push — iOS and Android push notifications (Mobile App Marketing)
- In-app messaging — Contextual messages within mobile applications (Mobile In-App Messaging)
- LINE — Native integration for the LINE messaging platform (critical for APAC markets); LINE Official Account messages (text, Imagemap, and Flex) also run as always-on campaigns alongside email and push
- Website Personalization — Personalization Studio lets marketers pick a page and content areas visually, target an existing audience, change copy, images, and calls to action, then preview, schedule, and launch. Content is delivered in under a second from the same customer profiles, without a separate profile store; technical teams handle the initial site setup
- In-browser messaging — Personalization Studio’s pop-up messages, in beta, add configurable in-browser promotions but require account enablement and Real-Time Personalization 2.0 (In-Browser Messaging)
- Landing pages — ZIP-based static sites published to custom subdomains for campaign destinations (Landing Pages)
Bundling messaging natively — rather than requiring a separate customer engagement platform — means that engagement outcomes (opens, clicks, conversions) flow directly back into the Customer Intelligence Loop without cross-vendor data latency.
Treasure Data (CDP) — Context Layer
The foundation of the entire platform is Treasure Data, the intelligent CDP that serves as the context layer. This is where customer data is ingested, identities are resolved, unified profiles are built, and governance policies are enforced. Every product above — Studio, Digital Workers, Messaging — reads from and writes to this layer.
Core capabilities of the context layer:
- Data ingestion — 170+ pre-built connectors for batch and streaming ingestion from CRM, e-commerce, web analytics, POS, support, and IoT sources
- Identity resolution — ML-powered deterministic and probabilistic matching that resolves customer identities across devices, channels, and accounts
- Unified profiles — Persistent customer 360 profiles that aggregate behavioral, transactional, and demographic data into a single record
- AI decisioning and model intelligence — Predictive analytics, propensity scoring, and real-time signal processing that power the UNDERSTAND and DECIDE stages of the loop
- Data governance — Field-level access controls, consent enforcement, and compliance automation across all downstream activation
This is the layer labeled “Composable” in the architecture diagram — organizations can connect it to their existing data warehouse (Snowflake, Databricks, BigQuery) through the hybrid deployment model, keeping data warehouse-resident while the context layer handles identity, AI, and governance.
The context layer operates in two modes. Complete CDP is a fully managed, all-in-one deployment where data is ingested and stored within the platform — connectors, identity resolution, segmentation, and activation without requiring existing warehouse infrastructure. Composable CDP (Composable Audience Studio) is the warehouse-first mode: Treasure AI sends federated queries to Snowflake, BigQuery, or Databricks, the warehouse runs them on its own compute, and only results come back — no reverse ETL sync into a second store. Marketers build audiences visually while the source tables stay in the warehouse; query results return to Treasure AI, and customer data reaches a destination only when an audience is activated. The same platform also offers managed identity resolution, AI decisioning, and native messaging — buyers comparing it with pure-play composable CDP vendors should check which of those each alternative provides natively and which it reaches through integrations, and which of them apply in the deployment mode they choose. For a comparison of composable CDP vendors, see the CDP Vendor Comparison Guide.
Composable Audience Studio on Snowflake, Databricks, and BigQuery
Composable Audience Studio is available on Snowflake and Databricks (release note) and on BigQuery (release note).
Recent additions address what an enterprise security or data team checks first. Premium audit log events bring audit logging to parity with the managed Audience Studio, including permission-denial events. Policy-based permissions grant full, limited, or no access per composable parent segment and per segment folder. Snowflake query tags label the segmentation, activation, and profile-lookup queries with a JSON QUERY_TAG, so warehouse compute can be attributed to individual audiences, segments, and activations for monitoring or chargeback.
Audiences, attributes, behaviors, segments, and activations can also be managed as code through YAML create and update with tdx cas push, with a preview before changes apply. In the reverse direction, Open Catalog Access publishes Complete CDP tables as read-only Apache Iceberg tables that the warehouse queries in place.
The composable mode puts Treasure AI in the same buyer conversation as pure-play composable vendors such as Hightouch: audiences built on warehouse tables, governed by the warehouse’s own access controls. The trade-offs move with the data. Treasure AI’s documentation says the composable mode carries variable cost because queries run on the customer’s warehouse compute, and that the customer’s team designs and maintains schemas and tunes performance (Composable CDP docs). The no-copy guarantee also covers batch data up to the point of activation — an audience sent to an ad platform or messaging channel does leave the warehouse, as it would with any composable tool. Teams that want Treasure AI to own the storage and schema work choose the Complete CDP mode instead.
Real-Time 2.0: Real-Time Profiles and Streaming Data
A returning shopper adds a jacket to the cart, browses, and leaves. While they are still on the site, an offer can reflect both the live cart and their purchase history; once they leave, a separate trigger can start a follow-up message. Treasure AI’s Real-Time 2.0 supports both by sending every incoming event down two paths at once (Real-Time overview). The real-time path’s decision engine processes each event in milliseconds: it stitches identities, updates real-time attributes such as session counters and cart value, and combines the live event with the customer’s stored batch profile. The batch path runs scheduled workflows, typically every few minutes to hours, that aggregate event history, compute predictive scores, and refresh identity relationships. Because the real-time engine reads the latest batch profile when it processes a customer’s event, an in-session decision draws on the customer’s history, not only the current session.
Identity stitching runs on the stream itself. When events carry a matching identifier on a configured stitching key — an email and a cookie ID in one event, the same cookie and a device ID in the next — the identifiers are unified into one profile as the events arrive, across both known and anonymous IDs (ID stitching overview). The batch layer remains the source of truth for historical profiles.
Treasure AI publishes the operating envelope for the real-time layer (Performance Limitations):
| Dimension | Published figure |
|---|---|
| Personalization API response | ≤100 ms at p95 for up to 20 attributes (the SLA requires Enterprise Support) |
| Triggered activations | Up to 3 minutes end to end, including evaluation, ID stitching, and dispatch |
| Streaming ingestion | 2,000 events per second per customer by default; the platform scales horizontally to 100,000+ events per second globally |
| Decisioning throughput | 8,000 events per second per customer |
| Identity limits | Up to 100 ID stitching keys; up to 200 IDs per profile, with the oldest ejected first |
| Real-time attributes | Up to 200 per profile, 500 bytes each |
Two additions extend the layer. The Lookup Catalog joins customer profile attributes against an external reference table at runtime, for uses such as product-level decisioning, coupon reminders, and time-limited sale banners. Real-time identity log tables record identifier values rejected for stitching, IDs evicted at the 200-ID limit, and the incoming IDs associated with each merge, so a data team can inspect how profiles were joined.
For a buyer, the two timing figures answer different questions. An on-site experience depends on the Personalization API’s read time, where the ≤100 ms p95 figure applies. An abandonment follow-up runs on the triggered-activation path, which Treasure AI bounds at 3 minutes. Deployments with 100 or more parent segments should be validated in a proof of concept first, and teams whose use cases are limited to weekly campaigns and monthly reporting may not need the real-time path at all.
Early Access Results
During 2026 early access, Treasure AI published two enterprise outcomes:
- Enterprise retail: A retail customer compressed the segment-to-launch workflow from five days to eight hours using an early-access Treasure AI agent. The agent discovered a 340,000-profile high-intent segment that manual analysis had missed, generating a 23 percent conversion lift.
- Financial services: A data analytics team replaced a three-day report cycle with 60-second natural-language queries through Treasure AI Studio, freeing analysts to focus on strategic interpretation rather than data extraction.
These results are self-reported by the vendor and represent early-stage deployments. Independent analyst validation and broader customer benchmarks are expected as the platform matures beyond early access.
Customer Intelligence Loop
The Customer Intelligence Loop is a five-stage continuous cycle that describes how customer data flows from collection through activation — and how engagement outcomes feed back to improve future decisions. Most marketing stacks run this loop in disconnected steps: a warehouse collects data, a separate tool resolves identities, another builds segments, and yet another sends messages. Each handoff introduces latency and context loss. The Customer Intelligence Loop is Treasure AI’s organizing principle for eliminating those gaps — all five stages execute within a single platform, and AI agents run the loop continuously rather than waiting for human-initiated batch cycles.
COLLECT → UNIFY → UNDERSTAND → DECIDE → ENGAGE → (back to COLLECT)
Each stage maps to specific platform capabilities:
| Stage | What Happens | Platform Capability |
|---|---|---|
| COLLECT | Ingest data from any source — behavioral, transactional, CRM, support, IoT | 170+ pre-built connectors, streaming and batch data ingestion |
| UNIFY | Resolve identities across devices, channels, and accounts into unified profiles | ML-powered identity resolution, deterministic and probabilistic matching |
| UNDERSTAND | Analyze customer behavior, predict intent, score propensity | Predictive analytics, LTV modeling, churn prediction |
| DECIDE | Determine the next best action for each customer | AI decisioning engine, real-time offer arbitration |
| ENGAGE | Execute personalized experiences across channels | Native omni-channel messaging, data activation to external systems |
Engagement outcomes (email opens, purchase conversions, support interactions) feed back to the COLLECT stage, closing the loop. In the agentic model, AI agents run this loop continuously rather than waiting for human-initiated campaign cycles. For organizations running weekly batch campaigns with no real-time or in-session personalization requirements, the continuous loop may not be necessary — composable architectures that run the loop on a daily or weekly cadence can deliver sufficient value at lower complexity.
Governance and Security
Enterprise data governance is a foundational requirement for any platform handling PII at scale. Treasure AI’s governance capabilities include:
- Compliance certifications: SOC 2 Type II, GDPR, CCPA, HIPAA-eligible
- Infrastructure: The managed platform runs on AWS with Bedrock integration for AI workloads; in composable mode, customer data stays in the customer’s own warehouse
- Audit trail: Tamper-evident logging of all data access, agent actions, and activation events. Premium audit log API events can carry client and client-version values taken from request headers; historical entries lack them, and Treasure AI cautions that the values alone are not reliable security attribution (release note)
- Consent management: Centralized consent enforcement across all activation channels
- Data residency: Regional data storage options for organizations subject to data localization requirements
- Organization-wide agent instructions: Administrators can set up to 16,384 characters of standing instructions that are added to the system prompt of every AI Studio agent in the organization, applied to new chats. These guide agent behavior; data access is still governed by the enforced controls above, not by instructions
- AI data policy: Customer data is never used to train AI models
For a complete list of certifications and security documentation, see the Treasure AI Trust Center.
The tamper-evident audit trail is particularly relevant for regulated industries — financial services and healthcare organizations require provable records of who (or what agent) accessed customer data and what actions were taken.
Who Should Consider Treasure AI
Treasure AI is best suited for organizations that:
- Need the full Customer Intelligence Loop in one platform — data ingestion, identity resolution, AI decisioning, and activation without stitching together multiple vendors
- Want AI agents to operate on unified customer data — not just dashboards for humans, but an agent-first architecture where AI executes continuously
- Require enterprise-grade governance — SOC 2, GDPR, CCPA, HIPAA compliance with auditable AI agent actions
- Operate across multiple channels — email, SMS, push, in-app, LINE, web personalization, and paid media activation
- Have existing data warehouse investments — Composable Audience Studio builds and activates audiences on Snowflake, Databricks, and BigQuery tables in place, and AI Studio agents can query Snowflake and Databricks directly in a chat
- Serve APAC markets — native LINE integration and regional data residency support
- Want their own AI tools to operate on governed customer data — Headless reaches Treasure AI from Claude, ChatGPT Enterprise, Claude Code, Slack, or Microsoft Teams under the same permissions and audit trail
Organizations that may find other architectures more suitable:
- Teams that only need reverse ETL — organizations with a mature data warehouse, existing segmentation logic in SQL, and no need for identity resolution, AI decisioning, or native messaging may find a standalone reverse ETL tool sufficient. Treasure AI’s hybrid architecture can connect to the same warehouses, but the full platform may be more capability than needed
- Organizations fully committed to a single suite (Adobe or Salesforce exclusively) may find tighter integration within that ecosystem, despite the suite tax trade-offs. However, organizations running both Salesforce and Adobe — or mixing suite products with best-of-breed tools — often find that a vendor-neutral platform like Treasure AI provides better cross-suite data unification than either suite’s own CDP
- Buyers who need published Digital Worker terms — Treasure AI has not published pricing or an error rate, so a purchase decision resting on Digital Workers needs those answered in writing first
- Small businesses with simple data needs (under 100,000 profiles, one or two channels) may not need the platform’s enterprise capabilities
FAQ
What happened to Treasure Data?
Treasure Data rebranded to Treasure AI on April 20, 2026. The company’s domain changed from treasuredata.com to treasure.ai, and the product evolved from a customer data platform into an agentic experience platform. All existing customer integrations, APIs, and SDKs remain backward-compatible — the rebrand reflects a product evolution, not a breaking change.
How does Treasure AI differ from other CDPs?
Treasure AI bundles CDP, omni-channel messaging, and AI agents into a single platform that runs the Customer Intelligence Loop continuously. Most CDPs handle data unification and segmentation but require separate tools for messaging and AI decisioning — typically 4-5 vendors in a composable stack (warehouse, reverse ETL, ESP, AI layer). Treasure AI keeps all five stages of the loop within a single platform boundary, eliminating the PII duplication and cross-vendor latency that reverse ETL introduces. For a detailed comparison, see the CDP Vendor Comparison Guide.
Is Treasure AI the right CDP for my organization?
Treasure AI is the right CDP for global, multi-brand enterprises — both B2C and B2B — with large-scale data and APAC coverage needs, and the wrong fit for SMB-sized budgets. Choose it for the span the platform covers on its own — packaged or composable deployment, native predictive and agentic AI, and native email, SMS, and push without copying PII to a separate suite product — plus APAC-native connectors (LINE, Yahoo! JAPAN Ads).
Is Treasure AI a CDP or something different?
Treasure AI includes a full CDP (data ingestion, identity resolution, segmentation, activation) and extends it with native messaging and AI agent capabilities. The “agentic experience platform” label reflects the addition of AI-driven decisioning and execution on top of the core CDP foundation. Organizations evaluating Treasure AI against CDPs should compare the full platform scope — not just the data unification layer. See What Is an Agentic CDP? for how this category is evolving.
Is Treasure AI a real-time CDP?
Yes — Treasure AI’s Real-Time 2.0 layer processes streaming events in milliseconds, stitches identities as events arrive, and publishes a Personalization API SLA of ≤100 ms at p95 for up to 20 attributes, available with Enterprise Support. Triggered activations are delivered within 3 minutes. A parallel batch path computes predictive scores and refreshes identity relationships on a schedule, and the real-time engine reads that batch profile when it processes an event, so live decisions still carry customer history.
Does Treasure AI work with Snowflake, Databricks, and BigQuery?
Yes — Treasure AI’s Composable Audience Studio builds and activates audiences directly on Snowflake, Databricks, and BigQuery without copying data into Treasure AI. Queries run on the warehouse’s own compute, so the warehouse bill carries the cost and the data team maintains the schema. AI Studio agents can also query Snowflake and Databricks in a chat through per-user OAuth connections.
What are Treasure AI Digital Workers?
Digital Workers are role-based AI marketing teammates from Treasure AI, with example roles of Marketing Analyst, Channel Marketer, and Web Marketer. Each is configured with a persona, goals, skills, tools, a schedule, and permissions, and runs in an isolated container. Customer-facing sends and large exports need explicit human approval. Treasure AI has not published pricing or an error rate.
Can I use Treasure AI from Claude, ChatGPT, or Slack?
Yes — Treasure AI’s Headless offering connects outside AI tools to its customer data and marketing tools through remote MCP, the tdx CLI, SDKs, and an Agent Gateway for Slack and Microsoft Teams. Treasure AI lists Claude and ChatGPT Enterprise as reachable through remote MCP. Studio stays the review interface, permissions and audit trail are shared, and customer-facing sends require human approval.
See how analysts rank CDP vendors → IDC MarketScape | Forrester Wave
This article is also available in: Treasure AI(旧Treasure Data)とは?特徴と沿革 · O que é Treasure AI (ex-Treasure Data)? · ¿Qué es Treasure AI (antes Treasure Data)? · Treasure Data (Treasure AI) : la CDP, ses limites · Treasure AI: CDP-Profil für Deutschland






