Skip to content

Commit

Permalink
Merge pull request #6254 from segmentio/thomas/delivrai
Browse files Browse the repository at this point in the history
Rebrand from cdp resolution to delivrai
  • Loading branch information
forstisabella authored Mar 26, 2024
2 parents 1fc8e74 + 234de59 commit b9a96a8
Show file tree
Hide file tree
Showing 3 changed files with 47 additions and 44 deletions.
32 changes: 0 additions & 32 deletions src/connections/destinations/catalog/cdpresolution/index.md

This file was deleted.

35 changes: 35 additions & 0 deletions src/connections/destinations/catalog/delivrai-resolve/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: Delivr.ai Resolve (Browser) Destination
id: 650c69e7f47d84b86c120b4c
beta: true
redirect_from:
- '/connections/destinations/catalog/actions-cdpresolution/'
---

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

[Delivr.ai Resolve](https://delivr.ai?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 Delivr.ai.

This destination is maintained by Delivr.ai. For any issues with the destination, [contact the Delivr.ai support team](mailto:[email protected]).

How this works: A visitor lands on a digital property that has the Segment analytics.js script connected to the Delivr.ai Resolve Destination enabled. For each session, the anonymous ID is sent to Delivr.ai to check if our cookie is present on the browser. This allows Delivr.ai to resolve the cookie against our graph. If found, the profile and firmographics data are sent to Segment against a source that is configured within Delivr.ai platform.

## Getting started

To set up the Delivr.ai destination:
1. Navigate to **Connections > Catalog** in the Segment app and select the **Destinations** tab of the catalog.
2. Search for *Delivr.ai* and select it.
3. Choose which of your sources to connect the destination to.
4. In the Settings, enter your Delivr.ai API key. You can find this in the CDP Connector Setting section of your [Delivr.ai Dashboard Connection Settings](https://app.cdpresolution.com/administration/cdp-connections/segment-io-f4241?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
5. Go to the Delivr.ai UI.
5. Go to the [Delivr.ai 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.
2. Paste your Delivr.ai API key in Segment to generate your Write Key.
3. Paste your Write Key into Delivr.ai's connection configuration.
4. Click **Upload Key**.

Further documentation can be found on the [Delivr.ai documentation site](https://docs.delivr.ai?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.

If you have configured your Delivr.ai Destination correctly, and if you've also configured Delivr.ai 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 %}

Original file line number Diff line number Diff line change
@@ -1,31 +1,31 @@
---
title: CDP Resolution Enrichment Source
title: Delivr.ai Enrich Source
id: HoFsjsDOW2
beta: true
hidden: true
---

[CDP Resolution](https://cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps customers identify their target audience for the purpose of activation, ongoing engagement, and conversion. You can find a [list of the different attributes](https://www.cdpresolution.com/resources/UPID?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} you can collect with CDP Resolution Enrichment.
[Delivr.ai](https://delivr.ai?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps customers identify their target audience for the purpose of activation, ongoing engagement, and conversion. You can find a [list of the different attributes](https://delivr.ai/resources/UPID?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} you can collect with Delivr.ai Enrich.

This source is maintained by CDP Resolution. For any issues with the destination, [contact the CDP Resolution support team](mailto:support@cdpresolution.com).
This source is maintained by Delivr.ai. For any issues with the destination, [contact the Delivr.ai support team](mailto:support@delivr.ai).

Here's how it works: When a user logs into the CDP Resolution UI application, they engage in a segmentation operation to identify their total addressable market. Concurrently, they enhance their Segment workspace by incorporating data sourced from CDP Resolution.
Here's how it works: When a user logs into the Delivr.ai UI application, they engage in a segmentation operation to identify their total addressable market. Concurrently, they enhance their Segment workspace by incorporating data sourced from Delivr.ai.

## Getting started

To set up your CDP Resolution Enrichment source:
To set up your Delivr.ai Enrich source:
1. Navigate to **Connections > Sources** and click **Add source** in the Segment app.
2. Search for *CDP Resolution Enrichment* in the Sources Catalog and click **Add source**.
2. Search for *Delivr.ai Enrich* in the Sources Catalog and click **Add source**.
3. Give the source a nickname and click **Add source**.
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 enrichment`).
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, `delivr.ai enrich`).
4. Copy the **Write Key** on the Overview page.
5. Go to the CDP Resolution UI.
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.
7. Paste your Write Key into CDP Resolution's Enrichment connection configuration.
5. Go to the Delivr.ai UI.
6. Go to the [Delivr.ai 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.
7. Paste your Write Key into Delivr.ai's Enrichment connection configuration.
8. Click **Upload Key**.

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"}.
Further documentation can be found on the [Delivr.ai documentation site](https://docs.delivr.ai?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.

## Events

If you've correctly set up your CDP Resolution Source and configured CDP Resolution to transmit user profile data to a Segment source, user profile data will begin to populate in the Segment Source debugger as Identify and Group calls.
If you've correctly set up your Delivr.ai Source and configured Delivr.ai to transmit user profile data to a Segment source, user profile data will begin to populate in the Segment Source debugger as Identify and Group calls.

0 comments on commit b9a96a8

Please sign in to comment.