Skip to content

Latest commit

 

History

History
32 lines (22 loc) · 2.56 KB

index.md

File metadata and controls

32 lines (22 loc) · 2.56 KB
title id beta
CDP Resolution (Browser) Destination
650c69e7f47d84b86c120b4c
true

{% include content/plan-grid.md name="actions" %}

CDP Resolution{:target="_blank"} 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{:target="_blank"} 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:

  1. Navigate to Connections > Catalog in the Segment app and select the Destinations tab of the catalog.
  2. Search for CDP Resolution and select it.
  3. Choose which of your sources to connect the destination to.
  4. 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{:target="_blank"}.
  5. Go to the CDP Resolution UI.
  6. Go to the CDP Resolution Connectors{:target="_blank"} page and select the Segment IO connector.
  7. Paste your CDP Resolution API key in Segment to generate your Write Key.
  8. Paste your Write Key into CDP Resolution's connection configuration.
  9. Click Upload Key.

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.

{% include components/actions-fields.html %}