Real-time
Real-time sync
Changes in Dun And Bradstreet or Reltio instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Dun And Bradstreet to Reltio integration — real-time data sync
Keep Dun And Bradstreet and Reltio 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 Reltio
Treat Dun And Bradstreet like part of your database: its records live in Reltio as real tables, and writes in either place sync to the other in seconds.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Reltio, so Reltio always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Reltio, where it can be queried and joined like everything else.
Common use cases
- 01 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
- 02 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.
- 03 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
- 04 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
Common sync patterns
Query the CRM like a database
Accounts, contacts, and custom objects from Dun And Bradstreet become tables in Reltio you can join with application data directly.
Product events onto CRM records
Signup, usage, or lifecycle changes written to Reltio sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Dun And Bradstreet API, limits, and retries.
What you can sync between Dun And Bradstreet and Reltio
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Matches (Potential Matches) to Reltio — 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. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Activity Log to Reltio — 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. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Data Change Requests (DCR) to Reltio — 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. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Criteria Search is specific to Dun And Bradstreet and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Monitoring Notifications is specific to Dun And Bradstreet and Entities to Reltio — each maps to any object or custom field on the other side. | |
| 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. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Company Information (Data Block) is specific to Dun And Bradstreet and Relations to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Dun And Bradstreet and Reltio
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 Reltio 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 Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Dun And Bradstreet Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
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 Reltio 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.
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Dun And Bradstreet ⇄ Reltio
Connect Dun And Bradstreet and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dun And Bradstreet or Reltio 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 Reltio record.
Observability
Monitoring
Track your Dun And Bradstreet ⇄ Reltio 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 Reltio.
How the Dun And Bradstreet and Reltio 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.
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Dun And Bradstreet to Reltio — 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 Dun And Bradstreet and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dun And Bradstreet
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dun And Bradstreet and Reltio 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 · Dun And Bradstreet ⇄ ReltioCustomers 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.
Dun And Bradstreet ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dun And Bradstreet and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Dun And Bradstreet and Reltio — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dun And Bradstreet and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dun And Bradstreet–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dun And Bradstreet and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dun And Bradstreet: 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. On Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Dun And Bradstreet side: Monitoring Notifications, Company Information (Data Block), Principals & Contacts (Data Block), Company Hierarchy & Connections (Family Tree), plus custom fields where Dun And Bradstreet exposes them. On the Reltio side: Entities, Relations, Crosswalks, Interactions. Stacksync auto-detects both schemas and converts types between the two systems.
-
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into Reltio. Field mapping and monitoring work the same as for two-way pairs.
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
CSA STAR
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 Dun And Bradstreet and Reltio.
Popular · 4 of 408
-
Dun And Bradstreet ⇄ Google Cloud SQL -
Dun And Bradstreet ⇄ IBM AS/400 -
Dun And Bradstreet ⇄ IBM Informix -
Dun And Bradstreet ⇄ InfluxDB
No integrations match .
