Real-time
Real-time sync
Changes in Dun And Bradstreet or Splunk instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Dun And Bradstreet to Splunk integration — real-time data sync
Keep Dun And Bradstreet and Splunk 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 Splunk
Put live Dun And Bradstreet data behind every dashboard and cohort in Splunk, and write the segments and scores Splunk 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 Splunk, so Splunk always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
Splunk 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 Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, Company Information (Data Block) from Dun And Bradstreet into Splunk 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 Splunk 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 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 02 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 03 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.
- 04 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
Common sync patterns
Customer context in Splunk
Accounts, contacts, deals, and activity from Dun And Bradstreet sync into Splunk, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
Report on live CRM data
New records and status changes in Dun And Bradstreet appear in Splunk within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
Where Dun And Bradstreet accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Splunk sync onto fields in Dun And Bradstreet, putting the analysis where reps and owners actually work the accounts.
What you can sync between Dun And Bradstreet and Splunk
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 | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Search Results to Splunk — 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. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Criteria Search is specific to Dun And Bradstreet and Saved Searches to Splunk — 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. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Monitoring Notifications is specific to Dun And Bradstreet and Fired Alerts to Splunk — 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. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Company Information (Data Block) is specific to Dun And Bradstreet and KV Store Collections to Splunk — 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. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Indexes to Splunk — 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. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Dun And Bradstreet and Splunk
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 Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Dun And Bradstreet Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
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 Splunk 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.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Dun And Bradstreet ⇄ Splunk
Connect Dun And Bradstreet and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dun And Bradstreet or Splunk 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 Splunk record.
Observability
Monitoring
Track your Dun And Bradstreet ⇄ Splunk 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 Splunk.
How the Dun And Bradstreet and Splunk 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.
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Dun And Bradstreet to Splunk — 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 Splunk 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
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dun And Bradstreet and Splunk 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 ⇄ SplunkCustomers 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 SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dun And Bradstreet and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Dun And Bradstreet and Splunk — 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.
-
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 Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Splunk side: KV Store Collections, Indexes, HTTP Event Collector, Users and Roles, plus custom fields where Splunk exposes them. On the Dun And Bradstreet side: Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, Company Information (Data Block). 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 Splunk. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Dun And Bradstreet and Splunk: Customer context in Splunk; Report on live CRM data; Where Dun And Bradstreet accepts updates: segments and scores back on the record. Accounts, contacts, deals, and activity from Dun And Bradstreet sync into Splunk, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
-
Dun And Bradstreet: 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. Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.
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 455 integrations available for Dun And Bradstreet and Splunk.
Popular · 4 of 455
No integrations match .
