Dun & Bradstreet Web Visitor ID Tag Setup Guide
This article describes how to set up the Dun & Bradstreet Web Visitor ID tag.
When using this tag with utag version 4.50 or later, you must set the utag.js always_set_v_id setting to true. This setting ensures that the visitor ID is available for cookie synchronization. For more information, see the utag 4.50 release notes and Considerations for tealium_visitor_id when upgrading to utag 4.50+.
Tag tips
- Use mapping to dynamically override standard configuration values.
- Use the JavaScript Code extension to set returned data.
Example:
window.tealium_dnbwvid = function(dnb_Data)
{
// Set data here, ex: visitor_duns = dnb_Data.duns;
}
To make Dun & Bradstreet data available as server-side attributes (once per session):
- Set Send to Tealium (server-side) to
true - If left blank, Tealium Account and Tealium Profile will be automatically populated with your current account and profile.
- Set Send to Tealium (server-side) to
Tag configuration
Go to the tag marketplace to add a new tag. For more information, see About tags.
When adding the tag, configure the following settings:
API Key
- Your API key supplied by Dun & Bradstreet.
- Example:
//API_KEY_HERE.d41.co/sync/
Data Key
- API Key supplied in the getData call.
- Leave blank to use the API Key.
- Example:
dnbvid.getData('DATA_KEY_HERE','json','T'... )
Send to Tealium (server-side)
Tealium Account
- (Optional) Override the
tealium_accountused for server-side requests.
- (Optional) Override the
Tealium Profile
- (Optional) Override the
tealium_profileused for server-side requests.
- (Optional) Override the
Data mappings
Data mappings send values from data layer variables to the corresponding variables in the vendor tag. For more information, see About data mappings.
The available categories are:
Standard
| Variable | Description |
|---|---|
api_key |
|
data_key |
|
send_to_tealium |
|
tealium_account |
|
tealium_profile |
|
This page was last updated: November 18, 2026