Show Menu
TOPICS×

Implementation with Dynamic Tag Management

Older implementations use Dynamic Tag Management (DTM) to set up, deploy, and integrate the Experience Cloud Identity Service with your other Experience Cloud solutions.

Implementation with Dynamic Tag Management

Older implementations use Dynamic Tag Management (DTM) to set up, deploy, and integrate the Experience Cloud Identity Service with your other Experience Cloud solutions.
Currently, Adobe Experience Platform Launch is the preferred and recommended implementation tool because it helps simplify complex tag management tasks and automates code placement beyond the capabilities of DTM. See Implement with Launch .

Dynamic Tag Management and the ID Service

Dynamic Tag Management lets you configure, deploy, and manage your ID service instance and related Experience Cloud solution integrations. DTM helps simplify the implementation process because it is deeply integrated with the ID service and other Experience Cloud solutions. Simply add and configure the Experience Cloud ID tool and specify information, such as:
  • Experience Cloud Organization ID (automatically populated if linked to the Experience Cloud)
  • Analytics tracking server (secure and non-secure)
  • Experience Cloud server (for first-party tracking servers)
DTM is available at no charge to any Experience Cloud customer.
Getting started with DTM
DTM is a simple yet powerful tool. If you're not already using it, we strongly encourage you to do so. See the DTM documentation and DTM Jump Start videos to get started with this service. For instructions on how to set up the ID service with DTM, see the information and procedures in the sections below.

Deployment guidelines

Review this these requirements and procedures before you try to implement the Experience Cloud Identity Service with Dynamic Tag Management (DTM).
Provision your account
Before you can get started, make sure your organization and solutions have been provisioned for the Experience Cloud and you're familiar with Dyanamic Tag Management. This documentation can help you get started:
ID Service code placement and load order
The ID service works by requesting and receiving a unique ID from the Adobe data collection servers. To work properly, your ID service code must be:
  • The first block of Adobe code that executes on the page.
  • Placed as high on the page as possible, usually within the
    <head>
    code block.
As long as you maintain all of your Adobe solutions and code libraries in DTM, it will ensure that your ID service code is placed in the right location and fires at the right time.
Validate regional data collection
Customers must provide a CNAME or use
*.sc.omtrdc
for regional data collection (RDC). Obtain the specific, RDC settings from your Adobe consultant.
Configure Analytics report suites
New Analytics customers should create a report suite for data collection.

Implement the Experience Cloud Identity Service with DTM

Follow these steps to implement the ID service with Dynamic Tag Management (DTM).
Prerequisites
Implementation steps
To implement the ID service with DTM:
  1. In the DTM Dashboard, click the web property you want to work with.
  2. In the
    Overview
    tab of your selected web property, click
    Add a Tool
    .
  3. In the
    Tool Type
    list, click
    Experience Cloud Identity Service
    .
    This action populates the
    Experience Cloud Organization ID
    box with your Organization ID. If your DTM account is not linked to the Experience Cloud, you will have to provide this ID. To link your account, see Link Accounts in the Experience Cloud . See the requirements for information about how to find your Organization ID.
  4. Type the name of your tracking server in the
    Tracking Server
    box. If you're not sure how to find your tracking server see the FAQ and Correctly Populate the trackingServer and trackingServerSecure variables .
  5. Click
    Create Tool
    and
    Save Changes
    .
    After saving, the ID service is set up as a tool in DTM. However, it is not ready to use yet. Your DTM tool still has to go through the DTM publishing/approval process and you may want to configure additional parameters. For information about the DTM approval process, see the User Basics Jump Start video. For information about the additional parameters you can add to DTM, see Experience Cloud Identity Service Settings for DTM .

Experience Cloud Identity Service Settings for DTM

Describes the Organization ID, General and Customer Settings fields and how they're used by the Experience Cloud ID service.

How do I find these settings?

The settings are available after you add and save the ID service as a tool in Dynamic Tag Management (DTM). You can also access these settings by clicking the gear icon from the Installed Tools section of your DTM web property.

Organization ID

This is the ID required by and associated with your provisioned Experience Cloud company. An organization is the entity that enables an administrator to configure users, groups, and control single sign-on access in the Experience Cloud. The Organization ID is a 24-character alphanumeric string, followed by (and must include) @AdobeOrg. Experience Cloud administrators can find this ID in Experience Cloud > Tools .

General settings

These settings let you specify tracking servers, code versions, and add other variables.
The following table lists and defines the General settings.
Automatically request Visitor ID
When checked, Dynamic Tag Management automatically calls the
getMarketingCloudVisitorID()
method before loading any of the Adobe solutions that use the Experience Cloud Identity Service.
Analytics Tracking Server
The name of the tracking server used for Analytics data collection. This is the domain at which the image request and cookie is written (e.g.,
http://site.omtrdc.net
).
If you don't know your tracking server URLs, check your
s_code.js
or
AppMeasurement.js
files. You'll want the URL set by the
s.trackingServer
variable.
Tracking Server Secure
The name of the secure tracking server used for Analytics data collection. This is the domain at which the image request and cookie is written (e.g.,
https://site.omtrdc.net
).
If you don't know your tracking server URLs, check your
s_code.js
or
AppMeasurement.js
files. You'll want the URL set by the
s.trackingServerSecure
variable.
Experience Cloud Server
If your company uses first-party data collection (CNAME) to utilize first-party cookies in a third-party context, enter the tracking server here (e.g.,
http://metrics.company.com
.)
Experience Cloud Server Secure
If your company uses first-party data collection (CNAME) to utilize first-party cookies in a third-party context, enter the tracking server here (e.g.,
https://metrics.company.com
.)
Library Version
Sets the version of the ID service code library (
VisitorAPI.js
) that you want to use. You cannot edit these menu options.
Settings
These fields let you add function variables as key-value pairs. Click
Add
to add one or more variables to your ID service implementation.
Set the
cookieDomain
variable here. It is required for multi-part, top-level domains where either of last 2 parts of the URL are > two characters. See the Configuration Variables documentation linked above.

Customer Settings

Additional fields that let you add an integration code or authenticated state status.
Integration Code
An integration code is a unique, customer provided ID. The integration code should contain the value you used to create a data source in Audience Manager.
Value
The value should be a data element containing the user id. Data elements are suitable containers for dynamic values like IDs from a client-specific internal system.
Auth State
Options that define or identify visitors according to their authentication status (e.g., logged in, logged out). See Customer IDs and Authentication States .

Test and verify the Experience Cloud Identity Service

These instructions, tools, and procedures help you determine if the ID service is working properly. These tests apply to the ID service in general and for different ID service and Experience Cloud solution combinations.

Before you begin

Important information to know before you begin testing and verifying the ID Service.
Browser environments
When testing in a normal browser session, clear your browser cache before each test.
Alternatively, you can test the ID service in an anonymous or incognito browser session. In an anonymous session, you don't need to clear your browser cookies or cache before each test.
Tools
The Adobe debugger and the Charles HTTP proxy can help you determine if the ID service has been configured to work properly with Analytics. The information in this section based on the results returned by the Adobe debugger and Charles. However, you should feel free to use whatever tool or debugger works best for you.

Testing with the Adobe Debugger

Your service integration is configured properly when you see a Experience Cloud ID (MID) in the Adobe debugger response. See Cookies and the Experience Cloud Identity Service for more information about the MID.
To verify the status of the ID service with the Adobe debugger :
  1. Clear your browser cookies or open an anonymous browsing session.
  2. Load your test page that contains ID service code.
  3. Open the Adobe debugger.
  4. Check the results for a MID.

Understanding Adobe Debugger results

The MID is stored in a key-value pair that uses this syntax:
MID= *
Experience Cloud ID
*
. The debugger displays this information as shown below.
Success
The ID service has been implemented properly if you see a response that looks similar to this:
mid=20265673158980419722735089753036633573
If you're an Analytics customer, you may see an Analytics ID (AID) in addition to the MID. This happens:
  • With some of your early/long-time site visitors.
  • If you have a grace period enabled.
Failure
Contact customer care if the debugger:
  • Does not return a MID.
  • Returns an error message that indicates your partner ID has not been provisioned.

Testing with the Charles HTTP proxy

To verify the status of the ID service with Charles:
  1. Clear your browser cookies or open an anonymous browsing session.
  2. Start Charles.
  3. Load your test page that contains ID service code.
  4. Check for the request and response calls and data described below.

Understanding Charles results

Refer to this section for information about where to look, and what to look for, when you use Charles to monitor HTTP calls.

Successful ID Service requests in Charles

Your ID service code is working properly when the
Visitor.getInstance
function makes a JavaScript call to
dpm.demdex.net
. A successful request includes your Organization ID . The Organization ID is passed as a key-value pair that uses this syntax:
d_orgid= *
organization ID
*
. Look for the
dpm.demdex.net
and the JavaScript calls under the Structure tab. Look for your Organization ID under the Request tab.

Successful ID Service responses in Charles

Your account has been provisioned correctly for the ID service when the response from the Data Collection Servers (DCS) return a MID. The MID is returned as a key-value pair that uses this syntax:
d_mid: visitor Experience Cloud ID
. Look for the MID in the Response tab as shown below.

Failed ID Service responses in Charles

Your account has not been provisioned correctly if the MID is missing from the DCS response. An unsuccessful response returns an error code and message in the Response tab as shown below. Contact customer care if you see this error message in the DCS response.
For more information about error codes, see DCS Error Codes, Messages, and Examples .