Adobe Identity Service (ECID)
Signal syncs your customers’ IDs to the Adobe Experience Cloud ID service (the ECID service) from the server, using Adobe’s documented direct integration: a GET to dpm.demdex.net/id with d_-prefixed query parameters.
Nothing is sent until you configure at least one integration code (see below). Validate against a non-production Adobe org before going live.
Why route Adobe Identity Service through Datafly Signal
- Customer IDs reach Adobe even when the browser blocks the ID service. Signal sends the sync from your own server whenever a visitor identifies, logs in or signs up.
- The e-mail address is hashed inside your infrastructure. Signal trims and lower-cases it and sends the SHA-256 digest, the format Adobe’s hashing support documents; the raw address never leaves your deployment.
- One consent decision governs every destination.
Prerequisites
- Your IMS Organization ID (
1234567890ABCDEF@AdobeOrg, Adobe Admin Console > Settings). - One or both of these data sources, set up in Audience Manager / the Experience Cloud (Data Sources), with their integration codes:
- a hashed e-mail data source (the digests Signal sends are SHA-256 of the trimmed, lower-cased address);
- a CRM / login ID data source (Signal sends its user ID).
Configuration fields
| Field | Required | Description |
|---|---|---|
org_id | Yes | IMS Organization ID, sent as d_orgid. |
email_integration_code | No | Integration code of your hashed e-mail data source. When set, identified visitors are synced as d_cid_ic=<code>%01<sha256 e-mail>%01<auth state>. |
crm_integration_code | No | Integration code of your CRM ID data source. When set, identified visitors are synced as d_cid_ic=<code>%01<user ID>%011. |
dcs_region | No | Data collection region ID, sent as dcs_region. Leave blank to let the service choose. |
API endpoint
GET https://dpm.demdex.net/id?d_orgid={org_id}&d_ver=2
&d_mid={ECID}
&d_cid_ic=email_sha256%01{sha256 of the e-mail}%011
&d_cid_ic=crm_id%01{user ID}%011
&dcs_region={region}The %01 separator is the control character Adobe documents between the integration code, the ID and the authentication state (0 unknown, 1 authenticated, 2 logged out). Signal sends state 1 when the visitor has a user ID, otherwise 0. Sources: direct integration and SHA-256 hashing support (both read 2026-09-22).
Event mapping
| Datafly event | Sent | Parameters |
|---|---|---|
identify, login, sign_up | Yes | d_mid (the visitor’s ECID, when Signal holds one), d_cid_ic (one per configured integration code), dcs_region |
| anything else | No |
No other personal data is sent: names and phone numbers are not ID-service parameters.
Consent
Default consent category: analytics. Add advertising if your Adobe ID syncs feed audience activation.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No requests at all | No integration code configured | Set email_integration_code and/or crm_integration_code. |
| IDs do not appear against the data source | Wrong integration code, or the data source is not set up for hashed IDs | Check the code in Data Sources; the e-mail source must expect SHA-256. |
Blueprint
Blueprint version 0.6.0 (not yet tested against a live Adobe org). One General preset.