Experience Cloud Identity Service overview

The Experience Cloud Identity Service enables the common identification framework for Experience Cloud Application Services. You can use the Experience Cloud Identity Service to set the Experience Cloud ID (ECID).

The ECID is a shared identity namespace used across Adobe Experience Platform and Experience Cloud applications to track visitor behavior and ensure that each device has a unique identifier that can persist across multiple sessions.

The Experience Cloud Identity Service, Experience Platform Identity Service, and ECID are three different entities.

The Experience Cloud Identity Service can replace different application-specific IDs and use the Customer IDs and Authentication States functionality to let you pass in your own customer IDs to the Experience Cloud.

The Experience Cloud Identity Service only works with Experience Cloud Application Services that you are subscribed to and will not provide access to other application services if you are not subscribed to them.

Experience Cloud Identity Service supports the following applications:

Going forward, the ID service is an integral component of many current and future Experience Cloud features, enhancements, and services. Currently, the ID service supports Analytics, Audience Manager, and Target. If you have not implemented the ID service, now is the time to start considering a migration strategy.

Feature Summary

In summary, the Experience Cloud Identity Service helps:

  • Uniquely identifies a visitor on a device across multiple applications.
  • Sets a first-party cookie in customer’s domain to ensure tracking on same domain. See the document on cookies and Experience Cloud Identity Service for more information.
  • Receives aliases and ID mappings from Experience Cloud customers and partners.
  • Manages ID synchronization within the Experience Cloud.
  • Supports ID synchronization with different third-parties across the ad tech ecosystem.

Experience Cloud Identity Service requirements

Your solution and other Adobe code libraries must meet certain requirements before you can use Identity Service.

  • Cookies and the Experience Cloud Identity Service: Experience Cloud Identity Service Identity Service uses your organization ID, the Experience Cloud AMCV cookie, and a demdex cookie to create and store unique, persistent identifiers for your site visitors. These cookies let Identity Service track visitors across your different domains and enable data sharing among different Experience Cloud solutions.
  • How the Experience Cloud Identity Service requests and sets IDs: An overview of the ID request and response process. These examples cover ID assignment on individual sites, across different sites, and for sites managed by different Experience Cloud customers with their own organization IDs.
  • Understanding ID synchronization and match rates: An overview of ID synchronization processes and match rates in the Experience Cloud Identity Service, including Adobe Media Optimizer and Identity Service.