Adobe Experience Cloud Identity Service
- Topics:
- Identities
- Integrations
CREATED FOR:
- Developer
- User
- Admin
- Leader
The Experience Cloud Identity Service enables the common identification framework for Experience Cloud Application and Services. It works by assigning a unique, persistent ID known as the Experience Cloud ID (ECID) to a site visitor.
Understanding the main entities of identity
To better understand how Adobe helps uniquely identify visitors and resolves identity information, reade the breakdown below:
- Experience Cloud Identity Service: The Experience Cloud Identity Service is responsible for setting the Experience Cloud ID (ECID). For more information, read the Experience Cloud Identity Service overview.
- Experience Cloud ID (ECID): The ECID is a shared identity namespace used across Adobe Experience Platform and Adobe Experience Cloud applications to identify people and devices. For more information on the ECID, read the ECID overview.
- Experience Platform Identity Service: The Experience Platform Identity Service provides you with a comprehensive view of your customers and their behavior by bridging identities across devices and systems. For more information, read Experience Platform Identity Service overview.
Getting Started
Experience Cloud ID Javascript Libraries JavaScript for the Experience Cloud Identity Service is located at: https://github.com/Adobe-Marketing-Cloud/id-service/releases New or Featured Items |
Release Notes Version 4.4 July 17, 2019 release includes support for the SHA-256 hashing algorithm that allows you to pass in customer IDs or email addresses, and pass out hashed IDs. Version 4.0 February 12, 2019 release includes the Opt-in service used to identify if you can place a cookie on a user's device or browser when visiting your site.
Experience Cloud Resources |
Experience Cloud Services
- Identity Service Help
- Overview
- Implementation
- Implementation methods
- Implementation guides
- Implement with Experience Platform tags
- Implement for Analytics
- Implement for Target
- Implement for Analytics and Audience Manager
- Implement for Analytics, Audience Manager, and Target
- Using the ID Service with A4T and a Server-side Implementation of Target
- Direct Integration with the ID Service
- Direct Integration Use Cases
- Test and verify the ID Service
- Opt-in Service
- ID Service API
- ID Service API Overview
- Configuration
- Configurations overview
- audienceManagerServer and audienceManagerServerSecure
- cookieDomain
- cookieLifetime
- disableIdSyncs
- disableThirdPartyCalls
- disableThirdPartyCookies
- idSyncAttachIframeOnWindowLoad
- idSyncContainerID
- idSyncSSLUseAkamai
- loadTimeout
- overwriteCrossDomainMCIDAndAID
- resetBeforeVersion
- sdidParamExpiry
- Secure and SameSite configurations
- secureCookie
- useCORSOnly
- whitelistParentDomain and whitelistIframeDomains
- Methods
- Methods
- appendSupplementalDataIDTo
- appendVisitorIDsTo (Cross-Domain Tracking)
- callTimeOut Methods
- ID Synchronization by URL or Data Source
- getInstance
- getAnalyticsVisitorID
- getCustomerIDs
- setCustomerIDs
- getMarketingCloudVisitorID
- getLocationHint
- getVisitorValues
- isClientSideMarketingCloudVisitorID
- resetState
- Reference
- Reference Overview
- Analytics Reference
- Analytics Reference Overview
- CNAME Implementation Overview
- Setting Analytics and Experience Cloud IDs
- Order of Operations for Analytics IDs
- ID Service Migration Decision Points
- ID Service Migration Scenarios
- Analytics and Identity Requests
- Server-side Implementation Mixed with JavaScript
- The ID Service Grace Period
- Google Chrome SameSite labelling changes
- Content Security Policies and the ID Service
- COPPA Support in the ID Service
- CORS Support in the ID Service
- Customer IDs and Authentication States
- ECID library methods in a Safari ITP world
- Identifying Unique Visitors
- Get Region and User IDs From the AMCV Cookie or the ID Service
- Requirements for the ID Service
- Video Heartbeat and the ID Service
- Data Workbench and the ID Service
- SHA256 Hashing Support for setCustomerIDs
- FAQs
- Release notes for ID Service