Skip to content
Marketing ⇄ Database

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

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

Give your team Demandbase's contacts, campaigns, and engagement in Firebase: 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 Firebase, hard to get into campaigns without manual exports.

Stacksync mirrors Company Details (B2B enrichment), Change Subscriptions, Accounts, Opportunities from Demandbase into Subcollections, Realtime Database Nodes, Authentication Users, Cloud Storage Objects in Firebase 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 Firebase, 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 Write CRM-side changes (plan, status, owner) back into Firestore documents the app reads.
  • 02 Combine Firebase Authentication users with billing and CRM records into one customer table.
  • 03 Enrich CRM Company and Contact records with Demandbase firmographics, technographics, and verified business emails through the B2B Company and Contact Details endpoints.
  • 04 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.

Common sync patterns

React to marketing changes as row changes

A new lead, form fill, or list change in Demandbase arrives as a row change in Firebase, so scoring, jobs, and notifications run in the tooling your team already uses.

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 Firebase as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

What you can sync between Demandbase and Firebase

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 Firebase 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. Realtime Database Nodes JSON tree paths in the older Realtime Database, synced by path. Activities is specific to Demandbase and Realtime Database Nodes to Firebase — 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. Authentication Users User accounts read into CRMs and warehouses for customer records. Campaigns is specific to Demandbase and Authentication Users to Firebase — 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. Cloud Storage Objects Files referenced from documents; usually synced as metadata plus URLs. Account & Person Lists (Audiences) is specific to Demandbase and Cloud Storage Objects to Firebase — 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. Cloud Functions Triggers Server-side hooks that fire on document changes and can push updates outward. Company Details (B2B enrichment) is specific to Demandbase and Cloud Functions Triggers to Firebase — 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. Firestore Collections Top-level groupings of documents that a sync maps to tables or SaaS objects. Change Subscriptions is specific to Demandbase and Firestore Collections to Firebase — 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. Firestore Documents Schemaless JSON-like records, the primary unit synced to and from external systems. Accounts is specific to Demandbase and Firestore Documents to Firebase — each maps to any object or custom field on the other side.

How changes propagate between Demandbase and Firebase

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

Firebase Demandbase Interval-based propagation

DetectionStacksync polls Firebase for changes on an incremental schedule, reading only records changed since the previous pass. Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes.

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.
  • Firebase: Subject to Firestore's documented operation quotas and per-document write throughput limits.
What ships with Demandbase ⇄ Firebase

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Demandbase ⇄ Firebase 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 Firebase.

How the Demandbase and Firebase 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.

Firebase

Integration surface
REST and gRPC APIs, typically accessed through the Firebase Admin SDK
Authentication
Google service account credentials (IAM) for server-side access; Firebase Auth tokens for client contexts
Change detection
Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes
Capabilities
read · write
Rate limits
Subject to Firestore's documented operation quotas and per-document write throughput limits
How it works

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

    Choose tables

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

Demandbase and Firebase 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.

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 492 integrations available for Demandbase and Firebase.

Popular · 8 of 492
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.