Data & Storage · Integration
Treasure Data
Add Treasure Data to your product for your customers, and give your AI agents governed access to it.
Treasure Data is a customer data platform, which in practice means two different surfaces sitting on the same store. Underneath it is a warehouse: databases and tables you write events into and query with SQL, where schema is applied on read so a new field in an incoming event does not break the ingest. Above that it resolves those events into unified customer profiles and the segments and audiences built from them, which is what marketing teams actually act on. An embedded Treasure Data integration can use either side, sending behaviour your product observed into a customer's own tables, running a query and collecting the result, or reading which segments a person belongs to. Accounts sit in a specific region, so the endpoint depends on where their account was created rather than being fixed. The key stays with fastn, bound to the account that issued it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Treasure Data account so behaviour your product observes lands in the store their whole business already queries.
Write events without waiting on a schema change, since fields are applied on read rather than declared up front.
Run a query against a customer's own tables and collect the result asynchronously, so a long job never blocks a request in your app.
Read unified profiles and segment membership so your product personalises from the same audience definitions marketing uses.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries a customer's tables to answer a question and names the database it read from.
An agent checks which segments a customer record belongs to before it decides what to do next.
An agent writes an approved result back within scoped permissions, with the table it touched logged.
Example prompt
Which segments has this customer entered in the last month, and what behaviour put them there?
Set up Treasure Data in 4 steps
- 01Enable the Treasure Data connector in your fastn dashboard.
- 02Have each customer supply their own API key and confirm which region their account sits in, since the endpoint follows the region.
- 03Map the databases, tables and profile attributes your product uses, then decide which queries and segments you expose.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Treasure Data integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Treasure Data integration without building it. Your customers connect their own Treasure Data account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Treasure Data update is not your on-call problem.
- One integration serves your product and your agents. The same governed Treasure Data connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
Databricks
AmplitudeOften used alongside
Tools the same teams tend to run next to Treasure Data, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceTreasure Data integration FAQ
How do I add a Treasure Data integration to my product?
Enable the Treasure Data connector in your fastn dashboard, then let each customer authenticate their own Treasure Data account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Treasure Data client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Treasure Data account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Treasure Data account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Treasure Data integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent queries a customer's tables to answer a question and names the database it read from.
Who maintains the Treasure Data integration?
fastn does. When Treasure Data changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Treasure Data integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Treasure Data reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Treasure Data integration?
A common starting point: let each customer connect their own Treasure Data account so behaviour your product observes lands in the store their whole business already queries. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Treasure Data integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Treasure Data does not change your per-connector cost. You can start free with 3 connected accounts.
Add Treasure Data to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.