Skip to content

Commit e258bfc

Browse files
committed
initial version
1 parent 626ecd0 commit e258bfc

File tree

1 file changed

+29
-1
lines changed
  • src/connections/sources/catalog/cloud-apps/cdpresolution

1 file changed

+29
-1
lines changed
Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,32 @@
11
---
22
title: 'CDPResolution Source'
33
hidden: true
4-
---
4+
---
5+
6+
7+
[CDP Resolution](https://cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){: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](https://cdpresolution.com/theattributes?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} you can collect with CDP Resolution.
8+
9+
This source is maintained by CDP Resolution. For any issues with the destination, [contact the CDP Resolution support team](mailto:[email protected]).
10+
11+
{% include content/ajs-upgrade.md %}
12+
13+
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.
14+
15+
## Getting started
16+
17+
To set up the CDP Resolution Enrichment source:
18+
1. Go to **Connections > Sources** and click **Add Source** in the Segment app.
19+
2. Search for *CDP Resolution Enrichment* in the Sources Catalog and click **Add Source**..
20+
3. Give the Source a nickname and click **Add Source**.
21+
The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name. The schema name is the namespace you'll query against in a warehouse. The nickname can be anything, but Segment recommends sticking to something that reflects the source itself and distinguishes amongst your environments (for example, `cdpresolution`).
22+
4. Copy the **Write Key** on the Overview page.
23+
5. To finish the setup, Go to the CDP Resolution UI.
24+
6. Go to the [CDP Resolution Connectors](https://app.cdpresolution.com/administration/cdp-connections?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} page and select the Segment IO connector.
25+
7. Paste your Write Key into CDP Resolution's connection configuration.
26+
8. Click **Upload Key**.
27+
28+
Further documentation can be found on the [CDP documentation site](https://docs.cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
29+
30+
If you have configured your CDP Resolution Source 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.
31+
32+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)