Adobe Identity Service (ECID)

Server-side identity syncing with the Adobe Experience Cloud Identity Service for cross-solution visitor identification using Experience Cloud IDs (ECIDs).

⚠️

This integration is alpha. Configuration and behaviour may change. Validate end-to-end against a non-production Adobe org before going live.

Prerequisites

Before configuring the Adobe Identity Service in Datafly Signal, you need an Adobe Experience Cloud organization and your Organization ID.

Get your Adobe credentials

Step 1: Verify Your Adobe Experience Cloud Organization

Go to experience.adobe.com and sign in with your Adobe ID.
Click your profile icon in the top-right corner and select Organization.
Verify that the correct organization is selected. You need admin or developer access.

Step 2: Find Your Organization ID

Go to the Adobe Admin Console.
Click your organization name in the top navigation.
Go to Settings and locate the Organization ID.
The format is 1234567890ABCDEF@AdobeOrg. Copy this value.

The Organization ID is the same across all Adobe solutions (Analytics, Target, Audience Manager, AEP). If you have already configured another Adobe integration in Signal, you can reuse the same Organization ID.

Step 3: Confirm Identity Service is Provisioned

The Identity Service is on by default for most Adobe Experience Cloud organisations. If you have never used Adobe Analytics, AAM, or AEP before, contact your Adobe account team to confirm the service is enabled for your org. [verify with current vendor docs]

Configure the integration in Signal

Configuration Fields

Field	Required	Description
`org_id`	Yes	Your Adobe IMS Organization ID in the format `XXXXX@AdobeOrg`. Found in the Adobe Admin Console under Settings.

Management UI Setup

Go to Integrations in the sidebar.
Open the Integration Library tab.
Find Adobe Identity Service or filter by Analytics.
Click Install and enter your Organization ID from Step 2.
Click Install Integration.

Management API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/adobe_id/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Adobe Identity Service",
    "variant": "general",
    "config": {
      "org_id": "1234567890ABCDEF@AdobeOrg"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Identity Service is identity-only — no e-commerce events. Signal sends a single sync per visitor lifecycle:

Datafly Event	Adobe Identity Service	Notes
`identify`	`identify`	Issues a `GET https://dpm.demdex.net/id?d_orgid={org_id}&d_ver=2` request and stores the returned ECID against the visitor.

Identity

The Adobe Identity Service (also known as ECID Service) provides a universal visitor ID that links a user across all Adobe Experience Cloud solutions.

The default blueprint sends:

Source	Adobe field
`user_id`	`customer_id`
`properties.email`	`email`

How identity sync works with Signal

First visit: Signal sends a server-side request to the Adobe DCS to generate an ECID.
ECID stored: The returned ECID is associated with the visitor’s anonymous identifier and persisted server-side.
Cross-solution sync: The ECID is included in subsequent calls to Adobe Analytics, Adobe Target, AAM, and Adobe Experience Platform.
Returning visitors: On subsequent visits, the existing ECID is reused — no additional DCS call is needed.

Default consent category: analytics. The Identity Service issues a stable cross-solution identifier — if you want it gated by marketing consent, add advertising to the integration’s consent categories.

Verify it’s working

In the Signal Management UI, open your Adobe Identity Service integration and watch the Live Events stream as you visit your site.
Confirm a 200 response from dpm.demdex.net/id and that the response body includes an ECID (numeric, 38 characters).
Open Adobe Analytics or AEP and search for a profile by ECID to confirm the identity graph is being built.

Troubleshooting

Symptom	Cause	Fix
No ECID returned	Incorrect Organization ID	Verify the `org_id` matches your Adobe Admin Console exactly, including the `@AdobeOrg` suffix.
`403` from DCS endpoint	Organization not provisioned for Identity Service	Contact Adobe support to verify Identity Service is enabled for your org.
ECID not matching across solutions	Multiple organizations configured	Ensure all Adobe integrations in Signal use the same Organization ID.
Intermittent timeouts	DCS regional endpoint overloaded	Signal retries automatically with exponential backoff.

Blueprint

The Adobe Identity Service blueprint version is 0.1.0 (alpha). It exposes a single General variant covering cross-solution visitor identity syncing with Adobe Experience Cloud.