Real-time
Two-way sync
Changes in Citus or Demandbase instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Marketing
Citus to Demandbase integration — real-time, two-way sync
Keep Citus and Demandbase 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 Citus and Demandbase
Give your team Demandbase's contacts, campaigns, and engagement in Citus: 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 Citus, hard to get into campaigns without manual exports.
Stacksync mirrors Activities, Campaigns, Account & Person Lists (Audiences), Company Details (B2B enrichment) from Demandbase into Distributed tables, Reference tables, Local tables, Schemas in Citus 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 Citus, 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 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- 02 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 03 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.
- 04 Push warehouse-computed account scores, custom fields, and audiences into Demandbase via the Data Import API so ABM campaigns and sales plays target the segments the warehouse defines.
Common sync patterns
Keep contact attributes consistent
Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.
Query Demandbase like a database
Contacts, leads, audiences, and campaign metrics from Demandbase live in Citus 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 Citus 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.
What you can sync between Citus and Demandbase
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.
| Citus objects | Demandbase objects | How this pairing syncs | |
|---|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Company Details (B2B enrichment) Firmographics, technographics, competitors, and corporate family tree fetched by domain or name via the B2B Company Search and Details endpoints; read-only enrichment. | Distributed tables is specific to Citus and Company Details (B2B enrichment) to Demandbase — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | 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. | Reference tables is specific to Citus and Change Subscriptions to Demandbase — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | 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. | Local tables is specific to Citus and Accounts to Demandbase — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | 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. | Schemas is specific to Citus and Opportunities to Demandbase — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | 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. | Views is specific to Citus and People (Persons) to Demandbase — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | 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. | Sequences is specific to Citus and Activities to Demandbase — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Demandbase
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.
Citus Demandbase Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Demandbase through its API, with automatic retries and rate-limit backoff.
Demandbase Citus 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 Citus as a row-level write, with types converted between the two schemas.
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.
What ships with Citus ⇄ Demandbase
Connect Citus and Demandbase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Demandbase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Demandbase 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 Citus or Demandbase record.
Observability
Monitoring
Track your Citus ⇄ Demandbase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Demandbase.
How the Citus and Demandbase connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
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.
How it works
How to connect Citus to Demandbase — 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.
- 01
Connect your apps
Authenticate Citus and Demandbase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Demandbase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Demandbase 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.
objects · Citus ⇄ DemandbaseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus DemandbaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Demandbase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Demandbase: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Demandbase: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Citus: The managed cloud offering is Azure Cosmos DB for PostgreSQL, which is Citus under a Microsoft brand. Demandbase: Demandbase splits data movement across a read-only Data Export API (accounts, opportunities, people, activities, campaigns, lists) and a write-capable Data Import API (import or update accounts, opportunities, persons, activities, intent, and custom source data). Stacksync's field mapping accounts for these differences between Citus and Demandbase without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Citus and Demandbase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Demandbase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Demandbase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Demandbase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 392 integrations available for Citus and Demandbase.
Popular · 7 of 392
-
Citus ⇄ Twitter Ads -
Citus ⇄ Marketo -
Citus ⇄ Salesforce Marketing Cloud -
Demandbase ⇄ SAP Hana -
Demandbase ⇄ Jdbc -
Demandbase ⇄ Render Postgres -
Demandbase ⇄ PostgreSQL
No integrations match .
