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 currently in beta. Configuration and behaviour may change.

Prerequisites

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

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 must have admin or developer access to the organization.

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 Datafly Signal, you can reuse the same Organization ID.

Step 3: Determine Your DCS Region

The Adobe Identity Service uses regional Data Collection Servers (DCS). Your DCS region determines the endpoint used for ID syncing.

Common DCS regions:

Region	DCS Region ID	Endpoint
US East	`6`	`dpm.demdex.net`
US West	`9`	`dpm.demdex.net`
Europe	`7`	`dpm.demdex.net`
Asia Pacific	`8`	`dpm.demdex.net`

To find your region:

Check your existing Adobe Analytics or Audience Manager implementation for the d_region parameter in network requests to dpm.demdex.net.
Alternatively, contact your Adobe account team to confirm your assigned DCS region.

If you are unsure of your DCS region, start with 6 (US East) — the Adobe Identity Service will redirect to the correct regional endpoint automatically. However, setting the correct region reduces latency.

API Endpoint

POST https://dpm.demdex.net/id?d_orgid={org_id}&d_region={dcs_region}

Identity sync requests are sent server-side to the Adobe DCS endpoint. The service returns an ECID that is associated with the visitor across all Adobe solutions.

Configuration

Field	Type	Required	Description
`org_id`	string	Yes	Your Adobe IMS Organization ID in the format `XXXXX@AdobeOrg`. Found in the Adobe Admin Console under Settings.
`dcs_region`	string	Yes	The DCS region ID for your Adobe organization (e.g. `6`, `7`, `8`, `9`). Determines the regional endpoint for ID sync requests.

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 fill in the required fields:
- Enter your Organization ID from Step 2.
- Enter your DCS Region from Step 3.
Click Install Integration to create the integration with a ready-to-use default blueprint.

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": "default",
    "config": {
      "org_id": "1234567890ABCDEF@AdobeOrg",
      "dcs_region": "6"
    },
    "delivery_mode": "server_side"
  }'

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.

How It Works with Datafly Signal

First visit: When a new visitor arrives, Datafly Signal sends a server-side request to the Adobe DCS to generate an ECID.
ECID stored: The returned ECID is stored in the Datafly Identity Hub and associated with the visitor’s Datafly anonymous ID.
Cross-solution sync: The ECID is included in subsequent calls to Adobe Analytics, Adobe Target, Adobe Audience Manager, and Adobe Experience Platform.
Returning visitors: On subsequent visits, the existing ECID is retrieved from the Identity Hub — no additional DCS call is needed.

Identity Flow

Visitor → Datafly.js (anonymous_id) → Signal → Identity Hub
                                                    ↓
                                          Adobe DCS (ECID request)
                                                    ↓
                                          ECID stored in Identity Hub
                                                    ↓
                                    Used by Adobe Analytics, AEP, etc.

Testing

Once your integration is active, verify that ECIDs are being generated:

In the Datafly Signal Management UI, go to Integrations and select the Adobe Identity Service integration.
Check the Delivery Logs for successful ID sync responses from Adobe DCS.
Open your Adobe Analytics implementation and verify that the ECID (MID) value matches across solutions.
In AEP, search for a profile by ECID to confirm the identity graph is being built.

ECID generation adds a small amount of latency to the first event for new visitors (typically 50-100ms). Subsequent events use the cached ECID from the Identity Hub with no additional latency.

Troubleshooting

Symptom	Cause	Fix
No ECID returned	Incorrect Organization ID	Verify the `org_id` matches your Adobe Admin Console exactly, including the `@AdobeOrg` suffix
High latency on first event	Wrong DCS region	Set `dcs_region` to the region closest to your infrastructure
ECID not matching across solutions	Multiple organizations configured	Ensure all Adobe integrations in Signal use the same Organization ID
`403` from DCS endpoint	Organization not provisioned for Identity Service	Contact Adobe support to verify Identity Service is enabled for your org
Intermittent timeouts	DCS regional endpoint overloaded	Signal retries automatically; consider switching to a different DCS region
ECID changes between visits	Identity Hub not persisting	Verify the Identity Hub service is running and connected to the database

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Adobe Experience Cloud Identity Service. No client-side Adobe scripts are loaded for this integration.

Visit the Adobe Experience Cloud Identity Service documentation for full API reference and advanced configuration options.

Adobe Experience Platform Amplitude