Dynamic Tag Management Product Documentation

Adobe® Marketing Cloud

Dynamic Tag Management ProductDocumentation

Contents

Dynamic Tag Management Product Documentation............................................6

Release Notes for Dynamic Tag Management.......................................................8

Dynamic Tag Management Overview.....................................................................9

DTM Demo Videos.................................................................................................13

Getting Started.......................................................................................................14

Planning for Dynamic Tag Management................................................................................16

Browser Support...................................................................................................................16

Access DTM through Experience Cloud...............................................................................16

Managing Users and the Publish Workflow...........................................................................16

Manage Account Settings.....................................................................................................17

Architecture...........................................................................................................................18

Best Practices for Getting Started with Adobe Dynamic Tag Management...........................18

Basics for the First-Time User..................................................................................................................19

DTM Technical Architecture and Hosting.................................................................................................29

Planning Your Migration to DTM...............................................................................................................36

Migrating to DTM: A Closer Look at Adobe Analytics...............................................................................40

Benefits of a Tag Management System: A Focus on DTM.......................................................................47

Web Properties......................................................................................................50

Create a web property...........................................................................................................53

Delete a web property...........................................................................................................55

Users and Permissions.........................................................................................56

Manage Users.......................................................................................................................56

Manage Users for DTM in the Adobe Marketing Cloud............................................................................57

Manage Users for DTM using the Legacy Process..................................................................................58


Last updated 1/2/2018

Manage Groups....................................................................................................................59

Create and Manage Groups for DTM in the Adobe Admin Console........................................................60

Create and Manage Groups in DTM........................................................................................................63

Frequently Asked Questions about Users and Permissions.................................................68

Embed Code and Hosting Options......................................................................70

Hosting Considerations (FAQ)...............................................................................................72

Akamai..................................................................................................................................74

Migrate from Amazon S3 to Akamai.........................................................................................................74

FTP.......................................................................................................................................75

Library Download..................................................................................................................76

Header and Footer Code.......................................................................................................78

Add header and footer code.....................................................................................................................78

Verify header and footer code..................................................................................................................79

Tools.......................................................................................................................80

Add Adobe Experience Manager ContextHub Tool...............................................................80

Data Layer Management Using the ContextHub Tool..............................................................................83

Add Adobe Analytics Tool....................................................................................................101

General..................................................................................................................................................105

Library Management..............................................................................................................................106

Global Variables.....................................................................................................................................107

Page Views and Content........................................................................................................................108

Link Tracking...........................................................................................................................................108

Referrers and Campaigns......................................................................................................................109

Cookies..................................................................................................................................................110

Customize Page Code...........................................................................................................................111

FAQ for Adobe Analytics Release - July 24 2014...................................................................................111

Manually implement Adobe Analytics (legacy).......................................................................................113

Add Adobe Audience Manager Tool....................................................................................115

Add Adobe Media Optimizer Tool........................................................................................116

Media Optimizer Rule Example..............................................................................................................118

Add Adobe Target Tool........................................................................................................120

Library Management - Adobe Target......................................................................................................121



Contents

Global Parameters - Adobe Target.........................................................................................................122

Mbox rule example for Dynamic Tag Management................................................................................123

Add Google Analytics Tool..................................................................................................125

Call Google Analytics Objects in DTM Using Scripts.............................................................................128

Add Google Universal Analytics Tool...................................................................................130

Call Google Universal Analytics Objects in DTM Using Scripts.............................................................133

Add Nielsen Tool.................................................................................................................135

Insert third-party tags..........................................................................................................138

Object References to Handle Cookies................................................................................139

Data Elements......................................................................................................140

Create a data element.........................................................................................................145

Rules.....................................................................................................................147

Event-Based Rules Example...............................................................................................149

Page Load Rules Example..................................................................................................152

Page Load Rules - Advanced.................................................................................................................155

Load Order for Rules...........................................................................................................157

Create new rule...................................................................................................................160

Create conditions for event-based rules.................................................................................................160

Create conditions for page-load rules....................................................................................................173

Create conditions for direct-call rules.....................................................................................................174

Set up actions for the condition to trigger...............................................................................................174

Test unpublished rules for Akamai hosting.............................................................................................176

Test rules for Library Download or FTP..................................................................................................176

Rule Conditions and Functions...........................................................................................176

Migrating to Dynamic Tag Management............................................................180

Migrating from Adobe Tag Management.............................................................................180

Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping...........................................................181

Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping...........................................................186

Dynamic Tag Management Object Reference ..................................................191



Frequently Asked Questions..............................................................................192

How Do Tag Management Systems Improve Page Load Speed?.......................................200

Adobe Cloud Platform Launch FAQ....................................................................................202

Resources............................................................................................................207

Troubleshooting...................................................................................................208

Chrome Warning on 2G Networks......................................................................................210

Dynamic Tag Management Plugins....................................................................212

Search Discovery Plugins...................................................................................................212

Disruptive Advertising Debugging Plugin............................................................................214

Tagtician Debugging Plugin.................................................................................................215

Documentation Updates.....................................................................................218

Previous Release Notes......................................................................................225

Contact and Legal Information...........................................................................244



Contents

Dynamic Tag Management Product Documentation

Dynamic Tag Management (DTM) lets you manage your Adobe Marketing Cloud solutions and other tags acrossall of your sites, regardless of your number of domains.

Last Updated: November 14, 2017

VideosGetting Started & Popular Topics

• DTM Demo Videos• Add Adobe Experience Manager ContextHub Tool• Best Practices for Getting Started with Adobe Dynamic

Tag Management (New) Plugins

• Best Practices for Implementing Adobe Target usingDynamic Tag Management (New)

• Dynamic Tag Management Plugins

Community Resources• Request access• Frequently asked questions (FAQ)

• Solution Overview• Troubleshooting

• Marketing Cloud ForumWhat's New and Release Notes • Adobe Marketing Cloud Community

• Idea Exchange• Launch, by Adobe• Adobe Training and Tutorials

Launch is the next-generation of tag managementcapabilities from Adobe. Launch gives customers a

• Featured Solutions Center

Digital Marketing Blogsimple way to deploy and manage all of the analytics,

• #Dynamic Tag Managementmarketing, and advertising tags necessary to powerrelevant customer experiences.

Twitter• Release Notes for Dynamic Tag Management

• If you have questions about dynamic tag managementyou can also tweet us at @AdobeMktgCare with thehashtag #DTM.

Current release notes and known issues for dynamictag management.

• Marketing Cloud ID Services settings

Learn how to deploy the Marketing Cloud ID Service(Visitor ID) using dynamic tag management.

• Deploy Adobe Analytics

Learn how to let dynamic tag management automaticallymanage your report suites accounts andAppMeasurement code.

• Manually implement Adobe Analytics (legacy)

Learn how to manually deploy an Adobe Analytics tool.This procedure describes a manual (legacy)implementation.

• Deploy Adobe Target

Learn now to automatically deploy Adobe Target.

• Google Universal Analytics

Settings for deploying Google Universal Analytics.

6Dynamic Tag Management ProductDocumentation

https://marketing.adobe.com/resources/help/en_US/target/dtm/

https://marketing.adobe.com/resources/help/en_US/target/dtm/

http://www.adobe.com/solutions/digital-marketing/dynamic-tag-management.html

http://help-forums.adobe.com/content/adobeforums/en/marketing-cloud-forum/adobe-marketing-cloud.html

http://helpx.adobe.com/marketing-cloud.html?promoid=KAWSE

http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/idb-p/IdeaExchange3

https://marketing.adobe.com/resources/help/en_US/experience-cloud/launch/

http://helpx.adobe.com/learning.html?promoid=KAUDK

http://www.omniture.com/en/products/online_business_optimization

http://blogs.adobe.com/digitalmarketing/tag/dynamic-tag-management/

https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-dtm-settings.html

Additional Help

• Documentation Updates

See the changes made to this documentation.

• Marketing Cloud Release Notes

Learn about what's new for all solutions.

• Product Documentation Home

Search and browse for help across all productdocumentation topics.

Contact Adobe Global Services for help with animplementation.

Contact your Adobe Account Manager to find out moreabout professional services.

7Dynamic Tag Management ProductDocumentation

https://marketing.adobe.com/resources/help/en_US/whatsnew/

https://marketing.adobe.com/resources/help/en_US/home/

Release Notes for Dynamic Tag ManagementRelease notes and known issues for Dynamic Tag Management.

This section contains the following information:

• Current Release Notes

• Documentation Updates, Previous Release Notes, and Marketing Cloud Release Notes

Current Release Notes

The June 17, 2016 Dynamic Tag Management release includes the following changes:

New Features

DescriptionFeature

Use the AEM ContextHub tool to integrate Dynamic Tag Management with the AdobeExperience Manager (AEM) ContextHub (AEM's version of the data layer).You can

AEM ContextHub Tool

also use this tool to integrate DTM with any data layer, even for websites that do notuse AEM.

See Add Adobe Experience Manager ContextHub Tool.

The dataelementchanged event lets you select a specific data element to use as atrigger.

dataelementchanged event

See Event Types.

Documentation Updates, Previous Release Notes, and Marketing Cloud Release Notes

In addition to the notes for each release, the following resources provide additional information:

DescriptionResource

View detailed information about updates to this guide that might not be included inthese release notes.

Documentation Updates

View information about new features and enhancements in previous releases ofDynamic Tag Management.

Previous Release Notes

View the latest release notes for the Adobe Marketing Cloud solutions.Marketing Cloud ReleaseNotes

8Release Notes for Dynamic Tag Management



Dynamic Tag Management OverviewDynamic tag management lets marketers quickly and easily manage tags and provides innovative tools for collectingand distributing data across digital marketing systems. Dynamic tag management also enables responsive deliveryof user-specific content —providing new levels of agility and control to companies seeking to thrive in today’s fastpaced digital marketplace.


• Business Challenge• Solution• Benefits• Key Features• Overview Videos

Business Challenge

The world of digital marketing is a complex space. Marketers are expected to consistently identify their customersand prospects and the online spaces they inhabit—and that’s just the beginning. Marketers must then deliver contentwhile measuring its engagement and effectiveness all the way through the conversion funnel and beyond. Toaccomplish this, marketers have historically needed to rely upon JavaScript “tags” to implement their strategies andprograms on their websites. For the most part, “tagging” sites and other online experiences has been the domainof IT, subjecting marketing strategy to IT process and prolonged implementations based upon technical releaseschedules and resource availability.

In addition, as the technologies and tools used by marketers to implement digital strategies and deliver consumerexperiences become more sophisticated, the technical requirements associated with installing and managing thesetools continues to grow.

These factors are hampering marketers’ ability to quickly adapt to the fast-paced, dynamic digital marketplace andcompromising the effectiveness of the very tools that are designed to make digital marketers successful.

Solution

Dynamic tag management provides digital marketers tremendous flexibility and control to implement and optimizedigital experiences while reducing IT dependence—allowing marketers to focus on marketing, rather than tags.Dynamic tag management not only solves standard tag management problems, such as code deployment, datamanagement, and rule building, but also provides an intuitive capability that maps directly to marketing scenariosand user experiences. This approach makes it easier for marketers to develop digital marketing strategies andquickly implement them without dealing with potentially frustrating IT projects. To allow marketers to deliver the rightmessage or collect the right data for any given scenario, this robust capability identifies specific users and audiencesegments on the site to enable instantaneous delivery of segment-specific content and to generate specificexperience-based reporting.

Dynamic tag management is offered to Adobe Marketing Cloud customers as an included, value-add feature. Adobeis committed to keeping the dynamic tag management capability open and will continue to develop features thatallow for deployment of the most popular digital marketing services, including non-Adobe services.

Benefits

Dynamic tag management provides the following benefits:

• Improved Site Speed: Optimize loading of multiple analytics and marketing tags, proven to slow page loads.

9Dynamic Tag Management Overview

• Quicker Implementations: Significantly reduce deployment time.

• Increased Efficiencies: Reclaim substantial amounts of time spent managing analytics and media tags.

• Control and Security: Develop and deploy tag strategies by collaborating with marketing, analysts, and IT torecommend, test, and deploy tags within protocols and across systems all within the capability.

• Enhanced Flexibility: Quickly test and optimize tags without being bound by release cycles.

• Centralized Tool Management: Trigger many tags and technologies simultaneously, rather than creating separaterules for each one.

• Reduced Costs: Minimize the need to use JavaScript-trained IT resources for tag management activities.

Key Features

Dynamic tag management provides the following key features:

• Unmatched rule-driven data collection

• Site-centric rather than tag-centric user interface

• Robust process and workflow management

• Lightweight, meta-based library

• Ability to host anywhere

• Built-in collaborative tools

• Management of multiple sites

Overview Videos

Activation, powered by dynamic tag management, gives you intuitive tools to manage an unlimited number of Adobeand third-party tags. Now, you have more control and flexibility to optimize almost anything online, all while reducingyour dependency on IT resources.

Time: 1:05What Is Adobe DTM - Intro

By the end of these videos youshould be able to:

• Explain what DTM is

• Explain its position in themarket

• Explain the "top down"approach

• Explain the importance of ourlibrary hosting options

• What tags does DTM support?

Time: 3:05What Is Adobe DTM - Background



Time: 3:05What Is Adobe DTM - Background






Time: 1:33What Is Adobe DTM - Scope of Usage







Time: 3:53What Is Adobe DTM - Top Down Approach







Time: 2:43What Is Adobe DTM - Hosting Options




Time: 2:43What Is Adobe DTM - Hosting Options





Time: 1:18What Is Adobe DTM - Tag Support








DTM Demo VideosA series of short videos to demonstrate Adobe Dynamic Tag Management features.

Time: 4:39DTM Demo Part 1 - Overview and Set Up Basics

Time: 4:54DTM Demo Part 2 - Analytics Tool Setup

Time: 3:27DTM Demo Part 3 - Data Elements

Time: 10:38DTM Demo Part 4 - Page Load Rules

Time: 6:59DTM Demo Part 5 - Event and Direct Call Rules

Time: 4:45DTM Demo Part 6 - Version Control & Governance

13DTM Demo Videos

Getting StartedInformation for new users of Dynamic Tag Management.


• Requesting Access to Dynamic Tag Management• Logging In• Getting Started Tasks

Requesting Access to Dynamic Tag Management

Before you start using Dynamic Tag Management, someone from your company must request access. Pleasecontact your Adobe account team and ask for access to Dynamic Tag Management.Your account team will useour internal Provisioning Hub tool to grant access.You should receive your login credentials within one to twobusiness days.

If you have access to the Adobe Marketing Cloud, you can also request access to dynamic tag management fromthe Tools menu.

Note: Administrators, see Getting Started in the Marketing Cloud if you need access to the Marketing Cloud.

Logging In

Browse to https://dtm.adobe.com.

Getting Started Tasks

The steps in the following table help you get up and running with Dynamic Tag Management:

DescriptionLocationGetting Started TasksStep

A web property is a library of rules and one embed code. Aweb property can be any grouping of one or more domains

Web Propertiestab on theDashboard

Create a web property.

and subdomains.You can manage and track these assetssimilarly. For example, suppose that you have multiplewebsites based on one template and you want to track thesame assets on all of these websites.You can apply one webproperty to multiple domains.

For general information about web properties and bestpractices, see Web Properties.

To get started, see Create a web property.

14Getting Started

http://marketing.adobe.com/resources/help/en_US/mcloud/admin_getting_started.html

https://dtm.adobe.com


Dynamic Tag Management provides a number of options tohost the required JavaScript files:

Embed tabConfigure your hostingoptions.

• Akamai

• Self-hosting: FTP Delivery

• Self-hosting: Library Download

See Embed Code and Hosting Options.

Dynamic Tag Management allows you to precisely time theloading of JavaScript and page content in your page.You can

Embed tabAdd header and footercode to each managedpage. choose to run rules at the beginning or end of a page. This

allows you to implement testing tools and other technologies,while retaining full control over tracking your pages.

Adobe provides staging and production embed code so youcan test your changes in your staging environment beforepushing changes to your production environment.

See Header and Footer Code.

Tools let you quickly integrate Adobe Marketing Cloud solutionson your site. Tools go beyond a basic tag, because they

Overview tabDeploy tools forsolutions.

provide additional configuration options. A tool correspondsto Adobe solutions like Analytics and Target, as well as GoogleAnalytics. After you add a tool to a property, it is available forinclusion in a rule.

See Tools.

Data elements are the building blocks for rules. Data elementslet you create a data dictionary (or data map) of commonly

Rules tabCreate data elements.

Andused items on a page, regardless of where they originate

Create rules, conditions,and actions.

(query strings, URLs, or cookie values) for any object that iscontained on your site.You use data elements to build a datalayer that can be used in rules for Analytics and other datacollection tools.

Rules can be triggered at page load or when a specific eventoccurs. Dynamic Tag Management provides a powerfulconditioning interface that provides granular control of whentags fire.

To get started, you should set up a basic page-load rule withno conditions to collect analytics data on all pages.

For more information, see Data Elements and Rules.

15Getting Started


After a rule is created, it is funneled through a multi-stepapproval process before it is published to a productionenvironment.

Publish tools and rulesto the production server.

See Rules.

Planning for Dynamic Tag Management

Dynamic tag management is an evolution of tag management, designed around the mapping of user interactionsto marketing technologies.Your tags and marketing tools are best used when reacting to visitors (or segments ofyour visitors) and their activity on your site in precise ways.

By starting with user interactions as the stimulus for marketing tool response, you can know how those interactionsresult in data collection, testing, or engagement with tools like chat, surveys, and more.

Planning Ahead

To make the most of dynamic tag management, establish a clear vision of how you want to use digital marketing.For help with planning, Adobe offers consulting on best practices. Also, a number of consulting agencies across theglobe have extensive experience deploying dynamic tag management and helping transform your organization'sproductivity, workflows, and sophistication.

Browser Support

DTM has been tested with the most commonly used browsers.

The DTM user interface supports the latest version of Safari, Chrome, and Firefox, as well as version 9 and aboveof Internet Explorer.

The DTM library supports the latest version of Safari, Chrome, and Firefox, as well as version 8 and above of InternetExplorer.

Access DTM through Experience Cloud

These instruction explain how to access DTM companies through the Experience Cloud.

1. Open the solution picker and click Activation.

2. Click Dynamic Tag Management.

Managing Users and the Publish Workflow

Dynamic tag management is based on a roles-oriented platform that lets you control the process.

Roles include the following:

DescriptionRole

Create and test rules.Users

16Getting Started

DescriptionRole

Review and approve rules, making approved states of rules publishable.Approvers

Publish rules to the production site. Only approved rules are published.Publishers

Create and manage users, as well as inheriting rights from the three preceding roles.Administrators

Publishing Workflow

1. A rule is saved.2. The rule is automatically pushed to your staging site where you can perform testing.3. The saved rule is funneled into the approval queue, where the details of the rule can be viewed in summary.4. The Approver, Approver & Publisher, or Administrator level user approves the rule.5. The rule goes into the publishing queue.6. In the publishing queue, the Admin, Publisher, or Approver & Publisher level user must publish the rule before

it goes live.

If you make changes to a published rule, the changes are not published to the site until they have been funneledthrough the approval process.

This process ensures that only approved rules and rule revisions are published to your live site. This approvalprocess also retains all past and present revision information. This retention makes it easy to follow a rule’shistory and pin-points when an issue may have occurred.

For details, see Users and Permissions.

Manage Account Settings

Manage your user account settings, including settings for names, title, mobile number, time zone, language for theuser interface, opt-out notifications, and password changes.

1.In the upper right corner of the dynamic tag management interface, click > Account Settings.

2. Edit the fields as necessary:

First Name: Specify your first name.

Last Name: Specify your last name.

Title: Specify your title.

Mobile Number: Specify your mobile telephone number.

Outside of US: Select this option if you are outside of the United States. Ensure that you provide a country codein the Mobile Number field if you choose this option.

Time Zone: Specify your time zone.

Language: Choose the desired language from the drop-down list. The user interface displays in the selectedlanguage.

Email Address: Specify your email address.You can add multiple email addresses separated by commas.

Opt Out of All Notifications: Opt out of all email notifications when one of your web properties is published. Byopting out of email notifications, you will no longer receive publish request, property published, note, or approvalemail notifications. However, you will continue to receive other email notifications.

17Getting Started

Current Password: If you want to change your dynamic tag management password, specify your currentpassword in this field.

Password: Specify your new password.

To maintain the utmost security possible for your account, all passwords must meet the following criteria:

• Must be at least seven characters in length• Must contain at least one number and at least one letter• Must contain at least one special character that is not a letter or number• Must not be one of your last five passwords

Password Confirmation: Specify your new password for confirmation.

3. Click Save Changes.

Architecture

Information about dynamic tag management architecture.

Architecturally, dynamic tag management comprises two main components:

• Management Application: Offers an easy-to-use, tab-structured configuration user interface.

• JavaScript libraries: Produced by the Management Application and transported to hosting servers. Dynamic tagmanagement includes two types of JavaScript libraries:

• Staging Library: Every change you make in the Management Application is immediately updated to use on thestaging server.

• Production Library: Only the final, approved version of a tool or rules makes it onto the production server.

This model fits well into the approval workflow, in that development or staging code is never accidentally includedin the production library. See Publish Workflow.

Time: 2:38DTM Basics: Architecture

By then end of this video youshould be able to:

• Describe the basic elementsof DTM's architecture

Best Practices for Getting Started with Adobe Dynamic Tag Management

If you are new to Adobe Dynamic Tag Management (DTM), getting ready to migrate to DTM, or brushing up onDTM, this guide is for you.

Last Updated: January 30, 2017

Dynamic Tag Management lets marketers quickly and easily manage tags and provides innovative tools for collectingand distributing data across digital marketing systems. DTM also enables responsive delivery of user-specificcontent-providing new levels of agility and control to companies seeking to thrive in today's fast-paced digitalmarketplace.

18Getting Started

In addition to this Best Practices Guide, the following resources are available to help you get the most out of DynamicTag Management:

DetailsResource

In-depth information and step-by-step instructions about how to use Dynamic TagManagement.

Dynamic Tag ManagementProduct Documentation

Information about how to start using Dynamic Tag Management.Getting Started Guide

This guide includes the following sections:

Basics for the First-Time User

An introduction to the Dynamic Tag Management (DTM) user interface.

This content was built in partnership with


• Dashboard

• Company Overview

• Property Overview

• Rules

• Data Elements

• Workflows

• Installation

Dashboard

Navigation: Home > Dashboard

The first page seen in DTM after logging in is the dashboard. The dashboard contains a list of all of the companiesto which you have access.

19Getting Started

https://marketing.adobe.com/resources/help/en_US/dtm/


http://www.searchdiscovery.com

Company Overview

Navigation: Home > Dashboard > Company Overview

Clicking into a company from the dashboard takes you to the company overview page.

Note: If you have access to only one company, you are directed to the company overview page instead ofthe dashboard upon login.

In DTM, a company is a collection of web properties. A web property is a collection of tools, rules, and data elements.

All web properties in the company are accessed from the company overview page.

Admin-level users can add new web properties from the company overview page by clicking Add Property. The onlyrequired fields when configuring a web property are Name and URL, which can be changed at a later time if needed.

20Getting Started

Admin-level users can also manage and provision users from the company overview page via the Users and Groupstabs.

Property Overview

Navigation: Company Overview > Property Overview

Clicking into any property from the company overview page takes you to the property overview page.

The property overview page gives a brief summary of the property configuration and serves as a gateway to themain property components: tools, rules, data elements, the publish workflow, and the property embed codes.

Navigation: Property Overview > Installed Tools

DTM tools are built-in integrations that allow for quick deployment of solutions to your site.

Currently, DTM offers tool integrations for Adobe solutions as well as for Google Analytics and Nielsen. Each ofthese integrations is uniquely designed to make configuration and deployment of that particular solution easier.

21Getting Started

Note: Any third-party tool or tag without a native integration can be implemented in a rule through the

JavaScript / 3rd Party Tag section discussed below.

Rules

Navigation: Property Overview > Rules

Clicking the Rules tab from the property overview page takes you to the property rules.

22Getting Started

Rules in DTM are used to conditionally execute tools, tags, scripts, and HTML.

Regardless of the type, rules in DTM have two main components: the condition and the trigger. The conditionindicates the scenario in which the rule will fire and the trigger indicates the item(s) that will execute when the rulefires.

There are three types of rules in DTM:

• Event-Based: Event-based rules are interaction driven. For example, if I wanted to track when a user clicks acertain button, I would use an event-based rule.

• Page-Load: Page-load rules are tied to the page load. For example, if I wanted to add a specific block of code onload of certain pages on my site, I would use a page-load rule.

23Getting Started

• Direct-Call: Direct-call rules are used in scenarios when DTM cannot detect an event in the DOM. For example,if I want to track an AJAX event that can't be detected in the DOM, I would use a direct call rule.

Regardless of the rule type, if the condition is met the trigger executes.

All rules types have the option to trigger third-party vendor tags or any other custom JavaScript or HTML via theJavascript / Third Party Tags modal.

Other trigger modals are enabled in rules when tools are added to the property. For example, if my property containsan Adobe Analytics tool and a Google Universal Analytics tool, the property rules will contain optional trigger modalsfor these tools.

Each tool modal offers easy methods to customize a trigger for that particular tool.

24Getting Started

Data Elements

Navigation: Property Overview > Rules > Data Elements

Clicking the Data Elements tab within the Rules tab displays the data element overview page.

Data elements are used to build a data mapping in DTM. Defining common data points as data elements enablesthose data points to be easily captured and leveraged within rules and tools in DTM.

25Getting Started

Workflows

An important concept in DTM is the idea of a single web property having both a staging library and a productionlibrary.

The staging library contains all of the rules, tools, and data elements configured in the web property.The productionlibrary includes only the rules, tools, and data elements that are approved and published.

Navigation: Property Overview > Approvals tab

When a rule, tool, or data element is added or changed in a property an approval is automatically generated.

26Getting Started

Navigation: Property Overview > History tab

After an item is approved, it becomes available in the Unpublished Changes queue 0n the History tab. After an itemis published, it becomes available in the production library.

This separation of libraries and associated workflow allows for more effective testing in staging without affectingproduction.

27Getting Started

Installation

Navigation: Property Overview > Embed tab

Clicking the Embed tab takes you to the DTM installation page.

This tab contains the various library hosting options available. By default the property leverages Akamai hosting.This method is typically acceptable for most organizations; however, if additional control over the serving of the DTMlibrary in needed two self-hosting options are available.

Expanding the Header Code section on the Embed tab reveals the staging and production embed codes for theproperty.

28Getting Started

Notice there's one embed code for staging and one for production. This is how DTM differentiates between thestaging and production libraries discussed above. When the staging embed code is installed, the staging libraryloads. When the production embed code is installed, the production library loads.

After the header and footer embed codes are properly installed on a site, the associated DTM library loadsautomatically on each page load.

Leverage the DTM Switch Plugin to test in the web console. This helps you understand what DTM is doing on thepage and allows you to locally switch to the staging library for more effective testing. For more information, seeSearch Discovery Plugins in the Dynamic Tag Management Product Documentation.

DTM Technical Architecture and Hosting

Information about the technical architecture of Dynamic Tag Managment (DTM) and its hosting options.



• Architecture

• Hosting

Architecture

The primary components of the DTM technical architecture include the web management application, the stagingand production JavaScript libraries, and the embed code.

The web management application is the online interface that you log in to and use to manage your DTMimplementation.This is where you'll create and configure tools, rules, and data elements and manage the deploymentof these configurations to your site(s).

29Getting Started


A web property in DTM is a collection of tool, rule, and data element configurations.

Each web property is associated with one staging JavaScript library and one production JavaScript library. Theselibraries are generated by the web application and contain the unique set of configurations in that web property.

30Getting Started

The staging JavaScript library contains all of the latest tool, rule, and data element configurations in the web property.This library is automatically updated with any change in the property and is intended for testing in staging environmentsor for local production testing via the DTM switch plugin.

31Getting Started

For more information about the DTM switch plugin, see Search Discovery Plugins in the Dynamic Tag ManagementProduct Documentation.

The production JavaScript library contains only tool, rule, and data element configurations that have been approvedand published through the web property workflow. This library is intended for the production environment.

Hosting

Both the staging and production JavaScript libraries can be hosted in the following ways.

• External hosting via Akamai-library hosted on Akamai's servers

• Self-hosting via SFTP or library download-library hosted on your servers

Choosing a hosting option(s) is a decision your business needs to make. Review the following option comparisonand use-case examples to help facilitate this decision.

DisadvantagesAdvantages

Akamai • Lack of control over file delivery• Standard deployment method

32Getting Started

https://marketing.adobe.com/resources/help/en_US/dtm/index.html?f=search_discovery_plugins

DisadvantagesAdvantages

External hosting • No configuration needed • Dependence on third-party infrastructure (i.e.if Akamai is unavailable, so is your library)• Minimal dependence on IT

• Automatic file updating

• Reliable & speedy file delivery via globallydistributed Akamai network

SFTP • Upfront configuration required• Complete control over file delivery

•• Greater dependence on ITMore secure option: SSH file transferSelf hosting• Automatic file updating

Library Download • Upfront configuration required• Complete control over file delivery

•• Greater dependence on ITMost secure hosting option: AES 256bundle encryption

Self hosting• Additional configuration required for automatic

file updating

Use Case Examples

SolutionScenario

Leverage Akamai hosting in all environments.I prefer to involve IT as little as possible and have a needfor a reliable file hosting method outside of my own siteinfrastructure.

Leverage Akamai hosting in staging environments andFTP delivery in production environment.

I want to have complete control over file delivery in myproduction environment; however, speed and agility ismore important than file control in my stagingenvironment.

Leverage library download hosting on secure pages andAkamai hosting on non-secure pages.

Certain sections of my site deal with highly confidentialinformation. Security is the most important thing on thesepages but isn't necessarily as important on other pagesof my site.

All hosting options are available to enable and configure on the Embed tab in your DTM property.

33Getting Started

Regardless of the hosting option chosen, the JavaScript library is served on your site via the installed embed code.Each hosting option provides a unique set of embed codes that reference the applicable file location configured forthat hosting option.

The embed code consists of two code snippets: the header and the footer code.

• Header Code

The header code is responsible for calling the associated JavaScript library from the host location and serving iton your site. This code snippet should be placed in the head section of the site code as close to the opening tagas possible.

• Footer Code

34Getting Started

The footer code is responsible for identifying the end of the page for timing control. This code snippet should beplaced in the body section of the site code as close to the closing tag as possible.

The appropriate placement of both the header and footer embed code snippets is critical to the effective deploymentof the DTM JavaScript library.

Note: Although you can use more than one hosting option, you must ensure that only a single embed codereference is included on any given page. Duplicative or improper placement of the embed code can result inunexpected library behavior.

The following illustration show how the discussed DTM architecture components work together to effectively deployand manage tools, tags, and scripts on your site.

35Getting Started

For more information on hosting options, see Embed Code and Hosting Options in the Dynamic Tag ManagementProduct Documentation.

Planning Your Migration to DTM

Information to consider as you plan your migration to Dynamic Tag Management (DTM) and best practices to helpget your implementation started correctly.



• Planning Your DTM Setup: Component Overview

• Planning Your DTM Setup: Decision Points

• Migration Best Practices

Planning Your DTM Setup: Component Overview

This section contains a quick overview of the basic DTM company structure to prepare for the decisions involved inplanning your DTM setup.

In DTM a company is a grouping of web properties.

A web property is a grouping of tools, rules, and data elements configured to collect data and deploy tags / scriptson your site(s).

36Getting Started


Each web property is associated with one embed code that's responsible for loading the specific property configurationson your site(s).

Users are managed at the company level but can be permissioned for each property with the exception of the Adminrole. The Admin role is global and has full permissions for all properties in a company.

37Getting Started

For more information on user roles, see Create and Manage Groups in the Dynamic Tag Management ProductDocumentation.

Planning Your DTM Setup: Decision Points

With the basic DTM company structure in mind, let's discuss the related decision points as you plan your DTM setup.

How many companies do I need?

In most cases one company will best meet business needs.

The primary reason for having more than one company is to accomplish complete separation of users and webproperties.

This type of configuration is most typical for large businesses with numerous sets of web entities that are run byvarious business divisions.

How should I distribute my domains and subdomains into web properties?

Web properties can be configured as one-to-one or one-to-many with your domains.

To decide what will work best for your business, consider the cross-domain similarities and differences of the followingvariables.

• Data collection methods and sources

• Tools and tags deployed

• Site code structure

• DTM user workflows

In most cases one web property per one domain will best meet business needs due to considerable differences inone or many of the above variables.

This type of setup most effectively accommodates each domain's needs while still allowing for easy duplication ofcross-domain constants via the 'copy' functionality.

38Getting Started

https://marketing.adobe.com/resources/help/en_US/dtm/index.html?f=groups

However, in cases where these variables are the same or very similar across domains, it may make more sense tohave multiple domains within one web property. In these cases, this setup can reduce unnecessary duplicationbetween properties.

This same reasoning can be used for subdomain distribution.

Use-Case Examples

SolutionScenario

Leverage one property for each domain.My business division manages several domains. We'redeploying Adobe Analytics across all domains, but eachdomain has its own reporting suite and tracking needs.

Leverage one property for each domain.My business division manages several domains. We'redeploying Adobe Analytics across all domains and useone global reporting suite to collect all of our data. Datasources between domains are very different due tovariations in site code structure.

Leverage one property for all domains.My business division manages several domains. We'redeploying Adobe Analytics across all domains and usea global reporting suite and global data layer to collectall of our data. The rest of our tools and tags are mostlyconsistent between domains and we're planning to havethe same users manage the publish workflow.

Migration Best Practices

After determining the optimal company and property distribution, consider the following best practices as you beginyour DTM migration.

Process Workflow: Develop a systematic process for migrating existing page code into DTM to help ensure asmooth transition.

It's generally recommended to start this process in lower-level staging environments and migrate code on apage-by-page or site section by site section basis.

39Getting Started

This will allow you to fully vet DTM configurations before removing any pre-existing page code reducing the risk ofimplementation disruption.

Working with IT: It's important to work with your IT team upfront to determine current processes and deploymentcycles.

This will help ensure proper and timely placement of the embed code and coordinated removal of effectively migratedpage code.

People Workflow & Governance: Another important concept is establishing a user workflow.Thoughtfully assigninguser roles provides governance to the DTM workflow.

CreateProperty

Create/EditUsers

PublishRules

ApproveRules

TestRules

EditRules

CreateRules

User Role

YesYesYesUser

YesYesYesYesApprover

YesYesYesYesPublisher

YesYesYesYesYesApprover andPublisher

YesYesYesYesYesYesYesAdmin

This will ensure that all items are fully vetted by the right members of your team before being pushed to production.

For more information, see Migrating to Dynamic Tag Management in the Dynamic Tag Management ProductDocumentation.

Migrating to DTM: A Closer Look at Adobe Analytics

Whether your current Adobe Analytics implementation is deployed via on-page methods or via another tagmanagement system, this section helps you understand your options as you migrate to DTM.


Phase 1: Quick Value Add

Because migrating Adobe Analytics code can be a lengthy process, DTM offers a feature that allows you to augmentyour existing Analytics implementation without disrupting it.


This feature is called Page Code is Already Present and is located in the Analytics tools settings in your DTM property.

40Getting Started

https://marketing.adobe.com/resources/help/en_US/dtm/index.html?f=migration



To access this feature, expand the Library Management section of the tool settings.

With this feature enabled, DTM is able to leverage the existing implementation to send supplemental s.t() /s.tl() calls via event-based and direct-call rules.

This functionality makes it easy to start using DTM to augment your Adobe Analytics implementation before migratingany code.

However, it's important to note the following limitations with this approach.

• Variables and settings configured in the DTM Adobe Analytics tool will not take effect.

• Adobe Analytics variables set in page-load rules will not take effect.

These limitations occur because DTM is fully relying on the existing implementation to serve the AppMeasurementcode and instantiate the s object.

41Getting Started

Phase 2: Full Migration

To take full advantage of the integrated Adobe Analytics functionality in DTM, a complete migration of Analyticscode is recommended.


This migration should include all s object references in the page code and included scripts on pages where DTM isdeploying Adobe Analytics.

The following sections contain more information:

• Migrating Global Code

• Migrating Page-Level Code

Migrating Global Code

The first step in migrating is to configure your global code in the Adobe Analytics tool settings in your DTM property.

The AppMeasurement code / s_code is configured in the Library Management section of the tool settings underCode Configuration.

42Getting Started


If Page Code is Already Present from phase 1 is currently leveraged, you'll need to uncheck this option to revealthe Code Configuration options. This change will take effect only in staging so you can fully configure and vet themigrated code before pushing this change to production.

The Custom configuration option is typically preferred as an initial migration approach because it allows you toreference your existing AppMeasurement / s_code as-is without the need for additional tool configuration.

• Custom - Hosted in DTM: Paste existing code into editor.

• Custom - Hosted at URL: Reference existing code at URL location.

43Getting Started

With the Managed by Adobe option, DTM automatically provides and hosts the selected AppMeasurement basecode version. This method allows for easy code version updating making it a great long-term option.

Regardless of the Code Configuration option, items not included in the AppMeasurement code can be set in the toolsettings via the provided interface fields or in the Customize Page Code editor.

The provided interface fields are a great long-term option for configuring global settings and variables as leveragingthese fields in place of custom code ultimately reduces the overall complexity of your implementation.

44Getting Started

Note: Dynamically populate variables by leveraging data elements directly in any field using the %dataElement%syntax.

The Customize Page Code editor is a convenient alternative for items that require code, such as plug-ins andconditional settings. Any code placed here will work in tandem with the hosted AppMeasurement code / s_code.

45Getting Started

Migrating Page-Level Code

The next step in migrating is to configure non-global code in DTM rules.

Here's an overview of each rule-type and their typical usage for setting Adobe Analytics triggers.

DetailsRule Type

Use to append variables to the default page view beacon on all or certain pages.Page-load rules

Use Case Example: Sending a particular eVar on load of my promotional page.

Use to trigger a s.t() or s.tl() beacon on specific user interactions.Event-based rule

Use Case Example: Sending a custom page view beacon with a particular event when apopover is enabled.

Use to trigger a s.t() or s.tl() beacon in scenarios when DOM event can't be detected.Direct-call rule

Use Case Example: Sending a s.tl() beacon with a particular event when a video isviewed.

Remember to follow Migration Best Practices.

As discussed in the previous section, it's important to remember the following best practices as you work to migrateyour Adobe Analytics code.

• Develop a systematic process

• Start in lower-level staging environments to fully vet migration

• Work with IT early to coordinate code removal

Note: A possible approach for progressive migration is to determine a flag for identifying pages that have notyet been fully migrated.This flag can then be leveraged in the Customize Page Code editor in the tool settingsto conditionally cancel the default DTM beacon on those pages by setting 's.abort = true'.

46Getting Started

Please note that this approach only affects the Analytics tool beacon; rules configured to fire Adobe Analytics shouldbe conditioned in the rule itself.

Please vet this approach fully in staging environments before leveraging in production.

Benefits of a Tag Management System: A Focus on DTM

Information about the basics of tag management and walks through how Dynamic Tag Management can specificallybenefit your business.



• What is a Tag Management System?

• Why Dynamic Tag Management (DTM)?

What is a Tag Management System?

Tag management systems are designed to make implementing and managing marketing and analytics tags on yoursite easier through the use of a container tag.

47Getting Started


A container tag is a single code snippet that when placed in your site markup is capable of triggering countless tagson your site.

This approach reduces strain on the IT group and places the control in the marketers' hands.

Why Dynamic Tag Management (DTM)

Dynamic Tag Management takes the tag management approach described above and enhances it through astraightforward, yet, highly capable design with integrated scenario and timing control.

Consider the following as you decide if Dynamic Tag Management is right for your business:

DetailsBenefit

With Dynamic Tag Management, marketing and analytics tags are moved from themarkup of your site into the DTM library. This in itself reduces page load time as theDTM library is optimized for file compression and speed

Improved site performance

.

However, performance is enhanced even farther through the use of the conditionalcontrols and asynchronous methods DTM offers.

Conditional controls make it easy to ensure that tags are triggered only when needed,eliminating unnecessary code deployment.

Asynchronous loading forces tags to stay out of the way of the page, greatly reducingthe burden on page render.

With less reliance on IT, you'll be able to deploy and manage tags on your watch.Increased control,decreased risk

This means less commitment and risk in deploying vendor tags and increased agilityto keep up with new tool / tag features.

Plus, DTM has built-in features to ensure compliance with data-privacy policies and toprevent vendor tags from interfering with your site or leaking data to third parties.

Dynamic Tag Management takes a behavior-centric approach and leveragescomprehensive integrations and data-centralization to make tag deployment easy.

Work faster and moreefficiently

The behavior-centric approach allows for countless tools / tags to be deployed at thesame time based on a certain behavior rather than deploying each tag individually.

DTM's built-in integrations facilitate easy configuration of tools such as Adobe Analyticsand Google Analytics, eliminating the need for extensive custom code.

Data elements centralize common data points, reducing code redundancy and optimizingdata lookup time.

Together these features save time and frustration so you can focus less on tagdeployment and more on moving your business forward.

Best of all, if you're an Adobe Marketing Cloud customer, Dynamic Tag Managementis free.

Use Dynamic TagManagement for free

48Getting Started

DetailsBenefit

Contact your Adobe Account Manager for details.

49Getting Started

Web PropertiesA web property is a library of rules and one embed code. A web property can be any grouping of one or more domainsand subdomains.You can manage and track these assets similarly. For example, suppose that you have multiplewebsites based on one template, and you want to track the same assets on all of them.You can apply one webproperty to multiple domains.

Time: 6:06DTM Basics: Web Properties


• Explain what a web propertyis

• Set up a web property

• Understand the web property'srelationship with the embedcode and report suites


• Best Practices for Planning Web Properties• How Web Properties Compare to Analytics Report Suites• Separating the DTM Environment for Multiple Entities• Deactivating a Web Property

Best Practices for Planning Web Properties

Considering the following when planning web properties:

Best PracticeConsideration

For all of your websites, is the data you are going to collect very similar, somewhatsimilar, or unique?

Data

If the data you need to collect is similar across websites, it might make sense togroup those sites into one web property to avoid duplicating rules or copying rulesfrom one property to another.

If your data collection needs are unique for each site, it might make sense toseparate those sites in their own web properties. This method lets you control thedata collection more specifically for each site, without using large amounts ofconditional logic in custom scripts.

For example, if 80 percent of the data you are collecting across your sites is thesame, or similar, it makes sense to group those sites together into the same webproperty. If the data is unique for each site, it makes sense to put each site into itsown web property.

Similar to data, for all of your websites, are the variables you are going to set inyour Analytics and other tools very similar, somewhat similar, or unique?

Variables

50Web Properties

Best PracticeConsideration

For example, if eVar27 is used for the same source value across all of your websites,it might make sense to group those sites together so you can set those commonvariables across your sites in just one web property.

If your variable usage is unique for each site, it might make more sense to separatethose sites into their own web properties so you can control the variables morespecifically for each site without using large amounts of conditional logic in customscripts.

Are the tools, tags and systems you are going to deploy through dynamic tagmanagement very similar, somewhat similar, or unique?

Tools, Tags, and Systems

If the tools, tags, and systems you are going to deploy through dynamic tagmanagement are very similar across your sites, you might want to include thosesites in the same web property.

If you are deploying Adobe Analytics on only one site, and your other tools andtags are also unique to certain sites, you might want to create separate webproperties for those sites so you can control those specific tools in one web property.

For example, If you are deploying Adobe Analytics, Target, and the same 3rd-partytags and tools across your sites, that is a reason to group sites together.

For the individuals, teams, and organizations that are working in dynamic tagmanagement, will they need access to all of your websites, some of them, or justone of your domains or sub-domains?

People

The User Management features allow you to assign different roles to different peoplefor all of your web properties, or on a per-property basis.The only role that includesall web properties within a dynamic tag management company account is the Adminrole. If someone is an Admin, that person can perform administrative actions acrossall the web properties in that dynamic tag management company. All the other rolescan be assigned on a per-property basis.You can even hide a web property fromcertain users (non-admins) by not giving them any role in that web property.

Each implementation can be very different in dynamic tag management, with a wide variety of data-collection needs,variable usage, tools, third-party tags, other systems and technologies, people, teams, geographic regions, and soon. Using the flexible User Management features and web properties, you can create a configuration that matchesyour workflow and processes.

If the scenarios you are tracking, the data you are collecting, the tools you are deploying, and the variables you aresetting are similar across all or some of your domains and subdomains, it is easier to have those domains andsubdomains grouped into the same web property in dynamic tag management. If those are unique for each domainand subdomain, it is easier to have those domains and subdomains in their own web property. If you choose togroup domains and subdomains in a single property now, you can always change your mind and later create severalweb properties.

51Web Properties

How Web Properties Compare to Analytics Report Suites

In Adobe Analytics, you can dynamically determine the report suite to which you want to send the data, if you arenot tracking all the websites in one suite of reports.

A web property can contain any number of domains or subdomains. It can also send analytics data to one or severalreport suites in Analytics.You can set multi-suite tagging, or you can use conditional logic that sets s.accountaccording to your particular needs.

If you want to send data to two report suites for every page view and event, you would add a comma-separated listof report suite IDs in the user interface in dynamic tag management, in the Account Numbers fields, on the AdobeAnalytics Global Settings page.

If you want to send data to a particular report suite based on conditional logic, you would add your logic in the Editor,in the General section of the Adobe Analytics Global Settings page.

Separating the DTM Environment for Multiple Entities

There are a few ways to handle multiple geo markets, business units, domains, and subdomains in dynamic tagmanagement.

First, you can have one or several dynamic tag management Company accounts. Companies contain web properties.You can have one or several or any number of web properties within a Company account. Within a web property,you can have one or any number of domains or subdomains.

Some customers have one Company that contains all of their web properties. Some have a Company that containsmany web properties, one for each domain. Some have a Company that contains several web properties, one foreach type of site they manage.

For example, you might have three web properties within your Company account where one contains all of yourblog sites, another contains all of your ecommerce sites, and the third contains all of your lead-generation sites.

Note: Each web property requires its own Embed Codes in your page templates. Any domains or subdomainsyou want included in a particular web property would have the same Embed Codes in the page templateswhen dynamic tag management is first installed on your site.

Can we use separate instances for each?

As described above, you can use separate Company accounts for your three entities, or you can combine the entitiesinto one Company account and split the domains / subdomains into different web properties within that Companyaccount.

Is there a clear way to separate domains and settings within the same dynamic tag management instance?

Within a Company account, you can use multiple web properties to separate domains and settings, or you can putmultiple domains into the same web property.

What are the pros and cons for using one dynamic tag management instance?

With one web property that contains multiple domains and subdomains, you will eventually add conditional logic toseparate unique data collection and tracking needs that only apply to individual domains, subdomains, or subsetsof domains / subdomains.

What is the approach recommended by Adobe: one or separate companies?

52Web Properties

Most clients use one Company account that contains all of their web properties. Information on this page can helpyou determine the best plan for your particular needs within those properties.

Deactivating a Web Property

Deactivating a web property does not deactivate everything within the property, it just prevents the associated libraryfiles from getting rebuilt (i.e. the staging and production libraries remain in the state they were in when the propertywas deactivated).

If you deactivate a property and expect a tool or rule to stop firing, you should deactivate those item(s) in the propertyand then publish that change, if applicable, before deactivating the property.

If the property is already deactivated, you might need to reactivate the property, inactivate the desired items, publish(if applicable), and then deactivate the property again.

Create a web property

Create a web property in dynamic tag management.

Note: Only a user with Admin rights can create a property. For more information about roles, see Create andManage Groups in DTM.

Before beginning, review the Best Practices for Planning Web Properties for web properties.

1. Navigate to your company page, then click Add Property.

2. Fill in the fields:

53Web Properties

DescriptionElement

The name of your property.Name

The base URL of the property.URL

You can add and remove domains if you want visitor data to persist between domains.This site spans multipledomains

This setting lets you specify how you would like to track traffic moving between yourassociated subdomains or domains.

Note: If you do not intend to integrate an analytics tool, this step isunnecessary and does not affect processing.

3. (Optional) Configure Advanced Settings.

DescriptionElement

Allows multiple rules for this property to be approved at one time. (The defaultapproval allows only single-rule approval.)

Allow Multi-RuleApprovals

Specifies whether to allow users to selectively publish approved rules. (This is thedefault option.)

Enable Selective Publish

Overrides the default tracking cookie name.You can customize the name thatdynamic tag management uses to track your opt-out status for receiving othercookies.

Tracking Cookie Name

Specifies how long dynamic tag management waits for a tag to fire before timingout.

Tag Timeout

Because of how dynamic tag management works, don't worry about this being ahigh number, as we have other, better methods of ensuring that slow tags do notaffect the user experience.

Specifies how long dynamic tag management waits for tags to fire on clicked linksbefore moving to the next page. The default value is 100 milliseconds.

Anchor Delay

Longer delays improve tracking accuracy. Adobe recommends a delay of 500milliseconds or less, which the user will not perceive.

Dynamic Tag Management will wait up to the time specified, but if the beacon firessooner, the delay is cut short. (That is, user won't always wait the full length of thedelay.)

4. Click Create Property.

54Web Properties

Delete a web property

Delete a web property from dynamic tag management.

Note: Property removal cannot be reversed. The requestor must be an admin-level user. This request cannotbe undone.

1. Navigate to the Overview page for the desired property.

2. Click Edit Property > Remove Property, then confirm the removal of the property.

55Web Properties

Users and PermissionsYou can invite users to dynamic tag management and assign user roles and add users to groups.

You must have administrative privileges to invite a new user in dynamic tag management. Administrators areautomatically granted permissions to a new property.

Note: If you link your DTM company to the Marketing Cloud, you must manage your users in the MarketingCloud.


Manage Users

You can invite users to the Adobe Marketing Cloud with the Adobe Admin Console (the preferred method) or youcan use the legacy provisioning process in Dynamic Tag Management.

Note: If you link your DTM company to the Marketing Cloud, you must manage your users in the MarketingCloud.

Important:

DTM accounts created after April 5, 2016 are managed by administrators using the Adobe Admin Console in theAdobe Marketing Cloud. To manage other users, the DTM administrator must be a Marketing Cloud administratorin the Adobe Admin Console. For more information, see Delegate Administrative Roles to Users in the MarketingCloud and Core Services Product Documentation.

For accounts created before April 5, 2016, users are managed using the Users page in DTM. For more information,see Manage Users for DTM using the Legacy Process.

There are a few scenarios to keep in mind when deciding whether to provision new users with the Marketing Cloudusing the Adobe Admin Console or by using the legacy provisioning process in DTM.

• Use the Adobe Admin Console: If the user has already authenticated to DTM for a company that does notmanage users with the Adobe Admin Console (the company was provisioned before April 5, 2016), that user canbe added to a new company that does manage users with the Adobe Admin Console.

• Use the Legacy Provisioning Process: If the user has already authenticated to the Adobe Marketing Cloudand the account was created by using the Adobe Admin Console (the company was provisioned after April 5,2016), that user cannot be added to an existing company that uses the legacy login. If this is the case, you mustcreate a new email address to use for authentication.

Recommended best practice is to provision new users using the Adobe Admin Console. However, if there is anychance that these new users (consultants or agency representatives, for example) will need to access an accountprovisioned using the legacy process, you should provision that user in DTM and then link the account to theMarketing Cloud.

The provisioning process in the Adobe Admin Console is forward-looking and not backwards compatible.

56Users and Permissions

https://marketing.adobe.com/resources/help/en_US/mcloud/index.html?f=t_admin-roles

Time: 5:05DTM Basics: User Group Management


• Understand user management

• Understand roles

• Understand default usergroups

• Understand how to add usersto a group

• Understand how to create agroup

Manage Users for DTM in the Adobe Marketing Cloud

Information to help you create user groups in the Adobe Marketing Cloud, invite new users to the Marketing Cloud,and to manage web property access in Dynamic Tag Management (DTM).

Important: Before deciding to add users using either the Adobe Admin Console or directly in DTM, read thenote in Manage Users.

1. From within the Adobe Admin Console, click Users.

2.Click to add a new user.

3. (Conditional) To add the user to multiple groups click the drop-down list, then select the product.


After the user is invited, they receive an invite email to the Marketing Cloud.

Time: 2:55DTM Basics: User Administration

By the end of this video youshould be able to:

• Create a user

• Set permissions

Manage Users for DTM using the Legacy Process

Information to help you invite new users to Dynamic Tag Management.

Important: Before deciding to add users using either the Adobe Admin Console or directly in DTM, read thenote in Manage Users.

Invite New Users to DTM using the Legacy Provisioning Process

1. From your company dashboard, click Users.


2. (Conditional) Click Restrict to Marketing Cloud to force all users in the company to log in to dynamic tagmanagement using Adobe Marketing Cloud credentials rather than using the legacy/company login process.

Important: If you are a DTM company admin, you must authenticate via the Marketing Cloud and haveyour DTM account linked before activating this option, otherwise you will essentially lock yourself out ofDTM.

If this option is selected, all users for the company must authenticate via the Marketing Cloud and link their DTMaccounts. If users log in to DTM using legacy/company credentials, they will be able to view their companyaccount, but they won't be able to access it. A message will display informing them that they must log in via theMarketing Cloud.

The company admin can reverse this option at any time by deselecting this option.

Note: This option is for current customers only. New customers provisioned to DTM will have usermanagement and authentication automatically restricted to the Marketing Cloud and Adobe Admin Console.

For more information about logging in to the Marketing Cloud, see Sign in to the Adobe Marketing Cloud. Formore information about the Marketing Cloud, see the Marketing Cloud and Core Services Product Documentation.

3. Click Invite User.

4. Enter the user's email address.

5. (Conditional) Select the group for the user.

Group management makes it easy to organize users and control their access levels. Permissions are set at theuser group level, so all users in the group inherit the group permissions, including access to specific properties.

6. Click Invite User.

An email message with a link is sent to the user. This email lets the user select a password and complete thesetup process.

Until the user completes this setup process, they appear in the Invited Users section on the Users tab. Theymove to Registered Users when the setup is complete.

Manage Groups

Information to help you create and manage user groups in the Adobe Adobe Admin Console and in Dynamic TagManagement.



• Understand user management

• Understand roles

• Understand default usergroups


https://marketing.adobe.com/resources/help/en_US/mcloud/index.html?f=t_sign_in

https://marketing.adobe.com/resources/help/en_US/mcloud/


• Understand how to add usersto a group

• Understand how to create agroup

Create and Manage Groups for DTM in the Adobe Admin Console

Information to help you create new user groups in the Marketing Cloud and to manage Dynamic Tag Managementproperty access.


• Create New User Groups in the Marketing Cloud

• Manage Web Property Access in DTM

Create New User Groups in the Marketing Cloud

1. Log in to the Adobe Admin Console via aedash.adobe.com.

2. Click Products > Dynamic Tag Management.

3.Click to add a new group (product configuration).

4. To select DTM user group types, click the drop-down list under Select Group, select the user group types, thensave the product configuration.


http://aedash.adobe.com/

In order for the group to display in the list, it must be added in the Adobe Admin Console, as explained in ManageWeb Property Access in DTM.

If a user has already been added as a user to the Marketing Cloud, that user can be added to the group byclicking into the Users tab. Adding a user creates or updates the user in DTM and assigns the user to theappropriate DTM group.

Important: Adding an Admin allows the user to manage the group in the Marketing Cloud. It does not addthe user as an admin in DTM.

For more information on user roles, see Create and Manage Groups in DTM.

Manage Web Property Access in DTM

1. Log in to DTM by clicking the Product Selection icon > Activation.

2. Click Groups.

3. Click Create New Group.

4. Select which tools users in this group are not allowed to modify. In this example, users in this group can't modifythe Nielsen tool for the Geometrixx Demo Test web property.


5. Select the Default Role for the user group.


This role can be defined by property if multiple properties are present in the company, as shown in the followingillustration:

6. Save the group.

7. Add the user group in the Adobe Admin Console.

a. Log in to the Adobe Admin Console by clicking Product Selection > Administration.

b. Click Products > Dynamic Tag Management.

c. Click Add New Group.

d. The new group displays in the Select Group drop-down list. Save the group.

e. Add users to the new group by clicking Users > Add New User.

Create and Manage Groups in DTM

Create user groups, assign group members, and specify default roles.

Group management makes it easy to organize users and control their access levels. The Groups page lists all ofthe user groups that are set up within the account. Permissions are set at the user group level, so all users in thegroup inherit the group permissions.

To access the Groups page, from your company dashboard, click Groups.


• Default Roles

• Migrated Groups for Existing Customers

Default Roles

Dynamic tag management has five different user roles with varying sets of permissions:


The following table illustrates the permissions that each default role inherits:

CreateProperty

Create/EditUsers

PublishRules

ApproveRules

TestRules

EditRules

CreateRules

User Role

YesYesYesUser



YesYesYesYesYesApprover and Publisher


Migrated Groups for Existing Customers

In addition to these default roles, if you are an existing dynamic tag management customer, you might see one ormore migrated legacy groups with appended date and time stamps.

For example, Group - 2015-07-21 21:19:57:884.

If you are an existing customer and certain users have the User role for every property, these users are automaticallymigrated to the new User group. However, if other users have the User role for some properties and the Publisherrole for other properties, they will be put into a migrated group with a date and time stamp. A legacy group will becreated for each scenario in your system. In our testing, we have seen some companies with as many as ten legacygroups.

Another example is if you have users who have not accepted invitations to join your dynamic tag managementcompany in the past and there are no matching default groups. These users, after accepting the invitations, will beadded to legacy groups according to their associated properties and roles.

These legacy groups can be edited as needed and should be renamed with descriptive names that make sense.

Add Users to Groups

Add (invite) users to existing groups.


1. From your company dashboard, click Groups.

2. Click Edit next to an existing group.

You can also invite users while creating new groups as explained in Create a New Group.

3. From the Add User drop-down list, select a user's email address, then click Add User to Group.

The drop-down list is populated with the available users in your system. As you add users, their email addressesare removed from the drop-down list.

Each user will receive an email message with a link to accept group membership. Users will not display in thelist until they accept invitations.

4. Add additional users as needed.

5. Click Save Group.

From your company dashboard, you can click the Users tab to view a list of users and see related information:name, email address, updated by, and which groups they belong to (Admin, Users, and so forth).

If a user belongs to multiple groups, the displayed role is the role with the highest level of access. For example, if auser has the User role for some properties and the Admin role for other properties, Admin displays in the list, asshown below:

You can click Revoke to rescind an invitation for a specific user or click Resend to send the invitation email messageto the user again.

You can also add users to groups for a specific property by navigating to the property (your company dashboard >the desired property) and then by clicking the Manage Groups button.

Create a New Group

Create a new user group, select its default role, and add users to the group.

Note: You must be a company administrator to create a new group.


2. Click Create New Group.



Name: (Required) Specify a descriptive name for the group.

Description: Specify an optional description for the group. The description displays on the Groups page andcan help you locate a specific group and determine its purpose.

Tool Check Boxes: (Optional) Select the desired check box next to any tools to restrict access to those tools.If the check box is selected, users in this group cannot create or modify the selected tools and related tool settingsin rules. By default, all users in the group have access to all tools.

A green checkmark ( ) next to a tool indicates that the corresponding tool is currently installed for this property.

If a user is a member of two groups and one group restricts tool access and the other group allows access,access rights are restricted for any selected tools.

Note that all users in the Admins group have full access to create and modify all tools and related tool settingsin rules. If you are creating or editing an Admins group, the tool check boxes do not display in the UI.

Default Role: (Optional) Select a default role. All newly created properties going forward inherit this role.

CreateProperty

Create/EditUsers

PublishRules

ApproveRules

TestRules

EditRules

CreateRules

User Role

YesYesYesUser



YesYesYesYesYesApprover and Publisher


Note that if you add users to the Approver group and to the Publisher group, those users have the same rolesas those in the Approver and Publisher group.

In most situations, the roles in the previous table are sufficient.You can, however, create custom default roles.

4. (Optional) To create a custom default role, click Define Role Per Property, then choose a different default rolefor each property, as needed.

In the following illustration, the default role for Property1 is "User" and the default role for Property2 is "Approver."


A use-case for having different roles for each property is in an agency in which you might want some users tohave access to certain properties, but not have access to other properties. Another benefit of having groups withdifferent access to varying properties is if you have users who come and go from the agency.You can simplydelete an existing user from the group and add a new user without spending considerable time setting up accessrights to different properties.

If you specify different default roles for each property, ensure that you name the group with a descriptive nameand provide an optional description.

Note: Be aware that if you collapse the Default Role section by clicking Define Role per Property again,all roles are set to the default role, regardless of how they were set before collapsing the section.

5. From the Add User drop-down list, select a user's email address, then click Add User to Group.

The drop-down list is populated with the available users in your system. As you add users, their email addressesare removed from the drop-down list.

Each user will receive an email message with a link to accept group membership. Users will not display in thelist until they accept invitations.

6. Add additional users as needed.



Edit a Group

Edit an existing user group to change its name, description, default role, or add users to the group.

Note: You must be a company administrator to edit a group.


2. Click Edit next to the desired group.

3. Edit the desired fields, as explained in Create a New Group.


Delete a Group

Delete an existing user group if it is no longer necessary.

Note: You must be a company administrator to delete a group.


2. Click Edit next to the desired group.

3. Click Delete.

4. Click Yes to confirm that you want to delete the group.

Users in this group might not have access to any associated properties.

Note: Do not delete the Admin group. Doing so might require that you call Adobe to re-add users to theAdmin group.


Frequently Asked Questions about Users and Permissions

List of Frequently Asked Questions (FAQs) about users and permissions in the Marketing Cloud and in DynamicTag Management.

I added a user using the Admin tab for the DTM product in the Adobe Admin Console, but that user was notadded as a user in DTM. Why wasn’t the user created in DTM?

Adding a user to the Admin tab in a group does not grant permissions in DTM. That process allows the user to editthe Product Configuration Groups in the Adobe Admin Console. In order to add the user to DTM, they need tobe added using the Users tab.

My DTM account was created prior to April 5, 2016, how do I manage my users?

If User Management in the Adobe Admin Console is not enabled, DTM users are managed from within DTM onthe Users tab.

My DTM account was created prior to April 5, 2016 and I want to migrate my users to log in through theMarketing Cloud. How do I accomplish this?

Contact Customer Care to restrict login access to the Marketing Cloud.


I invited a user through DTM, but I want the user to log in through the Marketing Cloud.

An account can be linked to a Marketing Cloud user by selecting the Product Selection box > Activation > LinkAccount. For more information, see Link Accounts in the Marketing Cloud.

Why do I see the error “Failed to fetch permission groups for this product”?

This is a provisioning error. Contact Customer Care to resolve this error.

I was invited to a DTM company, who do I get an error that my password is wrong?

If your DTM account is enabled for the Marketing Cloud, but the login company for the new invite is a legacy company,the account might be the issue.

First, try accepting the link by logging into the DTM account through DTM (not through the Marketing Cloud). If youreceive an error that the password is wrong, use the password reset option.

If the account was created through the Marketing Cloud and was not ever used to log in directly at dtm.adobe.com,a new email address must be used. This is only the case if the account was created via marketing.adobe.comand has never logged in via dtm.adobe.com. This scenario occurs when the invite comes from a legacy companythat has not migrated to the Marketing Cloud and the user was created through the Marketing Cloud.

For more information, see the note in Manage Users.


https://marketing.adobe.com/resources/help/en_US/mcloud/t_get_access.html

Embed Code and Hosting OptionsInformation about the various hosting options in dynamic tag management: Akamai, self-hosting FTP delivery, andself-hosting library download.

Important: For a successful implementation, it is critical that you follow these instructions as they appear inAdobe Help. Specifically, you must place the header code in the <head> section of your document templates.Also, you must place the footer code just before the closing </body> tag. Placing either of these embed codeselsewhere in your markup, or using asynchronous methods to append the embed codes, are not a supportedimplementation of dynamic tag management.

An unsupported implementation will yield unexpected results and prevent Customer Care and Engineeringfrom assisting with your implementation.

Including multiple embed codes on a single page is not supported, as it can cause conflicts.


• Hosting Workflow

• Hosting Options

Hosting Workflow

The following illustration shows the hosting workflow in dynamic tag management:

70Embed Code and Hosting Options

Hosting Options

You can deploy dynamic tag management using one or more of the following options, found on the Embed tab:

ImplementationDescriptionHosting Option

The simplest hosting option to implement.Akamai (migratedfrom Amazon S3)

1. Dynamic tag management generatescustom JavaScript libraries.Globally distributed delivery network.

2. Dynamic tag management exports thecustom JavaScript libraries to Akamai.Adds additional third-party infrastructure

dependencies (DNS lookup, Akamaiavailability).

3. The target website references theAkamai-hosted dynamic tag managementlibraries directly at the page level.See Akamai for information about migrating from

Amazon S3 to Akamai.

Amazon S3Note: After July 31, 2015 Adobe will nolonger support Amazon S3.Your dynamictag management libraries on Amazon S3will continue to be served until December31, 2015, but in a read-only state. Anychanges made in dynamic tagmanagement will no longer be reflectedin these files.

To deploy additional changes to your site afterJuly 31, 2015, you must select one of our otherhosting options. Self-hosting (FTP Delivery orLibrary Download) is always the suggested bestpractice, but our 3rd-party Akamai hosting is aworld-class option as well.

A push approach, whereby dynamic tagmanagement exports custom JavaScript

Self-hosting: FTPDelivery

1. Dynamic tag management generatescustom JavaScript libraries.

libraries directly to the web content server hostvia the FTP protocol.

2. Dynamic tag management exports thecustom JavaScript libraries to host servervia FTP.This solution requires an FTP server and

credentials to be available on the web content 3. The target website locally references thecustom dynamic tag management libraries.server to publish changes to the custom

dynamic tag management libraries.

For more detailed information, see FTP.

A pull approach, whereby the applicationexports custom JavaScript libraries to Amazon

Self-hosting:Library Download

1. Dynamic tag management generatescustom JavaScript libraries.

S3. There, the libraries can be accessed by ahosted server-side process.

2. Dynamic tag management exports thecustom JavaScript libraries to Akamai.


ImplementationDescriptionHosting Option

Additionally, the libraries are available via webdownload directly from the dynamic tagmanagement interface.

3. Custom dynamic tag management librariesare manually or programmatically moved tothe web content server.

This solution requires either a manual retrievaland publication of the dynamic tag management

4. The target website locally references thecustom dynamic tag management libraries.

libraries or the creation of an automated processthat pulls the libraries from Akamai onto the webcontent server.

This approach takes the most time to set up,but is also the most secure and flexible option.

For more detailed information, see LibraryDownload.

You can expect improved performance and more control over security by hosting the FTP Delivery and the LibraryDownload options on your CDN or infrastructure.

Time: 4:00DTM Basics: Library Hosting Options


• Explain the different hostingoptions

Hosting Considerations (FAQ)

Questions to consider when deciding on a hosting option.

You might consider the following questions when deciding which hosting option is best for your organization:

Dynamic tag management creates and uses various JavaScript files thatcontain all the code needed to run the system. These “library files” can

How do I choose a hosting option?

be hosted by Adobe, or they can be hosted on your own servers withinyour own Web architecture.

The Library Download hosting option also allows you to self-host thelibrary files. When an authorized dynamic tag management user makesa change in the software, our system writes those changes out to thelibrary files.When you host the library files on your servers with this option,our system needs a way to get those changes to your servers. With theLibrary Download hosting option, our system sends a ping (an http post)to your system to let your servers know there’s been an update to thelibrary files.Your IT team can create a cron job, or other scripted process,so your servers can pick up the changed files. In this way, whenever a


change is made in dynamic tag management, the files you’re hosting onyour servers can be updated in an automated manner.

You can use one or more of these hosting options for a web property,just don’t use more than one embed code in any single page. For example,you could use Akamai in your staging environments and one of theself-hosted options in your production environments. Or, you could usethe Akamai option for any sites, domains, or subdomains hosted by oneof your agency partners. These options give you more flexibility to hostthe library files according to your specific needs.

The answer to this question helps determine whether the JavaScriptlibrary can be hosted on Akamai, pushed to the website file structure viaFTP, or manually pulled into the file structure by a server-side process.

What is your current policy regardingwebsite content sources?

• Akamai• FTP delivery• Library download

Yes, you can turn on and use any number of the hosting options and usedifferent embed codes for different domains or subdomains.

Can I use more than one dynamic tagmanagement library hosting option atonce?

For example, you might want to use the Akamai option for your lower-level,non-production environments such as staging, dev, test, or UAT. At thesame time, you might use one of the self-hosted options, such as LibraryDownload, for your production environments.

Remember that you cannot use more than one option on the same page.You should not implement more than one Header Embed code on anypage.

The deployment process affects how quickly changes can be deployedto the site from the dynamic tag management administrative interface. It

What is your current website contentdeployment process?

also affects how long it takes to initially install dynamic tag managementon the website.

An understanding of the basic page-level markup and structural decisionson the website helps with the proper installation of dynamic tag

What is the current page-level markupand structure of the website?

management and the construction of rules within the administrativeinterface.

Key items to identify include:

• Which JavaScript libraries are referenced within the <head> section ofthe web page.

• Whether the individual sections of the page, such as headers and footers,are dynamically generated.

Knowledge of any content management systems that are used is helpfulin determining the appropriate hosting methodology.


Akamai

Akamai is the primary external hosting option. Akamai provides you with a reliable hosting experience and is thesimplest option to implement. Akamai provides the greatest third-party infrastructure dependencies, such as DNSlookup, faster load times, and faster round-trip delivery times.

The Akamai hosting option allows you to store your web property library files on Adobe’s Edge CDN, which sits onthe Akamai architecture. This option allows you to install the Embed codes in your page templates and quickly getup and running with dynamic tag management without involving your internal IT teams and servers.

Note: After July 31, 2015 Adobe will no longer support Amazon S3.Your dynamic tag management librarieson Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changesmade in dynamic tag management will no longer be reflected in these files.

To deploy additional changes to your site after July 31, 2015, you must select one of our other hosting options.Self-hosting (FTP Delivery or Library Download) is always the suggested best practice, but our 3rd-partyAkamai hosting is a world-class option as well.

• Why Choose Akamai Hosting for Library Files?• Can I Avoid Errors in Case of Akamai Unavailability?

Why Choose Akamai Hosting for Library Files?

When you choose the Akamai option in the Embed section of dynamic tag management, it means that your dynamictag management library files are served to your visitors from Adobe’s Edge CDN, which runs on Akamai architecture.

Akamai is robust when serving content to a global, high-volume audience of Web visitors. Akamai runs redundantnetworks of load-balanced, geo-optimized nodes to serve content as quickly as possible to visitors wherever theyare located throughout the world.

Specifically, Akamai runs more than 137,000 servers in 87 countries within more than 1,150 networks. In terms ofredundancy, Akamai does not just route from one server to another, Akamai routes from one node of servers toanother node of servers as-needed. In other words, each node consists of multiple servers for redundancy within anode, so a box going down is not an issue because he other boxes in the node take over. If a node goes down,Akamai serves from the next closest one, with the same cached content. Nodes are dynamically selected based onvisitor location, traffic load, and other factors so content is consistently served from the best local node for eachvisitor.

Can I Avoid Errors in Case of Akamai Unavailability?

No. Dynamic tag management can do nothing from the client side if the library is unavailable. However, it is extremelyunlikely that Akamai would be unavailable.

Migrate from Amazon S3 to Akamai

Migrate from Amazon S3 hosting to Akamai by replacing Amazon S3 code.


Note: After July 31, 2015 Adobe will no longer support Amazon S3.Your dynamic tag management librarieson Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changesmade in dynamic tag management will no longer be reflected in these files.

To deploy additional changes to your site after July 31, 2015, you must select one of our other hosting options.Self-hosting (FTP Delivery or Library Download) is always the suggested best practice, but our 3rd partyAkamai hosting is a world class option as well.

1. Navigate to the Embed tab.

2. Replace your existing Amazon S3 header codes with the new Akamai header codes.

No change is necessary in the footer code.

3. Click Akamai to the On position.

4. Click the Amazon S3 option to the Off position.

Note: After you disable Amazon S3, you can no longer use Amazon S3 hosting. Ensure that you no longerneed Amazon S3 before turning it off.

Akamai hosting in dynamic tag management functions independently of any Akamai hosting you currently usefor your website.

FTP

Steps to deploy dynamic tag management using FTP (the push methodology).

The FTP Delivery hosting option lets you self-host the library files. When an authorized dynamic tag managementuser makes a change in the software, dynamic tag management writes those changes to the library files. When you


host the library files on your servers with this option, dynamic tag management must get those changes to yourservers.With the FTP Delivery hosting option, dynamic tag management connects to your system, using credentialsand server locations you enter into the system, and delivers any changed files. In this way, whenever a change ismade in dynamic tag management, the files you are hosting on your servers can be updated automatically.

You must be an administrator to be able to deploy via FTP.

1. In the web property, click the Embed tab.

2. Click FTP Delivery.

3. Provide the required FTP information for the staging and production servers, then click Save FTP Information.

Note: Click Enable Relative Hostnames for Staging and Production Library Hosting, if desired.Enabling relative hostname prepends the provided library paths with "window.location.hostname". Thisallows DTM to load hosted scripts from relative paths, giving you the ability to host your library withoutediting your path for each deploy.

4. Toggle the switch in the top right corner to ON.

5. Click Header Code and Footer Code to expand those sections.

6. Click the appropriate Copy Embed Code button to copy header and footer codes for your staging or developmentenvironments.

Note: The staging code should go only into your staging or development environment. Production codeshould be placed on the live production site.

7. Copy the header code and place it within the HEAD section of the site HTML, on every page of the website.Place it as close to the beginning <head> tag as possible.

8. Copy the footer code and place it within the BODY section of the site HTML, on every page of the website. Placeit as close to the closing </body> tag as possible

Library Download

Steps to deploy dynamic tag management using Library Download (the pull methodology).

The Library Download hosting option also lets you self-host the library files. When an authorized dynamic tagmanagement user makes a change in the software, dynamic tag management writes those changes to the libraryfiles. When you host the library files on your servers with this option, dynamic tag management must get thosechanges to your servers. With the Library Download hosting option, dynamic tag management sends a ping (anHTTP post) to your system to let your servers know there has been an update to the library files.Your IT team cancreate a cron job, or other scripted process, so your servers can pick up the changed files. In this way, whenever achange is made in dynamic tag management, the files you are hosting on your servers can be updated automatically.


You must be an administrator to deploy using the Library Download.

1. In the web property, click the Embed tab.

2. Click Library Download in the left navigation.

3. Fill out one or both of the following optional fields:

DescriptionOption

Encrypts the dynamic tag management library during download.Shared Secret

If you enter a shared secret, we use AES-256 to encrypt your .zip file using thispassphrase.

The process of deploying dynamic tag management files to the server can be automatedwhenever there is an update. Create a script that is accessible via the specified publicURL.

Deploy Hook URL

If you enter a deploy hook URL, we make an HTTP POST to it every time wesuccessfully update your bundle.The body of the post will include a payload containingthe download URL of the bundle.

4. Complete the fields under Domain and Paths to Tracking File, for staging and production.

Specify the location where the files reside when deployed to your server. Do not include the protocol or anyleading or trailing slashes. Dynamic tag management requires a domain and a path for HTTP or HTTPS for theproduction and staging environments.

Note: Click Enable Relative Hostnames for Staging and Production Library Hosting, if desired.Enabling relative hostname prepends the provided library paths with "window.location.hostname". Thisallows DTM to load hosted scripts from relative paths, giving you the ability to host your library withoutediting your path for each deploy.

5. Download the files from the specified URL for the respective environment (staging or production), and deploythem to the location specified in the settings.

6. Click the Header Code and Footer Code sections.

7. Click the appropriate Copy Embed Code button to copy header and footer codes for your staging or developmentenvironments.

Note: The staging code should go only into your staging or development environment. Production codeshould be placed on the live production site.


8. Copy the header code and place it within the HEAD section of the site HTML, on every page of the website.Place it as close to the beginning <head> tag as possible.

9. Copy the footer code and place it within the BODY section of the site HTML, on every page of the website. Placeit as close to the closing </body> tag as possible

Header and Footer Code

Use dynamic tag management to add header and footer code that determines the loading of JavaScript and pagecontent on your site.You must install both the header and footer code on every page of your site, regardless of thehosting option used.

Time: 4:20DTM Basics: Embedding Code


• Understand the embeddingelements

• Explain the difference betweenstaging and production

• Not confuse embedding codeswith the s.code

Because dynamic tag management includes a snippet of code in both your header and footer, you can run rules atthe beginning or end of a page. This ability allows you to implement testing tools and other technologies whileretaining control over tracking your pages.

Dynamic tag management creates staging and production embed codes you can use to test your changes in yourstaging environment before pushing changes to your production environment.

Important: For a successful implementation, it is critical that you follow these instructions as they appear inAdobe Help. Specifically, you must place the header code in the <head> section of your document templates.Also, you must place the footer code just before the closing </body> tag. Placing either of these embed codeselsewhere in your markup, or using asynchronous methods to append the embed codes, or wrapping theembed codes in any way, are not a supported implementations of dynamic tag management. The embedcodes must be implemented exactly as provided.

An unsupported implementation will yield unexpected results and prevent Customer Care and Engineering fromassisting with your implementation.

Because dynamic tag management includes a snippet of code in both your header and footer, you can run rules atthe beginning or end of a page. This ability allows you to implement testing tools and other technologies whileretaining control over tracking your pages.

Add header and footer code

Add header and footer code in dynamic tag management.

1. Copy the production header code and place it within the HEAD section of your site HTML.


Place the code as close to the <head> tag as possible. This code snippet should be placed on every page ofyour live production site.

Note: Production embed code reflects only the published items in that property. However, embed codefor staging reflects all items in the associated property, regardless of the published or unpublished state.To test unpublished items on your production site, locally enable staging in the console by following theinstructions in Test unpublished rules for Akamai hosting.

2. Copy the production footer code and place it in the BODY section of your site HTML.

Place the code as close to the </body> tag as possible.

3. Copy the staging header and footer code, then repeat the steps above on your staging site.

Note: The difference between production and staging code snippets is the addition of -staging to thefilename in the staging version. The footer code remains the same in staging and production.

Verify header and footer code

Verify that your dynamic tag management library is loading properly on your site.

1. Open your site in your browser.

2. Open the Developer Console by right-clicking and choosing Inspect Element > Console.

3. Press Enter.

If the code was properly installed, you will see true display in the console.

If the code was not properly installed, you will see the reference error:

_satellite is not defined

If you receive this error, ensure that:

• You have included the full header code on every page of the site in the HEAD section, as close to the <head>tag as possible.

• You do not have unexpected characters appearing in the code snippet, potentially as a result of copying andpasting from a formatted document.


ToolsTools let you quickly integrate Adobe Marketing Cloud solutions on your site. Tools go beyond a basic tag becausethey provide additional configuration options. A tool corresponds to Adobe solutions, such as Analytics and Target,as well as Google Analytics. After you add a tool to a property, it is available for inclusion in a rule.

Dashboard > Company > Web Property Name > Overview

DescriptionElement

Displays the installed tools. Tools are deployments of Adobe Analytics, Adobe Target,Google Universal Analytics, and so on.

Installed Tools

Displays the Add a Tool page. Available tools include the following:Add a Tool

• Adobe Analytics• Adobe Audience Management• Adobe Media Optimizer• Adobe Target• Marketing Cloud ID Services settings (Analytics Visitor ID)• Google Analytics• Google Universal Analytics• Nielsen Tool

You can access rules to add a tag and to determine when your tag will fire.You openthe third-party tags section of your rule, paste your tag, and save the rule.

Add a Tag

See Rules.

Displays users, email addresses, and roles. Click Manage Users to add additionalusers and define their roles.

Assigned Users

See Users and Permissions.

Add Adobe Experience Manager ContextHub Tool

Use the AEM ContextHub tool to integrate Dynamic Tag Management with the Adobe Experience Manager (AEM)ContextHub (AEM's version of the data layer).You can also use this tool to integrate DTM with any data layer, evenfor websites that do not use AEM.

DTM customers often use data elements to map to their websites' data layers. For example, the data layer mightinclude information that a user is looking at a particular product or has placed an item into the shopping cart. DTMcan use this information in rule conditions and actions in a number of ways. This includes the sending of data toAnalytics for reporting purposes or to Target to display customized content for the user.

The AEM ContextHub tool solves many problems associated with data layers. Some data layers don't load at thetop of the page. Other data layers are dynamic or asynchronous and change frequently as the page changes. In thepast, both of these issues made it problematic for DTM to effectively send data or trigger actions.

The AEM ContextHub tool eliminates the need to write custom code that frequently checks to determine if the datalayer changes, loads somewhere other than the top of the page, or is modified as the page changes.

80Tools


As an example, suppose a customer places an item in the shopping cart and then removes that item. If the pagedoesn't refresh as the data layer changes DTM will not recognize the change without a custom code addition. TheAEM ContexHub tool contains a polling engine that checks every second to determine if there are changes.

Because DTM can now proactively populate data elements via the data layer, users can also use AEM ContextHubdata elements in conjunction with previously released conditions, such as Data Element Value. This allows usersto manage data layer values on a page load, or combine the Data Element Value condition with thedataelementchanged event, in cases where the data layer has changed due to user interaction.

When you configure this tool, you can use the default setting to integrate with the AEM ContextHub or you cancustomize the structure to work with any website.

1. Click Web Property Name > Overview > Add a Tool > AEM ContextHub.

2. Specify a descriptive name for the tool.

This name displays on the Overview tab under Installed Tools.

3. Click Create Tool to display the AEM ContextHub Settings page.

81Tools


DescriptionElement

Use the AEM ContextHub format.Use Default ContextHub DataLayer

With this option selected, DTM references the default ContextHub schema forthis integration. If you have made changes to your ContextHub schema, or wantto use a different data layer, use the customized option.

Use a custom format that maps to the data layer structure of any website, evenif it does not use AEM.

Customize ContextHub DataLayer

This option lets you edit your data layer schema. By default, it populates the editwindow with the default ContextHub data layer, where you can make changesor completely replace it with your code.

If you choose the Customize ContextHub Data Layer option, you can use theeditor to insert your custom code.

Open Editor

Add any notes regarding this implementation.Add a Note


82Tools

Data Layer Management Using the ContextHub Tool

The Dynamic Tag Management (DTM) AEM ContextHub tool can be used for both ContextHub and generic datalayer implementations. The ContextHub data layer schema is loaded by default in the tool and provides a simpleintegration with Adobe Experience Manager (AEM) ContextHub stores. Examples for both the default ContextHubimplementation and a custom generic data layer implementation are provided.


• Prerequisites

• AEM ContextHub Tool Components

• Data Element Monitoring

Prerequisites

To use the ContextHub Tool, you must meet the following prerequisites:

• An existing ContextHub or Javascript object data layer on a website.

• A JSON schema that properly defines the data layer in use on the website.

• An active DTM web property in use on the website.

AEM ContextHub Tool Components

The AEM ContextHub Tool adds two pieces of functionality to DTM:

• The Data Layer Definition• The AEM ContextHub data layer type

Additionally, a new event type has been added to facilitate data layer monitoring called dataelementchanged. Thisevent type can be used independently of the AEM ContextHub tool.

Each functional area corresponds to a configuration step described in both examples below.

Data Element Monitoring

The new dataelementchanged event type monitors any changes that occur to a specific data element value duringa page view. The following observations should be noted when using this event type.

1. The data element must map to a simple Javascript value. Complex values like arrays and objects that are returnedin a data element custom script will not work correctly. Cookies, CSS selectors, and URL parameters also produceunexpected results and might not work at all. Simple values like strings and integers work fine.

2. Be conservative in the number of dataelementchanged event types that are referenced on a single page. Althoughthe monitoring is efficient, large numbers of evaluations could impact page performance.

3. The dataelementchanged event type works only within the current page view because it is a DOM-basedmonitoring system.

4. The data element monitor polls for the values.

ContextHub Data Layer Default Example

Example using the AEM ContextHub tool that references and uses the default ContextHub data layer within theDynamic Tag Management configuration.

83Tools

The ContextHub data layer will be loaded on a test Adobe Experience Manager (AEM) website, but ContextHubcan be used independently of AEM. Contact your Adobe representative if you would like to use ContextHubindependently of AEM.

All of the ContextHub stores can be referenced from the browser console.

The DTM data layer monitor starts before any other DTM functions, so the examples will not deploy the data layerthrough DTM even though it is possible to do so. Instead they will depend on the server-generated data layer.Otherwise Javascript warnings might occur because certain data layer values may not be available.


• Define the Data Layer

• Create a Data Layer Data Element

• Create an Event-Based Rule that Uses the Data Element Change Event Type

• Validate the Implementation

Define the Data Layer

The first step in configuring the AEM ContextHub tool is to add it to a web property.

Note: At this time only one AEM ContextHub tool is allowed per DTM web property.




84Tools

4. Select Use Default ContextHub Data Layer to leverage the standard ContextHub stores.

Or

Select Customize ContextHub Data Layer to modify the schema. It is necessary to use the customized optionif a non-default ContextHub data layer is being used in the implementation.

The default Data Layer Root enables access to all of the ContextHub stores. Given the dynamic nature of theContextHub stores, there are additional functions available with this data layer that are not available in the simpleJavascript object reference used by the generic data layer approach.

5. (Conditional) To use a custom data layer, click Open Editor to view the data layer schema definition. If the customdata layer is a modification of the ContextHub schema be sure to add “ContextHub” in the Data Layer Root field.

85Tools

The default ContextHub schema is populated in the editor.

a. Modify the schema as necessary to match the site data layer schema.

b. Click Save and Close to save the schema and close the editor.


Create a Data Layer Data Element

1. In the web property, click the Rules tab, then click Data Elements in the left menu.

2. Click Create New Data Element.

86Tools

3. Specify a name for the data element. In this example, name the data element "total_price."

4. From the Type drop-down list, select AEM ContextHub.

The name of the AEM ContextHub Tool is populated in the “Source,” but only one AEM ContextHub Tool can bedefined in the current version.

5. Map the data element to the data layer by selecting a path in the Object selector.

In this example, select the cart.totalPriceFloat object.

6. Click Save Data Element.

Create an Event-Based Rule that Uses the Data Element Change Event Type

1. In the web property, click the Rules tab, then click Event Based Rules in the left menu.

2. Click Create New Rule.

3. Name the rule. In this example, name the rule "cart_total_update."

4. Expand the Conditions section.

87Tools

5. From the Event Type drop-down list, select dataelementchanged.

6. Select the data element that was created in the previous section (total_price).

88Tools

7. Under Rule Conditions, select Data Element Value from the drop-down list, then click Add Criteria.

8. Select the data element that was created in the previous section (total_price) and assign a value to cause therule to fire.

In this example, a regular expression is used to evaluate anything greater than or equal to 50:^([5-9]\d|[1-9]\d{2,})$

Note: If data element values are used in this way as conditions, it is important that the data element settingsare considered in the match. For example, selecting the Force Lowercase Value option in the data element

89Tools

settings would convert the value to all lowercase before evaluation. Because Javascript is case sensitive“test” is not the same as “Test” and the condition would not fire as expected.

9. Expand the Javascript / Third Party Tags section.

10. Click Add New Script.

11. Add a non-sequential Javascript that provides a notification if the rule fires. Name the rule “big_money_alert,”then add an alert script similar to the following example:

alert('$' + _satellite.getVar(‘total_price’) + ‘ is big money!’);

12. Click Save Code, then click Save Rule.

Validate the Implementation

On the DTM-enabled website that runs the above web property, validate the implementation.

• In the developer console check for the existence of the data layer (ContextHub).

90Tools

• Change the data layer object that is being monitored to a value that does NOT match the condition above:ContextHub.setItem('/store/cart/totalPriceFloat','5');

• Change the data layer object that is being monitored to a value that DOES match the condition above:ContextHub.setItem('/store/cart/totalPriceFloat','52');

• In the example implementation, an alert box should appear:

If DTM debugging is turned on, the failed evaluation should appear in the console.

Custom Data Layer Example

Example using the AEM ContextHub tool that references and uses a custom, non-ContextHub data layer within theDynamic Tag Management configuration.

The example data layer (_dl) will be loaded on the test web page as a Javascript object definition in the <head/>section of the page before the DTM embed code is referenced.

<head> <script> window._dl = { page: { name: 'homepage', quantity: 1, friend: 'No one' } } </script> <script src="//assets.adobedtm.com/satelliteLib-*.js"></script></head>

The DTM data layer monitor (see below) starts before any other DTM functions, so the examples will not deploy thedata layer through DTM. Otherwise Javascript warnings might occur because certain data layer values may not beavailable.


• Define the Data Layer

• Create a Data Layer Data Element

• Create an Event-Based Rule that Uses the Data Element Change Event Type

• Validate the Implementation

91Tools

Define the Data Layer

The first step in configuring the AEM ContextHub tool is to add it to a web property.

Note: At this time only one AEM ContextHub tool is allowed per DTM web property.




4. Select Customize ContextHub Data Layer to modify the schema.

92Tools

A root Javascript object name must be added to the Data Layer Root field for non-ContextHub data layers. The_dl definition is used in the generic examples in this section.

5. Click Open Editor to view the data layer schema definition.

By default, the default ContextHub schema is populated in the editor.

93Tools

6. Delete the default schema and paste in the site data layer schema.

The following sample non-ContextHub schema is used in the generic examples:

{ "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "properties": { "page": { "type": "object", "properties": { "name": { "type": "string" }, "quantity": { "type": "number" }, "friend": { "type": "string" } }, "required": [ "name", "quantity", "friend" ] } }, "required": [ "page" ]}

7. Click Save and Close to save the schema and close the editor, then click Save Changes.

94Tools

Create a Data Layer Data Element

1. In the web property, click the Rules tab, then click Data Elements in the left menu.


3. Specify a name for the data element. In this example, name the data element "my_friend."

4. From the Type drop-down list, select AEM ContextHub.

The name of the AEM ContextHub Tool is populated in the “Source,” but only one AEM ContextHub Tool can bedefined in the current version.

5. Map the data element to the data layer by selecting a path in the Object selector.

In this example, select the page.friend object.

95Tools


Create an Event-Based Rule that Uses the Data Element Change Event Type

1. In the web property, click the Rules tab, then click Event Based Rules in the left menu.

96Tools


3. Name the rule. In this example, name the rule "find_a_friend."

4. Expand the Conditions section.

97Tools

5. From the Event Type drop-down list, select dataelementchanged.

6. Select the data element that was created in the previous section (my_friend).

98Tools

7. Under Rule Conditions, select Data Element Value from the drop-down list, then click Add Criteria.

8. Select the data element that was created in the previous section (my_friend) and assign a value to cause therule to fire.

In this example use “Carl” as the value.

Note: If data element values are used in this way as conditions, it is important that the data element settingsare considered in the match. For example, selecting the Force Lowercase Value option in the data element

99Tools

settings would convert the value to all lowercase before evaluation. Because Javascript is case sensitive“test” is not the same as “Test” and the condition would not fire as expected.

9. Expand the Javascript / Third Party Tags section.


11. Add a non-sequential Javascript that provides a notification if the rule fires. Name the rule “found_my_friend,”then add an alert script similar to the following example:

alert(_satellite.getVar(‘my_friend’) + ‘ is my friend.’);

12. Click Save Code, then click Save Rule.

Validate the Implementation

On the DTM-enabled website that runs the above web property, validate the implementation.

• In the developer console check for the existence of the data layer (_dl).

• Change the data layer object that is being monitored to the value that was set in the condition above(_dl.page.friend = ‘Carl’).

100Tools

• In the example implementation, an alert box should appear:

• Change the object to a different value (_dl.page.friend = ‘Bob’) and no alert should display.

Note: If DTM debugging is turned on, the failed evaluation should appear in the console.

• Change the object to a lowercase value of the match (_dl.page.friend = ‘carl’) and no alert should display.

• Change the object to the correct case value of the match (_dl.page.friend = ‘Carl’) and the alert should onceagain display.

Add Adobe Analytics Tool

You can deploy Adobe Analytics (Standard and Premium) using dynamic tag management by creating the AdobeAnalytics tool and configuring the page code either automatically or manually.The automatic method is recommendedfor most users.

Note: For improved visitor tracking, it is strongly recommended that you enable Marketing Cloud ID Service.


• Add an Adobe Analytics Tool

• Edit an Existing Adobe Analytics Tool

• Enabling Adobe Analytics Premium

101Tools

https://marketing.adobe.com/resources/help/en_US/mcvid/

Add an Adobe Analytics Tool

1. Click Web Property Name > Overview > Add a Tool > Adobe Analytics.


DescriptionElement

The type of tool, such as Adobe Analytics.Tool Type

A descriptive name for this tool. This name displays on the Overview tab underInstalled Tools.Tool Name

Automatic (Recommended): Use dynamic tag management to manage theconfiguration.This method enables automatic synchronization of Adobe Analytics

Configuration Method

report suites via a Marketing Cloud login or Web Services ID, and manages theAppMeasurement code.

After the accounts are connected, dynamic tag management pulls the AdobeAnalytics report suite IDs and names into the tool configuration interface, allowingfor increased speed in tool deployment with less possibility for user errors.

Note: You must choose the Automatic option if you are an Adobe AnalyticsPremium customer. See Enabling Adobe Analytics Premium below.

Fill in the fields specific to automatic configuration:

• Marketing Cloud: (Default) Uses Marketing Cloud single sign-on. Specify yourMarketing Cloud ID and password.

• Web Services: Specify your Web Services username and shared secret.

102Tools

DescriptionElement

Shared secret credentials are located in Admin Tools > Company Settings> Web Services.

Developers, see Get Web Service Access to the Enterprise API for help withobtaining Web Services credentials.

Manual: Manually manage the AppMeasurement code.You can download theAnalytics AppMeasurement code from Admin Tools > Code Manager.

Click JavaScript (new) for information about downloading the code locally to copyand paste in the Edit Code field in Library Management.

Fill in the fields specific to a manual configuration:

• Production Account ID: (Required) Your production account for data collection.For Analytics, this is your report suite ID. Dynamic tag managementautomatically installs the correct account in the production and stagingenvironment.

• Staging Account ID: (Required) Used in your development or test environment.For Analytics, this is your report suite ID. A staging account keeps your testingdata separate from production.

• Tracking Server: Specify the information for your tracking server.

The Tracking Server and SSL Tracking Server variables are used for first-partycookie implementation to specify the domain at which the image request andcookie is written. For more information, see the Correctly Populate thetrackingServer and trackingServerSecure Variable article.

• SSL Tracking Server: Specify the information for your SSL tracking server.

3. Click Create Tool to create the tool and display it for editing.

Tools are displayed on the Overview tab, under Installed Tools.

4. (Conditional) Configure the tool further as necessary by following the directions in the links below (General,Library Management, Global Variables, Pageviews & Content, Link Tracking, Referrers & Campaigns,Cookies, and Customize Page Code).

See FAQ - Adobe Analytics Tool for additional information about this tool.

Edit an Existing Adobe Analytics Tool

You can edit an existing Adobe Analytics tool to change its configuration settings.

1.Click the icon next to an installed tool from the Overview tab.

2. Edit the fields as desired.

The following table includes only those elements that differ from the elements available when you are creatingan Analytics tool, as described above. However, you can change any element on the page, as described in bothtables.

103Tools

https://marketing.adobe.com/developer/en_US/get-started/enterprise-api/c-get-web-service-access-to-the-enterprise-api

https://marketing.adobe.com/resources/help/en_US/sc/implement/appmeasure_mjs.html

https://helpx.adobe.com/analytics/kb/determining-data-center.html

https://helpx.adobe.com/analytics/kb/determining-data-center.html

DescriptionElement

Enable AutomaticConfiguration

Note: Enabling this setting changes a manually configured implementationto the automatic configuration method described in Configuration Method.

This option lets dynamic tag management automatically retrieve your AdobeAnalytics account's configuration.

The latest available AppMeasurement code is used and upgrade notificationsare displayed for selection as new versions become available.You can also rollback to previous AppMeasurement versions as necessary, such as forcompatibility reasons. Up to five previous versions are displayed.

Refresh the API, for example, to update report suites associated with a user.Update Credentials

3. (Conditional) Configure the tool further as necessary by following the directions in the links below (General,Library Management, Global Variables, Pageviews & Content, Link Tracking, Referrers & Campaigns,Cookies, and Customize Page Code).


Enabling Adobe Analytics Premium

If you are an Adobe Analytics Premium customer, dynamic tag management lets you take advantage of advancedfeatures and additional eVars and events. For more information, see Adobe Analytics Premium.

The following table displays the number of eVars and events available in each Analytics account type:

Adobe Analytics PremiumAdobe Analytics (Standard)Adobe Analytics (PointProduct)

25010075eVars

1,0001,000100Events

You add the Adobe Analytics Premium tool using dynamic tag management the same way you add Adobe Analytics(Standard). In order to get the Analytics Premium functionality (if applicable), you must do the following:

• Use the Automatic configuration method (explained above).

• Use the Marketing Cloud or Web Services authentication method (explained above).

There is no "switch" to enable Analytics Premium functionality. Verification is done behind the scenes by APIchecks via the automatic configuration. The additional eVars are added to the UI if the account is authenticated asan Analytics Premium customer.

Note: If you downgrade to standard Analytics in the future, the added premium eVars that are out of thestandard range will be grayed out in both tools/rules.You can view any configured variables that are now outof range and make any necessary changes to an in-range variable.You cannot add or edit any of theseout-of-range variables, but you will be able to view them and delete them.

104Tools

http://wwwimages.adobe.com/content/dam/Adobe/en/solutions/digital-marketing/digital-analytics/pdfs/solution-overview-analytics-premium-ue.pdf

General

Field descriptions for the General settings in dynamic tag manager, for deploying Adobe Analytics.

Property > Edit Tool > General

DescriptionElement

Enables or disables tracking based on the EU privacy cookie.Enable EU compliance for Adobe Analytics

When a page is loaded, the system checks to see if a cookie calledsat_track is set (or the custom cookie name specified on theEdit Property page). Consider the following information:

• If the cookie does not exist or if the cookie exists and is set toanything but true, the loading of the tool is skipped when thissetting is enabled. Meaning, any portion of a rule that uses thetool will not apply.

If a rule has analytics with EU compliance on and third-partycode, and the cookie is set to false, the third-party code still runs.However, the analytics variables will not be set.

• If the cookie exists but it is set to true, the tool loads normally.

You are responsible for setting the sat_track (or custom named)cookie to false if a visitor opts out.You can accomplish this usingcustom code:

_satellite.setCookie(“sat_track”, “false”);

You must also have a mechanism to set that cookie to true if youwant a visitor to be able to opt in later:

_satellite.setCookie(“sat_track”, “true");

Displays the available character encoding sets.Character Set

Displays the supported currency codes for selection.Currency Code

The domain at which the image request and cookie is written.Tracking Server

See trackingServer.

The domain at which the image request and cookie is written.Used for secure pages. If not defined, SSL data goes totrackingServer.

SSL Tracking Server

See trackingServerSecure.

The Adobe data center used for data collection.Data Center

105Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=trackingServer

https://marketing.adobe.com/resources/help/en_US/sc/implement/trackingServerSecure.html

Library Management

Descriptions of the fields and options in the Library Management settings in dynamic tag management.

Property > Edit Tool > Library Management

Note: If more than one Adobe Analytics tool is used in a single web property, each tool must have a uniquetracker variable name. Duplicative object variable names between Adobe Analytics tools within a single webproperty will cause conflicts.

DescriptionElement

Prevents dynamic tag management from installing Adobe Analytics page code ifthe code is already present on your site.

Page code is already present

This feature allows you to use dynamic tag management to add to your existingimplementation rather than starting from scratch. Be sure to properly set yourtracker variable name when checking this box.

Specifies where and when to load the page code. Regardless of your selection,any rules using the Analytics tool will need to have the same setting.

Load library at <Page Top orPage Bottom>

Enable dynamic tag management to manage your library.Managed by Adobe(Recommended)

If you select this option, the following option becomes available:

Library Version: Select the latest version from the Library Version menu. Dynamictag management notifies you when new versions are available.You can revert toa previous version as necessary.

You can configure the library code.Custom

If you select this option, the following options become available:

Set report suites using custom code below: When this box is checked, dynamictag management looks for a variable in your custom code called s_account. Thisvariable should contain a comma-separated list of the report suites to which youwant to send data.

Code Hosted: Choose an option to host the s_code:

• In DTM:You can host the s_code within dynamic tag management. Click EditCode to cut and paste the file directly into the editor.

• URL: If you have a good s_code file and are happy with the process of updatingit, you can provide the URL to the file here. Dynamic tag management thenconsumes that s_code file for its implementation of Adobe Analytics.

Open Editor: Lets you insert core AppMeasurement code. This code is populatedautomatically when using the automatic configuration method described in AddAdobe Analytics Tool.

106Tools

DescriptionElement

Tracker Variable Name: If you want to run two instances of Adobe Analytics inparallel (one within dynamic tag management and one natively), you can renamethe main s object. Renaming the object name avoids collisions.

Insert core AppMeasurement code

Insert AppMeasurement code when manually deploying dynamic tag management in Adobe Analytics.

1. On the Adobe Analytics tool page, expand the General section, then click Open Editor.

2. Unzip the AppMeasurement_JavaScript*.zip file you downloaded in deploy Adobe Analytics.

If you opt for custom library, when you open the window it will already have the most recent code version present.There is no need to download the zip from the Admin Console.

3. Open AppMeasurement.js in a text editor.

4. Copy and paste the contents into the Edit Code window.

5. Adobe recommends adding the following code above the Do Not Alter Anything Below This Line:

var s_account="INSERT-RSID-HERE"var s=s_gi(s_account)

Important: If you add this code, it is recommended that you also select the Set report suites usingcustom code below checkbox in the overall library settings.

6. Click Save and Close.

If you are using the Media Module, Integrate Module, or implementation plug-ins, you can copy them into thecode section as well. The managed code in dynamic tag manager can be configured exactly like the JavaScriptfile in a typical implementation.

Global Variables

Field descriptions and information about variables when using dynamic tag management to deploy Adobe Analytics.

107Tools

These variables fire on all page load rule beacons.You can accomplish the same effect by using a Page-Load ruleset to fire on all pages. These variables might not fire in Direct Call Rules and Event-Based rules.

Global Variables - Field Descriptions

Property > Edit Tool > Global Variables

DescriptionElement

The predefined variable populates the Servers report in Adobe Analytics.Server

See server.

The eVar variables are used for building custom conversion reports.eVars

See eVarN.

Property (prop) variables are used for building custom traffic reports.Props

See propN.

A special prefix to the start of the value. The default prefix is "D=".Dynamic VariablePrefix

See Dynamic Variables.

Page Views and Content

Field descriptions in dynamic tag management for page views and content settings when deploying Analytics.

Property > Edit Tool > Page Views & Content

DescriptionElement

The name of each page on your site.Page Name

See pageName.

Overrides the actual URL of the page.Page URL Override

See pageURL.

Identifies a section of your site.Channel (Site Section)

See channel.

Determines the location of a page in your site's hierarchy.Hierarchy

Se hierN.

Link Tracking

Field descriptions in dynamic tag management for link tracking when deploying Analytics.

108Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/server.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/eVarN.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/propN.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/dynvars_overview.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/pageName.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/pageURL.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/channel.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/hierN.html

Property > Edit Tool > Link Tracking

DescriptionElement

Determines whether visitor click map data is gathered.Enable ClickMap

See trackInlineStats.

Tracks links to downloadable files on your site.Track download links

See trackDownLoadLinks.

If your site contains links to files with any of the listed extensions, the URLs of theselinks will appear in reporting.

Download Extensions

See linkDownloadFileTypes.

Determines whether any link clicked is an exit link.Track outbound links

See trackExternalLinks.

Single-Page App Considerations: Because of the way some SPA websites arecoded, an internal link to a page on the SPA site might look like it is an outboundlink.

You can use one of the following methods to track outbound links from SPA sites:

• If you do not want to track any outbound links from your SPA, insert an entry intothe Never Track section.

For example, http://testsite.com/spa/#

All # links to this host are ignored. All outbound links to other hosts are tracked,such as http://www.google.com.

• If there are some links that you want to track on your SPA, use the Always Tracksection.

For example, if you have a spa/#/about page, you could put "about" in the AlwaysTrack section.

The "about" page is the only outbound link that is tracked. Any other links on thepage (for example, http://www.google.com) are not tracked.

Note that these two options are mutually exclusive.

Preserves query strings.Keep URL Parameters

See linkLeaveQueryString.

Referrers and Campaigns

Field descriptions in dynamic tag management for referrers and campaign options when deploying dynamic tagmanagement in Adobe Analytics.

109Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=trackInlineStats.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=trackDownloadLinks.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=linkDownloadFileTypes.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=trackExternalLinks.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=linkLeaveQueryString.html

Property > Edit Tool > Referrers & Campaigns

DescriptionElement

Overrides the value set in the s.referrer variable, which is typically populated bythe referrer set in the browser.

Referrer Override

See referrer.

A variable that identifies marketing campaigns used to bring visitors to your site.The value of campaign is usually taken from a query string parameter.

Campaign

See campaign.

Use the DTM interface to choose whether you want to use a Query String or Value (which could pull from a dataelement):

You can either enter your query string directly in the interface, or you can reference a separate data element if youhave other means of tracking a campaign.

Cookies

Field descriptions for the Cookies global settings used for deploying dynamic tag management in Adobe Analytics.

Property > Edit Tool > Cookies

DescriptionElement

Unique value that represents a customer in both the online and offline systems.Visitor ID

See visitorID.

Variable to identify the domain with which cookies are set.Visitor Namespace

See visitorNamespace.

The domain on which the Analytics cookie s_cc and s_sq are set by determiningthe number of periods in the domain of the page URL. This variable is also usedby some plug-ins in determining the correct domain to set the plug-in's cookie.

Domain Periods

See cookieDomainPeriods.

110Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/referrer.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/campaign.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=visitorid

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=visitorNamespace.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=cookiedomainperiods.html

DescriptionElement

The fpCookieDomainPeriods variable is for cookies set by JavaScript (s_sq, s_cc,plug-ins) that are inherently first-party cookies, even if your implementation usesthe third-party 2o7.net or omtrdc.net domains.

FP Domain Periods

See fpCookieDomainPeriods.

Unique value that represents an online transaction that resulted in offline activity.Transaction ID

See transactionID.

Determines the life span of a cookie.Cookie Lifetime

See cookieLifetime.

Customize Page Code

Use field descriptions in dynamic tag management to customize page code when deploying Analytics.

Add plugins to ensure that the code runs at the same time as the Analytics tool.

Property > Edit Tool > Customize Page Code

DescriptionElement

You can insert any JavaScript call that must be triggered before the final s.t() call, which iscontained in the s_code.

Open Editor

Before UI settings: Interface settings take precedence over the custom code (for example,if you want to override an eVar if a setting in the interface was enabled).

Execute

After UI settings: Custom code takes precedence over interface settings.

FAQ for Adobe Analytics Release - July 24 2014

Dynamic tag management feature information and FAQ for Adobe Analytics released on July 24, 2014.

• New Features• Frequently Asked Questions• Potential Pitfalls

New Features

This release offers several key usability improvements for Adobe Analytics:

Automatic Configuration Method

Enables automatic synchronization of Adobe Analytics report suites via a Marketing Cloud login or Web ServicesID.

Add a Tool > Adobe Analytics

111Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=fpCookieDomainPeriods.html

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=transactionid

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=cookielifetime.html

Frequently Asked Questions

AnswerQuestion

A change to the existing tool. If you currently have an implementation of AdobeAnalytics in dynamic tag management, it will continue to function.

Is this a new Adobe Analytics tool,or a change to the existing tool?

Yes.If I make configuration changes inthe new version of the tool, can I test

All changes can be tested in staging just like you normally would beforedeploying to a production environment. If you choose not to publish, because

in staging before publishing toproduction?

you notice issues in staging, the production code will continue to function asit did before the new integration was released.

No.If I switch from manual configuration(the default setting for existing tools)to automatic configuration, will mycurrent settings be affected?

Any user code that you have specified is overwritten with the baseAppMeasurement library.You must move this code to the new Custom Page

If I switch from manual librarymanagement to Managed by Adobe,

Code section at the end of the tool configuration so that the code continueswill my current settings or code beaffected? executing. This method allows the AppMeasurement library to be managed

(and upgraded) separately from the user's custom code.

Yes.Will the revision history for theAdobe Analytics tool be retained

112Tools

AnswerQuestion

when the new integration isreleased?

Potential Pitfalls

There is a small chance that the new integration could cause data collection issues if you currently use AdobeAnalytics.These issues could arise only if you publish your library to production subsequent to the release. (Productioncode remains intact until publishing occurs.)

To avoid these issues, ensure that:

• Report suite IDs are correctly entered in the tool.• Report suite IDs in the tool match the IDs in the AppMeasurement code.• The currency code, character set, tracking server, and SSL tracking server configuration fields are correctly set

with supported values.• Custom code is defined in Library Management.

Manually implement Adobe Analytics (legacy)

Create an Adobe Analytics tool for deployment using dynamic tag management.This procedure describes a manual(legacy) implementation.

For information about automatic implementation management, see Add Adobe Analytics Tool.

If you want to change a manual configuration to automatic, edit a tool and click Enable Automatic Configuration.

1. Download Analytics measurement code:

a) In Adobe Marketing Cloud, click Reports & Analytics > Admin Tools.b) Click Code Manager.c) Click JavaScript (new) to download the code locally.

2. In dynamic tag management, create a web property.

After you create the web property, it is available for editing on the Web Properties tab on the Dashboard.Activating the web property is not required

3. Add an Adobe Analytics tool to the property:

a) On the Web Properties tab, click the property.b) On the Overview tab, click Add a Tool.c) From the Tool Type menu, select Adobe Analytics.

113Tools

https://marketing.adobe.com/resources/help/en_US/sc/implement/?f=appmeasure_mjs

d) Configure the following fields:

DescriptionElement

The Marketing Cloud solution, such as Analytics, Target, Social, and so on.Tool Type

The name for this tool.This name displays on the Overview tab under InstalledTools.

Tool Name

A number for your production account for data collection. Dynamic tagmanagement automatically installs the correct account in the production andstaging environment.

Production Account ID

A number used in your development or test environment. A staging accountkeeps your testing data separate from production.

Staging Account ID

4. Click Create Tool.

The installed tool displays on the Overview tab.

5. To configure the code, click Settings ( ).

At a minimum, click Cookies and configure your tracking server and SSL tracking server.

6. Click General and insert the core AppMeasurement code.

7. Define a page load rule to collect Analytics data.

114Tools

You are now ready to define rules to collect analytics data.You might want to define a few data elements first.Data elements let you extract data from the page that you can use to configure your rule. To get started, you candefine a page load rule that does not have any conditions to collect Analytics data on each page.

8. Add the header and footer code on the Embed tab.

For staging, you can leave the default Amazon hosting option.You can change it if needed before your productionrollout.

9. (Optional) Click Settings ( ) on the Options tab, and configure the Adobe Analytics code.

Note: The settings on the Adobe Analytics page (General, Cookies, and so on) override settings in yours_code. If these settings exist in your s_code, there is no need to reiterate them here.

Add Adobe Audience Manager Tool

Information about deploying Adobe Audience Manager using dynamic tag management.

<Web Property Name> > Overview > Add a Tool > Adobe Audience Managemer

DescriptionSetting

You can name this instance of audience manager.Tool Name

A unique alphanumeric identifier assigned by audience manager.Partner

You can control where and when to load the page code. The recommendedlocation is selected by default.

Load audience managementpage code at (Page Top or PageBottom)

Prevents dynamic tag management from installing audience manager code if itis already present on your site.This way, you can use dynamic tag managementto add to your existing implementation, rather than starting a new implementation.

Audience management pagecode already present

Select the API code version used by your implementation.Code version

Select the previously configured tool integration that you want to integrate. Ifnone, no integration is configured.

Integrate with

Select the integrations you want to enable. If enabled, you must provide aminimum amount of configuration code.

Modules:

Adobe Analytics

Google Analytics

Use the editor to insert the custom audience manager API code. The trackingcall should be included in the custom code.

Open Editor

Add any notes here regarding this implementation.Add a Note

115Tools

Add Adobe Media Optimizer Tool

Information about deploying Adobe Media Optimizer using dynamic tag management.

<Web Property Name> > Overview > Add a Tool > Adobe Media Optimizer

DescriptionSetting

A descriptive name for this implementation.Tool Name

Your advertising management account has an associated numeric user ID. It isdisplayed in the JavaScript generated for a pixel.

User ID

For example:

1234

Indicate a transaction ID property (ev_transid=<transid>) to include in the tag.When you include the ID, the advertiser must generate a unique value for <transid>

Transaction ID

(for example, an actual order ID) when the transaction is complete. The value ispassed back to advertising management. Advertising management uses thetransaction ID to eliminate duplicate transactions with the same transaction IDand property value.

The transaction ID is included in the Transaction Report in advertisingmanagement, which you can use to validate advertising management data withthe advertiser's data.

If the advertiser's data does not include a unique ID per transaction, MediaOptimizer still generates one, based on transaction time.

The transaction ID cannot contain ampersand symbols (&), which are reservedas parameter separators.

Note: If you use the Media Optimizer combo tracking service, you mustsubmit the transaction ID (ev_transid) for the online part of the transactionin the feed data for offline parts of the transaction.

For more information, see the Tracking section of the advertisingmanagement online help.

Transaction ID can be set globally at the tool level or conditionally at the rule level.A globally configured transaction ID is inherited by any dynamic tag managementrules utilizing the Adobe Media Optimizer tool, unless specifically overridden inthe rule.

Determines where and when the page code loads. The recommended locationis selected by default.

Load Media Optimizer pagecode at (Page Top or PageBottom)

Prevents dynamic tag management from installing advertising management codeif the code exists on your site.This method lets you use dynamic tag management

Media Optimizer page codealready present

116Tools

DescriptionSetting

to add to your existing advertising management implementation, rather thanstarting a new implementation.

A conversion property to be tracked when an end user views a page containingthe conversion tag.

Conversion Property Name /Value

Note: Properties added to this list are not integrated with the client'sTransaction Properties list in the Admin view in advertising management.However, properties are added to the client's Transaction Properties listautomatically, once advertising management actually gathers data for aproperty. Gathering happens when the conversion tag is implemented ona page and an end user completes a transaction that opens that page.

Conversion properties can be set globally at the tool level and conditionally at therule level. A globally configured Conversion Property is inherited by any dynamictag management rules utilizing the Adobe Media Optimizer tool in addition to anyconversion properties set in the rule.

Indicate the numeric ID for an advertising management segment in which to addthe users who complete the tracked transaction. (For JavaScript tags and fordisplay campaigns only)

Segment ID (Optional)

Note: If you associate multiple conversion tags with the same audiencesegment, the segment will include all of the users who complete thosetransaction types.

Segment ID can be set globally at the tool level or conditionally at the rule level.A globally configured Segment ID is inherited by any dynamic tag managementrules utilizing the Adobe Media Optimizer tool, unless specifically overridden inthe rule.

A conversion property name / value to be included in the tag when the specificrule is fired.

Tag Property / Value

Note: Properties added to this list are not integrated with the client'sTransaction Properties list in the Admin view in advertising management.However, properties are added to the client's Transaction Properties listautomatically, once advertising management gathers data for a property.Gathering happens when the conversion tag is implemented on a page andan end user completes a transaction.

Conversion properties can be set globally at the tool level and conditionally at therule level. If a rule uses the Adobe Media Optimizer tool, the configured globalvalue is inherited and used in addition to any conversion properties configured inthe rule.

117Tools

DescriptionSetting

Select the configured data element to populate the SKU value in the tag.SKU

See Data Elements for more information.

SKU can be set globally at the tool level or conditionally at the rule level. If a ruleuses the Adobe Media Optimizer tool and the rule does not specifically set a SKU,the configured global value is inherited and used. If the rule sets a SKU, any globalSKU configuration is overridden in that rule.

Media Optimizer Rule Example

An example of how to enable Adobe Media Optimizer in dynamic tag management for a specific rule when an AdobeMedia Optimizer tool is installed.

In this example, when this rule fires, Adobe Media Optimizer loads and fires a tag including the SKU value for thedata element ecomm_prodid instead of the SKU configured at the tool level. The tag also includes any TransactionID, Segment ID, and Conversion tags configured globally in the installed Adobe Media Optimizer tool.

1. Click Property > Rules > Event Based Rules > Create New Rule.

2. Name and configure the rule condition.

118Tools

Configure the rule so that it fires only in the desired cases. In this example, the rule fires on the click of Add tocart as indicated by the selector div with a class of addtocart.

Note: Adobe Media Optimizer is also available in page load and direct call rules in dynamic tag managementonce an Adobe Media Optimizer tool is installed in the property. See Conditions and Functions for informationabout available rule criteria.

3. Expand Adobe Media Optimizer in the rule.

119Tools

4. Enable Load Adobe Media Optimizer for this rule.

5. Configure the settings you want to apply in this rule.

All of the settings are optional, because global configurations from the installed Adobe Media Optimizer tool areinherited.

Add Adobe Target Tool

Information about creating the Adobe Target tool for deploying Adobe Target in dynamic tag management.You canconfigure the library automatically (recommended) or manually.

<Web Property Name> > Overview > Add a Tool > Adobe Target

120Tools

Field Descriptions - Add a Tool (Adobe Target)

The following table describes the fields and options on the Add a Tool page (and the tool edit page) for AdobeTarget. This table provides information for the automatic and manual configuration settings.

DescriptionSetting

The type of tool, such as Adobe Target.Tool Type

The name for this tool. This name displays on the Overview tab under Installed Tools.Tool Name

Specifies whether Adobe should manage your Adobe Target code automatically, or whetheryou would like to provide your own custom code manually.

Library retrievalmethod

Manual Configuration Method

You can manually manage the Adobe Target code.You can download the at.js or mbox.jsfile from the Target solution interface as follows:

• Target Standard: Setup > Implementation > Download at.js• Target Standard: Setup > Implementation > Download mbox.js• Target Classic: Configuration- > mbox.js > Download

After you download the code locally, copy and paste the code into the editor field in the LibraryManagement section of the tool settings.You also have the option of hosting the code at aspecific URL as an alternative to manually pasting in the code.

Automatic Configuration Method

Note: This works for mbox.js only.

Dynamic tag management automatically retrieves the latest mbox.js code from your AdobeTarget account configuration. If you select Automatic, you must either be logged in via theMarketing Cloud, or you must provide a Client Code value described below.

(Automatic method) A code unique to your Adobe Target account. It is required for your codeto be provided and managed automatically by Adobe. If you chose the Automatic method, you

Client coderetrieval method

must either be logged in via the Marketing Cloud, or provide your Client Code value afterselecting Manual as the retrieval method.

(Automatic method) The Client Code value can be retrieved from the Adobe Target solutioninterface as follows:

Client Code

• Target Classic: Configuration > mbox.js > Edit > copy value for Client.• Target Standard: Setup > Implementation > Download mbox.js > copy value for Client

from within mbox.js file.

Library Management - Adobe Target

Descriptions of the fields and options in the Adobe Target Library Management settings in dynamic tag management.


121Tools

DescriptionElement

This option ensures the at.js or mbox.js code is loaded synchronously inthe <head> section. It is generally recommended that you leave this optionenabled. It is an Adobe Target best practice to load the code in this way.

Load Adobe Target Librarysynchronously

Managed by Adobe:(mbox.js only) This option is equivalent to the Automaticconfiguration method available when creating the tool. This option loads thembox.js code directly from Adobe.

Code Configuration

This feature optimizes the configuration process when using a manual method,because no more copying or pasting from the Adobe Target admin consoleis required.

• You must be logged in via Marketing Cloud or have provided the appropriateClient Code for this option to be available.

• Clicking Check for Updates automatically checks for new versions of thembox.js code within your associated Adobe Target account. If a new versionis identified, you have the option to use it or retain the current version.

Custom: You can manually configure the at.js or mbox.js code. Twomethods are available to manually host the code in dynamic tag management:

• In DTM: Click Edit Code and paste the code in the editor. If you were usingManaged by Adobe and switch to custom, the editor automatically populateswith your mbox.js code.You can replace this with the content of the at.jslibrary.

• At URL: If your at.js or mbox.js is configured as desired, you can providethe URL to the file. Dynamic tag management will consume it for use in theAdobe Target tool.

Global Parameters - Adobe Target

Descriptions of the fields and options in the Global Parameters settings in dynamic tag management for an AdobeTarget Tool.

Global parameters let you pass additional data to the global Adobe Target mbox, and also on a per-page basis viapage load rules.

122Tools

The parameters configured in dynamic tag management do not override parameters already defined on the page,but instead appends and sequences to create maximum flexibility and customization on a per page basis.


DescriptionElement

Indicate the name of the additional parameter(s) you wish to pass to the global mbox.Name

Indicate the value of the additional parameter(s) you want to pass to the global mbox. Thevalue is typically a data element.

Value

Mbox rule example for Dynamic Tag Management

An example of how to place wrapping mboxes with built-in flicker handling via dynamic tag management when anAdobe Target tool is installed.

This functionality currently uses the mboxUpdate method.

1. Click Property > Rules > Page Load Rules > Create New Rule.

2. Name and configure the rule.

Configure the rule so that it fires only on the pages where you want to deploy the mbox.

123Tools

Note: Adobe recommends load rules triggering mboxes at Top of Page to ensure the default content ishidden until the mbox response has been received.

See Rule Conditions and Functions for information about available rule criteria.

3. Expand Adobe Target.

Specify the element to wrap with the mbox using a CSS selector, name the mbox, then configure the timeout ifneeded. (It is generally recommended to leave this at the default 1500 ms).

4. Configure the parameters you want to add to the Target mbox or to the global Target mbox.

In this example, this rule deploys an mbox named Hero that wraps a div element with an id of hero and includesan mbox parameter named Page Name with a value of homepage. It also includes a parameter named Path witha value of home that it passes to the global mbox.

124Tools

Note: You can also use data elements in the parameter UI fields to dynamically populate the value. SeeData Elements for more information on data elements.

Add Google Analytics Tool

Configuration options in dynamic tag management for Google Analytics.

<Web Property Name> > Overview > Add a Tool > Google Analytics

Google Analytics is configured as a tool in the dynamic tag management interface.

DescriptionSetting

The name of this instance of Google Analytics.Tool Name

You can point to production or staging accounts for data collection.Your stagingaccount number is used in your development or test environment. It keeps your testing


Staging Account ID

data separate from production. Dynamic tag management automatically installs thecorrect account in each environment.

Enable if you are a Google Analytics Premium customer.Enable support for GoogleAnalytics Premium features

Check this box to prevent dynamic tag management from installing Google Analyticscode if it is already present on your site. This way, you can use dynamic tag

Google Analytics page codeis already present

management to add to your existing implementation, rather than starting a newimplementation. Ensure that you properly set your tracker name when checking thisbox.

125Tools

DescriptionSetting

Enables or disables tracking based on the EU privacy cookie.Enable EU compliance forGoogle Analytics

When a page is loaded, the system checks to see if a cookie called sat_track isset (or the custom cookie name specified on the Edit Property page). Consider thefollowing information:

• If the cookie does not exist or if the cookie exists and is set to anything but true, theloading of the tool is skipped when this setting is enabled. Meaning, any portion ofa rule that uses the tool will not apply.

If a rule has analytics with EU compliance on and third-party code, and the cookieis set to false, the third-party code still runs. However, the analytics variables will notbe set.


You are responsible for setting the sat_track (or custom named) cookie to false ifa visitor opts out.You can accomplish this using custom code:


You must also have a mechanism to set that cookie to true if you want a visitor to beable to opt in later:


The tracker name you want to use for your Google Analytics installation. If you specifiedthat Google Analytics is already installed on your site's pages, you must use the same

Tracker Name

name here for proper data collection. The default tracker name for Google Analyticsis blank.

There are two ways to host Google Analytics code:Google Analytics Code

• Google Hosted:You can host the code through Google.• URL: Or you can simply provide the URL to the file here. Dynamic tag management

then consumes this code for its implementation of Google Analytics.

To have Google Analytics capture only a sample of your site's data, specify the samplerate. To gather all data, leave 100%.

Sample Defaults - DataSample

You can specify the sample rate for capturing data on site speed and pageperformance. The default is 1%.

Sample Defaults - SiteSpeed

Enables automatic link tracking on the above social buttons on your site.Social - Track Facebooklike, unlike, and share

Enables automatic link tracking on the Twitter button on your site.Social - Track official Twitterbutton use

Force all page views, events, and custom variables sent to GA to be in all lowercaseletters (a best-practice recommendation).

Force lowercase on allpageview, event, andcustom variable calls

126Tools

DescriptionSetting

You can control where and when to load the page code (on a rule-by-rule basis).Load Google Analytics pagecode at Page Top or PageBottom

Automates the tracking of cross-domain property. Google Analytics customers needto implement JavaScript codes for links to different but internal domains, so that cookiesare shared across internal domains.

Global Settings - Enableautomatic linker linktracking

For more information from Google, click here.

Specify the name of the tag you would like to track. Examples: A, IMG, INPUT, DIV,etc.

Element Tag or Selector toINCLUDE

Specify the name of any tags or selectors you do not wish to track.Element Tag or Selector toEXCLUDE

Example: a[target="_blank"]

How much time elapses before Google Analytics expires a session. Default is 30minutes.

Session Cookie Timeout

Control how long a cookie lasts for a visitor to count as a repeat visitor. Default is twoyears.

Visitor Cookie Timeout

You can restrict whether a Google Analytics cookie only functions with a specific folderon your site.

Cookie Path

You can change the default cookie domain. If you specified that your web propertyspans multiple domains or subdomains, dynamic tag management configures thisautomatically.

Cookie Domain

Allows dynamic tag management to recognize values in the URL after the # symbolas URL parameters.

Set # as a query stringdelimiter

If your campaign parameters do not show up in the default variables (like utm_source,etc.), configure them here.

Campaign Keys in URLParameters

Allows you to set campaigns around cookies.Enable campaign trackingfor cookies

Control how long a cookie lasts for a campaign. Default is 30 days.Campaign Cookie Timeout

Create a list of organic keywords that are automatically classified as direct traffic,comma separated. This list is most often used to classify brand searches as direct.Adobe does not recommend this practice.

Classify the followingkeywords as direct

127Tools

https://support.google.com/analytics/answer/1034342?hl=en

DescriptionSetting

Create a list of referral sources that are automatically classified as direct traffic, commaseparated.This is most often used to classify affiliate or in-network searches as direct.Adobe does not recommend this practice.

Classify the followingreferrers as direct

Removes keyword and referrer data from the Google Analytics user cookies set fromyour site.

Clear Keywords & Referrersfrom User Cookies

Use the editor to customize the page code. This code is inserted into every pageimmediately before the call to track the page view. If you want to cancel the initial

Open Editor

default _trackPageview command and write your own to customize page names, besure to "return false;" at the end of the script.

Call Google Analytics Objects in DTM Using Scripts

When you set up a Google Analytics Classic tool, you can choose between using the GA Default Name, DTMGenerated Name, or Specific Name.


• GA Default Name• DTM Generated Name• Specific Name

GA Default Name

When using the GA default name, you can use Google Analytics as follows in a script.

Without trackerName as variable:

_gaq._getAsyncTracker()._trackPageview();

With trackerName:

tracker = _gaq._getAsyncTracker();tracker._trackPageview()

DTM Generated Name

When using the GA DTM generated name, you can use Google analytics as follows in script.

Get the tracker name in DTM Google analytics classic interface:

128Tools


_gaq._getAsyncTracker("ddf16922edc9c2318ea19ad8369fcc92")._trackPageview();

With trackerName:

tracker = _gaq._getAsyncTracker("ddf16922edc9c2318ea19ad8369fcc92");tracker._trackPageview()

Specific Name

When using the specific name option, you can use Google Analytics classic as follows in script.

129Tools


_gaq._getAsyncTracker("alexisclassic")._trackPageview();

With trackerName:

tracker = _gaq._getAsyncTracker("alexisclassic");tracker._trackPageview()

Add Google Universal Analytics Tool

Configuration options in dynamic tag management for Google Universal Analytics.

<Web Property Name> > Overview > Add a Tool > Google Universal Analytics

Google Universal Analytics is configured as a tool in the dynamic tag management interface.

• Add a Tool• General• Cookies• Campaign Tracking• Hit Callback• Customize Page Code

Add a Tool

DescriptionSetting

The name of this instance of Google Analytics.Tool Name

130Tools

DescriptionSetting

Dynamic tag management allows you to point to production and staging accounts fordata collection.Your staging account number will be used in your development or test


Staging Account ID

environment, and will keep your testing data separate from production. Dynamic tagmanagement will automatically install the correct account in each environment.

General

DescriptionElement

Enables the max dimensions and metrics increase from 20 to 200.Enable support for Google UniversalAnalytics Premium features

Prevents dynamic tag management from installing Google Analytics pagecode if it is already present on your site. This feature allows you to use

Google Universal Analytics pagecode is already present

dynamic tag management to add to your existing implementation, rather thanstarting from scratch. Ensure that you properly set your tracker name whenchecking this box.

Enables or disables tracking based on the EU privacy cookie.Enable EU compliance for GoogleUniversal Analytics

When a page is loaded, the system checks to see if a cookie calledsat_track is set (or the custom cookie name specified on the Edit Propertypage). Consider the following information:

• If the cookie does not exist or if the cookie exists and is set to anything buttrue, the loading of the tool is skipped when this setting is enabled. Meaning,any portion of a rule that uses the tool will not apply.

If a rule has analytics with EU compliance on and third-party code, and thecookie is set to false, the third-party code still runs. However, the analyticsvariables will not be set.


You are responsible for setting the sat_track (or custom named) cookieto false if a visitor opts out.You can accomplish this using custom code:


You must also have a mechanism to set that cookie to true if you want avisitor to be able to opt in later:


Ensures that IP addresses are never recorded.Anonymize IP addresses

Forces the use of HTTPS.Force SSL

131Tools

DescriptionElement

The tracker name you want to use for your Google Analytics installation. Ifyou specified that Google Analytics is already installed on your site's pages,

Tracker Name

you must use the same name here for proper data collection. The defaulttracker name for Google Analytics is blank.

There are two ways to host Google Analytics code:Google Analytics Code

• Google Hosted:You can host the code through Google.• URL: Or you can simply provide the URL to the file here. Dynamic tag

management then consumes this code for its implementation of GoogleAnalytics.

To have Google Analytics only capture a sample of your site's data, specifythe sample rate for Data Sample. To gather all data, leave at 100%.

Data Sample

You can also specify the sample rate for capturing data on site speed andpage performance. The Google Analytics default is 1%.

Site Speed Sample

Enables automatic link tracking on the above social buttons on your site.Social - Track Facebook like, unlike,and share

Enables automatic link tracking on the Twitter button on your site.Social - Track official Twitter buttonuse

Force all page views, events, and custom variables sent to GA to be in alllowercase letters (a best-practice recommendation).

Force lowercase on all pageview,event, and custom variable calls

Typically, HTTP referrals come from outside the domain on which youimplemented Google Universal Analytics. Enable this setting if you havemany subdomains and want all URLs to be sent.

Always send HTTP referrer URL

You can control where and when to load the page code (on a rule-by-rulebasis).

Load Google Analytics page code atPage Top or Page Bottom

Automates the tracking of cross-domain property. Google Analytics customersneed to implement JavaScript codes for links to different but internal domains,so that cookies are shared across internal domains.

Global Settings - Enable automaticlinker link tracking

For more information from Google, click here.

Cookies

DescriptionElement

Control how long a cookie lasts for a visitor to count as a repeat visitor.Thedefault value is two years.

Visitor Cookie Timeout

132Tools

https://support.google.com/analytics/answer/1034342?hl=en

DescriptionElement

Name of the cookie used to store analytics data.Cookie Name

You can restrict whether a Google Analytics cookie only functions with aspecific folder on your site.

Cookie Path

You can change the default cookie domain. If you specified that your webproperty spans multiple domains or subdomains, dynamic tag managementconfigures this automatically.

Cookie Domain

This field is used to configure how analytics.js searches for cookiesgenerated by earlier Google Analytics tracking scripts such as ga.js andurchin.js.

Legacy Cookie Domain

Campaign Tracking

If your campaign parameters do not show up in the default variables (like utm_source, etc.) configure those here.

DescriptionElement

Allows dynamic tag management to recognize values inthe URL after the # symbol as URL parameters.

Set # as a query string delimiter

Hit Callback

The code you add here is executed after each hit has successfully been reported to Google Analytics.

DescriptionElement

Use the editor to customize the page code. This code is inserted into every pageimmediately before the call to track the page view. If you want to cancel the initial default

Open Editor

_trackPageview command and write your own to customize page names, be sure to"return false;" at the end of the script.

Customize Page Code

Use Tracker Name field to customize the page code. This code is inserted into every page immediately before thecall to track the page view.

If you want to cancel the initial default pageview command and write your own to customize page names, be sureto "return false;"

Call Google Universal Analytics Objects in DTM Using Scripts

When you create a Google Analytics Universal tool, you can choose between using the GA Default Name, DTMGenerated Name, or Specific Name.


• GA Default Name

133Tools

• DTM Generated Name• Specific Name

GA Default Name

When using the GA default name, you can use Google Analytics Universal as follows in script:

ga('send', 'pageview');

DTM Generated Name

When using the GA DTM generated name, you can use Google Analytics Universal as follows in script.

In this example, the tracker name is pulled from the DTM Google Analytics Universal interface:

For example:

ga('38f91ccf1ca252deaaba3c2fc421f0f3.send', 'pageview');

Specific Name

When using Specific Name, you can use Google Analytics Universal as follows in script.

134Tools

For example:

ga('alexisuniversal.send', 'pageview');

Add Nielsen Tool

You can enable Nielsen tracking using dynamic tag management by creating the Nielsen tool and configuring thepage code either automatically or manually. The automatic method is recommended for most users.

• Prerequisites

• Add the Nielsen Tool

• Set Up Nielsen Rules in Dynamic Tag Management

• Approve and Publish All Changes

Prerequisites

You must perform the following tasks before you deploy the Nielsen tool:

DescriptionTask

You can add header and footer code that determines the loading of JavaScriptand page content on your site.You must install both the header and footercode on every page of your site, regardless of the hosting option used.

1. Embed dynamic tagmanagement on the site (all sitewebpages).

135Tools

DescriptionTask

For more information, see Header and Footer Code.

The Marketing Cloud Visitor ID Service provides a universal visitor ID acrossMarketing Cloud solutions.The visitor ID service replaces the legacy Analytics

2. Add the Marketing Cloud IDService tool.

visitor ID mechanism, and is required by Analytics for Target; video heartbeat;and Marketing Cloud integrations, including the Adobe/Nielsen integration.

For general information about the service, see the Marketing Cloud Visitor IDService Guide.

For information about adding the Marketing Cloud ID Service tool in DTM, seeMarketing Cloud ID Services settings .

You can deploy Adobe Analytics (Standard and Premium) using dynamic tagmanagement by creating the Adobe Analytics tool and configuring the page

3. Add the Adobe Analytics tool.

code either automatically or manually.The automatic method is recommendedfor most users.

For more information, see Add Adobe Analytics Tool.

Add the Nielsen Tool

1. Click Web Property Name > Overview > Add a Tool > Nielsen.


DescriptionElement

The type of tool, such as Nielsen.Tool Type

136Tools

https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid_service.html

https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid_service.html


DescriptionElement

A descriptive name for this tool. This name displays on the Overview tab underInstalled Tools.

Tool Name

Specify the Client ID you obtained from Nielsen.Client ID

Specify the collection server you obtained from Nielsen (secure-us or secure-au,for example).

Collection Server

Automatic: Use dynamic tag management to manage the integration.Integration Method

After the accounts are connected, dynamic tag management pulls the AdobeAnalytics report suite IDs and names into the tool configuration interface, allowingfor increased speed in tool deployment with less possibility for user errors.

Manual: Manually manage the integration.

Note: We strongly suggest that you use the Automatic integration method.

3. Click Create Tool to create the tool and display it for editing.


DescriptionElement

Specify the application's ID that you obtained from Nielsen.Application ID

Specify the application's name that you obtained from Nielsen.Application Name

Specify the collection server you obtained from Nielsen (secure-us or secure-au,for example).The collection server carries over from the information you specifiedabove.

Collection Server

Specify the content group you obtained from Nielsen.Content Group

Specify the VCID you obtained from Nielsen.VCID


Set Up Nielsen Rules in Dynamic Tag Management

Dynamic tag management is a rule-based system. It looks for user interaction and associated data.When the criteriaoutlined in your rules are met, the rule triggers the tool, script, or HTML you identified. For general information, seeRules.

When you add the Nielsen tool, dynamic tag management automatically creates a default Nielsen Time Trackingrule.

137Tools

1. Click the Rules tab > Page Load Rules > Nielsen.

2. Set up the rules as desired by specifying when this page rule should fire.

a. Click Conditions, then specify where the rule fires (bottom of page, top of page, DOM ready, or onload).

b. Specify the criteria for firing the rule.

c. Include the path to the pages on which you want the rule to fire (for example, "videos").

d. Click Nielsen to see a set of pre-populated data elements.

e. Click Data Elements to map where you want dynamic tag management to pull the information in thesepre-populated data elements (Asset Name, Player ID, and so forth).

For example, Asset Name might be pulled from a DIV to which you need to point.

The following topics provide in-depth information:

• Page Load Rules Example

• EnterpriseTV Videos: Page-Load Rules

• Rule Conditions and Functions

• Data Elements

Approve and Publish All Changes

You must approve the changes you made in the previous sections before those changes become effective.

1. Click the Approvals tab > Approve.

Insert third-party tags

Deploy third-party tags from vendors or use your own custom code. The code editor allows for the addition of anycustom script and allows different load options, such as sequential, non-sequential, or HTML/Javascript. As a generalrule, tags that depend on page elements should be defined as sequential tags.

As a general rule, tags that depend on page elements should be defined as sequential tags.

138Tools

1. Click Property > Rules > JavaScript/Third Party Tags.


A text box opens, where you provide the script name and select how you want the script to trigger. (Non-SequentialJavaScript, Non-Sequential HTML, Sequential JavaScript).

3. Paste or type in the content into the text area, then click Save Code.

This step adds the new script into the queue for the rule.

Object References to Handle Cookies

Built-in object references to handle cookies.

Dynamic tag manager has some built-in object references to handle cookies:

• _satellite.readCookie(cookiename)• _satellite.setCookie(cookiename, value, days)• _satellite.removeCookie(cookiename)

139Tools

Data ElementsData elements are the building blocks for rules. Data elements let you create a data dictionary (or data map) ofcommonly used items on a page, regardless of where they originate (query strings, URLs, or cookie values) for anyobject that is contained on your site.You use data elements to build a data layer that can be used for Analytics andother data collection tools.

Rules > Data Elements > Edit.

Use data elements as widely as possible throughout rule creation to consolidate the definition of dynamic data andto improve the efficiency of your tagging process.You define data rules once and then use them many times.

The concept of reusable data elements is very powerful and you should use them as best practice.

For example, if there is a particular way that you reference page names or product IDs, or grab information fromquery string parameters from an affiliate marketing link or from AdWords, and so forth, you can create a data dictionary(data elements) by getting information from various sources and then using this data in various dynamic tagmanagement rules.

Using page name as an example, suppose you use a particular page-name schema by referencing a data layer,document.title element, or a title tag within the website. In dynamic tag management, you can create a dataelement as a single point of reference for that particular point of data.You can then use this data element in anyrule that needs to reference the page name. If for some reason in the future you decide to change the way youreference page name (for example, you have been referencing document.title but you now want to reference aparticular data layer), you don't need to edit many different rules to change that reference.You simply change thereference once in the data element and all rules that reference that data element automatically update.

Data elements are populated with data when they are used in rules or when manually calling in scripts. At a highlevel, you:

1. Create a data element, if you haven't done so already.2. Use the data element in a rule or a custom script.


• Types of Data Elements• Persistence• Built-In Data Elements• Data Element Usage• Data Element Availability• How to Collect Values from JavaScript Variables

Types of Data Elements

The following table describes the types of data elements.

ExampleDescriptionType

window.document.titleAny available JavaScript object or variable canbe referenced using the path field.

JavaScript Object

CSS Selector Chain:Any element value can be retrieved, such asa div or H1 tag.

CSS Selector

id#dc logo img

140Data Elements

ExampleDescriptionType

Get the value of:

src

cookieNameAny available domain cookie can bereferenced in the cookie name field.

Cookie

contentTypeSpecify a single URL parameter in the URLParameter field.

URL Parameter

Only the name section is necessary and anyspecial designators like "?" or "=" should beomitted

var pageType = $('div.page-wrapper').attr('class').split('Custom JavaScript can be entered into the UI

by clicking Open Editor and inserting codeinto the editor window.

Custom Script')[1];if (window.location.pathname ==

A return statement is necessary in the editorwindow in order to indicate what value should

'/'){return 'homepage'; }else{be set as the data element value. If a returnreturn pageType; }statement is not included, the default value or

an empty string will be returned as the dataelement value.

Persistence

Page view • Available only while the page persists.• Can be created and set in scripts using _satellite object syntax:

_satellite.setVar('data_element_name')

Session • Sets a session-level cookie in the browser.• Available throughout the site visit.

Visitor • Sets a 2-year cookie.

Can be manipulated using _satellite cookie methods:Cookie manipulation

• _satellite.setCookie(name,value,days);• _satellite.readCookie(name);• _satellite.removeCookie(name);

Built-In Data Elements

URI • Used in rule: %URI%• Returns document.location.pathname + document.location.search

141Data Elements

Protocol • Used in rule: %protocol%• Returns document.location.protocol

Hostname • Used in rule: %hostname%• Returns document.location.hostname

Data Element Usage

In Rules

You can use data elements in the rule editing interface by using the percent sign (%) syntax. Type a percent signinto the field and you will see a drop-down menu appear with the data elements that you created.

In Custom Script

You can use data elements in custom scripts by using the _satellite object syntax:

_satellite.getVar('data element name');

Data Element Availability

If a data element is not referenced in a rule, it is not loaded on any page unless specifically called in custom script

Forcing Data Element Retrieval through Custom Identifiers

Data elements can be set in the custom code section of a rule identifier to guarantee that the data element is availablefor the rule. This situation is sometimes necessary for specific timing considerations and issues with existingimplementation code.

142Data Elements

For example, entering the following code forces the retrieval of the data element named sample data during the ruleidentification step, prior to any data manipulation that happens in the rest of the rule.

143Data Elements

The custom code section in the identifier must return true, regardless of whether a valid value is available for thedata element. Otherwise, the rule never evaluates as true or runs.

How to Collect Values from JavaScript Variables

When you have JavaScript variables, or object properties in your markup, and you want to collect those values indynamic tag management to use with your analytics tools, or testing tools, or even with third party tags, one way tocapture those values is to use Data Elements in dynamic tag management. This way, you can refer to the DataElement throughout your Rules, and if the source of the data ever changes, you only need to change your referenceto the source (the Data Element) in one place in dynamic tag management.

For example, let's say your markup contains a JavaScript variable called "Page_Name", like this:

<script> //data layer var Page_Name = "Homepage" </script>

When you create the Data Element in dynamic tag management, simply provide the path to that variable like this:

144Data Elements

If you use a data collector object as party of your data layer, simply use dot notation in the Path to reference theobject and property you want to capture into the Data Element, like _myData.pageName, or digitalData.pageName,etc.

Adobe Training Video: Data Elements

Time: 10:28DTM Basics: Data Elements


• Understand what a dataelement is

• Explain the different elementtypes

• Create a data element

• Use a data element in a rule

Create a data element

Create a data element in dynamic tag management.

1. Create a web property.

2. In the web property, click Rules > Data Elements.


4. Complete the following fields and options:

DescriptionOption

The data element friendly name that a marketer can recognize. For example, ProductID.

Name

Note: The name is referenced by the rules builder, not an ID. If you change thename of the Data Element , you must change its reference in every rule that usesit.

Specifies where the data is pulled from, such as JS Object, CSS Selector, Cookie, URLParameter, or Custom Script.

Type

Depending on which type you select, different options display. See Types of Data Elementsfor more information and examples.

A default element. This value ensures that the data element always has a value, even ifa URL parameter does not exist or cannot be found by dynamic tag management.

Default Value

145Data Elements

DescriptionOption

Note: If there is no value and no default value, then nothing is returned. Anyvariable referencing that data element won't get set. Note also that the default valuefield is ignored if it's a "custom code" data element.

Dynamic tag management automatically makes the value lowercased.Force lowercasevalue

How long you want dynamic tag management to remember this value.Remember thisvalue for

Valid values include:

• Session: Session-based timing can vary depending on the implementation. Sessiondata elements are set to the session cookie. However, this setting could be based ona web server or the browser. It is not related to the session used in marketing reports& analytics.

• Pageview

• Visitor

See Data Elements for more information about how to use data elements.


146Data Elements

RulesDynamic tag management is a rule-based system. It looks for user interaction and associated data.When the criteriaoutlined in your rules are met, the rule triggers the tool, script, or HTML you identified.

A rule consists of two parts:

The identifier is what you want the rule to look for. The identifier you specify depends on thetype of rule.

Identifier

Triggers occur after a rule's conditions are met. A rule in dynamic tag management can triggeras many discrete actions as you want.

Trigger

For example, a single rule for an e-commerce Thank You page can trigger your analyticstools and third-party tags from a single rule. There is no need to create separate rules foreach tool or tag.

• Types of Rules• New vs Existing Rules

Types of Rules

There are three types of rules in dynamic tag management as well as several default rules:

DescriptionType of Rule

Events are where the majority of interactions on sites take place.You can measure andreact to these interactions in real-time, without the need for JavaScript.

Event-based

Event-based rules are executed when visitors interact with on-page elements.

By leveraging in-page interactions and page-level tagging, you can optimize based onthings like social media sharing, video interactions, tabbed interfaces, image galleries,and product sorting and filtering.

147Rules

DescriptionType of Rule

See Event-Based Rules Example for an example of how to set your condition to look forclicks on the various tabs on your product pages.

See EnterpriseTV Videos: Event-Based Rules to watch videos about event-based rules.

Let you target by URL, site section, or set up scenarios that are independent of the sitestructure. For example, a page-load rule can load a survey on the fifth page view or inthe seventh minute of a visitor’s session.

Page load

Advanced page-load rules let you, for example, target specific user segments in rules.

See Page Load Rules Example.

See EnterpriseTV Videos: Page-Load Rules to watch videos about page-load rules.

Designed to bypass dynamic tag management event detection and lookup systems.Direct call

Direct call rules are ideal for situations where you want to tell dynamic tag managementexactly what is happening. Also, they are ideal when dynamic tag management cannotdetect an event in the DOM, such as with Adobe Flash.

See Create conditions for direct-call rules for more information and to watch anEnterpriseTV video about direct-call rules.

When you activate a property, dynamic tag management includes several default rules.Default rules

These rules track common interactions with your site and can help you analyzeopportunities throughout your site.

Dynamic tag management includes the following default rules:

• Dead Header: Tracks any clicks on "dead" (i.e. unlinked) header items.• Dead Image: Tracks any clicks on "dead" (i.e. unlinked) images.

• Download Link: Tracks any clicks on downloadable site content.• Email Link: Tracks any clicks on linked emails.• Orientation Changed: Tracks any page orientation change (mobile relevant).• Outbound Link: Tracks any clicks on links driving off site.• Telephone Dial: Tracks any click on a phone number.• Zoom Changed: Tracks any change in page zoom.

New vs Existing Rules

You can create a new rule or add your script to an existing rule.

In each rule, you might notice that the screens look very similar: the Conditions section is listed first, then any InstalledTools, and finally the JavaScript / Third Party Tags section.

The reason the sections are listed in this order is that the Conditions (the visitor scenario being tracked) are the firstthings to think about when planning a new rule or a change to an existing rule.

What is the visitor doing? Where is it happening? When is it happening? If the Conditions are the same, if yourscenario is the same, then you can add as many tool actions or variables, and as many third party tags as you would

148Rules

like to an existing rule, if one exists with the Conditions you need. If you have a different set of Conditions, you needto create another rule.

For example, if you have a new conversion pixel or tag to place on your site, and you have some existing rules,think about the scenario that must occur for the rule to execute. Consider whether you have a rule in your webproperty with the condition you need, to execute the conversion pixel. Suppose that you already have a page-loadrule for your purchase confirmation page, and you are loading three conversion pixels in the JavaScript / Third PartyTags section.You can add your new pixel as a new Script in the same section of that rule, without creating a newrule.

If the Conditions are different, then you need to add a new rule.

Event-Based Rules Example

An example of how you to use event-based rules in click-tracking for a tabbed interface on a product page.

When using event-based rules, it helps to have some knowledge of CSS selectors so that you can identify elementson the page.

The CSS Selector lets you quickly and easily select CSS elements to use as triggers for event-based rules withoutleaving the DTM rule builder. For more information, see Using the CSS Selector.

The following links are useful resources to learn about CSS:

• CSS Selector Pattern Matching Syntax• CSS Selector Reference

Time: 7:02DTM Basics: Event-Based Rules, Part One


• Understand what anevent-based rule is

• Explain the event-based ruletypes

• Create an event-based rule

Time: 5:20DTM Basics: Event-Based Rules, Part Two





149Rules

http://www.w3.org/TR/CSS2/selector.html#pattern-matching

http://docs.webplatform.org/wiki/css/selectors

Time: 7:53DTM Basics: Event-Based Rules, Part Three





Set up how to track this click in Adobe Analytics.

150Rules

If you also have Google Analytics or any other platforms installed, you can leverage the same rule to configure orsend data to as many platforms as you want.

151Rules

When using event-based rules, dynamic tag management offers powerful tools to surface data from the page andpage elements with which the user interacts.

Page Load Rules Example

You can implement rules that trigger during the course of a page load. For example, you can display a survey aftera certain number of page views, or after a specified number of minutes into a session. Page load rules let you targetby URL, site section, or set up scenarios that are independent of the site structure.

Time: 6:02DTM Basics: Page Load Rules, Part One


• Understand what a page loadrule is

• Understand the conditioncriteria options

• Create a page load rule

Time: 7:00DTM Basics: Page Load Rules, Part Two


• Understand what a page loadrule is

152Rules

Time: 7:00DTM Basics: Page Load Rules, Part Two

• Understand the conditioncriteria options

• Create a page load rule

Google AdWords Example

A marketer would like to trigger a Google AdWords conversion tag when a user fills out a form and arrives on thepage http://www.mysite.com/form/thank-you.html

Here is how you can set up this scenario in dynamic tag management:

1. Create a new page load rule.

2. In the rule conditions, specify the page where this rule will be triggered.

3. Paste the tag your vendor gave you directly into the Third-Party Tags section.

Because dynamic tag management does not rely on templates, marketers can use any tag within a rule, even informatted HTML.

153Rules

4. Give your rule a name that describes the user interaction like “Forms: User submits form.”

You can also add descriptive metadata to your rule.

This description will help you and others identify this rule if they want to use it for their tags or tools later.

5. Save your rule, and you are ready to test it in a staging environment, request rule approval, and publish to theproduction site.

Note: By default, page load rules load at page bottom. This setup works for most scenarios. However, if therule you are setting up has some dependency on in page content, it might be better to configure the rule to

154Rules

load on DOM ready. Conversely, if you have other rules that rely on the outcome of the rule in question, loadthe rule at Top of Page or Onload to ensure that it fires first.

Page Load Rules - Advanced

Example showing how to deliver an A/B test to users on iPads.

You may want to target specific user segments in your rules. The following example shows how you can deliver anA/B test to a form, using a segment specific to users on iPads who have been on our site for more than fifteenminutes and came to the site through Google search.

1. Create the conditions.

The following image shows the setting you use for this visitor segment:

2. Set up a test on the form using Adobe Target.

You are not required to modify the page, and there are no mbox containers to place in your markup.

155Rules

3. Click Save, configure your test in Adobe Target and your test is running.

156Rules

Load Order for Rules

The dynamic tag management load order in relation to the JavaScript load order.

The following diagram shows the general page load order.

157Rules

Note: Red text on the above diagram represents non-sequential activity. Green text represents sequentialactivity.

158Rules

The following section discusses how the different JavaScript/third-party tags script options are utilized within thefour page-load phases:

• Top of Page

• Sequential HTML: Injected into <HEAD/> below DTM library include script if <SCRIPT/> tags are used, otherwiseis injected at top of <BODY/>

• Sequential JavaScript global: Injected into <HEAD/> below DTM include script as JavaScript include <SCRIPT/>

• Sequential JavaScript local: Injected into <HEAD/> below DTM include script as JavaScript include <SCRIPT/>

• Non-sequential JavaScript: Injected as asynchronous <SCRIPT/> in <HEAD> below DTM library include script

• Non-sequential HTML: Injected as hidden IFRAME and does not affect page HTML

• Bottom of Page

• Sequential HTML: Injected after _satellite.pageBottom() callback script with document.write() prior toDOMREADY so that there is no destruction of the visible page

• Sequential JavaScript global: Injected after _satellite.pageBottom() as JavaScript include <SCRIPT/>

• Sequential JavaScript local: Injected after _satellite.pageBottom() as JavaScript include <SCRIPT/>



• DOM Ready

• Sequential HTML: Will not work because DOMREADY is active and document.write() will overwrite the page





• Onload (window load)

• Sequential HTML: Will not work because DOMREADY is active and document.write() will overwrite the page





Non-sequential HTML third-party rules are always placed into iFrames. There is no such thing as asynchronousHTML so dynamic tag management refers to the iFrame functionality with that name.

Note: Even though scripts might be injected into the <HEAD/> later in the page processing like DOMREADY andONLOAD, scripts will only appear in the proper timing sequence and be either global, local, synchronous, orasynchronous. Also, dynamic tag management checks to make sure that the timing is being handled properlyand if DOMREADY has already occurred, it will not attempt a page-destructive document.write(). Dynamic tagmanagement is diligent about not breaking the visual page if at all possible. For this reason, you might seean "asyc installation" error when the installation might not actually be "async." It is simply an alert that helps

159Rules

you recognize that the timing on the page is somewhat questionable and that DOMREADY has fired prior to allof the synchronous scripts loading as they should. If that happens, check to make sure that the pageBottom()callback is actually in the correct place immediately prior to the </body> tag. If not then these types of errorscan occur.

The dynamic tag management queue processes them in the order listed above but does not distinguish between aJavaScript and an HTML script within the page load phase.

This means that the order of the page load rules in the queue determines the order in which they are de-queued.

A simple way to determine the queue order is to look at _satellite.configurationSettings.pageLoadRulesin the JavaScript console and examine the sequence.

For example, a complete view of the page load rule queue order can be seen by entering the following code intothe JavaScript console:

_satellite.each(_satellite.configurationSettings.pageLoadRules,function(i){(i.event=='pagetop')?_satellite.notify(i.event+': '+i.name,1):false})_satellite.each(_satellite.configurationSettings.pageLoadRules,function(i){(i.event=='pagebottom')?_satellite.notify(i.event+': '+i.name,1):false})_satellite.each(_satellite.configurationSettings.pageLoadRules,function(i){(i.event=='domready')?_satellite.notify(i.event+': '+i.name,1):false})_satellite.each(_satellite.configurationSettings.pageLoadRules,function(i){(i.event=='windowload')?_satellite.notify(i.event+': '+i.name,1):false})

Create new rule

Steps that describe how to create rules in dynamic tag management.

1. Create a web property, if you haven't done so already.

2. In the web property, click the Rules tab.

3. Select the type of rule you wish to create from the left navigation pane, such as Event Based Rules or Page LoadRules.


5. Name the rule and select a category, if you wish.

6. Next, set up the condition(s) for the rule. The setup differs depending on the type of rule you are implementing.

Refer to this TopicType of Rule

Create conditions for event-based rulesEvent-based rule

Create conditions for page-load rulesPage Load rule

Create conditions for direct-call rulesDirect Call rule

The category field is only for your own organizational purposes and is not required.You can delete categoriesby clicking the x icon in the category.

7. Set up actions for the condition to trigger.

Create conditions for event-based rules

Conditions determine when an event-based rule is triggered.

1. Select the type of interaction you want to track, such as mouse clicks, or submitting a form.

160Rules

For more information, see Event Types.

2. Enable the following options as necessary:

DescriptionElement

Enable if the event activates a link and you want the link to delay until theevent has time to fire.

Delay Link Activation

Applies the event handler to the specific element that is targeted. Thissetting is tied to the bubbling and layering concept in a browser.

Apply event handler directly toelement

For example, when you click an image inside an anchor tag like <a href="abc.html"><imgsrc="xyz.png"/></a>, you might expect the click to be associated with the anchor tag, because the tag is inthe bubble stream. However, when you inspect the click in the developer tools, the click may actually affect onlythe <img> tag. To ensure that the event is handled correctly, associate the click with the <img> tag and do notdepend on the browser to bubble up the click to a parent element. An event like a click can potentially bubble upto <body>. It is important to understand where the event is actually bound, and target it specifically to make surethat the rule fires correctly.

Bubbling means that the event is first captured and handled by the inner most element and then propagated toouter elements.

3. Indicate the name of the tag you want to track, and additional properties the tag has that you want to match.

161Rules

See Using the CSS Selector for information about finding the correct element tag.

4. Select and set up any additional criteria or condition types you wish to bind to the rule.

5. Indicate your preference regarding event bubbling.

Event bubbling is one way of event propagation in HTML DOM.

Check this optionIf you...

Allow events on child elements to bubbleWant related interactions on child elements of the ruleselector you identified to fire the rule.

Do not allow if child element already triggersevent.

Want to prevent bubbling when the child element alreadytriggers its own event.

Do not allow events to bubble upwards toparents

Don't want the events of the rule selector you identified togo beyond the element itself in the event hierarchy

Event Types

List of built-in event types and how each is defined.

162Rules

DefinitionEventCategory

A pointing device button is pressed and released on an element.clickMouse

A pointing device is moved onto the element that has thelistener attached or onto one of its children.

mouseover

A key is pressed and that key normally produces a charactervalue (use input instead).

keypressKeyboard

An element received focus (does not bubble).focusForms

An element lost focus (does not bubble).blur

A form is submitted.submit

An element loses focus and its value changed since gainingfocus.

change

Playback stopped because the end of the media was reached.endedHMTL5 Video

The first frame of the media finished loading.loadeddata

Playback began.play

Playback is paused.pause

The user agent is trying to fetch media data, but data isunexpectedly not forthcoming.

stalled

The volume has changed.volumechange

Emits an event given a specified percentage of total playingtime.

% complete

For example, entering 10% indicates that this rule fires onlywhen 10% of the total length of the video has been played.

Emits an event given a specified duration of playing time.time complete

For example, entering 10 indicates that this rule fires only when10 seconds of the total length of the video has been played.

The orientation of the device (portrait/landscape) has changed.orientationchangeMobile

163Rules


When a pinch or spread gesture is performed on a mobiledevice.

zoomchange

Event is triggered when the content gains focus.tab focusBrowser

Event is triggered when the content loses focus.tab blur

A custom event has been triggered on the DOM.customOther

Select Custom from the Event Type drop-down list, thenspecify the custom event name.

For more information, see CustomEvent on the MozillaDeveloper Network.

When the element first comes into the view of the visitor. If theelement is in view immediately upon page load, the rule fires

enters viewport

immediately. If the element comes in view after scrolling, therule fires then.

An optional delay can be specified in the rule that determineshow long the element has to be in view for before the event istriggered (the default value is 1 second).

When an element of a specified selector comes intoexistence–either because it is in the page markup ordynamically injected later on. Each rule fires only once.

element exists

The URL path or the hash (fragment identifier) at the end ofthe URL changed.

pushState or hashchange

The pushState or hashchange event can be used with SinglePage Apps (SPAs) in which a page does not reload but itscontent changes. Common development frameworks that canbe used to create SPAs include Angular and React.

This event type lets you create event-based rules without relyingon developers. These rules fire when common functions inSPAs occur, such as:

• The URL path changed based on use of the HTML5 HistorypushState API.

For more information about using pushState, see Adding andModifying History Entries on the Mozilla Developer Network.

• The hash changed due to the user changing views or locationson the page.

164Rules

https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent

https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history#Adding_and_modifying_history_entries

https://developer.mozilla.org/en-US/docs/Web/Guide/API/DOM/Manipulating_the_browser_history#Adding_and_modifying_history_entries


For more information about using hashchange, seeHashchange on the Mozilla Developer Network.

Value in seconds. The event is triggered after the specifiednumber of seconds has passed.

time passed

A date element changed. This event lets you select a specificdata element to use as a trigger.

dataelementchanged

For more information on a possible use case, see Add AdobeExperience Manager ContextHub Tool.

Using the CSS Selector

Use the CSS Selector to quickly and easily select CSS elements to use as triggers for event-based rules withoutleaving the DTM rule builder.

One of the biggest advantages of DTM is the ability to event off behaviors or page interactions on your website.However, finding the desired CSS elements to include in your rules is sometimes difficult and time-consuming.


• Example with Unique Element• Example with Similar Elements• CSS Selector Limitations

Example with Unique Element

As an example, we want to create a rule that triggers when users click the "Sign In or Register" link on our website,as shown in the following illustration. This example is simple because the "Sign In or Register" link does not haveany similar elements in the CSS.

165Rules

https://developer.mozilla.org/en-US/docs/Web/Events/hashchange

The more complex example described below illustrates how to use the CSS Selector when there are many similarelements on the page, such as the tabs along the top ("Men's," "Women's," "Equipment," and so forth).

To use the CSS Selector:

1.Access the CSS Selector widget within DTM by clicking the icon while creating a rule.

166Rules

In this example, we are creating an event-based rule that uses the Click event type to trigger the rule when usersclick the "Sign in or Register" link.

2. Specify the website's URL, then click Load.

Note: Be as specific to the web page that you want to event off as possible. Be aware that CSS stylesheets might change from one page to another, depending on your website and its architecture. It is helpfulto experiment to see how often your style sheet changes.

The website is now loaded in an iFrame with the CSS Selector widget embedded. Mouse over different elementsto get a feel for how the tool works.

167Rules

If we were creating this rule without using the CSS Selector, we would inspect the desired page element todetermine the proper CSS to use. Using the CSS Selector, simply click the element on the page that we wantto trigger the rule.

3. Click "Sign In or Register."

When you click a page element that you want the selector to match, it turns green. The CSS Selector thengenerates a minimal CSS selector for that element.

168Rules

Notice the panel at the bottom that contains information about the selected element and a button to send theinformation to DTM.

The number in parenthesis next to Clear indicates the number of items selected. In this example, the "Sign Inor Register" link does not have anything similar to it on the specified page, so "1" displays. Click Clear to removeselected items. Click Toggle Position to move the panel to the top or bottom of the iFrame as desired. Click ?to view help information about the CSS Selector.

4. Click Send to DTM to copy the CSS into the Element Tag or Selector field within DTM.

5. Finish configuring the rule as described in Create conditions for event-based rules.

Without writing any code or inspecting elements, we have created an event-based rule that triggers when usersclick the "Sign In or Register" link.

169Rules

Example with Similar Elements

Now let's suppose that we want to create a rule that triggers when users click the "Men's" tab at the top or ourwebsite. The difference between this example and the simple example discussed above is that the "Men's" tab hasmany similar elements on the page.

1.Access the CSS Selector widget within DTM by clicking the icon while creating a rule.

2. Specify the website's URL, then click Load.

3. Click the "Men's" tab to select it.

Notice that many elements on the page are selected and are highlighted in yellow. The number next to Clear inparenthesis is 28 in this example, which means there are 28 elements on the page that use the "a" tag.

We want to trigger the rule when users click the "Men's" link, so we need to deselect the other similar elements.

Mouse over any similar, highlighted element (for example "Women's) and you'll notice that a red box displaysaround the element.

170Rules

When you click a page element that you want the selector to match, it turns green. The CSS Selector thengenerates a minimal CSS selector for that element. In addition, the selector highlights everything that matchesthat element in yellow. The CSS Selector starts out broad and then lets you narrow your selection.

Click a highlighted element to reject it (red), or click an unhighlighted element to add it (green). Through thisprocess of selection and rejection, you can come up with the perfect CSS selector for your needs. Pressing Shiftwhile moving the mouse lets you select elements inside of other selected elements.

4. Click the element with the red box (Women's) to deselect it and all other similar elements.

Notice that the number in parenthesis next to Clear is now 1.

5. Click Send to DTM to copy the CSS into the Element Tag or Selector field within DTM.

6. Finish configuring the rule as described in Create conditions for event-based rules.

CSS Selector Limitations

The CSS Selector is in Beta and might not work well for some sites due to technical limitations.

Dynamically Populate Variables

You can assign element attributes to variables dynamically.

To dynamically assign element attributes to variables, use the following syntax:

%this.attributeName%

For example, suppose you have a search results page with multiple links to external web sites.You want to trackwhich link is clicked by dynamically populating an eVar with the id of the element clicked.

171Rules

Example Link: <a id='myFirstLink' href='www.exampleLink.com'>

To accomplish this, create an event-based rule to trigger on the click of the links on the page. Then, within theAnalytics section of the rule, set the eVar to %this.id%.

For non-standard attributes, you can similarly leverage the JavaScript function this.getAttribute() by wrapping it in'%' characters, as follows:

%this.getAttribute(attributeName)%

For example, suppose you have a similar search results page as the preceding example shows. However, theselinks contain a non-standard attribute, loc that you want to dynamically set to an eVar based on the link clicked.

Example link: <a id='myFirstLink' loc='top' href='www.exampleLink.com'>

To accomplish this, create an event-based rule to trigger on the click of the links on the page. Then, within theAnalytics section of the rule, set the eVar to %this.get Attribute(loc)%.

If you are unsure if the desired attribute is standard or non-standard, reference w3schools.com to learn more aboutstandard HTML attributes. However, if in doubt, you can use the non-standard getAttribute() format, which will workin either scenario.

This functionality can be utilized in dynamic tag management rule fields, including:

• Analytics Variables

• Custom Script

Analytics Variables

• Adobe Analytics:

172Rules

http://www.w3schools.com/

Link Tracking, Page Data, Hierarchy•

• Global Variables and Events

• Google Analytics

• Pageviews, Events, Custom Variables

Custom Script

Standard attributes can also be referenced using regular JavaScript in custom code.

Create conditions for page-load rules

Create rules that determine on what pages a rule is triggered.

1. Specify where on the page you want the rule to trigger.

The timing of where the rule fires on the page becomes more important when there are dependencies on pagecontent within the rule.

2. Specify for which condition you would like the rule to fire.

For example, you can select Path to identify specific pages for which you want the rule to fire.

173Rules

Create conditions for direct-call rules

Create conditions for direct-call rules.

In the Conditions dialog, specify the string that will be passed to _satellite.track() in your direct call, withoutquotes.

Watch an Adobe training video demonstrating how to set up a direct-call rule in dynamic tag management:

Time: 3:01DTM Basics: Direct Call Rules


• Understand what direct callrules are

• Set up a direct call rule

Note: If you specify the string that will be passed to _satellite.track() in your direct call using the UI,as described above, do not use quotation marks. If you insert customized page code using the editor, youmust use quotation marks.

Set up actions for the condition to trigger

Set up actions that you want the condition to trigger.

After setting up the condition, you must set up the actions that you want the condition to trigger. These actions caninclude Analytics events, third-party tags, and custom scripts. This example describes how to set up scripts orthird-party tags.

Beyond integrated tools like Adobe Analytics and Google Analytics, dynamic tag management can trigger any typeof JavaScript or inject HTML into your site, in select pages or in specific scenarios.

Each rule can trigger as many scripts or HTML injections as you want.

Note: Because DTM allows you to inject custom code into your page, please take care not to create cross-sitescripting (XSS) vulnerabilities (see OWASP’s guide for more info). Using data elements within a script requiresparticular attention. Always assume data element values might come from an untrusted source.

To set up actions for the condition to trigger

174Rules

https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)

1. Click JavaScript / Third Party Tags to add a new script to your rule.


3. Name the script.

4. Specify how you want the script to trigger, and paste the desired content into the text area.

5. Click Save Code, and the script will be added to the queue for the rule.

175Rules

Test unpublished rules for Akamai hosting

Test unpublished rules from your console if you use Akamai hosting.

The Switcher plugin is often the easiest way to test. See Search Discovery Plugins in the Dynamic Tag ManagementProduct Documentation for more information.

1. Access your web console on your site and type localStorage.setItem('sdsat_stagingLibrary',true).

2. Press Enter.

3. Type _satellite.setDebug(true), then press Enter.

4. Refresh the page.

This action loads your staging library and sets the debugger, so that you can see details of all available (published/ unpublished) rules firing on the page.

5. When finished, run localStorage.setItem('sdsat_stagingLibrary', false), then press Enter.

Test rules for Library Download or FTP

If you use library download or FTP delivery, or you do not have a testing environment, you can use a Rewrite toolsuch as Charles to test unpublished rules. This need varies based on your specific implementation.

Rule Conditions and Functions

Describes all dynamic tag management rule conditions and their functions.

Custom Script in a Rule Condition

When using custom code in rule conditions for a page load rule, you must use the boolean return true when youwant the rule to fire.

Conditions and Functions

The following table describes condition types, conditions, functions, and applicable notes:

NotesFunctionConditionCondition Type

Indicate rule to fire on HTTP or HTTPS.ProtocolURL

176Rules

https://marketing.adobe.com/resources/help/en_US/dtm/search_discovery_plugins.html


Enable regex on thiscondition to include

Indicate rule to fire or not fire on specifiedsubdomain(s).

Subdomain

multiple scenarios in asingle condition.


Indicate rule to fire or not fire on specified URLpath(s).

Path


The path conditionfunctions based on the_satellite.data.URI,which is inclusive ofquery params.


Indicate rule to fire if specific URL parameter(s)with specific values are present.

Parameter


Requires data elementsetup.

Indicate rule to fire only if user accepts cookiesbased on presence of sat_track cookie thatis set to 'true'

Cookie Opt-outTechnology

Cookie can be givencustom name on the EditProperty page.

Indicate rule to fire only in specified browsers.Browser

Indicate rule to fire only in specified operatingsystems.

Operating System

Indicate rule to fire only on specified devices.Device Type

Indicate rule to fire within specifiedscreen-resolution ranges.

Screen Resolution

Indicate rule to fire within specified window-sizeranges.

Window Size


Indicate rule to fire if visit came from specifiedsource.

Traffic SourceEngagement


177Rules



Indicate rule to fire if visit landed on specifiedpage(s).

Landing Page


Indicate rule to fire only if new/returning visit.New/Returning Visitor

Indicate rule to fire if visitor has had >, =, or <specified number of sessions.

Sessions

Indicate rule to fire if visitor has had >, =, or <specified number of page views in this sessionor all sessions.

Page Views

Indicate rule to fire if visit persists for specified# of minutes.

Time on Site


Indicate rule to fire based on user registrationstatus as indicated in data element. If theindicated data element has a value, then the

Registered User

condition evaluates as "true" (does not includethe default value).


Indicate rule to fire if user is / is not logged inas indicated in data element. If the indicateddata element has a value, then the condition

Logged In

evaluates as "true" (does not include thedefault value).


Indicate rule to fire if user is / is not a previousconverter as indicated data element. If theindicated data element has a value, then the

Previous Converter

condition evaluates as "true" (does not includethe default value).


Indicate rule to fire if user has certain numberof items in cart as indicated in data element.

Cart Item Quantity


Indicate rule to fire if user has certain dollarvalue in cart as indicated in data element.

Cart Amount


Indicate rule to fire if specified cookie withspecified value is present.

CookieData

178Rules




Indicate rule to fire if specified data elementwith specified value is present.

Data Element Value

Enable regex on thiscondition to includemultiple scenarios in asingle condition.


Indicate rule to fire if specified JS object withspecified value is present. It may be necessary

Variable Set


to prefix the object path with the appropriatescope depending on the scenario - 'this.','event.', 'target.', 'window.', or 'param.'

Opens a blank text box to input custom script.Custom

179Rules

Migrating to Dynamic Tag ManagementDynamic tag management provides several options to migrate from a typical JavaScript implementation or a TagManager implementation.

Analytics - Migrate Using Existing Page Code

Dynamic tag management can use the existing page code you have deployed. It will not deploy any page code tothe site, but you can still go ahead and add rules and expand upon your implementation without having to wait forall of the old code to be removed from the site.

Once the legacy code has been removed, you just uncheck this box and then dynamic tag management will beginto deploy the Analytics page code to your site, allowing you to get the benefits of dynamic tag management rightaway without having to wait.

Configure a Second Instance

Dynamic tag management provides the means for you to have a completely separate Analytics implementation whileleaving your original one intact, allowing you to run them in parallel. To do this, you can simply rename the main sobject for Analytics for the new installation.

Once you rename the Analytics object then you are able to run both implementations: your original one and the onewithin dynamic tag management.

Migrating from Adobe Tag Management

How to migrate from Adobe Tag Manager 1.0 or 2.0 to a new implementation of dynamic tag management.

DescriptionTaskStep

Adobe Tag Manager 1.0 to Dynamic Tag ManagementMapping

Migrate your existing Adobe Tag Managertags to dynamic tag management.

Step 1

Adobe Tag Manager 2.0 to Dynamic Tag ManagementMapping

180Migrating to Dynamic Tag Management

DescriptionTaskStep

In your staging environment, replace your Adobe TagManager page code, then validate your dynamic tagmanagement implementation.

Deploy your dynamic tag managementimplementation to staging.

Step 2

This involves replacing the Adobe Tag Manager pagecode with the header and footer code, and making surethat all changes are published.

Plan and execute your production rollout.Step 3

Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping

How to migrate from each Adobe Tag Manager 1.0 tag to a dynamic tag management tag.

• Custom Core JavaScript• Product Code• Custom Code (after products)

Custom Core JavaScript

Migration InstructionsDynamic TagManagement

Tag Manager 1.0 tag

Custom JavaScript can be deployed directly into the JavaScript /Third Party Tags section of a rule. In most cases, you can paste the

JavaScript / ThirdParty Tag

Custom CoreJavaScript

page code provided by the vendor directly into a tag with no additionalconfiguration.

If any product specific code was included in this section in AdobeTag Management, it will need to be specifically migrated into theapplicable tool in dynamic tag management.

Product Code


Tag Manager 1.0Product Code Tag

Follow the instructions in Add Adobe Analytics Tool to add an AdobeAnalytics tool in dynamic tag management.

Adobe AnalyticsTool

SiteCatalyst

SiteCatalyst > SurveyOption 1

SiteCatalyst > VideoTracking Host code using the Managed by Adobe option. This method

leverages the base version of the AppMeasurement code and allowsyou to choose between the latest available code versions.

SiteCatalyst > GenesisIntegrations




With this option, above this line customization can be configured inthe available interface fields or pasted into the Customize PageCode editor.

Option 2

Manually host the s_code / AppMeasurement file in dynamic tagmanagement. This method is recommended when the current codeis highly customized or if a legacy code version is used.

1. In Adobe Tag Management 1.0, click Edit next to the latestcontainer file.

2. Click Preview to view the generated file.3. Copy all of the above this line code.

This is all of the code beginning with the s_account declaration andending with the first s.setTagContainer command. (Do not includethis s.setTagContainer in this situation). Here is an example:




Paste this code into the Custom editor in the Adobe Analytics tool indynamic tag management.

Then, from the same preview file in ATM, copy the below the linecode. This code begins with:

‘/************* DO NOT ALTER ANYTHING BELOW THIS LINE! **************/’




and ends with the second setTagContainer function. (In this case,include the setTagContainer function, because this code should notbe altered). Ensure the code only in this block is included. Any codeset in the Custom Code (after products) section is included after thiscode block in the preview file, so ensure that only the intended codeblock is included in the copy. For example:




Paste the code into the same Custom editor in dynamic tagmanagement after the above this line code.

Note: Since mistakes can occur with copy / paste, please besure to review the implementation in dynamic tag managementthoroughly and test extensively in staging before publishing toproduction to ensure the expected behavior is accomplished.

Add and configure an audience management tool.Adobe AudienceManager ToolDemdex

Custom Code (after products)


1.0 Custom CodeTag

Create a rule with conditions mimicking the ATM firing rules.Copy all of the code into the JavaScript / Third Party Tags

HTMLHTML

editor in the rule. Select between non-sequential and sequentialHTML as applicable.


JavaScriptJavaScript

editor in the rule. Select between non-sequential and sequentialJavaScript as applicable.

Create a rule with conditions mimicking the ATM firing rules.Copy the image URL from the 1.0 tag into the JavaScript / Third

HTMLImage Beacon

Party Tags editor of the rule. Wrap the image url in <img> tagsand configure as non-sequential or sequential HTML asapplicable.

For example: <img height="1" width="1"style="border-style:none;" alt="" src="imageurl"/>

Create a rule with conditions mimicking the ATM firing rules.Copy the script URL from the 1.0 tag into the JavaScript / Third

HTMLRemote Script

Party Tags editor of the rule. Wrap the script url in script tagsand configure as non-sequential or sequential HTML asapplicable.

For example: <script type="text/javascript"src="scripturl"></script>



1.0 Custom CodeTag

Create a rule with conditions mimicking the ATM firing rules.Copy the iframe URL from the 1.0 tag into the JavaScript / Third

HTMLIFrame

Party Tags editor of the rule. Wrap the iframe url in iframe tagsand configure as non-sequential or sequential HTML asapplicable.

For example: <iframe height="0" width="0"style="display:none;visibility:hidden"

src="iframeurl"></iframe>

Note: If the conditions set in the firing rules are the same between each custom tag, they can be placed intoa single rule in dynamic tag management.

Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping

How to migrate from each Tag Manager 2.0 tag to a dynamic tag management tag.

• Product Code• Custom Code

Product Code


Tag Manager 2.0Product CodeTag

Follow the instructions in Add Adobe Analytics Tool to add an Adobe Analyticstool in dynamic tag management.

Adobe AnalyticsTool

SiteCatalyst

SiteCatalyst >Survey Option 1

SiteCatalyst >Video

Host code using the Managed by Adobe option. This method leverages thebase version of the AppMeasurement code and allows you to choose betweenthe latest available code versions.

SiteCatalyst >Integration Module




With this option, above this line customization can be configured in theavailable interface fields or pasted into the Customize Page Code editor.

Option 2

Manually host the s_code / AppMeasurement file in dynamic tag management.This method is recommended when the current code is highly customized orif a legacy code version is used.

1. In Adobe Tag Management 2.0, click Edit next to the latest container file.2. Click Preview to view the generated file.3. Locate the sitecatalyst JS file and click See content.4. Copy all of the above this line code.

This is all of the code beginning with the s_account declaration and endingwith the first s.setTagContainer command. (Do not include thiss.setTagContainer in this situation). Here is an example:

Paste this code into the Custom editor in the Adobe Analytics tool in dynamictag management.




"Then, from the same preview file in ATM, copy the below this line code. Thisis code begins with:

‘/************* DO NOT ALTER ANYTHING BELOW THIS LINE! **************/’

and continues to the bottom of the file. For example:

Paste the code into the same Custom editor in dynamic tag managementafter the above this line code.

Note: Since mistakes can occur with copy / paste, please be sure toreview the implementation in dynamic tag management thoroughly and




test extensively in staging before publishing to production to ensure theexpected behavior is accomplished.

Configure Add Adobe Target Tool.Adobe TargetToolAdobe Target

Configure Add Adobe Audience Manager Tool.Adobe AudienceManager ToolAudience

Management

Custom Code


2.0 Custom CodeTag


HTMLHTML

editor in the rule. Select between non-sequential and sequentialHTML as applicable.


JavaScriptJavaScript

editor in the rule. Select between non-sequential and sequentialJavaScript as applicable.

Create a rule with conditions mimicking the ATM firing rules.Copy the script URL from the 2.0 tag into the JavaScript / Third

HTMLRemote Script

Party Tags editor of the rule. Wrap the script url in script tagsand configure as non-sequential or sequential HTML asapplicable.

For example: <script type="text/javascript"src="scripturl"></script>

Create a rule with conditions mimicking the ATM firing rules.Copy the iframe URL from the 2.0 tag into the JavaScript / Third

HTMLIFrame

Party Tags editor of the rule. Wrap the iframe url in iframe tagsand configure as non-sequential or sequential HTML asapplicable.

For example: <iframe height="0" width="0"style="display:none;visibility:hidden"

src="iframeurl"></iframe>


Note: If the conditions set in the firing rules are the same between each custom tag, they can be placed intoa single rule in dynamic tag management.


Dynamic Tag Management Object ReferenceA basic object reference for _satellite.

The _satellite object is the essential dynamic tag management (DTM) JavaScript object that is generated by theDTM libraries.

Important: To ensure ongoing success of your implementation, do not configure custom code in your libraryto override any of the _satellite object methods. Only the methods specified below are safe to call directly.Reliance on custom code using other _satellite object methods may put your implementation at risk, asthese methods could be subject to change in future product releases.

_satellite object references that are safe to call directly in custom code:

_satellite.notify()_satellite.track()_satellite.getVar()_satellite.setVar()_satellite.getVisitorId()_satellite.setCookie()_satellite.readCookie()_satellite.removeCookie()_satellite.isLinked()

191Dynamic Tag Management Object Reference

Frequently Asked QuestionsFrequently asked questions about dynamic tag management.

• FAQ - Launch, by Adobe: Covers initial questions about the new version of dynamic tag management.• FAQ - Getting Started: Covers initial questions about your decision to use dynamic tag management.• FAQ - Dynamic Tag Management and the Adobe Marketing Cloud: Covers using dynamic tag management with

the Adobe Marketing Cloud.• FAQ - Advanced: Covers performance, rules, loading, hosting, and so on.• FAQ - Adobe Analytics Tool: Covers questions about the automatic configuration feature of the Adobe Analytics

tool.

FAQ - Getting Started

A FAQ answering common questions about your decision to use dynamic tag management.

AnswerQuestion

See Getting Started.How do I get started?

Dynamic tag management is free.How much does dynamic tag managementcost?

You can create as many Web Properties as you want and write asmany rules as you want.You can also use it to deliver any digital

Are there limitations on my use of dynamictag management?

marketing service, even if you don’t use it to deliver Adobe DigitalMarketing solutions. There is no effective limitation on your use ofthe capability.

The dynamic tag management advantage is the control and flexibilityof using rules. It is also the only market-leading tag management

Why is it an advantage for customers (overcompetitive offerings) to use dynamic tagmanagement from Adobe? solution that supports all of your digital marketing services and is

offered to customers at no additional cost.

Adobe Global Services provides dynamic tag managementimplementation, as do several implementation partners. Contactyour account manager for more information.

Who can help me with my dynamic tagmanagement implementation?

Dynamic tag management will support all of the Marketing Cloudsolutions as well as any digital marketing service, regardless ofvendor.

With which Adobe Marketing Cloud solutionsare dynamic tag management integrated?

Before you can start using dynamic tag management, someone fromyour company must request access. See Requesting Access toDynamic Tag Management.

How do I access dynamic tag managementthrough the Adobe Marketing Cloud?

192Frequently Asked Questions

AnswerQuestion

Make sure that your company has been provisioned to use theMarketing Cloud. See Access the Marketing Cloud in the MarketingCloud Product Documentation.

Why am I getting an "Access Failed" errorwhen I try to access the Marketing Cloud?

You must add an organization to the Marketing CloudOrganizations & Product Access page and set it as the default

How do I assign my account to a Companyname in the Marketing Cloud?

organization.You add an organization if you have access to morethan one company's Marketing Cloud accounts. See Organizationsin the Marketing Cloud Product Documentation.

When you click Join Marketing Cloud, you can step through awizard that helps you link your solution account credentials to your

How do I link my account to an Adobe ID?

Adobe ID.Your Adobe ID becomes your single login for all of theMarketing Cloud solutions and services. See Join the MarketingCloud from a Solution in the Marketing Cloud ProductDocumentation.

For more information, see Link Accounts in the Marketing Cloud inthe Marketing Cloud Product Documentation.

How do I link solutions from within theMarketing Cloud?

No.You can leverage dynamic tag management without touchingany of the existing tags on your site. Just place the embed code and

Do I need to remove my Analytics or othertags from my site to use dynamic tagmanagement? start creating rules. Dynamic tag management can work with existing

services tagged directly to the page.

For web apps (applications that run in the browser or for pages withmany Ajax sequences), DTM provides excellent data collection anddistribution capabilities. See Event Types.

Does dynamic tag management work for appsas well as sites?

For mobile apps, there is a bit of misinformation out there regardingtag management capabilities on mobile devices. The answerdepends on how the mobile application is built and deployed.

DTM is fully compatible with any hybrid mobile apps using a wrapper,such as PhoneGap or Cordova. DTM is also fully compatible withresponsive designs or mobile-optimized sites consisting of HTML,CSS, and JavaScript.

For fully-native, compiled, Objective-C mobile applications whereevery piece of screen content comes from within the compiled code,there is no tag management system available today to adequatelydeal with tagging use cases in those environments. For those cases,Adobe recommends the full power, flexibility, and visitor contextavailable through the Analytics SDK.

If the apps are a hybrid of native code for their screen "shells"(header, footer, & sidebar) and the native app pulls in HTML and


https://marketing.adobe.com/resources/help/en_US/mcloud/access.html

https://marketing.adobe.com/resources/help/en_US/mcloud/organizations.html

https://marketing.adobe.com/resources/help/en_US/mcloud/link_accounts.html



AnswerQuestion

CSS content from the web to display on the mobile device screen,DTM can be useful for the web content.

In other words, the tag management functionality you can use in amobile application depends on how the app was built.

Any third-party tag can be deployed through dynamic tagmanagement. Our top-down, rules-driven approach leverages thosethird-party tags as fuel for power digital marketing use cases.

What third-party tags are supported bydynamic tag management?

Yes, HTML5 is supported.Does dynamic tag management supportHTML5

Dynamic tag management does not yet support fully nativeapplications. It can handle an application if it has an in-applicationbrowser or is essentially a website wrapped in an app container.Properties for the mobile and desktop sites should be able to be setup as normal.

See Browser Support.Which browser versions does DTM support?

FAQ - Dynamic Tag Management and the Adobe Marketing Cloud

A FAQ about using dynamic tag management with the Adobe Marketing Cloud.

AnswerQuestion

Dynamic tag management will support all of the Marketing Cloudsolutions as well as any digital marketing service, regardless ofvendor.

With which Adobe Marketing Cloud solutionsare dynamic tag management integrated?

Before you can start using dynamic tag management, someone fromyour company must request access. See Requesting Access toDynamic Tag Management.

How do I access dynamic tag managementthrough the Adobe Marketing Cloud?

Make sure that your company has been provisioned to use theMarketing Cloud. See Access the Marketing Cloud in the MarketingCloud Product Documentation.

Why am I getting an "Access Failed" errorwhen I try to access the Marketing Cloud?

You must add an organization to the Marketing CloudOrganizations & Product Access page and set it as the default

How do I assign my account to a Companyname in the Marketing Cloud?

organization.You add an organization if you have access to morethan one company's Marketing Cloud accounts. See Organizationsin the Marketing Cloud Product Documentation.

When you click Join Marketing Cloud, you can step through awizard that helps you link your solution account credentials to your

How do I link my account to an Adobe ID?


https://marketing.adobe.com/resources/help/en_US/mcloud/access.html

https://marketing.adobe.com/resources/help/en_US/mcloud/organizations.html

AnswerQuestion

Adobe ID.Your Adobe ID becomes your single login for all of theMarketing Cloud solutions and services. See Join the MarketingCloud from a Solution in the Marketing Cloud ProductDocumentation.

For more information, see Link Accounts in the Marketing Cloud inthe Marketing Cloud Product Documentation.

How do I link solutions from within theMarketing Cloud?

See Marketing Cloud ID Services.How do I provision the Adobe Marketing CloudID service using DTM?

For more information about troubleshooting issues that arise fromaccount linking, see Troubleshooting Account Linking in theMarketing Cloud Product Documentation.

How do I troubleshoot my account accesswhen it is linked to the Marketing Cloud IDService.

Contact Customer Care to get the required information and to getstarted.

How do I implement Adobe ExperienceManager (AEM) using DTM?

FAQ - Advanced

A FAQ about performance, rules, loading, hosting, and so on.

AnswerQuestion

You can create and configure an Adobe Analytics tool automaticallyor manually. For more information about a manual (legacy)implementation, see Manually implement Adobe Analytics (legacy).

Can I manually implement s_Code throughdynamic tag management?

Yes.Can I use dynamic tag management on pageswith content type application/xhtml+xmlor text + xhtml?

The only potential issue is the use of document.write, becausecontent type text + xhtml does not support document.write.However, this issue can be avoided because document.write isused by dynamic tag management only in the situations statedbelow.

• Loading of the staging library using the dynamic tag managementswitch plugin uses document.write.

Workaround: Test in the staging environment by specificallyreferencing the staging library in the page code instead of usingthe dynamic tag management switch plugin to toggle betweenlibraries.

• Synchronously loading JS and HTML scripts via dynamic tagmanagement uses document.write.







AnswerQuestion

Workaround: The synchronous loading of scripts via dynamic tagmanagement cannot avoid document.write. Thus, when thiscontent type is being used, all third-party scripts (JS and HTML)should be loaded asynchronously in dynamic tag management toavoid document.write. Please always consider and test all codedependencies to ensure the desired behavior is still accomplishedwith asynchronous loading.

Dynamic tag management has never shown signs of negativelyaffecting page load time or execution speed.

Will dynamic tag management reduce mywebsite's performance?

However, because dynamic tag management can be used as adelivery system (a way to deliver JavaScript, HTML, images, orother Web content), if you load a large file, or a large image at thewrong point during render time, you can slow down page load speedand increase code execution time on that page. If you lazy loadimages, and if you use asynchronous (non-sequential) scripts asmuch as possible, and you follow best practices regarding the codeyou add into dynamic tag management, you should not see negativeperformance impacts.

The Embed code should be hard-coded in the <head> section ofyour templates. This is a synchronous JavaScript include. Thedynamic tag management engine is designed to work in a modularway, so scripts that do not apply to a particular page, site section,or domain will not load or execute when they are not needed. Mostusers increase the use of asynchronous (non-sequential) methodswhen deploying third-party scripts. This generally improves theperceived page load speed for site visitors. While the dynamic tagmanagement main library file itself is loaded synchronously, mostclients load any code from within dynamic tag management usingthe built-in asynchronous methods.

Adobe recommends using the rule Name, the Tag Name, and theCategories to label your rules in a way that helps you find things

How do I remember which tags are in whichrules? How do I keep track of my tags andmake it easier to find certain rules? faster later on, when you need to come back and change a rule, or

group of rules.

For example, because different Page Load and Event Based rulesrespond to different Conditions, it might make sense to add anindicator about the Conditions in the rule Name, like “Global PageLoad."

When working with Third Party Tags or custom JavaScript, you canadd information into the Tag Name field. Later, when you are lookingfor all the rules with a certain tag, you can filter the list of rules byTag Name to find all rules containing that tag.


AnswerQuestion

Finally, each rule can be labeled with a Category and a value. TheCategory is also available when filtering your list of rules, so youcan easily and quickly find the list of rules in a certain Category. Forexample, using a Category like “3rd Party” with a value of“DoubleClick” lets you search for all rules in the “3rd Party” Category,or all rules with the value of “DoubleClick”.

Adobe recommends the use of tag event callbacks provided byamc.on to wrap any code that depends on tags delivered by anytag management system.

Does dynamic tag management have featuresthat help avoid errors due to asynchronoustag loading or rare cases of CDNunavailability?

See amc.on Tag Event Callbacks.

Adobe offers two options for self-hosting the library files: FTPDelivery and Library Download. When you choose one of these

Can the dynamic tag management library fileswork with the version control system we useat my company? self-hosted options for the library, each time you make changes in

dynamic tag management, those changes are written out by thesystem to the library files. Those files are typically then "pushed" or"pulled" to your architecture automatically. Once the updated librarycode is on your servers, you can add the files to your version controlsystems and processes however you like. If you use GitHub, SVN,or some other system to manage your web development code orcontent, that works fine with dynamic tag management.

One note on version control: Ensure you do not overwrite theproduction version of the Embed code with the staging version ofthe Embed code when you commit and push code to production.The staging version of the Embed code has to stay in the staging(non-production, test, dev, QA, UAT, etc.) environment templates.The production version of the embed code has to stay in theproduction templates.

Currently, dynamic tag management can be used in any digitalexperience created with HTML, CSS, and JavaScript. This includes

Can I use dynamic tag management with ourmobile applications?

any mobile-optimized content or responsive designs. This alsoincludes mobile applications created with wrappers like Cordova orPhoneGap.

Unfortunately, at this time, dynamic tag management does not offera separate SDK for use with completely native, compiledapplications.You can still track your mobile applications using theAdobe Analytics SDK. Dynamic tag management can also be presenton HTML documents pulled into your mobile app when desktop orresponsive content is accessed within the native app experience,like in hybrid or crossover content situations.


https://marketing.adobe.com/resources/help/en_US/sc/implement/tm_amc_on.html

AnswerQuestion

There are a number of ways to set s.pageName for each page,without creating a separate dynamic tag management Page Load

How do I set s.pageName without creating aseparate rule for each of my web pages?

rule for each page. In dynamic tag management, the conditions foryour rules answer questions like: What’s the visitor doing? Whereare they doing it? When is it happening? You can set any numberof variables, trigger different tags or tools, and execute any numberof scripts from within the same rule, as long as you want all thosethings to happen in response to the same conditions.

For example, if you want document.title to be the source forthe value of the s.pageName variable, you could create a DataElement with a name of Page Name, a Type of JS Object, a Pathof document.title, a Default Value of None, and Remember thisvalue for Pageview.

Then, you could create a global Page Load rule and assign thatData Element to s.pageName, either in the interface, or in theCustom Editor code window. It will then be dynamically populatedwith the value of document.title for each page that meets yourconditions.

Dynamic tag management creates and uses various JavaScript filesthat contain all the code needed to run the system. These “library

How do I choose a hosting option?

files” can be hosted by Adobe, or they can be hosted on your ownservers, within your own Web architecture. Hosting options are:

• Akamai• FTP delivery• Library download

You can use one or more of these hosting options for a WebProperty. Do not use more than one Embed code in any single page.For example, you could use Akamai in your staging environments,and one of the self-hosted options in your production environments.Or, you could use the Akamai option for any sites, domains, orsubdomains hosted by one of your agency partners. These optionsgive you more flexibility to host the library files according to yourspecific needs.

See Hosting Considerations (FAQ).

Dynamic tag management is a way to get JavaScript and HTML toyour pages. It sends data only to the systems, tools, or tags that

Does the dynamic tag management code sendany information back to Adobe?

you specifically choose when using the system. In other words,dynamic tag management does not send any data anywhere, unlessyou specifically tell it what data should be collected, and then tell itwhen, where, and how it should be sent to any systems, tools, ortags.


AnswerQuestion

You have control over the specific data points that only get sent tothe places and technologies you designate.

See Separating the DTM Environment for Multiple Entities.How do I handle multiple geo markets,business units, and subdomains?

Navigate to a page where the data element should be available onyour site. Open your web console and type in

My data element setup does not seem to beworking. How do I test it?

_satellite.getVar(‘dataelementname’) and press enter. Thisaction returns any value that is present for the noted data elementon that page. If the value is undefined, the data element is likelysetup incorrectly. If the value is null, then that data element may nothave a value on that particular page.

DTM Switch is a browser plugin for easy switching between debugmode and staging mode for dynamic tag management users. It is

How can I tell if my site is in a live or stagingenvironment?

available for both Google Chrome and Mozilla Firefox. See DynamicTag Management Plugins.

FAQ - Adobe Analytics Tool

A FAQ about the automatic configuration of the Adobe Analytics deployment. The automatic configuration methodmanages the AppMeasurement code for you.

AnswerQuestion

If using DTM to manually host the s_code, plugins can be added in the sameeditor as the hosted s_code, just as it would be in a typical Adobe Analyticsimplementation.

Where do I put my plugins whenimplementing Adobe Analytics viaDTM?

However, it is also an option to place the plugins in the editor within theCustomize Page Code section of the tool settings. Both implementationmethods should be equally effective.

See DTM Switch Plugins.

Yes.If I make configuration changes inthe new version of the tool, can I test

All changes can be tested in staging just like you normally would beforedeploying to a production environment. If you choose not to publish, because

in staging before publishing toproduction?

you notice issues in staging, the production code will continue to function asit did before the new integration was released.

No.If I switch from manual configuration(the default setting for existing tools)to automatic configuration, will mycurrent settings be affected?


http://help-forums.adobe.com/content/adobeforums/en/marketing-cloud-forum/adobe-marketing-cloud.topic.html/forum__lkzf-_dtm_switchdt.html

AnswerQuestion

Any user code that you have specified is overwritten with the baseAppMeasurement library.You must move this code to the new Custom Page

If I switch from manual librarymanagement to Managed by Adobe,

Code section at the end of the tool configuration so that the code continueswill my current settings or code beaffected? executing. This method allows the AppMeasurement library to be managed

(and upgraded) separately from the user's custom code.

Yes.Will the revision history for theAdobe Analytics tool be retainedwhen the new integration isreleased?

See the Persistence section in Data Elements.How do I configure persistence fora data element?

See Add Adobe Analytics Tool for configuration information.

FAQ - Launch, by Adobe

A FAQ about the new version of dynamic tag management, announced in March 2017.

AnswerQuestion

Launch is the next-generation of the Adobe tag-management capability, builtinto the Adobe Cloud Platform. Launch enables clients to:

What is Launch?

• Deploy client-side web products using integrations called extensions

• Consistently capture, define, manage, and share data between marketingand advertising products from other vendors and from Adobe

Launch is an advanced JavaScript delivery system that evaluates conditionsand executed actions to efficiently and effectively deploy client-side librariesand products. It provides a highly scalable approach to managing and buildingextensions, together with a robust set of APIs for programmatic interactionwith the Adobe Cloud Platform.

For more frequently asked questions about Launch, see Adobe CloudPlatform Launch FAQ.

How Do Tag Management Systems Improve Page Load Speed?

Information about effective solutions to the issues affecting page load speed.

Adobe dynamic tag management provides a number of effective solutions to the issues affecting page load speed.Dynamic tag management approaches the page differently from most other solutions, by providing conditional logicin its core library file that delivers file assets only when needed. In addition to a focus on scenario-based logic andprecise activation of vendor technologies, dynamic tag management provides a series of features that dramaticallyimprove page speed. These include:


• Self-hosted static file delivery that eliminates the dependency on third-party hosting and DNS• Parallelization of tag loading through asynchronous delivery• Tag killing options with timeouts that can be modified by the client• Dramatically reduced file size through the optimized dynamic tag management library schema - over 90% smaller

than competitors• Enhanced file compression and delivery• Optimized timing and delivery sequencing that can be modified by the client• Client-side delivery of file assets that eliminates any additional server-side processing

Each tag management system (TMS) vendor must deal with the challenges of page load speed and Adobe dynamictag management provides the best set of options that can be assembled to meet these challenges. There are alsoa number of guiding questions that should be answered when evaluating page load speed and TMS options.

Page Load Speed

There are essentially six areas that affect page load speed:

1. Caching of site assets2. Creating site pages from the server3. Reducing the number of downloaded files4. Reducing the size of downloaded files5. Improving the connection speed to source files6. Converting sequential file loading to parallel file loading

The caching of site assets occurs at the browser level and is not something that TMS vendors can directly address.The same is true of the time that it takes for servers to create site pages and prepare them for delivery. Both of theseareas can increase and decrease the time that it takes for a page to load. Because TMS vendors cannot directlyaddress the first two page load issues, this overview focuses on the remaining four areas.

All major TMS options attempt to reduce the number of downloaded files and also optimize their size. The approachthat each TMS takes to accomplish those tasks might vary somewhat, but in the end they each provide someimprovement to the final file weight that is delivered to the page.When evaluating a TMS it is important to understandthe architecture involved in the packaging and deployment of the individual files to the client web browser.

• Are the files assembled server-side on each request or delivered from pre-published static files?• If files are assembled dynamically, how long does file assembly take for each request?• Is there a server-side-only management of a portion of the files, and if so, what are the limitations of that architecture?• What compression techniques are used in the generation of the files?• Are optimizations provided in the TMS file generation that might help mitigate browser errors?

In the final analysis, each major TMS vendor reduces the number of downloaded files and optimizes the file sizewith some degree of success.

The areas where TMS solutions can see appreciable speed differences on the page are in the areas of connectionspeed and file loading. All of the major TMS offerings provide the option of a globally distributed CDN to deliver theirfiles. Hosting files on any infrastructure is also available as an option when using Adobe dynamic tag management.In most cases a CDN provides an efficient means to deliver the TMS files. However, there are several cautionaryquestions that must be answered relating to the hosting methodology that is provided by the TMS.

• What happens if the host CDN or regional DNS service fails?

A number of enterprise-level failures have occurred in these areas during critical delivery times for some TMSvendors. Self-hosting of TMS assets prevents this situation from occurring because the files are delivered alongwith the rest of the client-hosted website assets either on their own architecture or an architecture of their choice.


• What are the response times for file retrieval?• Are international response times significantly different for regional visitors?• How responsive are the vendors of the third-party code that the TMS manages like Facebook, Google, Foresee,

etc.?

Each of these third-party connections can cause delays even if the TMS files are delivered quickly. Does the TMShave client-adjustable tag timeouts that mitigate vendor delays?

File loading also has an effect on page speed, but more specifically, on the user experience.The use of asynchronoustag loading, conditional logic that determines what file assets will be delivered, and the placement of timeouts ontags provide ways to parallelize tag behavior and improve the loading of the page. Although the final tag weight maynot be significantly different at the end of the page load, moving third-party vendor tags from a synchronous toasynchronous load allows multiple assets to load in parallel rather than one at a time. How much flexibility does theTMS provide regarding the timing and sequencing of vendor code? Does the TMS vendor provide best practicesfor optimizing page performance in relationship to file loading? Can third-party vendor code be easily changed fromsynchronous to asynchronous loading and vice-versa?

Adobe dynamic tag management excels in each of these four page speed areas and, in certain cases like hosting,provides a better solution than other vendors. However, page load speed is only one area that needs to be addressedwhen evaluating a TMS. Critical questions need to be answered regarding workflow and governance, rule deploymentmethodologies, the user interface, implementation, migration, maintenance, and user segmentation capabilities.These are areas that make Adobe dynamic tag management stand out as a system with a proven performancerecord that clients enjoy using over the long-term.

Adobe Cloud Platform Launch FAQ

Frequently asked questions about dynamic tag management.

A FAQ about the new version of dynamic tag management, announced in March 2017.

AnswerQuestion

Launch is the next-generation of the Adobe tag-management capability, builtinto the Adobe Cloud Platform. Launch enables clients to:

What is Launch?

• Deploy client-side web products using integrations called extensions

• Consistently capture, define, manage, and share data between marketingand advertising products from other vendors and from Adobe

Launch is an advanced JavaScript delivery system that evaluates conditionsand executed actions to efficiently and effectively deploy client-side librariesand products. It provides a highly scalable approach to managing and buildingextensions, together with a robust set of APIs for programmatic interactionwith the Adobe Cloud Platform.

Launch began a rolling release to production on November 7, 2017. Thismeans that Launch will be released to customers incrementally over the

When will Launch be released?

course of a few months. Customers who wish to gain access to Launch mayindicate their interest by providing their Company Name, Org ID, and a contactemail address in the Launch Release Form. Every two weeks, Adobe will


https://adobe.allegiancetech.com/cgi-bin/qwebcorporate.dll?WVFJ3K

AnswerQuestion

randomly select a number of these customers who will then be given accessand receive a single email notification of their access.

No. Launch is an entirely new product with a new code base. The systemhas been re-architected from scratch using modern front-end development

Is Launch just an updated DTM?

practices and an API-first approach. Everything is built on a robust set ofAPIs, which makes the system very powerful and highly flexible.

Yes, legacy DTM (the existing production version) will continue to besupported for the foreseeable future. Adobe will continue to fix any significant

Will the current DTM product remainavailable?

bugs and ensure consistent performance. At this time, no major featureenhancements are planned for legacy DTM.

The Launch team is working to make the migration process from legacy DTMto Launch as easy as possible so customers can take advantage of morethan twenty new features, extensions, and APIs that Launch provides.

There is no additional charge for Launch. It will be available for any AdobeExperience Cloud customer.

How much will Launch cost?

No, you won't have to change your Staging or Production embed codes ifyou're currently using the existing (legacy) DTM system.You can continue

Will I have to change the embedcodes in my current DTMimplementation? to work in your current DTM Company and Web Properties without worrying

at all about changing those embed codes.The product team has not finalizedthe migration process just yet, but they are working to make it as easy andautomated as possible.

Launch is built into the Adobe Cloud Platform and it is fully extensible.Customers, Adobe Partners, agencies, and marketing or advertising

I heard there are plug-ins now.What's that about?

technology vendors will soon be able to build Launch extensions that addnew functionality or modify existing functionality.The system allows partnersand clients to build, manage, and update their own integrations. This is justone way Adobe is opening up the Adobe Cloud Platform so customers andpartners can build products and businesses on the Platform, and so everyonecan more easily connect Adobe technology to the marketing and advertisingtechnologies from other vendors. Over time, this will be the place forcustomers to install and configure all of their client-side technologies.

Extensions will be available for all Adobe solutions and for a select group ofindependent vendors when Launch is released.The product team is working

Will all third-party tools be availableright away?

closely with several technology partners to ensure the availability of theseextensions upon release. After that initial release of Launch, the productteam will work to expand the number of extensions as quickly as possible.Because extensions can be built, managed, and updated by the Extension


AnswerQuestion

developer, vendors won't have to wait for Adobe engineering to build them,so this should be a very rapid process going forward.

After general availability, Launch will open its virtually self-service portal thatextension developers can use to build their own integrations with the AdobeCloud Platform.

When will clients or partners be ableto build extensions?

Yes. Launch is SOC-2 and Gramm-Leach-Bliley Act ready. Launch alsooffers the capability of being self-hosted. The JavaScript libraries can be

Will Launch meet my company'ssecurity standards?

served from your own servers, or the CDN of your choice. For I.T. and securityteams, this gives you the ability to run automated testing, to check the filesinto your own version control system, and to fully comply with any internalproduction migration processes, security-related or otherwise.

If you are already using legacy DTM, or are currently deploying DTM, youshould continue to do so. Don't wait. Move your projects forward using the

I have a project coming up very soon.Should I wait for Launch?

current DTM. Then, when you're ready to move to Launch, the migrationprocess will make it as easy and automated as possible (no on-page embedcode changes, and automated migration of Rules and Data Elements).

Launch will offer four major capabilities that aren't comparable to legacyDTM:

Which capabilities exist in Launchthat don't exist in legacy DTM?

• Deploy non-Adobe client-side browser technologies quickly and easily

Using extensions, clients and partners can easily control in-browsertechnologies in the interface, without managing custom code.

• Enterprise-grade publishing

Compartmentalize and control each piece of your libraries to deploy preciselywhat you need, where you need it, and when you need it.

• Robust approval workflows

Flexible approval workflows allow custom processes to match your existinginternal approval processes.

• Granular rights management

Administrators will designate which extensions users can, and can't use.They will also control which areas within Launch are accessible to certainusers.

Yes. Launch has capabilities to give users and extension developers flexibilityin collecting, managing, and distributing data within single page application

Does Launch support single pageapps and my favorite framework?

experiences or Ajax-heavy pages or sites. This applies regardless of yourdevelopment framework preferences, whether that's Angular, React.js, Ember,Meteor, etc.


AnswerQuestion

Yes. Launch includes an extension that specializes in listening for changesin dynamic data layers.

Does Launch support dynamic datalayers?

Event types are available through extensions.The pre-loaded DTM extensionincludes 30 built-in event types. Other extensions could add additional event

Which event types does Launchsupport?

types. For example, the YouTube extension includes four video event types:play, pause, end, and time played. Through extensions, Launch can supportany other browser event types or synthetic event types, such as specificvisitor activity sequences.

Launch is designed to deliver and run marketing and advertising technologieson your web site as efficiently as possible using today's best practices.When

Will the new Launch speed up (orslow down) my web site?

used properly, Launch has proven to improve performance of web sites overalternative methods of providing similar functionality.

Browser support in the Launch client-side libraries:Which browsers will Launch support?

• Chrome (latest)

• Safari (latest)

• Firefox (latest)

• Internet Explorer (9 and above)

• iOS Safari (latest)

• Android Chrome (latest)

Browser support in the Launch application interface:

• Chrome (latest)

• Safari (latest)

• Firefox (latest)

• Internet Explorer (11 and above)

Legacy DTM supported older versions of Internet Explorer, but over the lastfew years, the percentage of overall web users with older, outdated browsershas dropped to a small segment for our clients. Most Adobe clients nowleverage more modern web platform features in current browsers and createbetter user experiences, including single page applications and interactiveAjax-heavy web sites and pages. As most clients move to more modernapproaches with their sites, they demand a solution like Launch that enablesthose approaches.

Adobe continues to recommend the Mobile Services App SDK to implementdata collection and delivery in a native mobile app environment. With Adobe

Does the new Launch work on nativemobile apps?

mobile services, the process is streamlined with a single SDK that workswith multiple Adobe Cloud Platform solutions. Going forward, you will seeadditional tag management-like functionality in the Mobile Services interface


http://www.adobe.com/solutions/digital-marketing/mobile-services/app-sdk.html

AnswerQuestion

as the Launch and Mobile teams continue working closely together for moreseamless Cloud Platform access and user experiences.

These are the questions we've received most often from customers andpartners since the Launch announcement. If you have other questions, please

What if I have other questions?

ask in the Adobe Community on the main Launch page located athttps://adobe.com/go/launchme.

Launch is just one example of where our platform is headed: more open,more integrated and as always dedicated to customer success.


https://adobe.com/go/launchme

ResourcesAdditional resources to help you get the most out of Dynamic Tag Management.

Additional resources will be added to this list in the future.

DetailsResource

This post on the Digital Data Tactics blog is a great resource when using DTM onSingle Page Apps (SPAs)

How do I use DTM for aSingle Page App?

Digital Data Tactics contains additional posts about DTM and other Adobe MarketingCloud Solutions.

207Resources

http://www.digitaldatatactics.com/index.php/2016/04/20/how-do-i-use-dtm-for-a-single-page-app/

http://www.digitaldatatactics.com/index.php/2016/04/20/how-do-i-use-dtm-for-a-single-page-app/

http://www.digitaldatatactics.com

TroubleshootingDescribes several troubleshooting scenarios and their solutions and provides a list of Frequently Asked Questions(FAQ).


• View the Administrator Audit Log

• Implementation Issues

• Rule Issues

• Tool Issues

View the Administrator Audit Log

In addition to the specific troubleshooting categories listed below, company administrators can view, filter, and exporta list of all activities that take place within companies and web properties to which they have access. This featureis helpful both for auditing and troubleshooting purposes.

Click Log in the left-hand rail to display the audit log.

For example, you can view and filter by:

• Successful logins

• Account names

• IP addresses

• Companies

• Web properties (and see who created them and when)

• Roles

You can also export the log data to .csv.

Implementation Issues

I see a JavaScript error in my console when I load dynamic tag management.

There’s likely an issue with your dynamic tag management installation. To view the current installation, right clickon any page of the site and click View page source. Then type CTRL+F to open the search box and type satellite.This locates the embed snippets of dynamic tag manager. There should be two instances of these snippets on thepage. The first should be right before the </head> tag. The second should be right before the </body> tag.

Example of Header script:

<script src=“//assets.adobedtm.com/aaaabbbcccddddeeee1111222233344445555666/satelliteLib-aaaabbbcccddddeeee1111222233344445555666.js”></script></head>

Example of Footer script:

<script type="text/javascript">_satellite.pageBottom();</script></body>

I get this error: Unexpected token: operator (<) (line: X, col:Y).

You’ve likely chosen the incorrect setup type for your script. Based on the contents of the script, the editor wasexpecting HTML, but you set the script to JavaScript or vice versa.

208Troubleshooting

For example: if your script contains <script> tags, but you set the script up as JavaScript, you will receive this errorwhen you attempt to save the code.

Rule Issues

My rule does not fire.

If your event-based rule does not fire, then there is likely an issue with the selector or condition of the rule. Locatethe element on your site where the desired event action occurs, right click and select Inspect element. Inspect thehighlighted script in the box that opens and ensure you are targeting the correct element. Example:

Target element: <div class=’pauseButton’ style=’opacity: 1’>

Selector Syntax:

• CSS Selector Syntax: div.pauseButton OR div[class=’pauseButton’]• Manually assign attributes:

• Element Tag: div• Property: class• Value: pauseButton

I suspect that my rules are firing in the incorrect order. Where can I find more information about the loadorder of rules?

It is important that rules fire in the correct order. Many problems with rules are the result of rules firing in the wrongorder. For more information, see Load Order for Rules.

My rule fires inconsistently.

There are two possible reasons for a rule to fire inconsistently:

• Does the event action incite a link to load? If so, the rule may not have enough time to fire before the new pageloads.You need to check the box within the rule identifier indicating Delay link activation.This keeps the activatedlink from loading until the rule has fired.

• If the event does not incite a new page load, there may be an issue with bubbling. If the event action can occur ona child or parent item, ensure the button indicating Allow events on child elements to bubble is checked. Thisensures that the rule fires whether or not the user interacts with the child or parent element.

My third-party or custom script does not trigger when my page load rule fires.

Verify what type of script you are using and the load option you have chosen for the rule. If you use sequential HTML,your rule must be set to load at Bottom / Top of Page. The script will not work if the rule is set to load Onload orDOM ready.

My rule is firing, but my data element won’t populate.

There’s likely a timing issue. Check and see where the rule is loading; if it’s loading at Top of Page or Onload, thenthe data element is likely not available yet when the rule fires. Try switching the rule to load at Bottom of Page orDOM Ready. If the data element still does not populate, refer to method for the previous question to ensure the dataelement is available on the page.

How can I debug a rule?

You can use the DTM Switch, browser plugin for easy switching of debug mode and staging mode for dynamic tagmanagement users. It is available for both Google Chrome and Mozilla Firefox. For more information, see DynamicTag Management Plugins.

Watch an Adobe training video that demonstrates how to debug a rule by using the DTM switch plugins:

209Troubleshooting

Time: 3:41DTM Basics: Introduction


• Use the DTM debuggingplugin

Why aren't the variables set in the custom code editor in the Adobe Analytics section of my rule executing?

When executing variables via the Custom Page Code editor in the Adobe Analytics section of a rule, you must setlinkTrackVars / linkTrackEvents as appropriate for these variables to set in the beacon. When adding variables/ events via the rule UI, linkTrackVars / linkTrackEvents is set for you. However, when adding variables / eventsvia the Custom Page Code editor this must be done manually. For example:

s.linkTrackVars = "eVar1"s.eVar1 = _satellite.getVar('Title Tag');

Tool Issues

When I click an internal link on my site, a new window opens when it should not. How do I control the linkerlink?

There is likely a code conflict with the linker link feature. Navigate to your analytics tool within your web propertyand click the settings gear icon next to the tool. Expand the General tab of the settings. Under Global Settings,you can control the linker link functionality. From here, you can either turn the linker link feature off or you can setit up to activate / not activate on specific element types or selectors.

Chrome Warning on 2G Networks

Chrome might block document.write calls for visitors on 2G networks.

When using the most recent Chrome update for sites with DTM deployed, a warning might appear in the JavaScriptconsole, which says that Chrome might block document.write calls in the browser if the device has "poor networkconnectivity." Chrome specifically states they are currently targeting users on 2G networks. See "Intervening againstdocument.write()" on the Google Developers website.

Due to the limited usage of 2G network, the current 2G Google intervention should have a minimal impact onenterprise customers at this time. Adobe is proactively addressing future issues that might develop if Google continuesto promote practices that contradict Internet community standards.

DTM's goal has always been to create and support the most powerful and flexible features in the space.This includesallowing DTM users to leverage both synchronous and asynchronous technologies.

If you are concerned about 2G Chrome users, you can use a more asynchronous deployment of DTM and continueto use the robust set of asynchronous specific features of DTM.

If you see this warning and want to deploy an asynchronous DTM setup that removes all document.write calls(and prevents the warning), refer to the following sections.

210Troubleshooting

https://developers.google.com/web/updates/2016/08/removing-document-write?hl=en

https://developers.google.com/web/updates/2016/08/removing-document-write?hl=en

Target

If you are using Target via DTM, and are concerned about visitors on a 2G cellular network who are using Chrome,please do the following:

1. Update your Target code from mbox.js to at.js in the DTM target tool.

Make sure you use the custom code editor.

To learn more about implementing Target with at.js, see at.js Implementation in the Target help.

2. Uncheck the Load Adobe Target Library synchronously checkbox in the DTM Target tool.

3. Test well before deploying.

Note: Loading the Target library asynchronously prevents the warning, but might cause "flickering" on thepage if default content loads before the targeted content.

3rd Party Tags

If you are deploying 3rd party tags via rules in DTM, and are concerned about visitors on a 2G cellular network whoare using Chrome, please do the following:

1. Review all 3rd -party scripts that are deployed via "Sequential JavaScript" or "Sequential HTML" for "top of page"or "bottom of page" positioning rules.

2. In the code editor, change the Type to "Non-Sequential JavaScript" or "Non-Sequential HTML."

Note: Any functionality that requires synchronicity will no longer work.

3. Review the code within the editor to ensure it isn't using document.write.

Any code deployed through DTM that uses document.write might be affected.

4. Test well before deploying.

211Troubleshooting

https://marketing.adobe.com/resources/help/en_US/target/ov2/c_target-atjs-implementation.html

Dynamic Tag Management PluginsAdobe has partnered with Search Discovery and Disruptive Advertising to offer additional plugins to help you withdebugging tasks and to help you set up and configure other products.

Search Discovery Plugins

Adobe has partnered with Search Discovery to offer additional plugins to help you with debugging tasks and to helpyou set up and configure other products.

Note: Search Discovery is the creator of the plugins mentioned in this topic. Contact Search Discovery forsupport issues for these plugins. This topic contains information about the plugins currently offered. See theSearch Discovery website for an updated list.


• DTM Switch Plugins for Debugging (Chrome and Firefox)• WordPress Plugin• Video Tracking Plugin• Drupal Plugin

DTM Switch Plugins for Debugging (Chrome and Firefox)

DTM Switch is a browser plugin for easy switching of debug mode and staging mode for dynamic tag managementusers. It is available for both Google Chrome and Mozilla Firefox.

Note: The Chrome and Firefox plugins are early unsigned versions and are provided on an "as is" basis withno additional support from Adobe.You can also manually set the debugger and switch between libraries viathe dynamic tag management web console.


• Chrome Plugin• Firefox Plugin• EnterpriseTV Video - Debugging• Use the Debugger Via the DTM Web Console

Chrome Plugin

Add the Adobe DTM Switch extension from the Chrome Web Store.

You should see the DTM icon on the right side of your address bar.

212Dynamic Tag Management Plugins

http://www.searchdiscovery.com/contact/

http://www.searchdiscovery.com/solutions/technology/#sditools

https://chrome.google.com/webstore/detail/adobe-dtm-switch/nlgdemkdapolikbjimjajpmonpbpmipk

1. Click the DTM icon.2. Toggle the buttons on or off, as desired.3. Refresh the page to see the changes.

Firefox Plugin

Add the Adobe DTM Switch add-on from the Mozilla Add-Ons page.

You should see the DTM Switch icon on the right side of your address bar.


https://addons.mozilla.org/en-US/firefox/addon/adobe_dtm_switch/

1. Click the DTM Switch icon.2. Toggle the buttons on or off, as desired.3. Refresh the page to see the changes.

Use the Debugger Via the DTM Web Console

You can also manually set the debugger and switch between libraries via the web console. See Test unpublishedrules for Akamai hosting

WordPress Plugin

Easily set up and configure WordPress using dynamic tag management. This plugin installs the necessary DTMcode on your WordPress site.

Download the WordPress plugin at Wordpress.org.

Video Tracking Plugin

Easily track analytics across all popular video sites and send this data to your analytics tools.

Contact Search Discovery for more information and to obtain this tool.

Drupal Plugin

Set up and configure Drupal using dynamic tag management.

Contact Search Discovery for more information and to obtain this tool.

Disruptive Advertising Debugging Plugin

Adobe has partnered with Disruptive Advertising to offer a plugin to help you with debugging tasks.


https://wordpress.org

https://wordpress.org/plugins/adobe-dtm/


https://www.drupal.org


See Introducing the Adobe DTM Debugger on the Disruptive Advertising website for more information.

Note: Disruptive Advertising is the creator of the plugin mentioned in this topic. Contact Disruptive Advertisingfor support issues for this plugin.You can leave a comment on the bottom of the Introducing the Adobe DTMDebugger page.

Tagtician Debugging Plugin

Tagtician is a free plugin that helps you with debugging tasks

For more information about the plugin, see Introducing Tagtician: The Tag Management Companion.

To download Tagtician, go to the Tagtician website.

Note: Tagtician is the creator of the plugin mentioned in this topic. Contact Tagtician for support issues forthis plugin.


https://www.disruptiveadvertising.com/analytics/introducing-the-adobe-dtm-debugger/

http://www.disruptiveadvertising.com



http://jimalytics.com/tag-management/introducing-tagtician-beta-the-tag-management-companion/

http://tagtician.com

GlossaryTerms used in dynamic tag management.

DefinitionTerm

Adobe's hosted, subscription-based solution for real-time website reporting and analysis.You can deploy Adobe Analytics using dynamic tag management by creating the AdobeAnalytics Tool and configuring the page code either automatically or manually.

Adobe Analytics

Approvals

Audience management

Campaign

ClickMap

Cookie

Customize Page Code

Data Center

Data elements are the building blocks for rules. Data elements let you create a datadictionary (or data map) for any object that is contained on your site. They can beJavaScript objects, cookie values, and query strings.

Data Element

Designed to bypass dynamic tag management event detection and lookup systems.Direct Call Rule

Direct call rules are ideal for situations where you want to tell dynamic tag managementexactly what is happening. Also, they are ideal when dynamic tag management cannotdetect an event in the DOM, such as with Adobe Flash.

DTM Switch is a browser plugin for easy switching of debug mode and staging modefor DTM users. It is available for both Chrome and Firefox.

DTM Switch

Embed

Global Variables

Google Analytics

Page Load

Link Tracking

216Glossary


DefinitionTerm

The Marketing Cloud is an integrated family of digital marketing solutions, as well as anintuitive interface for new resources and capabilities, called core services, for yourbusiness.

Marketing Cloud

A Web Property is a library of rules and one embed code. It can be any grouping of oneor more domains and subdomains.You can manage and track these assets similarly.

Property

Publish

Referrer

Dynamic tag management is a rule-based system. It looks for user interaction andassociated data. When the criteria outlined in your rules are met, the rule triggers thetool, script, or HTML you identified.

Rules

Staging

Tag

Target

Tool

Tracking Server

217Glossary

https://marketing.adobe.com/resources/help/en_US/mcloud/

Documentation UpdatesInformation about updates to the dynamic tag management help.

LocationDescriptionDate

Fixed broken links.8/10/2017

MultipleFixed formatting of embedded videos.6/28/2017

DTM Demo VideosUpdated DTM demo videos.5/19/2017

Adobe Cloud Platform Launch FAQAdded frequently asked questions about theupcoming release of Adobe Launch.

3/29/2017

Browser SupportAdded information about supported browsers.11/28/2016

Marketing Cloud ID Services settingsAdded information about the AutomaticallyRequest Visitor ID option being automatically

7/27/2016

enabled when you add a Marketing Cloud IDService tool.

Data Layer Management Using theContextHub Tool

New topics.6/17/2016

• ContextHub Data Layer Default Example• Custom Data Layer Example

Add Adobe Experience Manager ContextHubTool

New topic.6/17/2016

Event TypesAdded the dataelementchanged event in theOther category.

6/17/2016

ResourcesAdded a new section to list additionalresources to help you get the most out ofDynamic Tag Management.

6/16/2016

Manage UsersAdded additional important information aboutadding users with the Adobe Admin Consolevs. in DTM.

6/15/2016

Jump Start Videos5/16/2016

Manage UsersAdded Important note at the top of the page.5/9/2016

218Documentation Updates



Manage Users for DTM in the AdobeMarketing Cloud

New topic.5/9/2016

Tagtician Debugging PluginNew topic.4/21/2016

Using the CSS SelectorNew topic.3/30/2016

Create a New GroupAdded information about restricting the abilityfor group members to create or modify toolsand related tool settings in rules.

3/30/2016

Invite Users to DTM using the LegacyProcess

Added information about the Restrict Loginto Marketing Cloud option.3/30/2016

Best Practices for Getting Started withDynamic Tag Management

New Section: Best Practices for GettingStarted with Dynamic Tag Management

2/29/2016

Call Google Analytics Objects in DTM UsingScripts

New topic.2/29/2016

Call Google Universal Analytics Objects inDTM Using Scripts

New topic.2/29/2016

Best Practices for Implementing AdobeTarget using Dynamic Tag Management

New section: Best Practices for ImplementingAdobe Target using Dynamic TagManagement

1/28/2016

Privacy Management SettingsNew topic.1/14/2016

Manage Account SettingsNew topic.1/14/2016

FTPAdded information about specifying relativehostnames for staging and production libraryhosting.

1/14/2016

Library Download

Add Nielsen ToolNew topic.1/07/2016

Event TypesAdded the following new event types forevent-based rules:

11/16/2015

• Other > time passed• Browser > tab focus• Browser > tab blur


https://marketing.adobe.com/resources/help/en_US/dtm/gs/

https://marketing.adobe.com/resources/help/en_US/dtm/gs/

https://marketing.adobe.com/resources/help/en_US/dtm/target/

https://marketing.adobe.com/resources/help/en_US/dtm/target/


Disruptive Advertising Debugging PluginNew Topic.10/26/2015

Set up actions for the condition to triggerAdded note about avoiding cross-site scripting(XSS) vulnerabilities in custom code.

10/07/2015

Web PropertiesAdded "Deactivating a Web Property" section.10/07/2015

Delete a web propertyNew Topic.09/29/2015

Embed Code and Hosting OptionsAdded the following to the Important note:09/29/2015

Including multiple embed codes on a singlepage is not supported, as it can causeconflicts.

TroubleshootingAdded the following information in the RuleIssues section:

09/25/2015

Why aren't the variables set in the customcode editor in the Adobe Analytics section ofmy rule executing?

Create conditions for direct-call rulesAdded note at the bottom of page specifyingwhether to use quotation marks or not.

09/25/2015

Create and Manage Groups in DTMNew Topics.09/03/2015

• Add Users to Groups

• Create a New Group

• Edit a Group

• Delete a Group

Link TrackingAdded information about link tracking andsingle-page app considerations.

09/03/2015

Frequently Asked QuestionsAdded information about using DTM for mobileapps.

09/03/2015

Added information about supported browsersand versions.

TroubleshootingAdded information about viewing the Auditlog.

07/29/2015



Invite Users to DTM using the LegacyProcessAdded note explaining how selecting a default

role affects rights for newly created properties.07/16/2015

Event TypesNew Topic.07/08/2015

New event types include "Custom" and"pushState or hashchange."

Data ElementsUpdated the description for the CustomScript data element.

06/17/2015

Rule Conditions and FunctionsUpdated table.06/01/2015

Dynamic Tag Management PluginsAdded information about the WordPress,Video Tracking, and Drupal plugins for DTM.

04/20/2015

Dynamic Tag Management OverviewNew topic.04/20/2015

Create a web propertyAdded information to indicate that SelectivePublish is the default setting when creatingweb properties.

04/07/2015

Add Adobe Analytics ToolAdded information about using Dynamic TagManagement with Adobe Analytics Premium.

02/24/2015

Load Order for RulesAdded information explaining how the differentJavaScript/third-party tags script options areutilized within the four page-load phases.

02/18/2015

Frequently Asked QuestionsUpdated FAQ with information about usingdynamic tag management with the AdobeMarketing Cloud.

02/18/2015

Add Google Universal Analytics ToolUpdated information about enabling EUcompliance.

01/28/2015

Add Google Analytics Tool

General

Dynamic Tag Management PluginsUpdated topic.01/28/2015

Migrating from Adobe Tag ManagementUpdated migration from Adobe Tag Manager1.0 and 2.0 to dynamic tag management.

12/15/2014



FAQ - AdvancedUpdated the advanced FAQ with contentregarding VisitorAPI.js breaks intext+html.

12/08/2014

Add Adobe Media Optimizer ToolUpdated Adobe Media Optimizer tool settings.11/21/2014

Header and Footer CodeUpdated the Important note regarding thewrapping of embed codes.

11/7/2014

Add Adobe Target ToolAdded feature content for Adobe Targetdeployment.

10/23/2014

FAQ - Adobe Analytics ToolAdded plug-in information to the AnalyticsFAQ.

10/23/2014

Embed Code and Hosting Options andHeader and Footer Code

Added and important note in the Hostingsection about the risks of unsupportedimplementations.

08/27/2014

Event-Based Rules ExampleAdded external links to resources for learningabout CSS.

08/26/2014

Add Adobe Target ToolAdded Load Adobe Target LibrarySynchronously field description.

08/08/2014

Added content for the Marketing Cloud IDService tool.

08/07/2014

FAQ for Adobe Analytics Release - July 242014

Updated the Adobe Analytics configurationwith new feature content for automaticallymanaging your configuration.

07/24/2014

Frequently Asked QuestionsAdded FAQ information for the automaticconfiguration for Adobe Analytics deployment

07/24/2014

tool. Separated other FAQ information intobeginner and advanced sections.

Separating the DTM Environment for MultipleEntities in Web Properties

Added information about handling multiplegeo markets, business units, and subdomains.

07/09/2014

Add Google Analytics ToolUpdated the Enable EU compliance forGoogle Analytics field description.

06/16/2014



Web PropertiesAdded bets practices for Web Properties.05/06/2014

Load Order for RulesAdded queue processing information after theLoad Order diagram.

05/06/2014

DTM Switch PluginsAdded external link to plugins in the table ofcontents.

04/22/2014

Add Google Universal Analytics ToolAdded Google Universal Analytics content04/04/2014

How Do Tag Management Systems ImprovePage Load Speed?

Added topic with information about how tagmanagement systems improve page loadspeed.

03/20/2014

AkamaiAdded Why Choose Akamai Hosting forLibrary Files?

03/19/2014

Web PropertiesAdded How Web Properties Compare toAdobe Analytics Report Suites.

03/19/2014

Added Domain Planning.

Data ElementsAdded a section How to Collect Values fromJavaScript Variables in a data element.

03/19/2014

Frequently Asked QuestionsUpdated the FAQ03/18/2014

in the Global Variables section.Added information about dynamicallypopulating variables(%this.attributeName%).

03/05/2014

Embed Code and Hosting OptionsAdded the following note:02/27/2014

Header and Footer CodeNote: Adobe supports the dynamic tagmanagement implementations only asoutlined on the pages in this section ofAdobe Help. Asynchronous or otherdeployment methods are not supported.

GeneralAdded the following text to the s_code fielddescription.

02/07/2014

Dynamic tag management supports any Hversions of legacy s_code.




Insert core AppMeasurement codeAdded new steps to insert coreAppMeasurement code.

01/29/2014

Akamai HostingAdded information about migrating fromAmazon S3 to Akamai hosting.

01/17/2014

Release Notes for Dynamic Tag ManagementRelease notes update01/16/2014

Frequently Asked QuestionsAdded information in the FAQ aboutsupporting HTML5

12/16/2013

All topics.Reauthored help.12/09/2013

Table of Contents.Added a link to the Community Forum to thetable of contents.

11/20/2013

Add Google Analytics ToolAdded information to the Enable EUCompliance field.11/13/2013

Manually implement Adobe Analytics (legacy)

Header and Footer CodeUpdated procedures for adding header andfooter code, and verifying code.11/06/2013

Data ElementsUpdated the Data Elements topic with newcontent.11/06/2013

Rules > Load Order for RulesA process graphic showing the DTM loadorder in relation to the JavaScript load order.10/30/2013


Previous Release NotesHistorical release notes for dynamic tag management.

See Current Release Notes for the latest release information.

April 21, 2016

The April 21, 2016 dynamic tag management release includes the following changes:

New Features

DescriptionFeature

As part of the Adobe Marketing Cloud Spring 2016 release, a new-top level navigationmenu displays at the top of all solution interfaces. The new interface lets you:

Marketing Cloud navigationand menu changes

• Single-click navigation between solutions: Choose your own default landingpage or take advantage of the solution-switcher widget.

• Improved notifications: Get notified about events (like posts, mentions, assetsshared, system updates) happening across your organization navigation widget.

• Updated Feed: We reimagined the Feed page to become a better platform forcross-channel collaboration between marketers.

See What's New in the Adobe Marketing Cloud - Spring 2016 in the Marketing Cloudand Core Services Product Documentation.

March 30, 2016

March 30, 2016

The March 30, 2016 dynamic tag management release includes the following changes:

New Features

DescriptionFeature

Use the CSS Selector to quickly and easily select CSS elements to use as triggersfor event-based rules without leaving the DTM rule builder.

CSS Selector

See Using the CSS Selector.

Use group membership to restrict the ability for users to create or modify tools andrelated tool settings in rules.

Restrict tool access usinguser groups

See Create a New Group.

Use the Restrict to Marketing Cloud option to force all users in the company tolog in to dynamic tag management using Adobe Marketing Cloud credentials ratherthan using the legacy/company login process.

Restrict login to MarketingCloud

See Invite Users to DTM using the Legacy Process.

Fixes and Enhancements:

225Previous Release Notes

https://marketing.adobe.com/resources/help/en_US/mcloud/index.html?f=marketing-cloud-interface

February 4, 2016

The February 4, 2016 dynamic tag management release includes the following changes:


• Fixed an issue that prevented a rule from firing when using the Element Exists event with the Manually AssignedProperties & Attributes option. (DTM-6681)

• Fixed an issue that caused the Enter Viewport trigger condition to not be respected by all rules that match thesame HTML element. (DTM-7108)

• Fixed an issue that caused pages to unload with a jQuery undefined error message. (DTM-7116)• Fixed an issue that sometimes caused the Original and Modified editor views seen during the approval process

to contain mismatched content. (DTM-7180)• Fixed an issue that caused an MCID authentication error when working with data elements. (DTM-7233)

January 14, 2016

The January 14, 2016 dynamic tag management release includes the following changes:

New Features

DescriptionFeature

Administrators can now receive an email notification when one of their web propertiesis published. The email contains the time and name of the property.

Admin notifications forproperty publishes

See Manage Account Settings.

You can specify relative hostnames for staging and production library hosting.Relative hostnames

See FTP and Library Download.

You can enable Nielsen tracking using dynamic tag management by creating theNielsen tool and configuring the page code either automatically or manually. Theautomatic method is recommended for most users.

Nielsen tool

See Add Nielsen Tool.


• Fixed an issue when using multiple custom event rules that caused only the first rule to fire. (DTM-7026)• Fixed an issue that prevented the main library from loading for certain customers. (DTM-7130)• Fixed an issue with Internet Explorer 9 that caused the Nielsen time-spent-on-page counter to remained paused

after the browser or browser tab loses and then regains focus. (DTM-7033)• In Internet Explorer 8, the non-human detection mechanism in forms malfunctions. Because IE8 is no longer

supported this issue will not be fixed. Please upgrade your browser if this is an issue for you. (DTM-7101)

November 17, 2015

The November 17, 2015 dynamic tag management release includes the following changes:

New Features


DescriptionFeature

Added the following new event types for event-based rules:New event types forevent-based rules • Other > time passed

• Browser > tab focus• Browser > tab blur

For more information, see Event Types.


• Fixed an issue that caused dynamic tag management to throw a fatal error on Microsoft Internet Explorer 8.DTM-7022

September 22, 2015

The September 22, 2015 dynamic tag management release includes the following changes:

New Features

DescriptionFeature

The newest library version (1.5.2) will enable improved customer ID support, addedsupport for authenticated state and improved multi-solution integration.

Marketing Cloud Visitor IDService Tool

The newest version is completely compatible with current deployments of theMarketing Cloud Visitor ID Service via DTM.To help all users benefit from this updatewe will automatically migrate your account to the new Marketing Cloud ID Servicelibrary.

As a result of this migration you will see added functionality to your Marketing CloudVisitor ID Service tool in DTM. We suggest that you test this update in your stagingenvironment before publishing.

The DTM team strives to add value for our customers, and we are confident that youwill see this realized in the update to the Marketing Cloud Visitor ID Service tool.

For more information, see .


• Fixed an issue when editing user groups that caused user groups from other companies to be removed.

• Fixed a security concern with rules using non-sequential HTML code. Please re-publish your web properties forthe fix to take effect.

September 3, 2015

September 17, 2015

New Features


DescriptionFeature

Group management makes it easy to organize users and control their access levels.Permissions are set at the user group level, so all users in the group inherit the grouppermissions, including access to properties.

Group management

For more information, see:

• Create and Manage Groups in DTM

• Add Users to Groups

• Create a New Group

• Edit a Group

• Delete a Group


• Improved the deployment of the satellite library (2-5 times speed increase). Customers with many rules or who aredeploying many third-party tags will greatly benefit from these changes.

• Improved the upload speed to Akamai (up to 5 times faster).

• Improved the load speed (2 times faster) for all rule listing pages.

• Fixed an issue that prevented some pages from loading in Internet Explorer (users received a pop-up error message).

July 8, 2015

New Features and Enhancements

DescriptionFeature

New event types let you trigger event-based rules on Single Page Apps:Event Types

New event types include "Custom" and "pushState or hashchange."

See Event Types.


• Fixed an issue in the Google Universal Analytics tool that prevented users from setting the account ID in dataelements.

• Fixed an issue in the Google Universal Analytics tool that suppressed rule beacons if the Page Code is AlreadyPresent check box is selected.

July 8, 2015

The July 8, 2015 dynamic tag management release includes the following changes:


DescriptionFeature

New event types let you trigger event-based rules on Single Page Apps:Event Types

New event types include "Custom" and "pushState or hashchange."


DescriptionFeature

See Event Types.


• Fixed an issue in the Google Universal Analytics tool that prevented users from setting the account ID in dataelements.

• Fixed an issue in the Google Universal Analytics tool that suppressed rule beacons if the Page Code is AlreadyPresent check box is selected.

June 8, 2015

The June 8, 2015 dynamic tag management release includes the following changes:


• Fixed an issue in some iOS Safari browsers that produced an error when localStorage options are restricted by auser.

April 23 2015

The April 23, 2015 dynamic tag management release includes the following changes:


DescriptionFeature

Enhancements to data elements include the following:Data Elements

• Users can now copy data elements across web properties and companies.

• Users can now bulk copy, activate, deactivate, and delete data elements.

• Users can now select a cleanText option when setting a data element.

This option causes dynamic tag management to remove beginning and endingwhitespace and replace all whitespace in the middle of return values with a singlespace. This option is useful to normalize data element values for easier matching.

April 7 2015


DescriptionFeature

When creating a web property, the Enable Selective Publish option is set by default.Selective Publish

See Create a web property.


• Added localization enhancements for the Adobe Analytics tool UI (Premium, Standard, and Point).• Updated the favicon icon that displays in browsers' address bars to match new Adobe branding.


March 24 2015


DescriptionFeature

If you are an Adobe Analytics Premium customer, dynamic tag management letsyou take advantage of advanced features and additional eVars and events.

Integration with AdobeAnalytics Premium

Note: If you do not use the Automatic configuration method, dynamic tagmanagement will treat you as an Adobe Analytics Standard account.

See Add Adobe Analytics Tool.

Fixes:

• Updated the variable and event interface for the Adobe Analytics tool to allow auto-complete selection and toenable access to additional eVars and events for Analytics Premium accounts. See Add Adobe Analytics Tool.

• Fixed an issue where the Store Path option for FTP library deployments wasn’t updating for production librarieswhen using nested directories.

• Updated data elements to support hyphenated names.• Fixed an issue where the column indicator in the Rules table displayed for a rule, even if the tool was deleted.• Updated the Sequential HTML code option to be available for page-load rules only. This option no longer appears

for event-based rules. A notice displays with a Sequential HTML tag on an event-based rule to notify users tochange the tag before the rule can be saved.

• Fixed an issue where the Sign in with Adobe ID login option wasn’t allowing users to sign in as a different user.Users can click Sign in with a Different Adobe ID to log out as the current Marketing Cloud user and be redirectedto the Adobe login page.

February 10 2015

Fixes:

• Added a deprecation warning message for all company administrators using Amazon hosting for their JavaScriptlibrary.

• Improved the error handling for instances where document.write is not available.• Addressed various localization issues to increase the user experience for supported languages.• Fixed an issue where the Channel field wasn’t included in rules specifying a s.tl() call in Adobe Analytics.• Fixed an issue where copied rules weren’t automatically added to the staging library until a change was made to

the rules.• Fixed an issue where Regex was firing for rules using the “parameters” condition option, even if the parameter

wasn’t present.

January 13 2015

Fixes:

• Dynamic tag management no longer overrides global variables with the name window.t.• Fixed an issue where Firefox was incorrectly trapping the right-click event handler in the browser and causing

click-based rules to fire.


November 13 2014

DescriptionFeature

Adobe improved our dynamic tagmanagement integration with AdobeMedia Optimizer, including.

• Default delivery of the latest (v3) Media Optimizer tag

• Support for a data-element based SKU

• Suppression of unneeded beacons

• Minor enhancements

See Add Adobe Media Optimizer Tool

Fixes and Improvements

• Fixed an issue where rule copying did not work after the release of the Adobe Media Optimizer integration on10/30/2014.

• Added the ability to specify name/value pairs for general settings and customer-specified IDs in the MarketingCloud ID tool.

• Added option for the Marketing Cloud ID tool to trigger the initial API call. This call enables support for Adobesolutions that do not currently trigger this call already in your own code.

• Fixed an issue where the browser version tracked by dynamic tag management for certain versions of InternetExplorer was returned as Unknown instead of Internet Explorer.

• Adobe tools will now be displayed first in the listing of installed tools on a given web property.

October 30 2014

Adobe improved our dynamic tag management integration with Adobe Media Optimizer, including:

• Default delivery of the latest (v3) Media Optimizer tag• Support for a data-element based SKU• Suppression of unneeded beacons• Minor enhancements

October 28 2014

New features in dynamic tag management released on October 28, 2014:

DescriptionFeature

Updated the Adobe Target tool to enable automatic deployment via dynamictag management.

Adobe Target integration

See Add Adobe Target Tool for configuration information.

Added a checkbox for premium Google Universal Analytics features in thetool (General group). This option enables the max dimensions and metricsincrease from 20 to 200.

Enable support for Google UniversalAnalytics Premium features

Fixes and Improvements

• Fixed an issue where the Tracking Server value automatically determined by dynamic tag management for theAdobe Analytics tool sometimes set an incorrect value.

• Fixed an issue where a restored data element had the name appended with "(Restored)," which caused previousreferences to that data element to be broken. (The appended value is now added only if restoring the data elementwould create a naming conflict with an existing data element.)


• Fixed an issue caused when triggering an event-based rule on a click event. If the click event had a delay linkactivation on an anchor tag with no HREF, the issue forced the browser to attempt to navigate to a blank HREFlocation.

• Fixed an issue where dynamic tag management was no longer saving global variables configured in an Analyticstool when changes to that tool had been rejected and then restored.

• Implemented significant performance improvements in the library generation process, which should result in ashorter wait for changes to appear in production, especially during peak usage hours.

• Fixed an issue where company administrators were unable to export their activity log to CSV when there was alarge amount of data present.

• Added the ability to use custom HTML data attributes with CSS selector-based data elements.

August 21 2014

Fixes and improvements:

• The help landing for dynamic tag management is now at:


Please update your bookmarks accordingly.

• Fixed an issue where re-enabling a previously disabled property caused all approved items to be immediatelypublished. A property will now be enabled, but published assets will not be affected until a publish request isexplicitly requested by a user with appropriate permissions.

• Fixed an issue where custom code editors in dynamic tag management were truncating the last few lines of displayedcode.

• Fixed an issue where reverting a tool to a previous version did not revert all settings for that tool.• Users can now force a data element's value to be automatically converted to lowercase before it is returned and

used.• Fixed issue where a race condition in the dynamic tag management engine prevented data from being sent correctly

to audience management.

August 7 2014

New features:

DescriptionFeature

You can automate the deployment of the Marketing Cloud ID Service usingdynamic tag management.

Marketing Cloud ID Service

See Marketing Cloud ID Service in Dynamic Tag Management Help.

Fixes and improvements:

• The help landing for dynamic tag management is now at:


Please update your bookmarks accordingly.

• Fixed an issue where reverting an Analytics account to a previous version resulted in a 404 error.• Fixed an issue where Approvers trying to view details on a previous version, while reviewing an approvable item,

were unable to expand the appropriate sections.• Added support in Adobe Analytics tool configuration for visitor namespace.• Upgraded the code editor used throughout dynamic tag management, which provides additional features, including

support for extra-long lines of code.



https://marketing.adobe.com/resources/help/en_US/dtm/macid.html


• Fixed an issue where events set in the Analytics rule UI were not being sent as part of data collection when therule was set to use s.t().

• Fixed an issue where the Force Lowercase option was not working in Google Universal Analytics.• Fixed an issue where the default value was not returned when specifying a DOM element that did not have the

attribute defined as specified in the CSS selector for the data element.• Fixed an issue where reverting an Analytics tool to a previous version did not revert all elements of that account,

resulting in a mixture of old and new settings for the tool.

July 24 2014

New features:

DescriptionFeature

Report suites are automatically synchronized via a Marketing Cloud login or WebServices ID.

Adobe Analytics account andreport suite synchronization.

Once the accounts are connected, dynamic tag management pulls the AdobeAnalytics report suite IDs and names into the tool configuration interface, allowingfor increased speed in tool deployment with less possibility for user errors.

You can let dynamic tag management loads and manage the base library directly.You no longer need to cut and paste library code from the Adobe Analytics

Adobe managed measurementlibrary option.

administration tools. This feature also makes upgrades to new versions ofAppMeasurement easier, because the base code and custom code are storedseparately.

You can now select whether you want the code in the Adobe Analytics code panelto fire before or after the interface settings for more implementation flexibility.

Custom Code timing.

The groups (General, Library Management, and so on) on the Tools page forAdobe Analytics has been reorganized and streamlined to simplify configuration.

Interface improvements.

Latest Links

See FAQ for Adobe Analytics Release - July 24 2014 for questions and answers.

See Add Adobe Analytics Tool for configuration information.

July 10 2014

Features and fixes:

DescriptionFeature

Click Log in the left-hand rail to view the Audit Log page.Audit Log for Administrator

Company administrators can view, filter, and export a list of all activities thattake place within companies and web properties to which they have access.This feature is helpful both for auditing and troubleshooting purposes.

For example, you can view and filter by:


DescriptionFeature

• Successful logins• Account names• IP addresses• Companies• Web Properties (and see who created them and when)• Roles, and more.

You can also export the log data to .csv.

Dynamic tag management is now available in the same languages (English,French, Spanish, German, Korean, Portuguese, Japanese, Traditional Chinese,and Simplified Chinese) as the rest of the Marketing Cloud.

Language Selector

In Account Settings, click the Languages menu to specify the language.

To enable this feature:Synchronous loading of the AdobeTarget tool.

1. Navigate to the Target tool configuration page.2. Enable Load Adobe Target Library synchronously.

Note: This value is enabled by default for new instances of the AdobeTarget tool, and disabled by default for existing instances of the tool.

Existing instances of the Adobe Target tool will continue to load asynchronouslyuntil you change the setting to synchronous.

Fixes

• Fixed an issue where disabling and then enabling a property caused the items in the approvals queue to beautomatically published by the system when the property was re-enabled.

• Added a message to the Embed tab for company administrators. This message is a reminder that no code ispublished to the production environment until someone explicitly clicks Publish. This fix was done to help avoidconfusion by some users who were seeing 404 Not Found errors on the production library, because they had notyet published.

• Fixed an issue where duplicate registrations were possible for the same user using a differing case. (For example,[email protected] vs [email protected]).

• Fixed an Adobe Analytics issue that prevented you from re-adding or editing an eVar or prop value after deletingthat specific variable or property.

• Fixed an issue where rejecting an approved or published tool, and then updating that tool, did not cause a newentry to be generated in the approvals queue.

• Fixed an issue where the Adobe Analytics tool configuration options for Always Track and Never Track did not emitthe correct values to the library and therefore did not have any effect on data collection.

• Fixed an issue where entering invalid regular expressions caused a broken interface and required you to reloadthe page.

• Google Analytics event tag: Fixed an issue where a Fill in all fields error appeared on a rule, but you were unableto save the rule or make any additional edits and was required to reload the page.

May 15 2014

Fixes and improvements for May 15, 2014:


• Fixed an issue where variables set in custom code were not being set on direct call or event-based rules usings.t(). The code contained within the custom code area for direct call or event-based rules using s.t() was notcorrectly adding any variables set to the beacon before an image request was being fired.

• Fixed and issue where the command bar was sticking to the bottom of the Approvals page. The persistent barwith the Edit and Reject commands on the Approvals page was sticking to the bottom of the page rather thanfollowing the page view upon scroll.

• Fixed an issue on the Rule List page, where a newly created rule showed Adobe Analytics in use, even if thoserules were not using Adobe Analytics.

• Fixed layout issues on Selective Publish queue page. We cleaned up the layout so that it is not truncated orstretching beyond the boundary of the content area of the page.

• Data elements now display in alphabetical order in the Data Element Value criteria of a rule. They have now beenalphabetized for easier viewing.

• The items on the publish history are now paginated to improve performance and user experience.• Added password security enhancements. To ensure the security for dynamic tag management accounts, we have

implemented a number of enhancements to our authentication system:

• New passwords must meet specific criteria (minimum 7 characters, at least one number, at least one letter, atleast one symbol, not one of the last 5 passwords).

• Company admins can now see how long it has been since a user last changed their password.• Company admins can now force users to reset their password.• Users attempting to log in 5 times unsuccessfully will be locked out for 30 minutes to prevent brute force attacks

(the user or their company admin can reset the password to re-enable access immediately).

May 8 2014

Fixes for May 8, 2014:

• Fixed an issue where trackingServer value was not being applied consistently. The value for s.TrackingServershould be used consistently for all types of calls throughout dynamic tag management, and the value should bepulled either from the custom code or from the UI, depending on the configuration of a specific web property. (TheUI value takes precedence if set in both locations.)

• Fixed an issue where properties with a large number of items awaiting approval was causing 500 errors andtimeouts. We optimized the queries for the approvals workflow to ensure that properties with a large number ofitems awaiting approval would load quickly and not result in timeouts, errors, or broken pages.

• Fixed an issue where pages with an existing object called 's' would cause errors in dynamic tag management.Dynamic tag management tries to initialize an 's' object on the page for Adobe Analytics tracking, and this wascausing a conflict if Analytics was implemented via dynamic tag management and the Page code already existsbox was not checked. The object is now locally scoped within dynamic tag management, so it will work in anycustom code scenarios but will not conflict with any on-page code.

• We made a number of improvements to the way that hierarchies are managed in Adobe Analytics tools and rules,including ensuring that non-sequential hierarchies could be used together in a tool or rule, and ensuring that thesame hierarchy could not be set more than once in a tool or rule.

April 28 2014

Fixes for April 28, 2014

• Fixed an issue where direct call and event-based rules that were configured to send a page view (using s.t())were not executing custom code.

April 17 2014


• Fixed an issue in which an error displayed when you delete data elements that were associated with rules that hadalready been deleted.


• Fixed an issue in which deleted data elements were still shown in the menu when you add a condition to a rulebased on a data element.

• Fixed an issue where fields and values for Google Universal Analytics rules were showing as modified in theApproval view, even if the rules had not been changed. This issue also occurred on new rules.

• Fixed an issue where the Google Universal Analytics tool configuration allowed you to configure the cookie timeoutin milliseconds, even though Google Universal Analytics does not support this.

• Changed AdLens to Media Optimizer.• Users can now use the % syntax to view the pop-up list of data elements when sending values to Media Optimizer.• Modified styling on tool lists to better accommodate tools with long names, and to improve readability.

April 8 2014


• Fixed the styling on the Forgot Password page to improve appearance.• Fixed an issue where approved/published rule conditions were being removed from production library upon deletion

in staging.• Fixed an issue where the Actions menu on the Rule List page was being cut off at the bottom, if there were less

than three rules being displayed.• Fixed alignment for the Create Data Element button on the Data Elements page.• Fixed alignment for the Create New Schedule button on the Scheduling page.• Fixed an issue where long rule names were breaking the Selective Publish page.• Fixed an issue where deleting Adobe Analytics variable values would, in certain cases, result in a broken UI that

required a page refresh to fix.

April 3 2014

Features for April 3, 2014

DescriptionFeature

Added native support for Google Universal Analytics.Google Universal Analytics support.

Integrated the Airlock JS library to perform automatic translationof all existing GA calls to Google Universal Analytics.

Upgrade from Google Analytics to GoogleUniversal Analytics

Fixes for April 3, 2014:

• Fixed an issue where clicks were not being tracked in certain scenarios when the Page code is already presentbox was enabled in the Adobe Analytics tool configuration.

• Fixed an issue where all approvables were being deployed in staging, rather than just the ones that were addedor modified. This issue potentially resulted in delays to seeing staging updates.

• Fixed an issue where linkTrackVars and linkTrackEvents were being overwritten by rules, rather than appendingto existing values (such as those set in s_code).

• Fixed an issue where use of special characters (such as brackets) in data element names caused exceptions whenyou edited the data element.

• Fixed an issue where a lengthy shared secret for library download bundles caused exceptions (showed as a 500Server Error).

• Fixed an issue where the cookieLifetime variable was being emitted to the library with incorrect capitalization,causing the corresponding setting from the interface to be disregarded when the page was loaded.


March 11 2014

Fixes for the March 11, 2014 release:

• Fixed issue where test files (ftp_test.txt) were being left on FTP/SFTP servers after upload was complete.This file is now deleted once the upload is complete as it is only used to test the ability to validate user credentialsand is not actually needed by dynamic tag management.

• Fixed issue where custom port for FTP/SFTP was not being saved.

March 6 2014

Features and fixes for the March 6, 2014 release:

DescriptionFeature

Dynamic tag management now supports transmitting publishedfiles to a client's server via secure FTP (SFTP).

Added support for SFTP.

A delimiter can now be specified when hierarchies are used in arule that sends data to Adobe Analytics. (Previously, the behavior

Added support for hierarchy delimiters.

was that all hierarchies were comma-delimited, and any otherdelimiter required use of custom code.)

Fixes

• Fixed issue with SVG images in older IE browsers. SVG images that were clicked in older IE browsers (prior to IEversion 9) caused errors and would sometimes cause the browser to crash.

• Fixed issue with custom links in direct call rules. Using custom links in direct call rules would generate a JavaScripterror in the browser.

• Fixed issue with data element rule conditions referencing the wrong name. If a user renamed a data element, andthe data element was being referenced in a rule condition, the rule would try to use the most recently specifiedname for that data element. This issue occurred even if the name change had not yet been published.

• Fixed issue where elements without an HREF attribute caused errors when clicked. This issue is regarding the"linker link" functionality in the dynamic tag management engine, which attempts to automatically track any clickedelements on the page. Elements without an HREF were generating errors. The "linker link" code now checks thatthe element is an anchor tag before attempting to track clicks on it.

February 4 2014

Fixes for the February 4 2014 release:

DescriptionFixed Issue

Users were able to enter invalid URLs on a web property. ValidURLs are now required.

Fixed issue with invalid URLs being accepted inweb property configurations.

The deploy hook URLs containing a non-default port would havethe port removed before the HTTP call was made. This issueresulted in deploy hook notifications being sent to the wrong URL.

Fixed issue with port being stripped from deployhook URL.

January 28 2014

Fixes for the January 28 2014 release:



A user attempting to set multiple Adobe Analytics variables wouldsee variables being overwritten unintentionally. (For example, a

Fixed an issue with Adobe Analytics variablesoverwriting one another in the interface.

user sets prop22, then sets prop2. Prop22 disappears and prop2contains wrong value.)

Note: This issue was visible in the interface but did notaffect existing code or data collection. In other words, ifyou did not see the variable being overwritten before yousaved the rule or tool configuration, then you were notaffected by this issue.

Having a long account ID for one or more tools on a web propertywould cause the tools list to be truncated, making it impossibleto then edit that tool.

Fixed an issue with long account IDs causingtools list to be truncated on right side.

January 21 2014



The Scheduling feature had a number of UI bugs relating toelement styling, etc. which have now been fixed.

Fixed UI bugs with Scheduling feature.

Fixed issue where campaign values set in the Adobe Analyticstool were not being retained when the tool was saved.

User can now correctly set global campaign inAdobe Analytics tool.

Fixed display formatting issues relating to tool-tips.Fixed formatting of tool-tips.

January 16 2014



Dynamic tag management is migrating from Amazon S3 toAkamai as the primary external hosting option in efforts to provide

Akamai hosting is the default embed option fornew web properties.

dynamic tag management customers a more reliable hostingexperience.We encourage all current customers utilizing AmazonS3 hosting to transition to Akamai as soon as possible, so thatthey may take advantage of increased performance due toAkamai's globally distributed network.

All new companies created after January 15, 2014 will haveAkamai as their external hosting option by default.



Companies created prior to January 15, 2014 will be able tochoose between Akamai and Amazon S3 until this option isdeprecated on December 31, 2014. Any new properties createdwithin dynamic tag management companies that existed prior toJanuary 15, 2014 will also have the option of choosing betweenAmazon S3 and Akamai.

For information about migrating from Amazon S3 to Akamai, seeAkamai Hosting

User lists for companies and web properties are now paginated(if the company or web property has more than 25 users). This

Paginated user lists.

change was done to improve both user experience and platformperformance.

Use caution when taking this action, because deleting the webproperty removes all tools, rules, and settings and cannot beundone.

Company administrators may delete webproperties.

Previously, if multiple page load rules fire and they all had customcode for Adobe Analytics, only one of the rules would take effect.

Multiple rules containing custom Adobe Analyticscode now fire correctly.

Fixed an issue that was causing batch deactivation of rules toshow as having taken effect in the UI, but were not actuallydeactivated in the library.

Batch deactivation of rules now working.

Login via Adobe ID now looks identical to the login page formarketing.adobe.com.

Login page reskin.

Users will now see an option on their Account Settings pageto opt out of non-essential emails, such as approval and publish

Opt-out of nonessential emails.

notifications, note creations, and so on. Essential emails, suchas invitations to new companies, properties, and password resetsare still sent.

November 19 2013

The following table provides information about release notes and fixes for this release.


Fixed an issue where a data element reference in a Target rulewas rendering the literal value (e.g. "%FirstName%") on the

Data elements not working correctly in Targetrules

request instead of the substituted value returned from the dataelement.



Fixed an issue where an invalid regular expression used in rulecriteria would cause the library updates to not be successfullysaved.

Invalid regex causing library save to fail

Added a new property to the engine (_satellite.isStaging).This property indicates whether the staging library is the libraryloaded on the current page.

True indicates staging library loaded.

New property for engine: isStaging

False indicates production library loaded.

November 12 2013



Fixed an issue where tools that had been deleted were still showingup in the Rules tab.

Deleted tools are no longer visible in rules.

Previously, the Time On Site criteria allowed you to specify only anexact number of minutes to match.Time on Site now supports greater

Time On Site criteria now allows forconditional operators.

than (<) and less than (>) for increased control over time basedscenarios.

Previously, the interface showed events 1 - 75. Now, support isavailable for events 76 - 100 to match the capabilities available inAnalytics.

Adobe Analytics rules may now use events76 - 100.

Previously, when creating a new Analytics tool instance, if you didnot add s_code to the tool, you would see a 403/Forbidden error

New Analytics installed tools with no s_codewill not show error.

displayed in the console. This error occurred because dynamic tagmanagement was requesting a file that did not exist.

Now whenever an Analytics tool is created, the s_code ispre-populated with helpful comments and a call to the Satellite enginenotification system. The result displays a message in the console,which instructs you to install s_code to complete the implementation.

October 30 2013



A user must click in a field or make a change to a rule before theSave button is activated. Otherwise, to leave a rule withoutmaking changes, you must click Cancel.

Interaction required to save a rule.

Fixed an issue where text was being displayed (when it shouldn'thave been) at the end of each row in the selective publish UI inFirefox only.

Errant text appearing on selective publish UI inFirefox.



Centered the Yes/No buttons in the approval confirmation modalwindow.

Buttons for approval modal are not centered.

The icon that appears to the left of the breadcrumbs allowing auser to collapse/expand their sidebar was not displaying correctlyin Firefox. It should now be displaying correctly.

Sidebar collapse icon not appearing correctly inFirefox.

Administrators can now see the name of the person who inviteda particular user to their company (if the person who invited the

Company admin can see who invited a user.

user is an Adobe employee, the admin will simply see DTM Adminin place of the name).

Fixed an issue where a user adding arguments to a rulecontaining an Adobe Target tool would see an incorrectlyformatted/broken UI

Adding Target arguments breaks rule formatting.

October 23 2013



Whenever a new version of the library is published, the_satellite object will now contain two new properties:

Timestamps embedded in the _satellite objectfor publish and build.

publishDate: The user requested the publish to happen (thesame date/time that appears in the History section of the UI).

buildDate: The file was created by our server processes. Thedifference between the two can be used to troubleshootpotentially processing latency issues.

Previously when a tool or data element was deleted, you couldnot create a new tool or data element with that same name. Now,

New tools and data elements can be created withthe same name as those of deleted tools and dataelements. after a tool or data element has been deleted, a new one can be

created with the same name.

If the original is later restored, "(restored)" is appended to thename to avoid naming conflicts.

An icon appears next to the breadcrumb header at the top of thepage allowing the user to toggle the left navigation sidebar onand off. The interface remembers the your preference.

Left navigation sidebar is now collapsible

Fixed an issue where a user adding arguments to a rulecontaining an Adobe Target tool would see an incorrectlyformatted/broken UI.

Adding Target arguments breaks rule formatting.

October 15 2013




The breadcrumb display at the top of the page was wrapping incorrectly in Chromeon certain types of pages.

Breadcrumb wrappingincorrectly in Chrome

Rule pages will now show only 25 rules per page and will require users to "pagethrough" to see the full list. This is being done both for user experience and for

Rule page pagination

performance reasons (it's less stressful on the server to produce a list of 25 rulesvs. several hundred in the case of some of our clients).

A user can now filter the rule page by the name of the rule or the name of thirdparty tags contained within a rule.

Rule page filtering

Tools in dynamic tag management (Analytics, Target, AdLens, Audience Manager,Google Analytics, etc.) are now part of the approval workflow. New tools,

Tool approvals

modifications to existing tools, or removals of tools will require approval beforethey are published to production. Users can now add/modify/delete tools (previouslyusers of type "user" were not able to do this).

When looking at debug messages from the dynamic tag management engine, itnow says "Adobe Analytics" instead of "SiteCatalyst" for any messages relatingto the Analytics product and its associated rules.

Engine shows Analytics insteadof SiteCatalyst

See Also

Previous Release Notes for historical dynamic tag management release notes.

September 30 2013



New web properties used to require approval by a superadmin. In order to expediteprovisioning of new accounts, we have removed the requirement for this approvalso that new properties are automatically approved and instantly available.

New properties do not requireapproval

This pertains to the above story about automating new property approval.Superadmins used to have a section called "Pending Activation" on their dashboard;this story was to remove that section since it's no longer needed.

User views dashboard

Company admins now have the same ability as superadmins to copy rules acrossany companies/properties they have access to.

Enable rule copy for allcompany admins

When changing the type of a data element previously, it used to retain some ofthe old parameters specified by the user. We're now clearing all parameters and

Changing type of data elementretains previous values

ensuring that the library only contains whatever parameters are relevant to thecurrently selected type.



Added the ability to click a "Resend" link in the Users tab for a company in casea user didn't receive their invitation e-mail for some reason. (Previously this requiredrevoking the invite and recreating it from scratch)

company admin resendsinvitation email

The "linker link" rule for Google Analytics was not emitting a selector to the libraryby default, so it was trying to attach linker link functionality to all clicked pageelements. We're now correctly defaulting it to "a" (all links).

Default selector for linker linkrule not being emitted to library


Contact and Legal InformationInformation to help you contact Adobe and to understand the legal issues concerning your use of this product anddocumentation.

Help & Technical Support

The Adobe Marketing Cloud Customer Care team is here to assist you and provides a number of mechanisms bywhich they can be engaged:

• Check the Marketing Cloud help pages for advice, tips, and FAQs• Ask us a quick question on Twitter @AdobeMktgCare• Log an incident in our customer portal• Contact the Customer Care team directly• Check availability and status of Marketing Cloud Solutions

Service, Capability & Billing

Dependent on your solution configuration, some options described in this documentation might not be available toyou. As each account is unique, please refer to your contract for pricing, due dates, terms, and conditions. If youwould like to add to or otherwise change your service level, or if you have questions regarding your current service,please contact your Account Manager.

Feedback

We welcome any suggestions or feedback regarding this solution. Enhancement ideas and suggestions for theAnalytics suite can be added to our Customer Idea Exchange.

Legal

© 2016 Adobe Systems Incorporated. All Rights Reserved.Published by Adobe Systems Incorporated.

Terms of Use | Privacy Center

Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems Incorporated in theUnited States and/or other countries. A trademark symbol (®, ™, etc.) denotes an Adobe trademark.

All third-party trademarks are the property of their respective owners. Updated Information/Additional Third PartyCode Information available at http://www.adobe.com/go/thirdparty.

244Contact and Legal Information

http://helpx.adobe.com/marketing-cloud.html

https://twitter.com/AdobeMktgCare

https://customers.omniture.com/login.php

http://helpx.adobe.com/marketing-cloud/contact-support.html

http://status.adobe.com/

https://my.omniture.com/login/?r=%2Fp%2Fsuite%2Fcurrent%2Findex.html%3Fa%3DIdeasExchange.Redirect%26redirectreason%3Dnotregistered%26referer%3Dhttp%253A%252F%252Fideas.omniture.com%252Ft5%252FAdobe-Idea-Exchange-for-Omniture%252Fidb-p%252FIdeaExchange3

https://marketing.adobe.com/resources/help/en_US/terms.html

http://www.adobe.com/privacy/policy.html

http://www.adobe.com/products/eula/third_party/

Date post:	12-Dec-2016
Category:	Documents
Upload:	vodan
View:	238 times
Download:	2 times

Dynamic Tag Management Product Documentation

Documents