CDP Resolution (Browser) Destination
CDP Resolution helps customers instantly match visitor website traffic to full profiles. It turns your anonymous web traffic into full company and buyer profiles — complete with PII and firmographics data, and much more. You can find a list of the different attributes you can collect with CDP Resolution.
This destination is maintained by CDP Resolution. For any issues with the destination, contact the CDP Resolution support team.
How this works: A visitor lands on a digital property that has the segment.io analytics.js script connected to the CDP Resolution (Browser) Destination enabled. For each session, the anonymous ID is sent to CDP Resolution to check if our cookie is present on the browser. This allows CDP Resolution to resolve the cookie against our graph. If found, the profile and firmographics data are sent to segment.io against a source that is configured within CDP Resolution platform.
Getting started
To set up the CDP Resolution destination:
- Navigate to Connections > Catalog in the Segment app and select the Destinations tab of the catalog.
- Search for CDP Resolution and select it.
- Choose which of your sources to connect the destination to.
- In the Settings, enter your CDP Resolution API key. You can find this in the CDP Connector Setting section of your CDP Resolution Dashboard Connection Settings.
- Go to the CDP Resolution UI.
- Go to the CDP Resolution Connectors page and select the Segment IO connector.
- Paste your CDP Resolution API key in Segment to generate your Write Key.
- Paste your Write Key into CDP Resolution’s connection configuration.
- Click Upload Key.
Further documentation can be found on the CDP documentation site.
If you have configured your CDP Resolution Destination correctly, and if you’ve also configured CDP Resolution to send user profile data to a Segment Source, you should start to see user profile data shown in the Segment Source debugger as identify() and group() calls.
Destination Settings
| Setting | Description |
|---|---|
| Client Identifier | Required. Client identifier provided by CDP Resolution [Hashed Account ID] |
| CDP Resolution Endpoint | Required. Identity resolution endpoint. CDP Resolution documentation |
Available Presets
CDP Resolution has the following presets:
| Preset Name | Trigger | Default Action |
|---|---|---|
| Sync Anonymous ID | Event type = "page" Event type = "track" Event type = "identify" |
Sync Anonymous ID |
Available Actions
Build your own Mappings. Combine supported triggers with the following CDP Resolution-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Sync Anonymous ID
Sync Anonymous ID to CDP Resolution.
Sync Anonymous ID is a Web action. The default Trigger is: type = "page" or type = "track" or type = "identify"
| Field | Description |
|---|---|
| Anonymous Id* | Type: STRINGThe anonymous id of the user |
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
| Setting | Description |
|---|---|
| Client Identifier (required) |
string. Client identifier provided by CDP Resolution [Hashed Account ID] |
| CDP Resolution Endpoint (required) |
select, defaults to https://a.usbrowserspeed.com/cs. Identity resolution endpoint. CDP Resolution documentation |
This page was last modified: 06 Dec 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!