Real-time
Two-way sync
Changes in Demandbase or DuckDB instantly reflect in both systems. No stale data, no manual imports.
Marketing ⇄ Database
Demandbase to DuckDB integration — real-time, two-way sync
Keep Demandbase and DuckDB 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 DuckDB
Give your team Demandbase's contacts, campaigns, and engagement in DuckDB: 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 DuckDB, hard to get into campaigns without manual exports.
Stacksync mirrors Campaigns, Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions from Demandbase into Views, External files (Parquet/CSV/JSON), Attached databases, Database files in DuckDB 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 DuckDB, 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 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 02 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- 03 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.
- 04 Enrich CRM Company and Contact records with Demandbase firmographics, technographics, and verified business emails through the B2B Company and Contact Details endpoints.
Common sync patterns
Build audiences from your own data
Segments computed in DuckDB 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 DuckDB beside the matching customer record, ready for reporting and revenue attribution.
React to marketing changes as row changes
A new lead, form fill, or list change in Demandbase arrives as a row change in DuckDB, so scoring, jobs, and notifications run in the tooling your team already uses.
What you can sync between Demandbase and DuckDB
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 | DuckDB objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Schemas Namespaces within a database used to organize tables in sync outputs. | Activities is specific to Demandbase and Schemas to DuckDB — 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. | Tables Columnar tables created via SQL; the destination for materialized sync data. | Campaigns is specific to Demandbase and Tables to DuckDB — each maps to any object or custom field on the other side. | |
| Account & Person Lists (Audiences) Named account and person segments exported via Data Export; custom audiences pushed into Demandbase through the Data Import API. Read and write. | Views SQL views used to shape or filter data for downstream consumers. | Account & Person Lists (Audiences) is specific to Demandbase and Views to DuckDB — each maps to any object or custom field on the other side. | |
| 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. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Company Details (B2B enrichment) is specific to Demandbase and External files (Parquet/CSV/JSON) to DuckDB — each maps to any object or custom field on the other side. | |
| 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. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | Change Subscriptions is specific to Demandbase and Attached databases to DuckDB — 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. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Accounts is specific to Demandbase and Database files to DuckDB — each maps to any object or custom field on the other side. |
How changes propagate between Demandbase and DuckDB
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 DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.
DuckDB Demandbase Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
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.
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with Demandbase ⇄ DuckDB
Connect Demandbase and DuckDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Demandbase–DuckDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Demandbase or DuckDB 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 DuckDB record.
Observability
Monitoring
Track your Demandbase ⇄ DuckDB 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 DuckDB.
How the Demandbase and DuckDB 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.
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
How it works
How to connect Demandbase to DuckDB — 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 Demandbase and DuckDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Demandbase
connected
DuckDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Demandbase and DuckDB 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 · Demandbase ⇄ DuckDBCustomers 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.
Demandbase DuckDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Demandbase and DuckDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Demandbase and DuckDB: authenticate both systems, choose the objects to sync (such as Demandbase's Activities and Campaigns), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Demandbase and DuckDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Demandbase: 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. On DuckDB: Polling or full re-reads; no change feed or transaction log API. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the DuckDB side: Views, External files (Parquet/CSV/JSON), Attached databases, Database files, plus custom fields where DuckDB exposes them. On the Demandbase side: Campaigns, Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Demandbase and DuckDB: Build audiences from your own data; Engagement and results next to the customer; React to marketing changes as row changes. Segments computed in DuckDB 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.
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 408 integrations available for Demandbase and DuckDB.
Popular · 8 of 408
-
Demandbase ⇄ Amazon RDS -
Demandbase ⇄ Supabase -
Demandbase ⇄ MySQL -
Demandbase ⇄ MariaDB -
DuckDB ⇄ Marketo -
DuckDB ⇄ Salesforce Marketing Cloud -
DuckDB ⇄ Cvent -
DuckDB ⇄ Eloqua
No integrations match .
