Delivr.ai Resolve (Browser) Destination
Destination Info
- Accepts Page, Alias, Group, Identify and Track calls.
- Refer to it as CDP Resolution, or Delivr.ai, or Delivr.ai Resolve in the Integrations object
- This destination is not compatible with Destination Insert Functions.
- This integration is partner owned. Please reach out to the partner's support for any issues.
- This destination is in Beta
Delivr.ai Resolve 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 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.
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.
To set up the Delivr.ai destination:
- Navigate to Connections > Catalog in the Segment app and select the Destinations tab of the catalog.
- Search for Delivr.ai and select it.
- Choose which of your sources to connect the destination to.
- 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.
- Go to the Delivr.ai UI.
- Go to the Delivr.ai Connectors page and select the Segment IO connector.
- Paste your Delivr.ai API key in Segment to generate your Write Key.
- Paste your Write Key into Delivr.ai's connection configuration.
- Click Upload Key.
Further documentation can be found on the Delivr.ai documentation site.
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.
Client identifier provided by CDP Resolution [Hashed Account ID]
Identity resolution endpoint. CDP Resolution documentation
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 |
Build your own Mappings. Combine supported triggers with the following Delivr.ai Resolve-supported actions:
Mapping limits per destination
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"
The anonymous id of the user
Segment lets you change these destination settings from the Segment app without having to touch any code.
Client identifier provided by CDP Resolution [Hashed Account ID]
Identity resolution endpoint. CDP Resolution documentation
https://a.usbrowserspeed.com/cs