Skip to content
CRM ⇄ Analytics

Dun And Bradstreet to Pendo integration — real-time data sync

Keep Dun And Bradstreet and Pendo 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 Dun And Bradstreet and Pendo

Put live Dun And Bradstreet data behind every dashboard and cohort in Pendo, and write the segments and scores Pendo computes back onto the Dun And Bradstreet record — one connection, not a nightly export.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Pendo, so Pendo always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

Pendo turns data into dashboards, cohorts, and metrics; Dun And Bradstreet is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Principals & Contacts (Data Block), Company Hierarchy & Connections (Family Tree), Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch) from Dun And Bradstreet into Pendo field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Pendo write back to fields in Dun And Bradstreet, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Pendo Visitors and Accounts into a data model to score product-qualified accounts alongside behavioral event data.
  • 02 Load guide-engagement events into a reporting database to measure onboarding-flow adoption against retention and expansion.
  • 03 Poll D&B Monitoring notifications for a registered portfolio of key accounts and suppliers and update the CRM or warehouse record whenever a firmographic or risk score changes.
  • 04 Pull D&B risk and credit signals (PAYDEX, Failure Score, D&B Rating) into a warehouse for credit-risk, vendor-risk, and third-party-risk analytics.

Common sync patterns

One customer across analytics and CRM

The same account or person is keyed consistently in both systems, so a profile or row in Pendo lines up with the contact or account in Dun And Bradstreet.

A record that outlives edits in the CRM

A continuously synced copy of Dun And Bradstreet's records and activity in Pendo keeps a queryable history even as records change or age out of the CRM.

Customer context in Pendo

Accounts, contacts, deals, and activity from Dun And Bradstreet sync into Pendo, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.

What you can sync between Dun And Bradstreet and Pendo

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.

Dun And Bradstreet objects Pendo objects How this pairing syncs
Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. Visitors End-user records with agent-collected and custom fields; queried through the Aggregation API and enriched with custom fields written back via the Metadata API. Company Information (Data Block) is specific to Dun And Bradstreet and Visitors to Pendo — each maps to any object or custom field on the other side.
Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Accounts to Pendo — each maps to any object or custom field on the other side.
Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Feature Events to Pendo — each maps to any object or custom field on the other side.
Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Page Events to Pendo — each maps to any object or custom field on the other side.
Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Guide Events to Pendo — each maps to any object or custom field on the other side.
Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. Criteria Search is specific to Dun And Bradstreet and Poll / NPS Responses to Pendo — each maps to any object or custom field on the other side.

How changes propagate between Dun And Bradstreet and Pendo

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.

Dun And Bradstreet Pendo Interval-based propagation

DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).

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

Pendo Dun And Bradstreet Interval-based propagation

DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.

DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Pendo records.

Rate-limit considerations

  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
  • Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
What ships with Dun And Bradstreet ⇄ Pendo

Connect Dun And Bradstreet and Pendo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Pendo connection.

Real-time

Real-time sync

Changes in Dun And Bradstreet or Pendo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dun And Bradstreet or Pendo 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 Dun And Bradstreet or Pendo record.

Observability

Monitoring

Track your Dun And Bradstreet ⇄ Pendo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and Pendo.

How the Dun And Bradstreet and Pendo connectors work

Dun And Bradstreet

Integration surface
D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
Authentication
OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.

Pendo

Integration surface
Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
Authentication
Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
Change detection
Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
Capabilities
read · write
Rate limits
Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
How it works

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

    Choose tables

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

Dun And Bradstreet and Pendo 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 455 integrations available for Dun And Bradstreet and Pendo.

Popular · 6 of 455
All Dun And Bradstreet integrations All Pendo 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