Skip to content
Data warehouse ⇄ Analytics

ClickHouse to Treasuredata integration — real-time, two-way sync

Keep ClickHouse and Treasuredata in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect ClickHouse and Treasuredata

Put the same events, users, and metrics on both sides: Treasuredata and ClickHouse stay current in real time, in both directions.

Treasuredata is where teams explore, visualize, and report; ClickHouse is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Stacksync syncs Tables, Master (Parent) Segments, Segments, Journeys in Treasuredata with Views, Materialized views, Distributed tables, Dictionaries in ClickHouse field by field, in real time, and in both directions. You decide which system owns which fields, and Stacksync resolves conflicts by rules you set. Whether the flow is warehouse tables feeding live reports or captured events and segments landing back in ClickHouse, every copy stays consistent.

Common use cases

  • 01 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 02 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
  • 03 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 04 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Treasuredata matches the ClickHouse table it was built from instead of drifting between refreshes.

Where ClickHouse holds the source tables: live data in the reporting layer

Records maintained in ClickHouse flow into Treasuredata as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between ClickHouse and Treasuredata

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

ClickHouse objects Treasuredata objects How this pairing syncs
Databases Namespaces that group tables and scope permissions for sync users. Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Materialized views is specific to ClickHouse and Segments to Treasuredata — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Distributed tables is specific to ClickHouse and Journeys to Treasuredata — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. Dictionaries is specific to ClickHouse and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. Tables (MergeTree family) is specific to ClickHouse and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. Views is specific to ClickHouse and Query Jobs to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse and Treasuredata

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

ClickHouse Treasuredata Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.

Treasuredata ClickHouse Interval-based propagation

DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.

DeliveryEach detected change is applied to ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with ClickHouse ⇄ Treasuredata

Connect ClickHouse and Treasuredata for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Treasuredata connection.

Real-time

Two-way sync

Changes in ClickHouse or Treasuredata instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ClickHouse or Treasuredata data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single ClickHouse or Treasuredata record.

Observability

Monitoring

Track your ClickHouse ⇄ Treasuredata sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between ClickHouse and Treasuredata.

How the ClickHouse and Treasuredata connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

Treasuredata

Integration surface
TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
Authentication
API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
Change detection
Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
Capabilities
read · write
Rate limits
TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works

How to connect ClickHouse to Treasuredata — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate ClickHouse and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    ClickHouse connected
    Treasuredata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ClickHouse and Treasuredata objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · ClickHouse ⇄ Treasuredata
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    ClickHouse Treasuredata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

ClickHouse and Treasuredata integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 414 integrations available for ClickHouse and Treasuredata.

Popular · 5 of 414
All ClickHouse integrations All Treasuredata integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own