Skip to content
CRM ⇄ Analytics

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

Keep Close 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 Close and Treasuredata

Put live Close data behind every dashboard and cohort in Treasuredata, and write the segments and scores Treasuredata computes back onto the Close record — one connection, not a nightly export.

Treasuredata turns data into dashboards, cohorts, and metrics; Close is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Activities, Tasks, Custom Activities, Custom Fields from Close into Treasuredata field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Treasuredata write back to fields in Close, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

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 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 04 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.

Common sync patterns

Report on live CRM data

New records and status changes in Close appear in Treasuredata within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.

Where Close accepts updates: segments and scores back on the record

Cohorts, scores, and computed metrics from Treasuredata sync onto fields in Close, putting the analysis where reps and owners actually work the accounts.

One customer across analytics and CRM

The same account or person is keyed consistently in both systems, so a profile or row in Treasuredata lines up with the contact or account in Close.

What you can sync between Close 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.

Close objects Treasuredata objects How this pairing syncs
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. Custom Activities is specific to Close and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. Custom Fields is specific to Close and Query Jobs to Treasuredata — each maps to any object or custom field on the other side.
Users Sales reps referenced as owners on leads, opportunities, and activities. Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. Users is specific to Close and Databases to Treasuredata — each maps to any object or custom field on the other side.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. 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. Smart Views is specific to Close and Tables to Treasuredata — each maps to any object or custom field on the other side.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. 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. Leads is specific to Close and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Contacts is specific to Close and Segments to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between Close 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.

Close Treasuredata Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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

Treasuredata Close 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 written to Close through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • 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 Close ⇄ Treasuredata

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Close and Treasuredata connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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

    Choose tables

    Pick the Close 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 · Close ⇄ 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
    Close Treasuredata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Close 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 403 integrations available for Close and Treasuredata.

Popular · 5 of 403
All Close 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