Skip to content
Analytics

Connect Treasuredata to any app with two-way sync.

Two-way sync Treasuredata across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Treasuredata.

These objects sync between Treasuredata and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Treasuredata exposes them.

Databases
Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables.
Tables
Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables.
Master (Parent) Segments
Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records.
Segments
Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records.
Journeys
Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation.
Predictive Segments
AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization.
Scheduled Queries
Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream.
Query Jobs
Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems.
API surface

How Stacksync connects to Treasuredata.

The connector runs on Treasuredata's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Not available
What ships with Treasuredata

Connect Treasuredata for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Treasuredata instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever 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 Treasuredata record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Treasuredata connector.

Treasure Data is an enterprise Customer Data Platform owned by marketing operations, MarTech, and data engineering teams. Behavioral, transactional, and CRM data lands in its columnar databases and tables, then gets unified into parent (master) segments — customer profiles — that drive segmentation, journeys, and predictive scoring. It is the system of engagement for audience data: where raw events accumulate and where unified profiles and campaign segments are built before activation to ad, email, and CRM destinations.

  • Marketing operations / MarTech
  • Data engineering
  • CDP administrators
  • Analytics engineering
  • RevOps

  1. Two-way sync of a TD database's Tables with Postgres or BigQuery so engineering works in SQL while events keep landing in TD via its import APIs.

  2. Read Master (Parent) Segment attributes and Segment membership out of TD and write them onto Salesforce Accounts or HubSpot Contacts so reps see CDP audience flags on the record.

  3. Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.

  4. Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.

  5. Materialize Scheduled Query results into a warehouse table for BI, keeping TD's aggregates in sync with downstream reporting.

  6. Read Master (Parent) Segment attributes and Segment membership from TD and write them onto Salesforce Accounts or HubSpot Contacts, so sales and lifecycle teams see CDP audience flags on the record.

All Treasuredata integrations

Pick the system you need to keep in sync with Treasuredata. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 31

ERP · 24

Database · 12

Data warehouse · 8

Accounting and finance · 13

How it works

Set up Treasuredata in minutes, without APIs.

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 Treasuredata with its 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
    Treasuredata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Treasuredata objects to sync — Stacksync auto-detects the schema, 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 · 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
    Treasuredata database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Treasuredata connector FAQ

What can I sync with the Treasuredata connector?

Treasuredata's core objects — Databases, Tables, Master (Parent) Segments, Segments and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Treasuredata?

Via TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys, authenticated with 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). Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Treasuredata connector two-way?

Yes. Changes made in Treasuredata propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Treasuredata integration take to set up?

Most Treasuredata integrations go live in minutes: authenticate Treasuredata and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Treasuredata data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Treasuredata data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
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