Show Menu
TOPICS×

Enable your implementation for cross-solution services

If you recently implemented Experience Cloud using Experience Platform Launch, you're already set up for Customer Attributes and Experience Cloud Audiences. You can also manage users and products in the Admin Console.
For existing customers, you may need to modernize your solution implementations and implement the Experience Cloud. Doing so enables you to leverage Customer Attributes and audience features across Adobe Analytics, Audience Manager, and Adobe Target. To accomplish this, you will:

Step 1. Join the Experience Cloud and become an administrator

What you need to do to join the Experience Cloud:
Ensure that you have the appropriate Adobe Analytics or Adobe Target SKUs.
  • Adobe Analytics: Standard or Premium (not the legacy SiteCatalyst SKU).
  • Adobe Target: Standard or Premium.
For Target, migrate to at.js from mbox.js. See Upgrading from at.js 1. x to at.js 2. x .
Modernize your implementation and get provisioned an administrator.
  1. Follow the steps below in Deploy the [Experience Cloud ID Service] .
  2. Contact your Account Manager and start the provisioning process for the Experience Cloud.
Manage users and products in the Admin Console.

Administrator login

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.

User login

To log in to the Experience Cloud, your users must:
  1. Have an Adobe ID (or Enterprise ID for your company).
  2. Belong to a solution group that is mapped to an enterprise group.
  3. If necessary, link their solution accounts to their Adobe ID (described below).
Optional: Link existing user accounts.
Most likely, you have users who are already members of solution groups, such an Analytics group that you previously 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.
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.

Step 2. Implement the Experience Cloud ID Service using Experience Platform Launch, or Dynamic Tag Management

The Experience Cloud ID Service provides a common ID for cross-solution integration. It provides cross-domain visitor identification and a path for cross-device/browser targeting and personalization based on CRM data uploaded via Customer Attributes.
The simplest method for enabling Experience Cloud core services is to activate it automatically for Analytics and Adobe Target via the Experience Cloud ID Service extension in Experience Platform Launch, or via the ECID tool in Dynamic Tag Management. (Experience Platform Launch is strongly recommended.)
For complete Experience Cloud ID Service help (formerly, visitor ID), go here .
Not Using Experience Platform Launch or Dynamic Tag Management?
If you are not using Experience Platform Launch or Dynamic Tag Management, manually implement the ID service via the JavaScript Deployment (VisitorAPI.js), as follows:
Task
Description
Adobe also recommends setting additional customer IDs . These IDs are associated with each visitor and enable current and future functionality in Experience Cloud.
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. (The JavaScript Implementation guide is available if you need more information about AppMeasurement.js.)
Synchronize the customer ID for Analytics

Analytics & Adobe Target - synching the customer ID

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 Adobe 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:
  • Call visitor.setCustomerIDs({"crm_id":"52mc210tr42"}) using the Visitor ID service. Or,
  • Populate the Customer ID (52mc210tr42) in a prop or eVar.
The Customer ID must be set on each Analytics server call where the Customer ID is known.

Mobile SDKs

See the Experience Cloud ID Service section for syntax examples about how to set additional customer IDs in Android and iOS Mobile applications.

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.

Step 3. Map report suites to an Experience Cloud Organization

Experience Cloud services (such as Experience Cloud ID Service and the People service) are associated with an Experience Cloud organization instead of an individual Analytics report suite. To ensure that these services operate correctly, each Analytics report suite must be mapped to an Experience Cloud organization.

Step 4. (Adobe Analytics) Update your Analytics AppMeasurement code

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 Experience Cloud ID Service for information about data collection CNAMEs and cross-domain tracking.
It is recommended that you modernize your Analytics implementation by updating your JavaScript libraries, including the Visitor API. The simple way to accomplish this is to add an Adobe Analytics tool in Dynamic Tag Management, specifying Automatic as the configuration method.
In Dynamic Tag Management, click <Web Property Name> > Overview > Add a Tool > Adobe Analytics . See Adobe Analytics Settings in Dynamic Tag Management for deployment information.

Step 5. (Adobe Target) Update your Adobe Target implementation

  • It is recommended that you add an Adobe Target extension in Experience Platform Launch, so that your library retrieval is automatic. You can also set up the Experience Cloud ID Service extension for Adobe Target (and other solutions) using Experience Platform Launch. The Experience Cloud ID Service update is required for Adobe Target to use core services. (If you use Dynamic Tag Management, add an Adobe Target tool . You can also use Dynamic Tag Management to deploy the Experience Cloud ID Service for Adobe Target.)
  • If you are not using Experience Platform Launch or Dynamic Tag Management, update your mbox library manually.
  • Request access to use Adobe Analytics as the reporting source for Adobe Target. Target and Analytics data are combined on the same server call during processing so that visitors are connected between the two solutions. See Analytics for Target Implementation .
    All Analytics customers are already provisioned for core services like Customer Attributes. If you are not an Analytics customer, contact Customer Care to request to be provisioned.

Step 6. Verify the implementation

Use the following process to ensure the Experience Cloud ID Service is implemented correctly on your site.
  1. Clear cookies for your site so you can see the request to the Experience Cloud ID Service (the request happens on the first visit, then approximately once per visitor per week).
  2. Using a packet analyzer or the network panel in a web browser debugger, look for a request going to dpm.demdex.net.
  3. Verify that the response contains d_mid and a value, for example: _setMarketingCloudFields({"d_mid":"4235...
  4. Verify that the Analytics request contains the mid parameter (the Experience Cloud ID). During the grace period (if it is enabled), you should also see an aid parameter (the Analytics visitor ID).
Expected response containing the Experience Cloud ID:
Analytics image request containing the Experience Cloud ID (also known as mid or visitor ID ):
Experience Cloud ID in the mbox request:

What Is the Grace Period?

After you deploy the Experience Cloud ID Service, new visitors no longer receive an Analytics Experience Cloud ID from your data collection server. If sections of your site have not yet implemented the Experience Cloud 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.
For example, if the support section of your site is managed in a separate CMS, you might have a different Analytics JavaScript file for this section. If you deploy the Experience Cloud ID on your main site before you deploy the ID service to the support site, new visitors receive a legacy Analytics ID when they visit the support section, and visits that span both site sections are reported as different visits.
Deploying the Experience Cloud ID Service on sites that are using multiple JavaScript files or other technologies (such as Flash) can cause coordination issues because you need to enable the Experience Cloud ID Service on all portions of your site at the same time. By configuring a grace period, new visitors to continue to receive an Analytics visitor ID from the ID service, so visitors can be consistently identified on sections of your site that have not been upgraded to use the visitor ID service.

Step 7. Manage users and products

Once you are up and running, navigate to the Admin Console , where you can manage users and product profiles.

Customer Attributes

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.

Step 8. Begin sharing attribute and audience data

Take advantage of the following 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

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 service must reside within Audience Manager servers in the United States.
When leveraging core services made available via the People service, the types of data sent from other Adobe products to audience management are:
  • Analytics key/value pairs (props, eVars, list vars, and so on). By default, the log lines include IP address, including the last octet of the IP (assuming that the IP address was not modified by IP obfuscation settings within Adobe Analytics).
  • Traits and segments that visitors qualify for based on rules set up in Audience Manager.
  • (Optional) One or more of your IDs. Depending on your implementation of the ID service, you might also be sending in one or more of your IDs, such as CRM IDs or hashed email addresses. If this data is sent into Adobe Analytics, it is transferred to Adobe audience management. Adobe recommends against providing personal data to Adobe Analytics. Rather, use a one-way hash to mask the data before it is sent to Adobe.
  • Segments originating in Analytics via the back-end segment sharing capability.
  • The demdex.net cookie is set if third-party cookies are not blocked. The AMCV_###@AdobeOrg first-party cookie is always set with the Experience Cloud ID Service.
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 Data Collection CNAMEs and Cross-Domain Tracking for enabling cross-domain tracking.