Implement the Experience Cloud and become an administrator. This process modernizes your solutions for core service features like customer attributes and audiences.
On this page:
What you need to do to join the Experience Cloud:
Ensure that you have the appropriate Adobe Analytics or Adobe Target SKUs.
Modernize your implementation and get provisioned an administrator.
Manage users and products in the Admin Console.
After you are an administrator, you can log in at experiencecloud.adobe.com.
You will see the Administration link in the Experience Cloud menu navigation.
See Manage Experience Cloud users and products for help.
To log in to the Experience Cloud, your users must:
Optional: Link existing user accounts.
Most likely, you have users who are already members of solution groups, such an Analytics group that you managed in Analytics > Admin Tools.
When you map these groups to Experience Cloud enterprise groups, those users must manually link their solution account credentials to their Adobe ID.
Note: After enterprise and solution groups are mapped, new users are automatically linked. (Solution credentials are automatically created and linked to their Adobe ID.)
The following sections describe how to modernize your implementation. Modernizing your implementation enables core services in the Experience Cloud.
The simplest method for enabling Experience Cloud core services is to activate it automatically for Analytics and Target via the Experience Cloud ID service tool in Dynamic Tag Manager. (Or Launch, by Adobe.)
For complete Experience Cloud ID service (formerly, visitor ID), go here.
Also, the next-generation tag management is Launch, by Adobe
Not Using Dynamic Tag Management or Launch?
Perform the steps described in Implement the Experience Cloud ID Service for Analytics.
Adobe also recommends setting additional customer IDs. These IDs are associated with each visitor and enable current and future functionality in Experience Cloud core services.
Update your existing s_code to version H.27.3 or later, or your existing AppMeasurement.js to version 1.4 or later.
These files are available for download in the Code Manager in Analytics Admin Tools.
Synchronize the customer ID for Analytics. See Analytics & Target - synching the customer ID (below).
As a part of setting up the Experience Cloud ID service, Adobe recommends for Analytics and Target that you synchronize your customer IDs with the Experience Cloud.
In Target, the mbox3rdpartyid needs to get the customer ID and send it to Target. (See Working with Customer Attributes in Target.)
When a visitor authenticates on your website, or otherwise identifies himself, your implementation must expose that person's CRM customer ID to the page or app. Then you can use the appropriate function call to synchronize your customer ID to the Experience Cloud. This synchronization stores the visitor's CRM customer ID in the Experience Cloud, and activates that customer's attributes for use in the Experience Cloud.
For example, assume that Bob has Customer ID 52mc210tr42 in your CRM system. When Bob authenticates on your site, you must expose this ID on the page, and use the ID to synchronize it by one of two means:
The Customer ID must be set on each Analytics server call where the Customer ID is known.
Enabling Attributes for Historical Data
Customer attribute data is made available after visitors log in. If you have not yet implemented the latest Experience Cloud ID service, and if you have historically been tracking customer IDs in a prop or eVar, you can request a process that sends historical logins to the Experience Cloud. This process lets you begin using customer attributes immediately.
Contact Customer Care to enable historical data.
Experience Cloud services (such as Experience Cloud ID service and People) are associated with an Experience Cloud organization instead of an individual report suite. To ensure that these services operate correctly, each Analytics report suite must be mapped to an Experience Cloud organization.
Verify that you are on regional data collection (RDC). If your data collection domain is omtrdc.net, or if your CNAME is mapped to omtrdc.net, you are on RDC. See Transitioning to RDC for more information. If you are using first-party cookies, refer to CNAME and the Visitor ID Service for information about data collection CNAMEs and cross-domain tracking.
In Dynamic Tag Management, click Adobe Analytics Settings in Dynamic Tag Management for deployment information.. See
Use the following process to ensure the Experience Cloud ID service is implemented correctly on your site.
Expected response containing the Experience Cloud ID:
Analytics image request containing the Experience Cloud ID (mid):
Experience Cloud ID in the mbox request:
What Is the Grace Period?
After you deploy the visitor ID service, new visitors no longer receive an Analytics visitor ID from your data collection server. If sections of your site have not yet implemented the visitor ID service, when visitors browse to these sections, the Experience Cloud ID is not recognized and visitors are assigned a legacy Analytics visitor ID. This can cause potential problems, including duplicate visits and incorrect attribution.
Once you are up and running, navigate to Administration > Launch Admin Console, where you can manage users and product profiles.
Users that are added to the Customer Attributes group will see the Customer Attributes menu item on the left side of the Experience Cloud interface
Take advantage of the following core service features.
People > Customer Attributes
If you capture enterprise customer data in a customer relationship management (CRM) database, you can upload the data into a customer attribute data source in the Experience Cloud. Once uploaded, leverage the data in Adobe Analytics and Adobe Target.
People > Audience Library
Experience Cloud Audiences is the interface that lets you create audiences, combine existing audiences to create composite audiences, and view all shared audiences.
Data storage and privacy disclosure for using People.
If you leverage real-time audience profiling and other core services within the Adobe Experience Cloud, use of these services might impact which data center (and country) your data resides. Specifically, because the core services of the Adobe Experience Cloud leverage Adobe Audience Manager, data used within the People core service must reside within Audience Manager servers in the United States.
When leveraging core services made available via the People core service, the types of data sent from other Adobe products to audience management are:
Adobe recommends against providing personal data to Adobe Analytics. Rather, use a one-way hash to pseudonymize the data before it is sent to Adobe.
All these data elements are delivered to Adobe Audience Manager in the form of log files. Audience Manager processes and stores this data within the United States. Audience Manager does not provide an option to store or process this data outside of the United States.
Cookies and Opt-Outs
Use of real-time audience profiling leverages the Audience Manager cookie, in addition to the cookies used for Analytics and Target.
If you want to provide the proper opt-out ability, visitors to your site must add the Audience Manager opt-out to your existing opt-out process.
See Adobe Experience Cloud - Implementing Adobe Opt-Outs for instructions.
See Data Collection CNAMEs and Cross-Domain Tracking for enabling cross-domain tracking.