Two-way sync
Changes in Demandbase or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Demandbase and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Starburst Enterprise is where your team models customers, product usage, and revenue into trusted tables; Demandbase runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.
Stacksync syncs Tables, Views, Materialized views, Columns in Starburst Enterprise with Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions, Accounts in Demandbase field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Demandbase while sends, opens, and conversions flow back to Starburst Enterprise — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Starburst Enterprise holds the current state for auditing.
Product-usage counts, plan tier, region, or account owner computed in Starburst Enterprise appear on the matching record in Demandbase, so targeting, routing, and personalization use up-to-date context.
A segment or score built in Starburst Enterprise — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Demandbase, so campaigns target the people your data actually points to instead of a static export.
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 | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Materialized views Precomputed results that make repeated sync reads cheaper. | Opportunities is specific to Demandbase and Materialized views to Starburst Enterprise — 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. | Columns Typed per the Trino type system, mapped from each source's native types. | People (Persons) is specific to Demandbase and Columns to Starburst Enterprise — 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. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Activities is specific to Demandbase and Catalogs to Starburst Enterprise — 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. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Campaigns is specific to Demandbase and Schemas to Starburst Enterprise — 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. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Account & Person Lists (Audiences) is specific to Demandbase and Tables to Starburst Enterprise — 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. | Views Engine-level SQL views used to shape federated data before syncing it out. | Company Details (B2B enrichment) is specific to Demandbase and Views to Starburst Enterprise — each maps to any object or custom field on the other side. |
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.
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 Starburst Enterprise as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is written to Demandbase through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Demandbase–Starburst Enterprise connection.
Changes in Demandbase or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Demandbase or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Demandbase or Starburst Enterprise record.
Track your Demandbase ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Demandbase and Starburst Enterprise.
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.
Authenticate Demandbase and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Demandbase and Starburst Enterprise 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Demandbase and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Demandbase's Opportunities and People (Persons)), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Starburst Enterprise side: Tables, Views, Materialized views, Columns, plus custom fields where Starburst Enterprise exposes them. On the Demandbase side: Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions, Accounts. 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 Starburst Enterprise: Suppression and consent stay aligned; Enrich records with warehouse context; Activate a modeled audience. Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Starburst Enterprise holds the current state for auditing.
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. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 396 integrations available for Demandbase and Starburst Enterprise.