Skip to content

Commit e4c16ea

Browse files
Update src/connections/destinations/catalog/cdpresolution/index.md
Co-authored-by: stayseesong <[email protected]>
1 parent ebb242b commit e4c16ea

File tree

1 file changed

+0
-5
lines changed
  • src/connections/destinations/catalog/cdpresolution

1 file changed

+0
-5
lines changed

src/connections/destinations/catalog/cdpresolution/index.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,6 @@ To set up the CDP Resolution destination:
2727
4. Click **Upload Key**.
2828

2929

30-
Setup within CDP Resolution:
31-
1. From your [CDP Resolution Connectors](https://app.cdpresolution.com/administration/cdp-connections?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) page click on the Segment IO connector.
32-
2. Paste your CDP Resolution API key in Segment to generate your Write key.
33-
3. Paste your Write Key into CDP Resolution's connection configuration.
34-
4. Click ‘Upload Key’.
3530

3631
To verify that the destination has been set up correctly, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing resolution data populate in the `identify` and `group` events – click on the specific event you’re interested in to see CDP Resolutions traits. These traits will now be available to other Segment destinations in your account. Notice that all CDP Resolution traits are prefixed with `cdpresolution_` to ensure they don’t conflict with existing traits.
3732

0 commit comments

Comments
 (0)