CX Enterprise atlas / Shared Services & Administration | Platform & administration
ProductGenerally available
Shared Services & AdministrationPlatform & administration
Also known as CX Enterprise Identity Service (ECID), CX Enterprise Identity Service, Experience Cloud Identity Service, Adobe Experience Cloud Identity Service, Experience Cloud ID Service, ECID Service, Visitor ID Service, Marketing Cloud ID Service, Marketing Cloud Visitor ID Service
The CX Enterprise core service that gives each browser or device a persistent Experience Cloud ID (ECID) shared by Analytics, Audience Manager, Target and the other applications, so one visitor is recognised the same way everywhere. On websites it runs as the VisitorAPI.js library (usually through the tags extension); the Web SDK and Mobile SDK set the same ECID through the Edge Network. It also carries customer IDs with an authentication state, synchronises IDs with partners and gates Adobe cookies through the Opt-in service.
Also known as ECID, MID, MCID, Marketing Cloud Visitor ID, Experience Cloud Visitor ID
The persistent, organisation-specific ID for a browser or device. It is the shared identity namespace across CX Enterprise applications and Experience Platform, and the primary device ID and base node of Experience Platform identity graphs. It identifies a device, not a person.
Last checked 2026-09-30
On the first page load the library calls the regional data collection server at dpm.demdex.net with the organisation ID. The ECID is derived mathematically from the organisation ID and the demdex ID, so the same visitor gets the same ECID on every domain the organisation owns, and a different one on another organisation's sites. After that the ID is read from the cookie, with a server refresh about every 7 days.
Last checked 2026-09-30
The standard ECID namespace in Experience Platform, used to stitch device activity with CRM IDs, hashed emails and other identities in the identity graph and in Real-Time Customer Profile.
Integrates with: Identity namespaces, Identity graph
Last checked 2026-09-30
The priority Analytics uses to pick a visitor identifier for each hit: a custom visitor ID, the legacy s_vi cookie (AID), the ECID (MID), the fallback cookie (FID), the mobile subscriber header, then IP address and user agent. Adobe recommends the ECID as the primary identifier.
Integrates with: Analytics
Last checked 2026-09-30
The ways to deploy the Visitor ID Service on websites, servers and devices. Adobe recommends the tags extension; manual (non-standard) deployments must follow the documented code order.
Last checked 2026-09-30
Also known as ECID JavaScript library, Visitor API, Visitor.js
The client-side JavaScript library behind the Visitor ID Service, used with AppMeasurement, at.js and DIL. Version 5.5.0 (October 2022) is the latest release; new web implementations generally use the Web SDK, which sets the ECID itself.
Last checked 2026-09-30
Options passed to Visitor.getInstance, such as cookieDomain, cookieLifetime, disableIdSyncs, disableThirdPartyCalls, disableThirdPartyCookies, loadTimeout, overwriteCrossDomainMCIDAndAID, resetBeforeVersion, sdidParamExpiry, secureCookie, useCORSOnly and the parent and iFrame domain allowlists.
Last checked 2026-09-30
Functions to read and set IDs: getInstance, getMarketingCloudVisitorID, getAnalyticsVisitorID, getVisitorValues, getCustomerIDs, setCustomerIDs, getLocationHint, isClientSideMarketingCloudVisitorID, resetState and the callback timeout helpers.
Last checked 2026-09-30
Also known as visitor-js-server
A trimmed Node.js version of the library (npm @adobe-mcid/visitor-js-server) for mixed implementations that call Target from the server and Analytics from the browser, keeping one ECID and supplemental data ID for Analytics for Target (A4T).
Integrates with: Analytics for Target
Last checked 2026-09-30
Also known as Direct integration with the Visitor ID Service
HTTP calls straight to the data collection servers (dpm.demdex.net) for devices that cannot run the JavaScript library or an SDK, such as game consoles and smart TVs; the response returns the ECID, region and blob.
Last checked 2026-09-30
Checking an implementation with Adobe Experience Platform Debugger and browser tools to confirm the ECID request, cookies and IDs sent to each application.
Integrates with: Experience Platform Debugger
Last checked 2026-09-30
How the older CX Enterprise applications depend on the Visitor ID Service. It supports Analytics, Audience Manager and Target directly, and only for applications the organisation licenses.
Last checked 2026-09-30
Replaces the legacy Analytics visitor ID (AID) with the ECID for AppMeasurement implementations; needed for published segments, Customer Attributes and A4T. Setting a custom s.visitorID breaks those integrations.
Integrates with: AppMeasurement
Last checked 2026-09-30
Shares the demdex ID and data collection servers with Audience Manager, runs its ID syncs and passes declared IDs, and lets Analytics and Audience Manager exchange segments on the same ID.
Integrates with: Declared IDs
Last checked 2026-09-30
When Campaign is connected to CX Enterprise, the Visitor ID Service replaces Campaign's own tracking cookie and links a visitor ID to a profile when the recipient clicks an email, so shared audiences can be matched on visitor IDs.
Integrates with: Campaign
Last checked 2026-09-30
Adobe Advertising (formerly Media Optimizer) is synchronised from the parent page rather than the ID sync iFrame, through its legacy domain cm.everesttech.net.
Integrates with: Advertising
Last checked 2026-09-30
The Web SDK and Mobile SDK generate and manage the ECID through the Edge Network without VisitorAPI.js, and add identity features that the legacy library does not have.
Last checked 2026-09-30
Also known as Web SDK ECID
The Edge Network generates the ECID and keeps it in a first-party kndctr identity cookie; the getIdentity command reads it, and CRM IDs or hashed emails travel alongside it in the XDM identityMap.
Integrates with: Web SDK, Edge Network
Last checked 2026-09-30
Also known as FPID
Device IDs the customer generates and sets from its own servers; the Edge Network seeds the ECID from them, which keeps the ID stable when browsers shorten the life of script-set cookies.
Last checked 2026-09-30
Also known as idMigrationEnabled
The idMigrationEnabled setting makes the Web SDK read and write the AMCV cookie so visitors keep their ECID when a site moves from VisitorAPI.js to the Web SDK, or while both run side by side.
Last checked 2026-09-30
Lets the Edge Network link first-party ECIDs (from FPIDs or random) with the third-party demdex ID when the browser allows it, so audiences built on first-party IDs can still be activated through third-party destinations. The ECID is seeded from the demdex ID, then the FPID, then randomly.
Last checked 2026-09-30
The demdex-based identifier, distinct from the ECID, that takes part in third-party identity flows when third-party cookies are available; readable through getIdentity. The Customer Attributes source in Experience Platform maps its IDs to the CORE namespace.
Last checked 2026-09-30
Carries the ECID in the URL between web properties the organisation owns so reporting and personalization stay continuous.
Last checked 2026-09-30
Hands the app's ECID to a WebView or mobile web page so a visitor who starts in the app keeps one identity on the web.
Last checked 2026-09-30
How the defaultConsent and setConsent settings decide when the Web SDK generates an ECID, sets cookies and sends data.
Integrates with: Consent management
Last checked 2026-09-30
Also known as Mobile SDK Identity extension
The Mobile SDK extension that gives an app its ECID for the Analytics, Audience Manager, Campaign Standard, Media Analytics and Target extensions; it syncs customer IDs, appends visitor data to URLs for web views and sets advertising IDs and push tokens.
Integrates with: Experience Platform Mobile SDK
Last checked 2026-09-30
The Mobile SDK extension that manages the ECID and identityMap for apps sending data through the Edge Network extension; apps that also use the direct application extensions need both identity extensions.
Integrates with: Experience Platform Mobile SDK
Last checked 2026-09-30
The ADBMobile visitorSyncIdentifiers and syncIdentifiers calls of the version 4 mobile SDKs, which were sunset on 31 August 2021 along with Mobile Services.
Replaced by Identity for Experience Cloud ID Service
Last checked 2026-09-30
How the service links the ECID to the customer's own IDs and to partner IDs.
Last checked 2026-09-30
Also known as setCustomerIDs, AuthState
setCustomerIDs attaches one or more CRM or login IDs to the ECID, each with an integration code and an authentication state (unknown, authenticated or logged out). These declared IDs are what Customer Attributes and Audience Manager match on; they are not stored in the cookie and must be set on every page.
Integrates with: Declared IDs, CX Enterprise Customer Attributes
Last checked 2026-09-30
Optional normalisation and SHA-256 hashing of customer IDs such as email addresses inside setCustomerIDs or a tags action, so plain identifiers are not sent to Adobe.
Last checked 2026-09-30
Also known as Sync Services, Destination Publishing iFrame
Matches the ECID with IDs held by data providers, ad platforms and cross-device partners by firing sync URLs in a separate iFrame; idSyncByURL and idSyncByDataSource add custom syncs. Match rates measure how well it works.
Integrates with: Audience Manager
Last checked 2026-09-30
Features that keep the ECID consistent across domains and under browser cookie limits.
Last checked 2026-09-30
Also known as appendVisitorIDsTo
appendVisitorIDsTo adds the ECID to links between domains the organisation owns, so the destination page reuses it when third-party cookies are blocked.
Last checked 2026-09-30
Also known as appendSupplementalDataIDTo
The ID that stitches a Target request to the matching Analytics hit for A4T; a helper carries it across a redirect to another page.
Integrates with: Analytics for Target
Last checked 2026-09-30
Also known as ECID library methods in a Safari ITP world
Library behaviour under Apple's Intelligent Tracking Prevention: since November 2020 Safari caps script-set and CNAME-set cookies, including s_ecid, at seven days; ECID 4.3.0 and later write the ECID through the CNAME tracking server.
Last checked 2026-09-30
The library uses CORS requests (falling back to JSONP on old browsers), and Adobe lists the domains to allow when a site has a strict Content Security Policy.
Last checked 2026-09-30
Also known as CX Enterprise data collection
The shared infrastructure through which CX Enterprise applications collect data from sites and apps: first-party collection on the customer's own domain, the regional edge sites that receive the data, and the hosts and IP ranges to allow through firewalls.
Integrates with: Experience Platform Data Collection
Last checked 2026-09-30
Also known as CNAME implementation, First-party CNAME data collection
Adobe's recommended way to set up first-party collection. The customer points a subdomain such as data.example.com at Adobe with a CNAME record and states the RDC type, and Adobe buys, installs and renews the TLS certificate. Collecting on the customer's own domain lets the ECID be set server-side in a first-party cookie and is less often blocked; the Web SDK uses it too.
Integrates with: Web SDK
Last checked 2026-09-30
Also known as RDC
Visitors connect to the nearest Adobe edge site, which forwards the data securely to a core site for processing and buffers it during outages. First-party collection can be limited to one region (Global by default, or Americas, Europe or Asia Pacific only); third-party collection on Adobe domains such as adobedc.net and omtrdc.net uses the default global set.
Last checked 2026-09-30
Also known as China Performance Optimization
A Beijing data collection centre, used on its own or with the global sites, that requires the China Performance Optimization add-on. It covers only Adobe Analytics with AppMeasurement, not other CX Enterprise services or Web SDK collection.
Integrates with: Analytics
Last checked 2026-09-30
Also known as Domains used by CX Enterprise, IP addresses used by CX Enterprise
Reference lists for firewall allowlists: the hosts the CX Enterprise interface uses (Adobe domains, adobelogin.com for IMS, typekit.net, adobedtm.com and Gainsight), Adobe's IP blocks, and the IP ranges of data collection and FTP servers by location. Analytics, Customer Journey Analytics, Marketo Engage and Workfront publish their own lists.
Last checked 2026-09-30
Adding dns-prefetch link tags for the Analytics tracking server, demdex.net, Advertising and Target hosts, because browsers cannot prefetch the hosts these libraries call dynamically; it saves a few milliseconds of page load.
Last checked 2026-09-30
Controls for consent, children's privacy and data subject requests tied to the ECID.
Last checked 2026-09-30
Also known as Adobe Opt-in
An extension of the ECID library that decides which Adobe libraries may set cookies before and after a visitor consents, per category, and connects to a consent management platform. It does not collect or store consent itself.
Last checked 2026-09-30
Connects Opt-in to a CMP that implements IAB TCF 2.0 (Visitor.js 5.0 or later), so the ECID and Audience Manager DIL libraries turn on or off from the TCF consent string.
Last checked 2026-09-30
Also known as disableThirdPartyCookies
The disableThirdPartyCookies setting stops the service from using the demdex.net cookie, so sites directed at children can measure visits with a first-party ECID only.
Last checked 2026-09-30
The ECID serves as the identifier in access and delete requests sent through Privacy Service under GDPR, CCPA and similar laws.
Integrates with: Privacy Service
Last checked 2026-09-30