# Delivr.ai Resolve (Browser) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **CDP Resolution**, **Delivr.ai**, **Delivr.ai Resolve** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This destination is not compatible with [Destination Insert Functions.](/docs/segment/connections/functions/insert-functions/)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Delivr.ai Resolve](https://delivr.ai?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) 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) 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:support@delivr.ai).

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).
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) page and select the Segment IO connector.
7. Paste your Delivr.ai API key in Segment to generate your Write Key.
8. Paste your Write Key into Delivr.ai's connection configuration.
9. 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).

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.

## Destination Settings

| Field                   | Description                                                                                         | Required | Type   |
| ----------------------- | --------------------------------------------------------------------------------------------------- | -------- | ------ |
| Client Identifier       | Client identifier provided by CDP Resolution \[Hashed Account ID]                                   | Yes      | string |
| CDP Resolution Endpoint | Identity resolution endpoint. \[CDP Resolution documentation]\(https://www.cdpresolution.com/docs/) | Yes      | select |

## Available Presets

Delivr.ai Resolve has the following presets

| Preset Name       | Trigger                                                              | Default Action    |
| ----------------- | -------------------------------------------------------------------- | ----------------- |
| Sync Anonymous ID | Event type = "page", Event  type = "track", Event  type = "identify" | Sync Anonymous ID |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Delivr.ai Resolve-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Sync Anonymous ID](#sync-anonymous-id)

### Sync Anonymous ID

Sync Anonymous ID to CDP Resolution.

Sync Anonymous ID is a **Web** action. The default Trigger is `type = "page" or type = "track" or type = "identify"`

| Field        | Description                  | Required | Type   |
| ------------ | ---------------------------- | -------- | ------ |
| Anonymous Id | The anonymous id of the user | Yes      | STRING |

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field                   | Description                                                                                         | Required | Type   |
| ----------------------- | --------------------------------------------------------------------------------------------------- | -------- | ------ |
| Client Identifier       | Client identifier provided by CDP Resolution \[Hashed Account ID]                                   | Yes      | string |
| CDP Resolution Endpoint | Identity resolution endpoint. \[CDP Resolution documentation]\(https://www.cdpresolution.com/docs/) | Yes      | select |