Skip to content
Marketing ⇄ Database

Demandbase to TiDB integration — real-time, two-way sync

Keep Demandbase and TiDB 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 Demandbase and TiDB

Give your team Demandbase's contacts, campaigns, and engagement in TiDB: query them with SQL, push audiences built from your own data back to Demandbase, and skip the marketing API.

Demandbase holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in TiDB, hard to get into campaigns without manual exports.

Stacksync mirrors Change Subscriptions, Accounts, Opportunities, People (Persons) from Demandbase into Columns, Indexes, Sequences, Databases in TiDB field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in TiDB, from usage, orders, or account status, sync back into Demandbase to drive campaigns and ads, with Demandbase kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • 02 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • 03 Sync Opportunities and Activities two-way so CRM deal and engagement data flows into Demandbase reporting and Demandbase-calculated insights flow back to the warehouse.
  • 04 Subscribe to Demandbase company and person change webhooks - firmographic updates, M&A, and leadership or employment changes - and land them in an operational store for real-time account alerts.

Common sync patterns

Query Demandbase like a database

Contacts, leads, audiences, and campaign metrics from Demandbase live in TiDB as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Build audiences from your own data

Segments computed in TiDB from product usage, orders, or account status sync into Demandbase as lists or audiences, so campaigns and ads target the people your data says they should.

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Demandbase land in TiDB beside the matching customer record, ready for reporting and revenue attribution.

What you can sync between Demandbase and TiDB

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.

Demandbase objects TiDB objects How this pairing syncs
Change Subscriptions Company firmographic, company news, family-tree (ownership), and DB person employment subscriptions delivered as webhook alerts with a signing secret; the real-time change feed. Columns MySQL-compatible types mapped to fields in the paired system. Change Subscriptions is specific to Demandbase and Columns to TiDB — each maps to any object or custom field on the other side.
Accounts Company/account records with firmographics, intent, and Demandbase qualification and engagement scores; exported via the Data Export API and imported or updated via the Data Import API. Indexes Secondary indexes that keep incremental sync queries efficient. Accounts is specific to Demandbase and Indexes to TiDB — each maps to any object or custom field on the other side.
Opportunities Opportunity records synced from the CRM into Demandbase; exported with calculated insights and imported or updated through the Data Import API. Read and write. Sequences Server-side ID generation relevant when external systems write rows. Opportunities is specific to Demandbase and Sequences to TiDB — each maps to any object or custom field on the other side.
People (Persons) Contact/person records with verified business email, title, seniority, and quality grades; fetched and matched via the B2B Contact endpoints and exported or imported. Databases MySQL-style schemas addressed by any MySQL-compatible client. People (Persons) is specific to Demandbase and Databases to TiDB — each maps to any object or custom field on the other side.
Activities Engagement and custom activity records (web, campaign, intent); exported via Data Export and pushed in through the Data Import API using custom activity types. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Activities is specific to Demandbase and Tables to TiDB — each maps to any object or custom field on the other side.
Campaigns Marketing campaign records and creative assets exported through the Data Export API; read-only reporting feed. Views Logical views for shaping reads before syncing outward. Campaigns is specific to Demandbase and Views to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Demandbase and TiDB

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.

Demandbase TiDB Sub-second propagation

DetectionDemandbase notifies Stacksync of record changes through webhook events. Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL.

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

TiDB Demandbase Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

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

Rate-limit considerations

  • Demandbase: Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Demandbase ⇄ TiDB

Connect Demandbase and TiDB for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Demandbase or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Demandbase or TiDB 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 Demandbase or TiDB record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Demandbase and TiDB.

How the Demandbase and TiDB connectors work

Demandbase

Integration surface
REST APIs (Demandbase One) - a B2B API (company/contact search, details, and match with async bulk enrichment jobs), a read-only Data Export API and a write-capable Data Import API (both async bulk jobs), and a Subscription API for webhook change alerts.
Authentication
JWT bearer tokens minted from Demandbase One API Key Sets at the platform level; each credential set expires after 8 hours and is rotated. Legacy single-user API tokens are deprecated.
Change detection
Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL secured with a signing secret; bulk reads run as async export jobs (submit, poll, download). No log-based CDC.
Capabilities
read · write · webhooks
Rate limits
Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

How to connect Demandbase to TiDB — 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 Demandbase and TiDB 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
    Demandbase connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Demandbase and TiDB 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 389 integrations available for Demandbase and TiDB.

Popular · 7 of 389
All Demandbase integrations All TiDB 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