Treasure Data + clariBI
Connect Treasure Data with your API key, sync your query job history, and see how your platform is being queried next to the rest of your business data.
Native Treasure Data data-source connector.
Paste your Treasure Data API key, sync your job history, and clariBI pulls your recent query jobs into preprocessed datasets and auto-generated dashboards, right next to your other tools. Access is read-only.
What is Treasure Data?
Treasure Data is an enterprise customer data platform that stores unified customer data and runs queries against it as jobs.
clariBI reads Treasure Data through its REST API using your own API key: your query job history, with each job carrying its type, status, target database, timing, and row count. This is operational metadata about how your platform is queried, not the customer data inside it. Access is read-only, and clariBI never submits or edits a job.
Learn more at treasuredata.com
Connect Treasure Data in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source, find Treasure Data, and paste your API key (Treasure Data console, then your profile). The key is Fernet-encrypted at rest.
Choose what to sync
Pick the job history resource to pull. clariBI reads it read-only.
Sync, then get dashboards
clariBI syncs the recent jobs, preprocesses them, and builds an insights dashboard. Ask "How many query jobs ran this week and how many failed?" and the AI engine queries the synced job history.
What you can analyze
Out of the box with the Treasure Data connector:
- Query jobs created over time
- Jobs by status (success, error, running, killed)
- Jobs by type (hive, presto, trino) and target database
- Rows returned and result sizes per job
- Query load lined up with releases or reporting cycles
- Cross-source: query job volume → reporting cadence → team activity
Treasure Data is one of many data sources you can connect to clariBI. See the full list →
What gets synced
clariBI pulls your recent query jobs through the Treasure Data REST API, lands them as a preprocessed dataset, and refreshes them on your schedule. Access is read-only.
clariBI syncs each job with its created date, type, status, target database, and row count, then builds an insights dashboard you can query, extend, or pull into reports. This is job history, the operational record of how your platform is queried, not the customer data stored inside it.
clariBI only ever reads. It never submits a query or edits a job in Treasure Data.
Cross-source questions Treasure Data makes possible
Treasure Data data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Treasure Data × Reporting
"Did query load spike during month-end reporting?"
Planner: read daily job counts from Treasure Data, align to reporting dates, and flag the spikes.
Treasure Data × Reliability
"Is our job failure rate creeping up?"
Planner: read job status over time from Treasure Data, compute the failure rate by week, and report the trend.
Treasure Data connector FAQ
What do I need to connect Treasure Data?
Your Treasure Data API key (the console, then your profile). You paste it into clariBI once; the key is Fernet-encrypted at rest.
Does this connector read my actual customer data?
No. It reads your query job history, the operational record of how your platform is queried. Reading the customer data inside Treasure Data needs submitting a query job, which this connector does not do.
Which clariBI plan includes the Treasure Data connector?
Data-source connectors are available on the Trial, Starter, Professional, and Enterprise plans. You can connect it during the free 14-day trial.
Start your free trial and connect Treasure Data in a minute
API key in, read-only, synced job-history dashboards in seconds.
Start free trial