Cdpresolution/sync

[ajaysikri]

Proposed changes

Merge timing

Related issues (optional)

[joe-ayoub-segment]

Hi Ajay, I understand, however the instructions won't make sense to the customer as they won't be able to follow them. Happy to meet and discuss. Can you schedule a call please? http://calendly.com/joe_ayoub/integration-workshop Best regards. Joe

…

On Mon, Oct 9, 2023 at 4:31 PM ajaysikri ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/connections/destinations/catalog/cdpresolution/index.md <https://urldefense.com/v3/__https://github.com/segmentio/segment-docs/pull/5495*discussion_r1350461466__;Iw!!NCc8flgU!cj24WLtPJJFSLhKj8mwGfJcRtxAWGigxY0Le5mmMere-AUD20a-AODIIcCjd9Tk10LB9sGbNmpDL1BvZAUNHaGLHMQ$> : > +{% include content/ajs-upgrade.md %} + +## Getting started + +Setup within Segment: +1. From the Segment web app, click **Catalog**. +2. Search for “CDP Resolution” in the Catalog, select it, and choose which of your sources to connect the destination to. +3. In your Segment Settings UI, enter your CDP Resolution API key. You can find this in the CDP Connector Setting section of your [CDP Resolution Dashboard Connection Settings](https://app.cdpresolution.com/administration/cdp-connections/segment-io-f4241?utm_source=segmentio&utm_medium=docs&utm_campaign=partners <https://urldefense.com/v3/__https://app.cdpresolution.com/administration/cdp-connections/segment-io-f4241?utm_source=segmentio&utm_medium=docs&utm_campaign=partners__;!!NCc8flgU!cj24WLtPJJFSLhKj8mwGfJcRtxAWGigxY0Le5mmMere-AUD20a-AODIIcCjd9Tk10LB9sGbNmpDL1BvZAUPDb0i6gw$>). + +Setup within CDP Resolution: +1. From your [CDP Resolution Connectors](https://app.cdpresolution.com/administration/cdp-connections?utm_source=segmentio&utm_medium=docs&utm_campaign=partners <https://urldefense.com/v3/__https://app.cdpresolution.com/administration/cdp-connections?utm_source=segmentio&utm_medium=docs&utm_campaign=partners__;!!NCc8flgU!cj24WLtPJJFSLhKj8mwGfJcRtxAWGigxY0Le5mmMere-AUD20a-AODIIcCjd9Tk10LB9sGbNmpDL1BvZAUPV2MPqWg$>) page click on the Segment IO connector. +2. Paste your CDP Resolution API key in Segment to generate your Write key. +3. Paste your Write Key into CDP Resolution's connection configuration. +4. Click ‘Upload Key’. + +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. Hi Joe, You are correct from the description above. However, we do have processing that takes place on the server side, in terms of what happens after we receive the anonymous Id. And that is what we are stating in the above. Our goal with this documentation was to provide a review of the complete offering that CDP Resolution is providing. Please let me know if we need a call. Thanks, Ajay — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/segmentio/segment-docs/pull/5495*discussion_r1350461466__;Iw!!NCc8flgU!cj24WLtPJJFSLhKj8mwGfJcRtxAWGigxY0Le5mmMere-AUD20a-AODIIcCjd9Tk10LB9sGbNmpDL1BvZAUNHaGLHMQ$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AK2F3ME5DKFSSJSRUEHKWUTX6QKE5AVCNFSM6AAAAAA5V5OUFGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMNRUG44TEOJQGY__;!!NCc8flgU!cj24WLtPJJFSLhKj8mwGfJcRtxAWGigxY0Le5mmMere-AUD20a-AODIIcCjd9Tk10LB9sGbNmpDL1BvZAUP9McgGgQ$> . You are receiving this because you commented.Message ID: ***@***.***>

[github-actions]

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.