Adobe Marketing Cloud Dynamic Tag Management Product Documentation

Transcription

1 Adobe Marketing Cloud Dynamic Tag Management Product Documentation

2 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 Dynamic Tag Management Product Documentation

3 Contents 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 General Library Management Global Variables Page Views and Content Link Tracking Referrers and Campaigns Cookies Customize Page Code FAQ for Adobe Analytics Release - July Manually implement Adobe Analytics (legacy) Add Adobe Audience Manager Tool Add Adobe Media Optimizer Tool Media Optimizer Rule Example Add Adobe Target Tool Library Management - Adobe Target Last updated 1/2/2018 Dynamic Tag Management Product Documentation

4 Global Parameters - Adobe Target Mbox rule example for Dynamic Tag Management Add Google Analytics Tool Call Google Analytics Objects in DTM Using Scripts Add Google Universal Analytics Tool Call Google Universal Analytics Objects in DTM Using Scripts Add Nielsen Tool Insert third-party tags Object References to Handle Cookies Data Elements Create a data element Rules Event-Based Rules Example Page Load Rules Example Page Load Rules - Advanced Load Order for Rules Create new rule Create conditions for event-based rules Create conditions for page-load rules Create conditions for direct-call rules Set up actions for the condition to trigger Test unpublished rules for Akamai hosting Test rules for Library Download or FTP Rule Conditions and Functions Migrating to Dynamic Tag Management Migrating from Adobe Tag Management Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping Dynamic Tag Management Object Reference Last updated 1/2/2018 Dynamic Tag Management Product Documentation

5 Contents Frequently Asked Questions How Do Tag Management Systems Improve Page Load Speed? Adobe Cloud Platform Launch FAQ Resources Troubleshooting Chrome Warning on 2G Networks Dynamic Tag Management Plugins Search Discovery Plugins Disruptive Advertising Debugging Plugin Tagtician Debugging Plugin Documentation Updates Previous Release Notes Contact and Legal Information Last updated 1/2/2018 Dynamic Tag Management Product Documentation

6 Dynamic Tag Management Product Documentation 6 Dynamic Tag Management Product Documentation Dynamic Tag Management (DTM) lets you manage your Adobe Marketing Cloud solutions and other tags across all of your sites, regardless of your number of domains. Last Updated: November 14, 2017 Getting Started & Popular Topics Add Adobe Experience Manager ContextHub Tool Best Practices for Getting Started with Adobe Dynamic Tag Management (New) Best Practices for Implementing Adobe Target using Dynamic Tag Management (New) Request access Frequently asked questions (FAQ) Troubleshooting What's New and Release Notes Launch, by Adobe Launch is the next-generation of tag management capabilities from Adobe. Launch gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences. Release Notes for Dynamic Tag Management Current release notes and known issues for dynamic tag management. Marketing Cloud ID Services settings Videos DTM Demo Videos Plugins Dynamic Tag Management Plugins Community Resources Solution Overview Marketing Cloud Forum Adobe Marketing Cloud Community Idea Exchange Adobe Training and Tutorials Featured Solutions Center Digital Marketing Blog #Dynamic Tag Management Twitter If you have questions about dynamic tag management you can also tweet us with the hashtag #DTM. 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 automatically manage your report suites accounts and AppMeasurement 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.

7 Dynamic Tag Management Product Documentation 7 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 product documentation topics. Contact Adobe Global Services for help with an implementation. Contact your Adobe Account Manager to find out more about professional services.

8 Release Notes for Dynamic Tag Management 8 Release Notes for Dynamic Tag Management Release 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 Feature AEM ContextHub Tool Description 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, even for websites that do not use AEM. See Add Adobe Experience Manager ContextHub Tool. dataelementchanged event The dataelementchanged event lets you select a specific data element to use as a trigger. 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: Resource Documentation Updates Description View detailed information about updates to this guide that might not be included in these release notes. Previous Release Notes View information about new features and enhancements in previous releases of Dynamic Tag Management. Marketing Cloud Release Notes View the latest release notes for the Adobe Marketing Cloud solutions.

9 Dynamic Tag Management Overview 9 Dynamic Tag Management Overview Dynamic tag management lets marketers quickly and easily manage tags and provides innovative tools for collecting and distributing data across digital marketing systems. Dynamic tag management also enables responsive delivery of user-specific content providing new levels of agility and control to companies seeking to thrive in today s fast paced digital marketplace. This section contains the following information: 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 customers and prospects and the online spaces they inhabit and that s just the beginning. Marketers must then deliver content while measuring its engagement and effectiveness all the way through the conversion funnel and beyond. To accomplish this, marketers have historically needed to rely upon JavaScript tags to implement their strategies and programs on their websites. For the most part, tagging sites and other online experiences has been the domain of IT, subjecting marketing strategy to IT process and prolonged implementations based upon technical release schedules and resource availability. In addition, as the technologies and tools used by marketers to implement digital strategies and deliver consumer experiences become more sophisticated, the technical requirements associated with installing and managing these tools continues to grow. These factors are hampering marketers ability to quickly adapt to the fast-paced, dynamic digital marketplace and compromising 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 optimize digital 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, data management, and rule building, but also provides an intuitive capability that maps directly to marketing scenarios and user experiences. This approach makes it easier for marketers to develop digital marketing strategies and quickly implement them without dealing with potentially frustrating IT projects. To allow marketers to deliver the right message or collect the right data for any given scenario, this robust capability identifies specific users and audience segments on the site to enable instantaneous delivery of segment-specific content and to generate specific experience-based reporting. Dynamic tag management is offered to Adobe Marketing Cloud customers as an included, value-add feature. Adobe is committed to keeping the dynamic tag management capability open and will continue to develop features that allow 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.

10 Dynamic Tag Management Overview 10 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 to recommend, 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 separate rules 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 Adobe and third-party tags. Now, you have more control and flexibility to optimize almost anything online, all while reducing your dependency on IT resources. What Is Adobe DTM - Intro Time: 1:05 By the end of these videos you should be able to: Explain what DTM is Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support? What Is Adobe DTM - Background Time: 3:05 By the end of these videos you should be able to:

11 Dynamic Tag Management Overview 11 What Is Adobe DTM - Background Time: 3:05 Explain what DTM is Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support? What Is Adobe DTM - Scope of Usage Time: 1:33 By the end of these videos you should be able to: Explain what DTM is Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support? What Is Adobe DTM - Top Down Approach Time: 3:53 By the end of these videos you should be able to: Explain what DTM is Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support? What Is Adobe DTM - Hosting Options Time: 2:43 By the end of these videos you should be able to: Explain what DTM is

12 Dynamic Tag Management Overview 12 What Is Adobe DTM - Hosting Options Time: 2:43 Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support? What Is Adobe DTM - Tag Support Time: 1:18 By the end of these videos you should be able to: Explain what DTM is Explain its position in the market Explain the "top down" approach Explain the importance of our library hosting options What tags does DTM support?

13 DTM Demo Videos 13 DTM Demo Videos A series of short videos to demonstrate Adobe Dynamic Tag Management features. DTM Demo Part 1 - Overview and Set Up Basics Time: 4:39 DTM Demo Part 2 - Analytics Tool Setup Time: 4:54 DTM Demo Part 3 - Data Elements Time: 3:27 DTM Demo Part 4 - Page Load Rules Time: 10:38 DTM Demo Part 5 - Event and Direct Call Rules Time: 6:59 DTM Demo Part 6 - Version Control & Governance Time: 4:45

14 Getting Started 14 Getting Started Information for new users of Dynamic Tag Management. This section contains the following information: 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. Please contact your Adobe account team and ask for access to Dynamic Tag Management. Your account team will use our internal Provisioning Hub tool to grant access. You should receive your login credentials within one to two business days. If you have access to the Adobe Marketing Cloud, you can also request access to dynamic tag management from the Tools menu. Note: Administrators, see Getting Started in the Marketing Cloud if you need access to the Marketing Cloud. Logging In Browse to Getting Started Tasks The steps in the following table help you get up and running with Dynamic Tag Management: Step Getting Started Tasks Location Description Create a web property. Web Properties tab on the Dashboard A web property is a library of rules and one embed code. A web property can be any grouping of one or more domains and subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template and you want to track the same assets on all of these websites.you can apply one web property to multiple domains. For general information about web properties and best practices, see Web Properties. To get started, see Create a web property.

15 Getting Started 15 Step Getting Started Tasks Location Description Configure your hosting options. Embed tab Dynamic Tag Management provides a number of options to host the required JavaScript files: Akamai Self-hosting: FTP Delivery Self-hosting: Library Download See Embed Code and Hosting Options. Add header and footer code to each managed page. Embed tab Dynamic Tag Management allows you to precisely time the loading of JavaScript and page content in your page.you can 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 you can test your changes in your staging environment before pushing changes to your production environment. See Header and Footer Code. Deploy tools for solutions. Overview tab Tools let you quickly integrate Adobe Marketing Cloud solutions on your site. Tools go beyond a basic tag, because they provide additional configuration options. A tool corresponds to Adobe solutions like Analytics and Target, as well as Google Analytics. After you add a tool to a property, it is available for inclusion in a rule. See Tools. Create data elements. And Create rules, conditions, and actions. Rules tab Data elements are the building blocks for rules. Data elements let you create a data dictionary (or data map) of commonly used items on a page, regardless of where they originate (query strings, URLs, or cookie values) for any object that is contained on your site. You use data elements to build a data layer that can be used in rules for Analytics and other data collection tools. Rules can be triggered at page load or when a specific event occurs. Dynamic Tag Management provides a powerful conditioning interface that provides granular control of when tags fire. To get started, you should set up a basic page-load rule with no conditions to collect analytics data on all pages. For more information, see Data Elements and Rules.

16 Getting Started 16 Step Getting Started Tasks Location Description Publish tools and rules to the production server. After a rule is created, it is funneled through a multi-step approval process before it is published to a production environment. See Rules. Planning for Dynamic Tag Management Dynamic tag management is an evolution of tag management, designed around the mapping of user interactions to marketing technologies. Your tags and marketing tools are best used when reacting to visitors (or segments of your 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 interactions result 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 the globe have extensive experience deploying dynamic tag management and helping transform your organization's productivity, 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 above of Internet Explorer. The DTM library supports the latest version of Safari, Chrome, and Firefox, as well as version 8 and above of Internet Explorer. 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: Role Users Description Create and test rules.

17 Getting Started 17 Role Approvers Publishers Administrators Description Review and approve rules, making approved states of rules publishable. Publish rules to the production site. Only approved rules are published. Create and manage users, as well as inheriting rights from the three preceding roles. 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 funneled through the approval process. This process ensures that only approved rules and rule revisions are published to your live site. This approval process also retains all past and present revision information. This retention makes it easy to follow a rule s history 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 the user interface, opt-out notifications, and password changes. 1. In the upper right corner of the dynamic tag management interface, click 2. Edit the fields as necessary: > Account Settings. 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 code in 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 selected language. Address: Specify your address. You can add multiple addresses separated by commas. Opt Out of All Notifications: Opt out of all notifications when one of your web properties is published. By opting out of notifications, you will no longer receive publish request, property published, note, or approval notifications. However, you will continue to receive other notifications.

18 Getting Started 18 Current Password: If you want to change your dynamic tag management password, specify your current password 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 tag management includes two types of JavaScript libraries: Staging Library: Every change you make in the Management Application is immediately updated to use on the staging 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 included in the production library. See Publish Workflow. DTM Basics: Architecture Time: 2:38 By then end of this video you should be able to: Describe the basic elements of 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 on DTM, 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 collecting and distributing data across digital marketing systems. DTM also enables responsive delivery of user-specific content-providing new levels of agility and control to companies seeking to thrive in today's fast-paced digital marketplace.

19 Getting Started 19 In addition to this Best Practices Guide, the following resources are available to help you get the most out of Dynamic Tag Management: Resource Dynamic Tag Management Product Documentation Details In-depth information and step-by-step instructions about how to use Dynamic Tag Management. Getting Started Guide Information about how to start using Dynamic Tag Management. 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 This section contains the following information: 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 companies to which you have access.

20 Getting Started 20 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 of the 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 only required fields when configuring a web property are Name and URL, which can be changed at a later time if needed.

21 Getting Started 21 Admin-level users can also manage and provision users from the company overview page via the Users and Groups tabs. 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 the main 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 of these integrations is uniquely designed to make configuration and deployment of that particular solution easier.

22 Getting Started 22 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.

23 Getting Started 23 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 condition indicates the scenario in which the rule will fire and the trigger indicates the item(s) that will execute when the rule fires. 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 a certain 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 on load of certain pages on my site, I would use a page-load rule.

24 Getting Started 24 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 the Javascript / Third Party Tags modal. Other trigger modals are enabled in rules when tools are added to the property. For example, if my property contains an Adobe Analytics tool and a Google Universal Analytics tool, the property rules will contain optional trigger modals for these tools. Each tool modal offers easy methods to customize a trigger for that particular tool.

25 Getting Started 25 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 enables those data points to be easily captured and leveraged within rules and tools in DTM.

26 Getting Started 26 Workflows An important concept in DTM is the idea of a single web property having both a staging library and a production library. The staging library contains all of the rules, tools, and data elements configured in the web property. The production library 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.

27 Getting Started 27 Navigation: Property Overview > History tab After an item is approved, it becomes available in the Unpublished Changes queue 0n the History tab. After an item is published, it becomes available in the production library. This separation of libraries and associated workflow allows for more effective testing in staging without affecting production.

28 Getting Started 28 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 DTM library 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 the property.

29 Getting Started 29 Notice there's one embed code for staging and one for production. This is how DTM differentiates between the staging and production libraries discussed above. When the staging embed code is installed, the staging library loads. 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 loads automatically on each page load. Leverage the DTM Switch Plugin to test in the web console. This helps you understand what DTM is doing on the page and allows you to locally switch to the staging library for more effective testing. For more information, see Search 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. This content was built in partnership with This section contains the following information: Architecture Hosting Architecture The primary components of the DTM technical architecture include the web management application, the staging and 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 DTM implementation. This is where you'll create and configure tools, rules, and data elements and manage the deployment of these configurations to your site(s).

30 Getting Started 30 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. These libraries are generated by the web application and contain the unique set of configurations in that web property.

31 Getting Started 31 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 environments or for local production testing via the DTM switch plugin.

32 Getting Started 32 For more information about the DTM switch plugin, see Search Discovery Plugins in the Dynamic Tag Management Product Documentation. The production JavaScript library contains only tool, rule, and data element configurations that have been approved and 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 comparison and use-case examples to help facilitate this decision. Akamai Advantages Standard deployment method Disadvantages Lack of control over file delivery

33 Getting Started 33 Advantages Disadvantages 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 globally distributed Akamai network SFTP Self hosting Complete control over file delivery Upfront configuration required More secure option: SSH file transfer Greater dependence on IT Automatic file updating Library Download Self hosting Complete control over file delivery Upfront configuration required Most secure hosting option: AES 256 Greater dependence on IT bundle encryption Additional configuration required for automatic file updating Use Case Examples Scenario I prefer to involve IT as little as possible and have a need for a reliable file hosting method outside of my own site infrastructure. I want to have complete control over file delivery in my production environment; however, speed and agility is more important than file control in my staging environment. Solution Leverage Akamai hosting in all environments. Leverage Akamai hosting in staging environments and FTP delivery in production environment. Certain sections of my site deal with highly confidential information. Security is the most important thing on these pages but isn't necessarily as important on other pages of my site. Leverage library download hosting on secure pages and Akamai hosting on non-secure pages. All hosting options are available to enable and configure on the Embed tab in your DTM property.

34 Getting Started 34 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 for that 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 it on your site. This code snippet should be placed in the head section of the site code as close to the opening tag as possible. Footer Code

35 Getting Started 35 The footer code is responsible for identifying the end of the page for timing control. This code snippet should be placed 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 deployment of the DTM JavaScript library. Note: Although you can use more than one hosting option, you must ensure that only a single embed code reference is included on any given page. Duplicative or improper placement of the embed code can result in unexpected library behavior. The following illustration show how the discussed DTM architecture components work together to effectively deploy and manage tools, tags, and scripts on your site.

36 Getting Started 36 For more information on hosting options, see Embed Code and Hosting Options in the Dynamic Tag Management Product Documentation. Planning Your Migration to DTM Information to consider as you plan your migration to Dynamic Tag Management (DTM) and best practices to help get your implementation started correctly. This content was built in partnership with This section contains the following information: 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 in planning 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 / scripts on your site(s).

37 Getting Started 37 Each web property is associated with one embed code that's responsible for loading the specific property configurations on your site(s). Users are managed at the company level but can be permissioned for each property with the exception of the Admin role. The Admin role is global and has full permissions for all properties in a company.

38 Getting Started 38 For more information on user roles, see Create and Manage Groups in the Dynamic Tag Management Product Documentation. 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 web properties. This type of configuration is most typical for large businesses with numerous sets of web entities that are run by various 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 following variables. 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 in one or many of the above variables. This type of setup most effectively accommodates each domain's needs while still allowing for easy duplication of cross-domain constants via the 'copy' functionality.

39 Getting Started 39 However, in cases where these variables are the same or very similar across domains, it may make more sense to have multiple domains within one web property. In these cases, this setup can reduce unnecessary duplication between properties. This same reasoning can be used for subdomain distribution. Use-Case Examples Scenario My business division manages several domains. We're deploying Adobe Analytics across all domains, but each domain has its own reporting suite and tracking needs. My business division manages several domains. We're deploying Adobe Analytics across all domains and use one global reporting suite to collect all of our data. Data sources between domains are very different due to variations in site code structure. My business division manages several domains. We're deploying Adobe Analytics across all domains and use a global reporting suite and global data layer to collect all of our data. The rest of our tools and tags are mostly consistent between domains and we're planning to have the same users manage the publish workflow. Solution Leverage one property for each domain. Leverage one property for each domain. Leverage one property for all domains. Migration Best Practices After determining the optimal company and property distribution, consider the following best practices as you begin your DTM migration. Process Workflow: Develop a systematic process for migrating existing page code into DTM to help ensure a smooth transition. It's generally recommended to start this process in lower-level staging environments and migrate code on a page-by-page or site section by site section basis.

40 Getting Started 40 This will allow you to fully vet DTM configurations before removing any pre-existing page code reducing the risk of implementation disruption. Working with IT: It's important to work with your IT team upfront to determine current processes and deployment cycles. This will help ensure proper and timely placement of the embed code and coordinated removal of effectively migrated page code. People Workflow & Governance: Another important concept is establishing a user workflow. Thoughtfully assigning user roles provides governance to the DTM workflow. User Role Create Rules Edit Rules Test Rules Approve Rules Publish Rules Create/Edit Users Create Property User Yes Yes Yes Approver Yes Yes Yes Yes Publisher Yes Yes Yes Yes Approver and Publisher Yes Yes Yes Yes Yes Admin Yes Yes Yes Yes Yes Yes Yes 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 Product Documentation. Migrating to DTM: A Closer Look at Adobe Analytics Whether your current Adobe Analytics implementation is deployed via on-page methods or via another tag management system, this section helps you understand your options as you migrate to DTM. This content was built in partnership with Phase 1: Quick Value Add Because migrating Adobe Analytics code can be a lengthy process, DTM offers a feature that allows you to augment your existing Analytics implementation without disrupting it. This content was built in partnership with This feature is called Page Code is Already Present and is located in the Analytics tools settings in your DTM property.

41 Getting Started 41 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 migrating any 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 AppMeasurement code and instantiate the s object.

42 Getting Started 42 Phase 2: Full Migration To take full advantage of the integrated Adobe Analytics functionality in DTM, a complete migration of Analytics code is recommended. This content was built in partnership with This migration should include all s object references in the page code and included scripts on pages where DTM is deploying 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 under Code Configuration.

43 Getting Started 43 If Page Code is Already Present from phase 1 is currently leveraged, you'll need to uncheck this option to reveal the Code Configuration options. This change will take effect only in staging so you can fully configure and vet the migrated code before pushing this change to production. The Custom configuration option is typically preferred as an initial migration approach because it allows you to reference 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.

44 Getting Started 44 With the Managed by Adobe option, DTM automatically provides and hosts the selected AppMeasurement base code 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 tool settings 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 leveraging these fields in place of custom code ultimately reduces the overall complexity of your implementation.

45 Getting Started 45 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 and conditional settings. Any code placed here will work in tandem with the hosted AppMeasurement code / s_code.

46 Getting Started 46 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. Rule Type Page-load rules Details Use to append variables to the default page view beacon on all or certain pages. Use Case Example: Sending a particular evar on load of my promotional page. Event-based rule Use to trigger a s.t() or s.tl() beacon on specific user interactions. Use Case Example: Sending a custom page view beacon with a particular event when a popover is enabled. Direct-call rule Use to trigger a s.t() or s.tl() beacon in scenarios when DOM event can't be detected. Use Case Example: Sending a s.tl() beacon with a particular event when a video is viewed. 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 migrate your 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 not yet been fully migrated. This flag can then be leveraged in the Customize Page Code editor in the tool settings to conditionally cancel the default DTM beacon on those pages by setting 's.abort = true'.

47 Getting Started 47 Please note that this approach only affects the Analytics tool beacon; rules configured to fire Adobe Analytics should be 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 specifically benefit your business. This content was built in partnership with The following sections contain more information: 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 your site easier through the use of a container tag.

48 Getting Started 48 A container tag is a single code snippet that when placed in your site markup is capable of triggering countless tags on 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 a straightforward, 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: Benefit Improved site performance Details With Dynamic Tag Management, marketing and analytics tags are moved from the markup of your site into the DTM library. This in itself reduces page load time as the DTM library is optimized for file compression and speed. However, performance is enhanced even farther through the use of the conditional controls 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 reducing the burden on page render. Increased control, decreased risk With less reliance on IT, you'll be able to deploy and manage tags on your watch. This means less commitment and risk in deploying vendor tags and increased agility to keep up with new tool / tag features. Plus, DTM has built-in features to ensure compliance with data-privacy policies and to prevent vendor tags from interfering with your site or leaking data to third parties. Work faster and more efficiently Dynamic Tag Management takes a behavior-centric approach and leverages comprehensive integrations and data-centralization to make tag deployment easy. The behavior-centric approach allows for countless tools / tags to be deployed at the same 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 Analytics and Google Analytics, eliminating the need for extensive custom code. Data elements centralize common data points, reducing code redundancy and optimizing data lookup time. Together these features save time and frustration so you can focus less on tag deployment and more on moving your business forward. Use Dynamic Tag Management for free Best of all, if you're an Adobe Marketing Cloud customer, Dynamic Tag Management is free.

49 Getting Started 49 Benefit Details Contact your Adobe Account Manager for details.

50 Web Properties 50 Web Properties A web property is a library of rules and one embed code. A web property can be any grouping of one or more domains and subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template, and you want to track the same assets on all of them. You can apply one web property to multiple domains. DTM Basics: Web Properties Time: 6:06 By then end of this video you should be able to: Explain what a web property is Set up a web property Understand the web property's relationship with the embed code and report suites This section contains the following information: 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: Consideration Data Best Practice For all of your websites, is the data you are going to collect very similar, somewhat similar, or unique? If the data you need to collect is similar across websites, it might make sense to group those sites into one web property to avoid duplicating rules or copying rules from one property to another. If your data collection needs are unique for each site, it might make sense to separate those sites in their own web properties. This method lets you control the data collection more specifically for each site, without using large amounts of conditional logic in custom scripts. For example, if 80 percent of the data you are collecting across your sites is the same, or similar, it makes sense to group those sites together into the same web property. If the data is unique for each site, it makes sense to put each site into its own web property. Variables Similar to data, for all of your websites, are the variables you are going to set in your Analytics and other tools very similar, somewhat similar, or unique?

51 Web Properties 51 Consideration Best Practice 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 common variables across your sites in just one web property. If your variable usage is unique for each site, it might make more sense to separate those sites into their own web properties so you can control the variables more specifically for each site without using large amounts of conditional logic in custom scripts. Tools, Tags, and Systems Are the tools, tags and systems you are going to deploy through dynamic tag management very similar, somewhat similar, or unique? If the tools, tags, and systems you are going to deploy through dynamic tag management are very similar across your sites, you might want to include those sites in the same web property. If you are deploying Adobe Analytics on only one site, and your other tools and tags are also unique to certain sites, you might want to create separate web properties 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-party tags and tools across your sites, that is a reason to group sites together. People For the individuals, teams, and organizations that are working in dynamic tag management, will they need access to all of your websites, some of them, or just one of your domains or sub-domains? The User Management features allow you to assign different roles to different people for all of your web properties, or on a per-property basis.the only role that includes all web properties within a dynamic tag management company account is the Admin role. If someone is an Admin, that person can perform administrative actions across all the web properties in that dynamic tag management company. All the other roles can be assigned on a per-property basis. You can even hide a web property from certain 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 so on. Using the flexible User Management features and web properties, you can create a configuration that matches your workflow and processes. If the scenarios you are tracking, the data you are collecting, the tools you are deploying, and the variables you are setting are similar across all or some of your domains and subdomains, it is easier to have those domains and subdomains grouped into the same web property in dynamic tag management. If those are unique for each domain and subdomain, it is easier to have those domains and subdomains in their own web property. If you choose to group domains and subdomains in a single property now, you can always change your mind and later create several web properties.

52 Web Properties 52 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 are not 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 several report suites in Analytics. You can set multi-suite tagging, or you can use conditional logic that sets s.account according 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 list of report suite IDs in the user interface in dynamic tag management, in the Account Numbers fields, on the Adobe Analytics 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 tag management. 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 contains many web properties, one for each domain. Some have a Company that contains several web properties, one for each type of site they manage. For example, you might have three web properties within your Company account where one contains all of your blog 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 subdomains you want included in a particular web property would have the same Embed Codes in the page templates when 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 entities into one Company account and split the domains / subdomains into different web properties within that Company account. 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 put multiple 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 to separate unique data collection and tracking needs that only apply to individual domains, subdomains, or subsets of domains / subdomains. What is the approach recommended by Adobe: one or separate companies?

53 Web Properties 53 Most clients use one Company account that contains all of their web properties. Information on this page can help you 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 library files from getting rebuilt (i.e. the staging and production libraries remain in the state they were in when the property was deactivated). If you deactivate a property and expect a tool or rule to stop firing, you should deactivate those item(s) in the property and 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 and Manage 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:

54 Web Properties 54 Element Name URL This site spans multiple domains Description The name of your property. The base URL of the property. You can add and remove domains if you want visitor data to persist between domains. This setting lets you specify how you would like to track traffic moving between your associated subdomains or domains. Note: If you do not intend to integrate an analytics tool, this step is unnecessary and does not affect processing. 3. (Optional) Configure Advanced Settings. Element Allow Multi-Rule Approvals Enable Selective Publish Tracking Cookie Name Tag Timeout Description Allows multiple rules for this property to be approved at one time. (The default approval allows only single-rule approval.) Specifies whether to allow users to selectively publish approved rules. (This is the default option.) Overrides the default tracking cookie name. You can customize the name that dynamic tag management uses to track your opt-out status for receiving other cookies. Specifies how long dynamic tag management waits for a tag to fire before timing out. Because of how dynamic tag management works, don't worry about this being a high number, as we have other, better methods of ensuring that slow tags do not affect the user experience. Anchor Delay Specifies how long dynamic tag management waits for tags to fire on clicked links before moving to the next page. The default value is 100 milliseconds. Longer delays improve tracking accuracy. Adobe recommends a delay of 500 milliseconds or less, which the user will not perceive. Dynamic Tag Management will wait up to the time specified, but if the beacon fires sooner, the delay is cut short. (That is, user won't always wait the full length of the delay.) 4. Click Create Property.

55 Web Properties 55 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 cannot be undone. 1. Navigate to the Overview page for the desired property. 2. Click Edit Property > Remove Property, then confirm the removal of the property.

56 Users and Permissions 56 Users and Permissions You 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 are automatically granted permissions to a new property. Note: If you link your DTM company to the Marketing Cloud, you must manage your users in the Marketing Cloud. This section contains the following information: Manage Users You can invite users to the Adobe Marketing Cloud with the Adobe Admin Console (the preferred method) or you can 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 Marketing Cloud. Important: DTM accounts created after April 5, 2016 are managed by administrators using the Adobe Admin Console in the Adobe Marketing Cloud. To manage other users, the DTM administrator must be a Marketing Cloud administrator in the Adobe Admin Console. For more information, see Delegate Administrative Roles to Users in the Marketing Cloud 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 Cloud using 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 not manage users with the Adobe Admin Console (the company was provisioned before April 5, 2016), that user can be 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 Cloud and 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 must create a new address to use for authentication. Recommended best practice is to provision new users using the Adobe Admin Console. However, if there is any chance that these new users (consultants or agency representatives, for example) will need to access an account provisioned using the legacy process, you should provision that user in DTM and then link the account to the Marketing Cloud. The provisioning process in the Adobe Admin Console is forward-looking and not backwards compatible.

57 Users and Permissions 57 DTM Basics: User Group Management Time: 5:05 By then end of this video you should be able to: Understand user management Understand roles Understand default user groups Understand how to add users to a group Understand how to create a group 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 the note 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.

58 Users and Permissions 58 After the user is invited, they receive an invite to the Marketing Cloud. DTM Basics: User Administration Time: 2:55 By the end of this video you should 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 the note in Manage Users. Invite New Users to DTM using the Legacy Provisioning Process 1. From your company dashboard, click Users.

59 Users and Permissions (Conditional) Click Restrict to Marketing Cloud to force all users in the company to log in to dynamic tag management 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 have your DTM account linked before activating this option, otherwise you will essentially lock yourself out of DTM. If this option is selected, all users for the company must authenticate via the Marketing Cloud and link their DTM accounts. If users log in to DTM using legacy/company credentials, they will be able to view their company account, but they won't be able to access it. A message will display informing them that they must log in via the Marketing 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 user management 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. For more information about the Marketing Cloud, see the Marketing Cloud and Core Services Product Documentation. 3. Click Invite User. 4. Enter the user's 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 the user group level, so all users in the group inherit the group permissions, including access to specific properties. 6. Click Invite User. An message with a link is sent to the user. This lets the user select a password and complete the setup process. Until the user completes this setup process, they appear in the Invited Users section on the Users tab. They move 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 Tag Management. DTM Basics: User Group Management Time: 5:05 By then end of this video you should be able to: Understand user management Understand roles Understand default user groups

60 Users and Permissions 60 DTM Basics: User Group Management Time: 5:05 Understand how to add users to a group Understand how to create a group 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 Management property access. This section contains the following information: 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, then save the product configuration.

61 Users and Permissions 61 In order for the group to display in the list, it must be added in the Adobe Admin Console, as explained in Manage Web 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 by clicking into the Users tab. Adding a user creates or updates the user in DTM and assigns the user to the appropriate DTM group. Important: Adding an Admin allows the user to manage the group in the Marketing Cloud. It does not add the 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 modify the Nielsen tool for the Geometrixx Demo Test web property.

62 Users and Permissions Select the Default Role for the user group.

63 Users and Permissions 63 This role can be defined by property if multiple properties are present in the company, as shown in the following illustration: 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 of the user groups that are set up within the account. Permissions are set at the user group level, so all users in the group inherit the group permissions. To access the Groups page, from your company dashboard, click Groups. This section contains the following information: Default Roles Migrated Groups for Existing Customers Default Roles Dynamic tag management has five different user roles with varying sets of permissions:

64 Users and Permissions 64 The following table illustrates the permissions that each default role inherits: User Role Create Rules Edit Rules Test Rules Approve Rules Publish Rules Create/Edit Users Create Property User Yes Yes Yes Approver Yes Yes Yes Yes Publisher Yes Yes Yes Yes Approver and Publisher Yes Yes Yes Yes Yes Admin Yes Yes Yes Yes Yes Yes Yes Migrated Groups for Existing Customers In addition to these default roles, if you are an existing dynamic tag management customer, you might see one or more migrated legacy groups with appended date and time stamps. For example, Group :19:57:884. If you are an existing customer and certain users have the User role for every property, these users are automatically migrated to the new User group. However, if other users have the User role for some properties and the Publisher role for other properties, they will be put into a migrated group with a date and time stamp. A legacy group will be created for each scenario in your system. In our testing, we have seen some companies with as many as ten legacy groups. Another example is if you have users who have not accepted invitations to join your dynamic tag management company in the past and there are no matching default groups. These users, after accepting the invitations, will be added 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.

65 Users and Permissions 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 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 addresses are removed from the drop-down list. Each user will receive an message with a link to accept group membership. Users will not display in the list 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, 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 a user has the User role for some properties and the Admin role for other properties, Admin displays in the list, as shown below: You can click Revoke to rescind an invitation for a specific user or click Resend to send the invitation message to 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. 1. From your company dashboard, click Groups. 2. Click Create New Group.

66 Users and Permissions Fill in the fields: Name: (Required) Specify a descriptive name for the group. Description: Specify an optional description for the group. The description displays on the Groups page and can 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 settings in 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 settings in 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. User Role Create Rules Edit Rules Test Rules Approve Rules Publish Rules Create/Edit Users Create Property User Yes Yes Yes Approver Yes Yes Yes Yes Publisher Yes Yes Yes Yes Approver and Publisher Yes Yes Yes Yes Yes Admin Yes Yes Yes Yes Yes Yes Yes Note that if you add users to the Approver group and to the Publisher group, those users have the same roles as 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 role for each property, as needed. In the following illustration, the default role for Property1 is "User" and the default role for Property2 is "Approver."

67 Users and Permissions 67 A use-case for having different roles for each property is in an agency in which you might want some users to have access to certain properties, but not have access to other properties. Another benefit of having groups with different access to varying properties is if you have users who come and go from the agency. You can simply delete an existing user from the group and add a new user without spending considerable time setting up access rights to different properties. If you specify different default roles for each property, ensure that you name the group with a descriptive name and 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 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 addresses are removed from the drop-down list. Each user will receive an message with a link to accept group membership. Users will not display in the list until they accept invitations. 6. Add additional users as needed. 7. Click Save Group.

68 Users and Permissions 68 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. 1. From your company dashboard, click Groups. 2. Click Edit next to the desired group. 3. Edit the desired fields, as explained in Create a New Group. 4. Click Save 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. 1. From your company dashboard, click Groups. 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 the Admin group. 5. Click Save Group. Frequently Asked Questions about Users and Permissions List of Frequently Asked Questions (FAQs) about users and permissions in the Marketing Cloud and in Dynamic Tag Management. I added a user using the Admin tab for the DTM product in the Adobe Admin Console, but that user was not added 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 edit the Product Configuration Groups in the Adobe Admin Console. In order to add the user to DTM, they need to be 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 on the Users tab. My DTM account was created prior to April 5, 2016 and I want to migrate my users to log in through the Marketing Cloud. How do I accomplish this? Contact Customer Care to restrict login access to the Marketing Cloud.

69 Users and Permissions 69 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 > Link Account. 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 you receive 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 address must be used. This is only the case if the account was created via marketing.adobe.com and has never logged in via dtm.adobe.com. This scenario occurs when the invite comes from a legacy company that 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.

70 Embed Code and Hosting Options 70 Embed Code and Hosting Options Information about the various hosting options in dynamic tag management: Akamai, self-hosting FTP delivery, and self-hosting library download. Important: For a successful implementation, it is critical that you follow these instructions as they appear in Adobe 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 codes elsewhere in your markup, or using asynchronous methods to append the embed codes, are not a supported implementation of dynamic tag management. An unsupported implementation will yield unexpected results and prevent Customer Care and Engineering from assisting with your implementation. Including multiple embed codes on a single page is not supported, as it can cause conflicts. This section contains the following information: Hosting Workflow Hosting Options Hosting Workflow The following illustration shows the hosting workflow in dynamic tag management:

71 Embed Code and Hosting Options 71 Hosting Options You can deploy dynamic tag management using one or more of the following options, found on the Embed tab: Hosting Option Description Implementation Akamai (migrated from Amazon S3) The simplest hosting option to implement. Globally distributed delivery network. Adds additional third-party infrastructure dependencies (DNS lookup, Akamai availability). See Akamai for information about migrating from Amazon S3 to Akamai. 1. Dynamic tag management generates custom JavaScript libraries. 2. Dynamic tag management exports the custom JavaScript libraries to Akamai. 3. The target website references the Akamai-hosted dynamic tag management libraries directly at the page level. Amazon S3 Note: After July 31, 2015 Adobe will no longer support Amazon S3.Your dynamic tag management libraries on Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made in dynamic tag management will no longer be reflected in these files. Self-hosting: FTP Delivery 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-party Akamai hosting is a world-class option as well. A push approach, whereby dynamic tag management exports custom JavaScript libraries directly to the web content server host via the FTP protocol. This solution requires an FTP server and credentials to be available on the web content server to publish changes to the custom dynamic tag management libraries. For more detailed information, see FTP. 1. Dynamic tag management generates custom JavaScript libraries. 2. Dynamic tag management exports the custom JavaScript libraries to host server via FTP. 3. The target website locally references the custom dynamic tag management libraries. Self-hosting: Library Download A pull approach, whereby the application exports custom JavaScript libraries to Amazon S3. There, the libraries can be accessed by a hosted server-side process. 1. Dynamic tag management generates custom JavaScript libraries. 2. Dynamic tag management exports the custom JavaScript libraries to Akamai.

72 Embed Code and Hosting Options 72 Hosting Option Description Additionally, the libraries are available via web download directly from the dynamic tag management interface. This solution requires either a manual retrieval and publication of the dynamic tag management libraries or the creation of an automated process that pulls the libraries from Akamai onto the web content server. This approach takes the most time to set up, but is also the most secure and flexible option. For more detailed information, see Library Download. Implementation 3. Custom dynamic tag management libraries are manually or programmatically moved to the web content server. 4. The target website locally references the custom dynamic tag management libraries. You can expect improved performance and more control over security by hosting the FTP Delivery and the Library Download options on your CDN or infrastructure. DTM Basics: Library Hosting Options Time: 4:00 By then end of this video you should be able to: Explain the different hosting options 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: How do I choose a hosting option? Dynamic tag management creates and uses various JavaScript files that contain all the code needed to run the system. These library files can be hosted by Adobe, or they can be hosted on your own servers within your own Web architecture. The Library Download hosting option also allows you to self-host the library files. When an authorized dynamic tag management user makes a change in the software, our system writes those changes out to the library 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 the Library 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 the library 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

73 Embed Code and Hosting Options 73 change is made in dynamic tag management, the files you re hosting on your 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 the self-hosted options in your production environments. Or, you could use the Akamai option for any sites, domains, or subdomains hosted by one of your agency partners. These options give you more flexibility to host the library files according to your specific needs. What is your current policy regarding website content sources? The answer to this question helps determine whether the JavaScript library can be hosted on Akamai, pushed to the website file structure via FTP, or manually pulled into the file structure by a server-side process. Akamai FTP delivery Library download Can I use more than one dynamic tag management library hosting option at once? Yes, you can turn on and use any number of the hosting options and use different embed codes for different domains or subdomains. 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 the same time, you might use one of the self-hosted options, such as Library Download, 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 any page. What is your current website content deployment process? The deployment process affects how quickly changes can be deployed to the site from the dynamic tag management administrative interface. It also affects how long it takes to initially install dynamic tag management on the website. What is the current page-level markup and structure of the website? An understanding of the basic page-level markup and structural decisions on the website helps with the proper installation of dynamic tag management and the construction of rules within the administrative interface. Key items to identify include: Which JavaScript libraries are referenced within the <head> section of the 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 helpful in determining the appropriate hosting methodology.

74 Embed Code and Hosting Options 74 Akamai Akamai is the primary external hosting option. Akamai provides you with a reliable hosting experience and is the simplest option to implement. Akamai provides the greatest third-party infrastructure dependencies, such as DNS lookup, 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 on the Akamai architecture. This option allows you to install the Embed codes in your page templates and quickly get up 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 libraries on Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made 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-party Akamai 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 dynamic tag 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 redundant networks of load-balanced, geo-optimized nodes to serve content as quickly as possible to visitors wherever they are located throughout the world. Specifically, Akamai runs more than 137,000 servers in 87 countries within more than 1,150 networks. In terms of redundancy, Akamai does not just route from one server to another, Akamai routes from one node of servers to another node of servers as-needed. In other words, each node consists of multiple servers for redundancy within a node, 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 on visitor location, traffic load, and other factors so content is consistently served from the best local node for each visitor. 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 extremely unlikely that Akamai would be unavailable. Migrate from Amazon S3 to Akamai Migrate from Amazon S3 hosting to Akamai by replacing Amazon S3 code.

75 Embed Code and Hosting Options 75 Note: After July 31, 2015 Adobe will no longer support Amazon S3. Your dynamic tag management libraries on Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made 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 party Akamai 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 longer need Amazon S3 before turning it off. Akamai hosting in dynamic tag management functions independently of any Akamai hosting you currently use for 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 management user makes a change in the software, dynamic tag management writes those changes to the library files. When you

76 Embed Code and Hosting Options 76 host the library files on your servers with this option, dynamic tag management must get those changes to your servers. With the FTP Delivery hosting option, dynamic tag management connects to your system, using credentials and server locations you enter into the system, and delivers any changed files. In this way, whenever a change is made 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". This allows DTM to load hosted scripts from relative paths, giving you the ability to host your library without editing 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 development environments. Note: The staging code should go only into your staging or development environment. Production code should 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. Place it 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 tag management user 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 your servers. With the Library Download hosting option, dynamic tag management sends a ping (an HTTP post) to your system to let your servers know there has been an update to the library 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 are hosting on your servers can be updated automatically.

77 Embed Code and Hosting Options 77 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: Option Description Shared Secret Encrypts the dynamic tag management library during download. If you enter a shared secret, we use AES-256 to encrypt your.zip file using this passphrase. Deploy Hook URL The process of deploying dynamic tag management files to the server can be automated whenever there is an update. Create a script that is accessible via the specified public URL. If you enter a deploy hook URL, we make an HTTP POST to it every time we successfully update your bundle. The body of the post will include a payload containing the 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 any leading or trailing slashes. Dynamic tag management requires a domain and a path for HTTP or HTTPS for the production 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". This allows DTM to load hosted scripts from relative paths, giving you the ability to host your library without editing your path for each deploy. 5. Download the files from the specified URL for the respective environment (staging or production), and deploy them 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 development environments. Note: The staging code should go only into your staging or development environment. Production code should be placed on the live production site.

78 Embed Code and Hosting Options 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. Place it 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 page content on your site. You must install both the header and footer code on every page of your site, regardless of the hosting option used. DTM Basics: Embedding Code Time: 4:20 By then end of this video you should be able to: Understand the embedding elements Explain the difference between staging and production Not confuse embedding codes with the s.code Because dynamic tag management includes a snippet of code in both your header and footer, you can run rules at the beginning or end of a page. This ability allows you to implement testing tools and other technologies while retaining control over tracking your pages. Dynamic tag management creates staging and production embed codes you can use to test your changes in your staging environment before pushing changes to your production environment. Important: For a successful implementation, it is critical that you follow these instructions as they appear in Adobe 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 codes elsewhere in your markup, or using asynchronous methods to append the embed codes, or wrapping the embed codes in any way, are not a supported implementations of dynamic tag management. The embed codes must be implemented exactly as provided. An unsupported implementation will yield unexpected results and prevent Customer Care and Engineering from assisting with your implementation. Because dynamic tag management includes a snippet of code in both your header and footer, you can run rules at the beginning or end of a page. This ability allows you to implement testing tools and other technologies while retaining 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.

79 Embed Code and Hosting Options 79 Place the code as close to the <head> tag as possible. This code snippet should be placed on every page of your live production site. Note: Production embed code reflects only the published items in that property. However, embed code for 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 the instructions 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 the filename 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 and pasting from a formatted document.

80 Tools 80 Tools Tools let you quickly integrate Adobe Marketing Cloud solutions on your site. Tools go beyond a basic tag because they 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 Element Installed Tools Description Displays the installed tools. Tools are deployments of Adobe Analytics, Adobe Target, Google Universal Analytics, and so on. Add a Tool Displays the Add a Tool page. Available tools include the following: 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 Add a Tag You can access rules to add a tag and to determine when your tag will fire. You open the third-party tags section of your rule, paste your tag, and save the rule. See Rules. Assigned Users Displays users, addresses, and roles. Click Manage Users to add additional users and define their roles. 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, even for websites that do not use AEM. DTM customers often use data elements to map to their websites' data layers. For example, the data layer might include information that a user is looking at a particular product or has placed an item into the shopping cart. DTM can use this information in rule conditions and actions in a number of ways. This includes the sending of data to Analytics 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 the top of the page. Other data layers are dynamic or asynchronous and change frequently as the page changes. In the past, 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 data layer changes, loads somewhere other than the top of the page, or is modified as the page changes.

81 Tools 81 As an example, suppose a customer places an item in the shopping cart and then removes that item. If the page doesn't refresh as the data layer changes DTM will not recognize the change without a custom code addition. The AEM 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 ContextHub data elements in conjunction with previously released conditions, such as Data Element Value. This allows users to manage data layer values on a page load, or combine the Data Element Value condition with the dataelementchanged 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 can customize 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.

82 Tools Fill in the fields: Element Use Default ContextHub Data Layer Description Use the AEM ContextHub format. With this option selected, DTM references the default ContextHub schema for this integration. If you have made changes to your ContextHub schema, or want to use a different data layer, use the customized option. Customize ContextHub Data Layer Use a custom format that maps to the data layer structure of any website, even if it does not use AEM. This option lets you edit your data layer schema. By default, it populates the edit window with the default ContextHub data layer, where you can make changes or completely replace it with your code. Open Editor If you choose the Customize ContextHub Data Layer option, you can use the editor to insert your custom code. Add a Note Add any notes regarding this implementation. 5. Click Save Changes.

83 Tools 83 Data Layer Management Using the ContextHub Tool The Dynamic Tag Management (DTM) AEM ContextHub tool can be used for both ContextHub and generic data layer implementations. The ContextHub data layer schema is loaded by default in the tool and provides a simple integration with Adobe Experience Manager (AEM) ContextHub stores. Examples for both the default ContextHub implementation and a custom generic data layer implementation are provided. This section contains the following information: 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. This event 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 during a 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 returned in a data element custom script will not work correctly. Cookies, CSS selectors, and URL parameters also produce unexpected 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. Although the 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-based monitoring 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 the Dynamic Tag Management configuration.

84 Tools 84 The ContextHub data layer will be loaded on a test Adobe Experience Manager (AEM) website, but ContextHub can be used independently of AEM. Contact your Adobe representative if you would like to use ContextHub independently 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 layer through 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. The following sections contain more information: 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. 1. Click Web Property Name > Overview > Add a Tool > AEM ContextHub. 2. Specify a descriptive name for the tool. 3. Click Create Tool to display the AEM ContextHub Settings page.

85 Tools 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 option if 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 the ContextHub stores, there are additional functions available with this data layer that are not available in the simple Javascript 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 custom data layer is a modification of the ContextHub schema be sure to add ContextHub in the Data Layer Root field.

86 Tools 86 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. 6. Click Save Changes. 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.

87 Tools 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 be defined 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.

88 Tools From the Event Type drop-down list, select dataelementchanged. 6. Select the data element that was created in the previous section (total_price).

89 Tools 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 the rule 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 settings are considered in the match. For example, selecting the Force Lowercase Value option in the data element

90 Tools 90 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).

91 Tools 91 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 the Dynamic 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 the data layer through DTM. Otherwise Javascript warnings might occur because certain data layer values may not be available. This section contains the following information: 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

92 Tools 92 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. 1. Click Web Property Name > Overview > Add a Tool > AEM ContextHub. 2. Specify a descriptive name for the tool. 3. Click Create Tool to display the AEM ContextHub Settings page. 4. Select Customize ContextHub Data Layer to modify the schema.

93 Tools 93 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.

94 Tools 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": " "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.

95 Tools 95 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. 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 be defined 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.

96 Tools 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.

97 Tools Click Create New Rule. 3. Name the rule. In this example, name the rule "find_a_friend." 4. Expand the Conditions section.

98 Tools From the Event Type drop-down list, select dataelementchanged. 6. Select the data element that was created in the previous section (my_friend).

99 Tools 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 the rule 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 settings are considered in the match. For example, selecting the Force Lowercase Value option in the data element

100 Tools 100 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 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 ).

101 Tools 101 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 once again display. Add Adobe Analytics Tool You can deploy Adobe Analytics (Standard and Premium) using dynamic tag management by creating the Adobe Analytics tool and configuring the page code either automatically or manually. The automatic method is recommended for most users. Note: For improved visitor tracking, it is strongly recommended that you enable Marketing Cloud ID Service. This section contains the following information: Add an Adobe Analytics Tool Edit an Existing Adobe Analytics Tool Enabling Adobe Analytics Premium

102 Tools 102 Add an Adobe Analytics Tool 1. Click Web Property Name > Overview > Add a Tool > Adobe Analytics. 2. Fill in the fields: Element Tool Type Tool Name Configuration Method Description The type of tool, such as Adobe Analytics. A descriptive name for this tool. This name displays on the Overview tab under Installed Tools. Automatic (Recommended): Use dynamic tag management to manage the configuration. This method enables automatic synchronization of Adobe Analytics report suites via a Marketing Cloud login or Web Services ID, and manages the AppMeasurement code. After the accounts are connected, dynamic tag management pulls the Adobe Analytics report suite IDs and names into the tool configuration interface, allowing for increased speed in tool deployment with less possibility for user errors. Note: You must choose the Automatic option if you are an Adobe Analytics Premium 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 your Marketing Cloud ID and password. Web Services: Specify your Web Services username and shared secret.

103 Tools 103 Element Description Shared secret credentials are located in Admin Tools > Company Settings > Web Services. Developers, see Get Web Service Access to the Enterprise API for help with obtaining Web Services credentials. Manual: Manually manage the AppMeasurement code. You can download the Analytics AppMeasurement code from Admin Tools > Code Manager. Click JavaScript (new) for information about downloading the code locally to copy and 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 management automatically installs the correct account in the production and staging environment. Staging Account ID: (Required) Used in your development or test environment. For Analytics, this is your report suite ID. A staging account keeps your testing data separate from production. Tracking Server: Specify the information for your tracking server. The Tracking Server and SSL Tracking Server variables are used for first-party cookie implementation to specify the domain at which the image request and cookie is written. For more information, see the Correctly Populate the trackingserver 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 2. Edit the fields as desired. icon next to an installed tool from the Overview tab. The following table includes only those elements that differ from the elements available when you are creating an Analytics tool, as described above. However, you can change any element on the page, as described in both tables.

104 Tools 104 Element Enable Automatic Configuration Description Note: Enabling this setting changes a manually configured implementation to the automatic configuration method described in Configuration Method. This option lets dynamic tag management automatically retrieve your Adobe Analytics account's configuration. The latest available AppMeasurement code is used and upgrade notifications are displayed for selection as new versions become available. You can also roll back to previous AppMeasurement versions as necessary, such as for compatibility reasons. Up to five previous versions are displayed. Update Credentials Refresh the API, for example, to update report suites associated with a user. 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). 4. Click Save Changes. Enabling Adobe Analytics Premium If you are an Adobe Analytics Premium customer, dynamic tag management lets you take advantage of advanced features 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 (Point Product) Adobe Analytics (Standard) Adobe Analytics Premium evars Events 100 1,000 1,000 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 API checks via the automatic configuration. The additional evars are added to the UI if the account is authenticated as an Analytics Premium customer. Note: If you downgrade to standard Analytics in the future, the added premium evars that are out of the standard range will be grayed out in both tools/rules. You can view any configured variables that are now out of range and make any necessary changes to an in-range variable. You cannot add or edit any of these out-of-range variables, but you will be able to view them and delete them.

105 Tools 105 General Field descriptions for the General settings in dynamic tag manager, for deploying Adobe Analytics. Property > Edit Tool > General Element Enable EU compliance for Adobe Analytics Description Enables or disables tracking based on the EU privacy cookie. When a page is loaded, the system checks to see if a cookie called sat_track is set (or the custom cookie name specified on the Edit Property page). Consider the following information: If the cookie does not exist or if the cookie exists and is set to anything but true, 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 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 using custom code: _satellite.setcookie( sat_track, false ); You must also have a mechanism to set that cookie to true if you want a visitor to be able to opt in later: _satellite.setcookie( sat_track, true"); Character Set Displays the available character encoding sets. Currency Code Displays the supported currency codes for selection. Tracking Server The domain at which the image request and cookie is written. See trackingserver. SSL Tracking Server The domain at which the image request and cookie is written. Used for secure pages. If not defined, SSL data goes to trackingserver. See trackingserversecure. Data Center The Adobe data center used for data collection.

106 Tools 106 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 unique tracker variable name. Duplicative object variable names between Adobe Analytics tools within a single web property will cause conflicts. Element Page code is already present Description Prevents dynamic tag management from installing Adobe Analytics page code if the code is already present on your site. This feature allows you to use dynamic tag management to add to your existing implementation rather than starting from scratch. Be sure to properly set your tracker variable name when checking this box. Load library at <Page Top or Page Bottom> 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. Managed by Adobe (Recommended) Enable dynamic tag management to manage your library. If you select this option, the following option becomes available: Library Version: Select the latest version from the Library Version menu. Dynamic tag management notifies you when new versions are available. You can revert to a previous version as necessary. Custom You can configure the library code. If you select this option, the following options become available: Set report suites using custom code below: When this box is checked, dynamic tag management looks for a variable in your custom code called s_account. This variable should contain a comma-separated list of the report suites to which you want 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 Edit Code 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 updating it, you can provide the URL to the file here. Dynamic tag management then consumes that s_code file for its implementation of Adobe Analytics. Open Editor: Lets you insert core AppMeasurement code. This code is populated automatically when using the automatic configuration method described in Add Adobe Analytics Tool.

107 Tools 107 Element Description Tracker Variable Name: If you want to run two instances of Adobe Analytics in parallel (one within dynamic tag management and one natively), you can rename the 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 using custom 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 the code section as well. The managed code in dynamic tag manager can be configured exactly like the JavaScript file in a typical implementation. Global Variables Field descriptions and information about variables when using dynamic tag management to deploy Adobe Analytics.

108 Tools 108 These variables fire on all page load rule beacons. You can accomplish the same effect by using a Page-Load rule set to fire on all pages. These variables might not fire in Direct Call Rules and Event-Based rules. Global Variables - Field Descriptions Property > Element Server Edit Tool > Global Variables Description The predefined variable populates the Servers report in Adobe Analytics. See server. evars The evar variables are used for building custom conversion reports. See evarn. Props Property (prop) variables are used for building custom traffic reports. See propn. Dynamic Variable Prefix A special prefix to the start of the value. The default prefix is "D=". See Dynamic Variables. Page Views and Content Field descriptions in dynamic tag management for page views and content settings when deploying Analytics. Property > Element Page Name Edit Tool > Page Views & Content Description The name of each page on your site. See pagename. Page URL Override Overrides the actual URL of the page. See pageurl. Channel (Site Section) Identifies a section of your site. See channel. Hierarchy Determines the location of a page in your site's hierarchy. Se hiern. Link Tracking Field descriptions in dynamic tag management for link tracking when deploying Analytics.

109 Tools 109 Property > Edit Tool > Link Tracking Element Enable ClickMap Description Determines whether visitor click map data is gathered. See trackinlinestats. Track download links Tracks links to downloadable files on your site. See trackdownloadlinks. Download Extensions If your site contains links to files with any of the listed extensions, the URLs of these links will appear in reporting. See linkdownloadfiletypes. Track outbound links Determines whether any link clicked is an exit link. See trackexternallinks. Single-Page App Considerations: Because of the way some SPA websites are coded, an internal link to a page on the SPA site might look like it is an outbound link. 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 into the Never Track section. For example, All # links to this host are ignored. All outbound links to other hosts are tracked, such as If there are some links that you want to track on your SPA, use the Always Track section. For example, if you have a spa/#/about page, you could put "about" in the Always Track section. The "about" page is the only outbound link that is tracked. Any other links on the page (for example, are not tracked. Note that these two options are mutually exclusive. Keep URL Parameters Preserves query strings. See linkleavequerystring. Referrers and Campaigns Field descriptions in dynamic tag management for referrers and campaign options when deploying dynamic tag management in Adobe Analytics.

110 Tools 110 Property > Element Edit Tool > Referrers & Campaigns Description Referrer Override Overrides the value set in the s.referrer variable, which is typically populated by the referrer set in the browser. See referrer. Campaign 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. See campaign. Use the DTM interface to choose whether you want to use a Query String or Value (which could pull from a data element): You can either enter your query string directly in the interface, or you can reference a separate data element if you have other means of tracking a campaign. Cookies Field descriptions for the Cookies global settings used for deploying dynamic tag management in Adobe Analytics. Property > Element Visitor ID Edit Tool > Cookies Description Unique value that represents a customer in both the online and offline systems. See visitorid. Visitor Namespace Variable to identify the domain with which cookies are set. See visitornamespace. Domain Periods The domain on which the Analytics cookie s_cc and s_sq are set by determining the number of periods in the domain of the page URL. This variable is also used by some plug-ins in determining the correct domain to set the plug-in's cookie. See cookiedomainperiods.

111 Tools 111 Element FP Domain Periods Description 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 uses the third-party 2o7.net or omtrdc.net domains. See fpcookiedomainperiods. Transaction ID Unique value that represents an online transaction that resulted in offline activity. See transactionid. Cookie Lifetime Determines the life span of a cookie. 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 > Element Open Editor Edit Tool > Customize Page Code Description You can insert any JavaScript call that must be triggered before the final s.t() call, which is contained in the s_code. Execute 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). After UI settings: Custom code takes precedence over interface settings. FAQ for Adobe Analytics Release - July Dynamic tag management feature information and FAQ for Adobe Analytics released on July 24, 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 Services ID. Add a Tool > Adobe Analytics

112 Tools 112 Frequently Asked Questions Question Is this a new Adobe Analytics tool, or a change to the existing tool? Answer A change to the existing tool. If you currently have an implementation of Adobe Analytics in dynamic tag management, it will continue to function. If I make configuration changes in the new version of the tool, can I test in staging before publishing to production? Yes. All changes can be tested in staging just like you normally would before deploying to a production environment. If you choose not to publish, because you notice issues in staging, the production code will continue to function as it did before the new integration was released. If I switch from manual configuration (the default setting for existing tools) to automatic configuration, will my current settings be affected? No. If I switch from manual library management to Managed by Adobe, will my current settings or code be affected? Any user code that you have specified is overwritten with the base AppMeasurement library.you must move this code to the new Custom Page Code section at the end of the tool configuration so that the code continues executing. This method allows the AppMeasurement library to be managed (and upgraded) separately from the user's custom code. Will the revision history for the Adobe Analytics tool be retained Yes.

113 Tools 113 Question Answer when the new integration is released? Potential Pitfalls There is a small chance that the new integration could cause data collection issues if you currently use Adobe Analytics. These issues could arise only if you publish your library to production subsequent to the release. (Production code 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.

114 Tools 114 d) Configure the following fields: Element Tool Type Tool Name Production Account ID Staging Account ID Description The Marketing Cloud solution, such as Analytics, Target, Social, and so on. The name for this tool.this name displays on the Overview tab under Installed Tools. A number for your production account for data collection. Dynamic tag management automatically installs the correct account in the production and staging environment. A number used in your development or test environment. A staging account keeps your testing data separate from production. 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.

115 Tools 115 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 can define 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 production rollout. 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 your s_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 Setting Tool Name Partner Description You can name this instance of audience manager. A unique alphanumeric identifier assigned by audience manager. Load audience management page code at (Page Top or Page Bottom) You can control where and when to load the page code. The recommended location is selected by default. Audience management page code already present Code version Integrate with Modules: Adobe Analytics Google Analytics Open Editor Add a Note Prevents dynamic tag management from installing audience manager code if it is already present on your site. This way, you can use dynamic tag management to add to your existing implementation, rather than starting a new implementation. Select the API code version used by your implementation. Select the previously configured tool integration that you want to integrate. If none, no integration is configured. Select the integrations you want to enable. If enabled, you must provide a minimum amount of configuration code. Use the editor to insert the custom audience manager API code. The tracking call should be included in the custom code. Add any notes here regarding this implementation.

116 Tools 116 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 Setting Tool Name User ID Description A descriptive name for this implementation. Your advertising management account has an associated numeric user ID. It is displayed in the JavaScript generated for a pixel. For example: 1234 Transaction ID 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> (for example, an actual order ID) when the transaction is complete. The value is passed back to advertising management. Advertising management uses the transaction ID to eliminate duplicate transactions with the same transaction ID and property value. The transaction ID is included in the Transaction Report in advertising management, which you can use to validate advertising management data with the advertiser's data. If the advertiser's data does not include a unique ID per transaction, Media Optimizer still generates one, based on transaction time. The transaction ID cannot contain ampersand symbols (&), which are reserved as parameter separators. Note: If you use the Media Optimizer combo tracking service, you must submit the transaction ID (ev_transid) for the online part of the transaction in the feed data for offline parts of the transaction. For more information, see the Tracking section of the advertising management 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 management rules utilizing the Adobe Media Optimizer tool, unless specifically overridden in the rule. Load Media Optimizer page code at (Page Top or Page Bottom) Media Optimizer page code already present Determines where and when the page code loads. The recommended location is selected by default. Prevents dynamic tag management from installing advertising management code if the code exists on your site.this method lets you use dynamic tag management

117 Tools 117 Setting Description to add to your existing advertising management implementation, rather than starting a new implementation. Conversion Property Name / Value A conversion property to be tracked when an end user views a page containing the conversion tag. Note: Properties added to this list are not integrated with the client's Transaction Properties list in the Admin view in advertising management. However, properties are added to the client's Transaction Properties list automatically, once advertising management actually gathers data for a property. Gathering happens when the conversion tag is implemented on a 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 the rule level. A globally configured Conversion Property is inherited by any dynamic tag management rules utilizing the Adobe Media Optimizer tool in addition to any conversion properties set in the rule. Segment ID (Optional) Indicate the numeric ID for an advertising management segment in which to add the users who complete the tracked transaction. (For JavaScript tags and for display campaigns only) Note: If you associate multiple conversion tags with the same audience segment, the segment will include all of the users who complete those transaction 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 management rules utilizing the Adobe Media Optimizer tool, unless specifically overridden in the rule. Tag Property / Value A conversion property name / value to be included in the tag when the specific rule is fired. Note: Properties added to this list are not integrated with the client's Transaction Properties list in the Admin view in advertising management. However, properties are added to the client's Transaction Properties list automatically, once advertising management gathers data for a property. Gathering happens when the conversion tag is implemented on a page and an end user completes a transaction. Conversion properties can be set globally at the tool level and conditionally at the rule level. If a rule uses the Adobe Media Optimizer tool, the configured global value is inherited and used in addition to any conversion properties configured in the rule.

118 Tools 118 Setting SKU Description Select the configured data element to populate the SKU value in the tag. See Data Elements for more information. SKU can be set globally at the tool level or conditionally at the rule level. If a rule uses 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 global SKU 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 Adobe Media Optimizer tool is installed. In this example, when this rule fires, Adobe Media Optimizer loads and fires a tag including the SKU value for the data element ecomm_prodid instead of the SKU configured at the tool level. The tag also includes any Transaction ID, 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.

119 Tools 119 Configure the rule so that it fires only in the desired cases. In this example, the rule fires on the click of Add to cart 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 management once an Adobe Media Optimizer tool is installed in the property. See Conditions and Functions for information about available rule criteria. 3. Expand Adobe Media Optimizer in the rule.

120 Tools 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 are inherited. Add Adobe Target Tool Information about creating the Adobe Target tool for deploying Adobe Target in dynamic tag management. You can configure the library automatically (recommended) or manually. <Web Property Name> > Overview > Add a Tool > Adobe Target

121 Tools 121 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 Adobe Target. This table provides information for the automatic and manual configuration settings. Setting Tool Type Description The type of tool, such as Adobe Target. Tool Name The name for this tool. This name displays on the Overview tab under Installed Tools. Library retrieval method Specifies whether Adobe should manage your Adobe Target code automatically, or whether you would like to provide your own custom code manually. Manual Configuration Method You can manually manage the Adobe Target code. You can download the at.js or mbox.js file 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 Library Management section of the tool settings. You also have the option of hosting the code at a specific 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 Adobe Target account configuration. If you select Automatic, you must either be logged in via the Marketing Cloud, or you must provide a Client Code value described below. Client code retrieval method (Automatic method) A code unique to your Adobe Target account. It is required for your code to be provided and managed automatically by Adobe. If you chose the Automatic method, you must either be logged in via the Marketing Cloud, or provide your Client Code value after selecting Manual as the retrieval method. Client Code (Automatic method) The Client Code value can be retrieved from the Adobe Target solution interface as follows: 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. Property > Edit Tool > Library Management

122 Tools 122 Element Load Adobe Target Library synchronously Description This option ensures the at.js or mbox.js code is loaded synchronously in the <head> section. It is generally recommended that you leave this option enabled. It is an Adobe Target best practice to load the code in this way. Code Configuration Managed by Adobe:(mbox.js only) This option is equivalent to the Automatic configuration method available when creating the tool. This option loads the mbox.js code directly from Adobe. This feature optimizes the configuration process when using a manual method, because no more copying or pasting from the Adobe Target admin console is required. You must be logged in via Marketing Cloud or have provided the appropriate Client Code for this option to be available. Clicking Check for Updates automatically checks for new versions of the mbox.js code within your associated Adobe Target account. If a new version is 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. Two methods 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 using Managed by Adobe and switch to custom, the editor automatically populates with your mbox.js code.you can replace this with the content of the at.js library. At URL: If your at.js or mbox.js is configured as desired, you can provide the URL to the file. Dynamic tag management will consume it for use in the Adobe Target tool. Global Parameters - Adobe Target Descriptions of the fields and options in the Global Parameters settings in dynamic tag management for an Adobe Target Tool. Global parameters let you pass additional data to the global Adobe Target mbox, and also on a per-page basis via page load rules.

123 Tools 123 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. Property > Edit Tool > Library Management Element Name Description Indicate the name of the additional parameter(s) you wish to pass to the global mbox. Value Indicate the value of the additional parameter(s) you want to pass to the global mbox. The value is typically a data element. 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 an Adobe 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.

124 Tools 124 Note: Adobe recommends load rules triggering mboxes at Top of Page to ensure the default content is hidden 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 if needed. (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 includes an mbox parameter named Page Name with a value of homepage. It also includes a parameter named Path with a value of home that it passes to the global mbox.

125 Tools 125 Note: You can also use data elements in the parameter UI fields to dynamically populate the value. See Data 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. Setting Tool Name Production Account ID Staging Account ID Enable support for Google Analytics Premium features Google Analytics page code is already present Description The name of this instance of Google Analytics. You can point to production or staging accounts for data collection. Your staging account number is used in your development or test environment. It keeps your testing data separate from production. Dynamic tag management automatically installs the correct account in each environment. Enable if you are a Google Analytics Premium customer. Check this box to prevent dynamic tag management from installing Google Analytics code if it is already present on your site. This way, you can use dynamic tag management to add to your existing implementation, rather than starting a new implementation. Ensure that you properly set your tracker name when checking this box.

126 Tools 126 Setting Enable EU compliance for Google Analytics Description Enables or disables tracking based on the EU privacy cookie. When a page is loaded, the system checks to see if a cookie called sat_track is set (or the custom cookie name specified on the Edit Property page). Consider the following information: If the cookie does not exist or if the cookie exists and is set to anything but true, 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 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 using custom code: _satellite.setcookie( sat_track, false ); You must also have a mechanism to set that cookie to true if you want a visitor to be able to opt in later: _satellite.setcookie( sat_track, true"); Tracker Name Google Analytics Code Sample Defaults - Data Sample Sample Defaults - Site Speed Social - Track Facebook like, unlike, and share Social - Track official Twitter button use Force lowercase on all pageview, event, and custom variable calls The tracker name you want to use for your Google Analytics installation. If you specified that Google Analytics is already installed on your site's pages, you must use the same name here for proper data collection. The default tracker name for Google Analytics is blank. There are two ways to host 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 sample rate. To gather all data, leave 100%. You can specify the sample rate for capturing data on site speed and page performance. The default is 1%. Enables automatic link tracking on the above social buttons on your site. Enables automatic link tracking on the Twitter button on your site. Force all page views, events, and custom variables sent to GA to be in all lowercase letters (a best-practice recommendation).

127 Tools 127 Setting Load Google Analytics page code at Page Top or Page Bottom Global Settings - Enable automatic linker link tracking Description You can control where and when to load the page code (on a rule-by-rule basis). Automates the tracking of cross-domain property. Google Analytics customers need to implement JavaScript codes for links to different but internal domains, so that cookies are shared across internal domains. For more information from Google, click here. Element Tag or Selector to INCLUDE Element Tag or Selector to EXCLUDE Session Cookie Timeout Visitor Cookie Timeout Cookie Path Cookie Domain Set # as a query string delimiter Campaign Keys in URL Parameters Enable campaign tracking for cookies Campaign Cookie Timeout Classify the following keywords as direct Specify the name of the tag you would like to track. Examples: A, IMG, INPUT, DIV, etc. Specify the name of any tags or selectors you do not wish to track. Example: a[target="_blank"] How much time elapses before Google Analytics expires a session. Default is 30 minutes. Control how long a cookie lasts for a visitor to count as a repeat visitor. Default is two years. You can restrict whether a Google Analytics cookie only functions with a specific folder on your site. You can change the default cookie domain. If you specified that your web property spans multiple domains or subdomains, dynamic tag management configures this automatically. Allows dynamic tag management to recognize values in the URL after the # symbol as URL parameters. If your campaign parameters do not show up in the default variables (like utm_source, etc.), configure them here. Allows you to set campaigns around cookies. Control how long a cookie lasts for a campaign. Default is 30 days. 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.

128 Tools 128 Setting Classify the following referrers as direct Clear Keywords & Referrers from User Cookies Open Editor Description Create a list of referral sources that are automatically classified as direct traffic, comma separated. This is most often used to classify affiliate or in-network searches as direct. Adobe does not recommend this practice. Removes keyword and referrer data from the Google Analytics user cookies set from your site. Use the editor to customize the page code. This code is inserted into every page immediately before the call to track the page view. If you want to cancel the initial default _trackpageview command and write your own to customize page names, be sure 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, DTM Generated Name, or Specific Name. This section contains the following information: 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:

129 Tools 129 Without trackername as variable: _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.

130 Tools 130 Without trackername as variable: _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 Setting Tool Name Description The name of this instance of Google Analytics.

131 Tools 131 Setting Production Account ID Staging Account ID Description Dynamic tag management allows you to point to production and staging accounts for data collection.your staging account number will be used in your development or test environment, and will keep your testing data separate from production. Dynamic tag management will automatically install the correct account in each environment. General Element Enable support for Google Universal Analytics Premium features Description Enables the max dimensions and metrics increase from 20 to 200. Google Universal Analytics page code is already present Prevents dynamic tag management from installing Google Analytics page code if it is already present on your site. This feature allows you to use dynamic tag management to add to your existing implementation, rather than starting from scratch. Ensure that you properly set your tracker name when checking this box. Enable EU compliance for Google Universal Analytics Enables or disables tracking based on the EU privacy cookie. When a page is loaded, the system checks to see if a cookie called sat_track is set (or the custom cookie name specified on the Edit Property page). Consider the following information: If the cookie does not exist or if the cookie exists and is set to anything but true, 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 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 using custom code: _satellite.setcookie( sat_track, false ); You must also have a mechanism to set that cookie to true if you want a visitor to be able to opt in later: _satellite.setcookie( sat_track, true"); Anonymize IP addresses Ensures that IP addresses are never recorded. Force SSL Forces the use of HTTPS.

132 Tools 132 Element Tracker Name Description The tracker name you want to use for your Google Analytics installation. If you specified that Google Analytics is already installed on your site's pages, you must use the same name here for proper data collection. The default tracker name for Google Analytics is blank. Google Analytics Code There are two ways to host 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. Data Sample To have Google Analytics only capture a sample of your site's data, specify the sample rate for Data Sample. To gather all data, leave at 100%. Site Speed Sample You can also specify the sample rate for capturing data on site speed and page performance. The Google Analytics default is 1%. Social - Track Facebook like, unlike, and share Enables automatic link tracking on the above social buttons on your site. Social - Track official Twitter button use Force lowercase on all pageview, event, and custom variable calls Enables automatic link tracking on the Twitter button on your site. Force all page views, events, and custom variables sent to GA to be in all lowercase letters (a best-practice recommendation). Always send HTTP referrer URL Typically, HTTP referrals come from outside the domain on which you implemented Google Universal Analytics. Enable this setting if you have many subdomains and want all URLs to be sent. Load Google Analytics page code at Page Top or Page Bottom You can control where and when to load the page code (on a rule-by-rule basis). Global Settings - Enable automatic linker link tracking Automates the tracking of cross-domain property. Google Analytics customers need to implement JavaScript codes for links to different but internal domains, so that cookies are shared across internal domains. For more information from Google, click here. Cookies Element Visitor Cookie Timeout Description Control how long a cookie lasts for a visitor to count as a repeat visitor. The default value is two years.

133 Tools 133 Element Cookie Name Cookie Path Cookie Domain Description Name of the cookie used to store analytics data. You can restrict whether a Google Analytics cookie only functions with a specific folder on your site. You can change the default cookie domain. If you specified that your web property spans multiple domains or subdomains, dynamic tag management configures this automatically. Legacy Cookie Domain This field is used to configure how analytics.js searches for cookies generated by earlier Google Analytics tracking scripts such as ga.js and urchin.js. Campaign Tracking If your campaign parameters do not show up in the default variables (like utm_source, etc.) configure those here. Element Set # as a query string delimiter Description Allows dynamic tag management to recognize values in the URL after the # symbol as URL parameters. Hit Callback The code you add here is executed after each hit has successfully been reported to Google Analytics. Element Open Editor Description Use the editor to customize the page code. This code is inserted into every page immediately before the call to track the page view. If you want to cancel the initial default _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 the call to track the page view. If you want to cancel the initial default pageview command and write your own to customize page names, be sure to "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, DTM Generated Name, or Specific Name. This section contains the following information: GA Default Name

134 Tools 134 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.

135 Tools 135 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 the page 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: Task 1. Embed dynamic tag management on the site (all site webpages). Description You can add header and footer code that determines the loading of JavaScript and page content on your site. You must install both the header and footer code on every page of your site, regardless of the hosting option used.

136 Tools 136 Task Description For more information, see Header and Footer Code. 2. Add the Marketing Cloud ID Service tool. The Marketing Cloud Visitor ID Service provides a universal visitor ID across Marketing Cloud solutions. The visitor ID service replaces the legacy Analytics 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 ID Service Guide. For information about adding the Marketing Cloud ID Service tool in DTM, see Marketing Cloud ID Services settings. 3. Add the Adobe Analytics tool. You can deploy Adobe Analytics (Standard and Premium) using dynamic tag management by creating the Adobe Analytics tool and configuring the page code either automatically or manually. The automatic method is recommended for most users. For more information, see Add Adobe Analytics Tool. Add the Nielsen Tool 1. Click Web Property Name > Overview > Add a Tool > Nielsen. 2. Fill in the fields: Element Tool Type Description The type of tool, such as Nielsen.

137 Tools 137 Element Tool Name Description A descriptive name for this tool. This name displays on the Overview tab under Installed Tools. Client ID Specify the Client ID you obtained from Nielsen. Collection Server Specify the collection server you obtained from Nielsen (secure-us or secure-au, for example). Integration Method Automatic: Use dynamic tag management to manage the integration. After the accounts are connected, dynamic tag management pulls the Adobe Analytics report suite IDs and names into the tool configuration interface, allowing for 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. 4. Fill in the fields: Element Application ID Description Specify the application's ID that you obtained from Nielsen. Application Name Specify the application's name that you obtained from Nielsen. Collection Server Specify the collection server you obtained from Nielsen (secure-us or secure-au, for example). The collection server carries over from the information you specified above. Content Group Specify the content group you obtained from Nielsen. VCID Specify the VCID you obtained from Nielsen. 5. Click Save Changes. 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 criteria outlined in your rules are met, the rule triggers the tool, script, or HTML you identified. For general information, see Rules. When you add the Nielsen tool, dynamic tag management automatically creates a default Nielsen Time Tracking rule.

138 Tools 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 these pre-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 any custom script and allows different load options, such as sequential, non-sequential, or HTML/Javascript. As a general rule, 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.

139 Tools Click Property > Rules > JavaScript/Third Party Tags. 2. Click Add New Script. A text box opens, where you provide the script name and select how you want the script to trigger. (Non-Sequential JavaScript, 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)

140 Data Elements 140 Data Elements Data elements are the building blocks for rules. Data elements let you create a data dictionary (or data map) of commonly used items on a page, regardless of where they originate (query strings, URLs, or cookie values) for any object that is contained on your site. You use data elements to build a data layer that can be used for Analytics and other data collection tools. Rules > Data Elements > Edit. Use data elements as widely as possible throughout rule creation to consolidate the definition of dynamic data and to 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 from query 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 tag management 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 data element as a single point of reference for that particular point of data. You can then use this data element in any rule that needs to reference the page name. If for some reason in the future you decide to change the way you reference page name (for example, you have been referencing document.title but you now want to reference a particular data layer), you don't need to edit many different rules to change that reference. You simply change the reference 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 high level, 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. This section contains the following information: 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. Type JavaScript Object Description Any available JavaScript object or variable can be referenced using the path field. Example window.document.title CSS Selector Any element value can be retrieved, such as a div or H1 tag. CSS Selector Chain: id#dc logo img

141 Data Elements 141 Type Cookie Description Any available domain cookie can be referenced in the cookie name field. Example Get the value of: src cookiename URL Parameter Custom Script Specify a single URL parameter in the URL Parameter field. Only the name section is necessary and any special designators like "?" or "=" should be omitted Custom JavaScript can be entered into the UI by clicking Open Editor and inserting code into the editor window. A return statement is necessary in the editor window in order to indicate what value should be set as the data element value. If a return statement is not included, the default value or an empty string will be returned as the data element value. contenttype var pagetype = $('div.page-wrapper').attr('class').split(' ')[1]; if (window.location.pathname == '/'){return 'homepage'; } else { return pagetype; } 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 Visitor Sets a session-level cookie in the browser. Available throughout the site visit. Sets a 2-year cookie. Cookie manipulation Can be manipulated using _satellite cookie methods: _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

142 Data Elements 142 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 sign into 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 available for the rule. This situation is sometimes necessary for specific timing considerations and issues with existing implementation code.

143 Data Elements 143 For example, entering the following code forces the retrieval of the data element named sample data during the rule identification step, prior to any data manipulation that happens in the rest of the rule.

144 Data Elements 144 The custom code section in the identifier must return true, regardless of whether a valid value is available for the data 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 in dynamic tag management to use with your analytics tools, or testing tools, or even with third party tags, one way to capture those values is to use Data Elements in dynamic tag management. This way, you can refer to the Data Element throughout your Rules, and if the source of the data ever changes, you only need to change your reference to 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:

145 Data Elements 145 If you use a data collector object as party of your data layer, simply use dot notation in the Path to reference the object and property you want to capture into the Data Element, like _mydata.pagename, or digitaldata.pagename, etc. Adobe Training Video: Data Elements DTM Basics: Data Elements Time: 10:28 By then end of this video you should be able to: Understand what a data element is Explain the different element types 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. 3. Click Create New Data Element. 4. Complete the following fields and options: Option Description Name The data element friendly name that a marketer can recognize. For example, Product ID. Note: The name is referenced by the rules builder, not an ID. If you change the name of the Data Element, you must change its reference in every rule that uses it. Type Specifies where the data is pulled from, such as JS Object, CSS Selector, Cookie, URL Parameter, or Custom Script. Depending on which type you select, different options display. See Types of Data Elements for more information and examples. Default Value A default element. This value ensures that the data element always has a value, even if a URL parameter does not exist or cannot be found by dynamic tag management.

146 Data Elements 146 Option Description Note: If there is no value and no default value, then nothing is returned. Any variable referencing that data element won't get set. Note also that the default value field is ignored if it's a "custom code" data element. Force lowercase value Remember this value for Dynamic tag management automatically makes the value lowercased. How long you want dynamic tag management to remember this value. Valid values include: Session: Session-based timing can vary depending on the implementation. Session data elements are set to the session cookie. However, this setting could be based on a 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. 5. Click Save Data Element.

147 Rules 147 Rules Dynamic tag management is a rule-based system. It looks for user interaction and associated data. When the criteria outlined in your rules are met, the rule triggers the tool, script, or HTML you identified. A rule consists of two parts: Identifier The identifier is what you want the rule to look for. The identifier you specify depends on the type of rule. Trigger Triggers occur after a rule's conditions are met. A rule in dynamic tag management can trigger as many discrete actions as you want. For example, a single rule for an e-commerce Thank You page can trigger your analytics tools and third-party tags from a single rule. There is no need to create separate rules for each 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: Type of Rule Event-based Description Events are where the majority of interactions on sites take place. You can measure and react to these interactions in real-time, without the need for JavaScript. 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 on things like social media sharing, video interactions, tabbed interfaces, image galleries, and product sorting and filtering.

148 Rules 148 Type of Rule Description See Event-Based Rules Example for an example of how to set your condition to look for clicks on the various tabs on your product pages. See EnterpriseTV Videos: Event-Based Rules to watch videos about event-based rules. Page load Let you target by URL, site section, or set up scenarios that are independent of the site structure. For example, a page-load rule can load a survey on the fifth page view or in the seventh minute of a visitor s session. 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. Direct call Designed to bypass dynamic tag management event detection and lookup systems. Direct call rules are ideal for situations where you want to tell dynamic tag management exactly what is happening. Also, they are ideal when dynamic tag management cannot detect an event in the DOM, such as with Adobe Flash. See Create conditions for direct-call rules for more information and to watch an EnterpriseTV video about direct-call rules. Default rules When you activate a property, dynamic tag management includes several default rules. These rules track common interactions with your site and can help you analyze opportunities 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. Link: Tracks any clicks on linked s. 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 Installed Tools, 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 first things 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 your scenario is the same, then you can add as many tool actions or variables, and as many third party tags as you would

149 Rules 149 like to an existing rule, if one exists with the Conditions you need. If you have a different set of Conditions, you need to 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 web property with the condition you need, to execute the conversion pixel. Suppose that you already have a page-load rule for your purchase confirmation page, and you are loading three conversion pixels in the JavaScript / Third Party Tags section. You can add your new pixel as a new Script in the same section of that rule, without creating a new rule. 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 elements on the page. The CSS Selector lets you quickly and easily select CSS elements to use as triggers for event-based rules without leaving 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 DTM Basics: Event-Based Rules, Part One Time: 7:02 By then end of this video you should be able to: Understand what an event-based rule is Explain the event-based rule types Create an event-based rule DTM Basics: Event-Based Rules, Part Two Time: 5:20 By then end of this video you should be able to: Understand what an event-based rule is Explain the event-based rule types Create an event-based rule

150 Rules 150 DTM Basics: Event-Based Rules, Part Three Time: 7:53 By then end of this video you should be able to: Understand what an event-based rule is Explain the event-based rule types Create an event-based rule Set up how to track this click in Adobe Analytics.

151 Rules 151 If you also have Google Analytics or any other platforms installed, you can leverage the same rule to configure or send data to as many platforms as you want.

152 Rules 152 When using event-based rules, dynamic tag management offers powerful tools to surface data from the page and page 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 after a certain number of page views, or after a specified number of minutes into a session. Page load rules let you target by URL, site section, or set up scenarios that are independent of the site structure. DTM Basics: Page Load Rules, Part One Time: 6:02 By then end of this video you should be able to: Understand what a page load rule is Understand the condition criteria options Create a page load rule DTM Basics: Page Load Rules, Part Two Time: 7:00 By then end of this video you should be able to: Understand what a page load rule is

153 Rules 153 DTM Basics: Page Load Rules, Part Two Time: 7:00 Understand the condition criteria 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 the page 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 in formatted HTML.

154 Rules 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 the production site. Note: By default, page load rules load at page bottom. This setup works for most scenarios. However, if the rule you are setting up has some dependency on in page content, it might be better to configure the rule to

155 Rules 155 load on DOM ready. Conversely, if you have other rules that rely on the outcome of the rule in question, load the 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 an A/B test to a form, using a segment specific to users on ipads who have been on our site for more than fifteen minutes 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.

156 Rules Click Save, configure your test in Adobe Target and your test is running.

157 Rules 157 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.

158 Rules 158 Note: Red text on the above diagram represents non-sequential activity. Green text represents sequential activity.

159 Rules 159 The following section discusses how the different JavaScript/third-party tags script options are utilized within the four page-load phases: Top of Page Sequential HTML: Injected into <HEAD/> below DTM library include script if <SCRIPT/> tags are used, otherwise is 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 to DOMREADY 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/> 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 DOM Ready Sequential HTML: Will not work because DOMREADY is active and document.write() will overwrite the page 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 Onload (window load) Sequential HTML: Will not work because DOMREADY is active and document.write() will overwrite the page 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 Non-sequential HTML third-party rules are always placed into iframes. There is no such thing as asynchronous HTML 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 and ONLOAD, scripts will only appear in the proper timing sequence and be either global, local, synchronous, or asynchronous. Also, dynamic tag management checks to make sure that the timing is being handled properly and if DOMREADY has already occurred, it will not attempt a page-destructive document.write(). Dynamic tag management is diligent about not breaking the visual page if at all possible. For this reason, you might see an "asyc installation" error when the installation might not actually be "async." It is simply an alert that helps

160 Rules 160 you recognize that the timing on the page is somewhat questionable and that DOMREADY has fired prior to all of 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 errors can occur. The dynamic tag management queue processes them in the order listed above but does not distinguish between a JavaScript 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.pageloadrules in 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 into the 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 Load Rules. 4. Click Create New Rule. 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. Type of Rule Refer to this Topic Event-based rule Page Load rule Direct Call rule Create conditions for event-based rules Create conditions for page-load rules Create conditions for direct-call rules The category field is only for your own organizational purposes and is not required. You can delete categories by 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.

161 Rules 161 For more information, see Event Types. 2. Enable the following options as necessary: Element Delay Link Activation Description Enable if the event activates a link and you want the link to delay until the event has time to fire. Apply event handler directly to element Applies the event handler to the specific element that is targeted. This setting is tied to the bubbling and layering concept in a browser. For example, when you click an image inside an anchor tag like <a href="abc.html"><img src="xyz.png"/></a>, you might expect the click to be associated with the anchor tag, because the tag is in the bubble stream. However, when you inspect the click in the developer tools, the click may actually affect only the <img> tag. To ensure that the event is handled correctly, associate the click with the <img> tag and do not depend on the browser to bubble up the click to a parent element. An event like a click can potentially bubble up to <body>. It is important to understand where the event is actually bound, and target it specifically to make sure that the rule fires correctly. Bubbling means that the event is first captured and handled by the inner most element and then propagated to outer elements. 3. Indicate the name of the tag you want to track, and additional properties the tag has that you want to match.

162 Rules 162 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. If you... Want related interactions on child elements of the rule selector you identified to fire the rule. Want to prevent bubbling when the child element already triggers its own event. Don't want the events of the rule selector you identified to go beyond the element itself in the event hierarchy Check this option Allow events on child elements to bubble Do not allow if child element already triggers event. Do not allow events to bubble upwards to parents Event Types List of built-in event types and how each is defined.

163 Rules 163 Category Mouse Event click Definition A pointing device button is pressed and released on an element. mouseover A pointing device is moved onto the element that has the listener attached or onto one of its children. Keyboard keypress A key is pressed and that key normally produces a character value (use input instead). Forms focus An element received focus (does not bubble). blur An element lost focus (does not bubble). submit A form is submitted. change An element loses focus and its value changed since gaining focus. HMTL5 Video ended Playback stopped because the end of the media was reached. loadeddata The first frame of the media finished loading. play Playback began. pause Playback is paused. stalled The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. volumechange The volume has changed. % complete Emits an event given a specified percentage of total playing time. For example, entering 10% indicates that this rule fires only when 10% of the total length of the video has been played. time complete Emits an event given a specified duration of playing time. For example, entering 10 indicates that this rule fires only when 10 seconds of the total length of the video has been played. Mobile orientationchange The orientation of the device (portrait/landscape) has changed.

164 Rules 164 Category Event zoomchange Definition When a pinch or spread gesture is performed on a mobile device. Browser tab focus Event is triggered when the content gains focus. tab blur Event is triggered when the content loses focus. Other custom A custom event has been triggered on the DOM. Select Custom from the Event Type drop-down list, then specify the custom event name. For more information, see CustomEvent on the Mozilla Developer Network. enters viewport When the element first comes into the view of the visitor. If the element is in view immediately upon page load, the rule fires immediately. If the element comes in view after scrolling, the rule fires then. An optional delay can be specified in the rule that determines how long the element has to be in view for before the event is triggered (the default value is 1 second). element exists When an element of a specified selector comes into existence either because it is in the page markup or dynamically injected later on. Each rule fires only once. pushstate or hashchange The URL path or the hash (fragment identifier) at the end of the URL changed. The pushstate or hashchange event can be used with Single Page Apps (SPAs) in which a page does not reload but its content changes. Common development frameworks that can be used to create SPAs include Angular and React. This event type lets you create event-based rules without relying on developers. These rules fire when common functions in SPAs occur, such as: The URL path changed based on use of the HTML5 History pushstate API. For more information about using pushstate, see Adding and Modifying History Entries on the Mozilla Developer Network. The hash changed due to the user changing views or locations on the page.

165 Rules 165 Category Event Definition For more information about using hashchange, see Hashchange on the Mozilla Developer Network. time passed Value in seconds. The event is triggered after the specified number of seconds has passed. dataelementchanged A date element changed. This event lets you select a specific data element to use as a trigger. For more information on a possible use case, see Add Adobe Experience 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 without leaving 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. The following sections contain more information: 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 have any similar elements in the CSS.

166 Rules 166 The more complex example described below illustrates how to use the CSS Selector when there are many similar elements 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.

167 Rules 167 In this example, we are creating an event-based rule that uses the Click event type to trigger the rule when users click 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 style sheets might change from one page to another, depending on your website and its architecture. It is helpful to 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 elements to get a feel for how the tool works.

168 Rules 168 If we were creating this rule without using the CSS Selector, we would inspect the desired page element to determine the proper CSS to use. Using the CSS Selector, simply click the element on the page that we want to 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 then generates a minimal CSS selector for that element.

169 Rules 169 Notice the panel at the bottom that contains information about the selected element and a button to send the information to DTM. The number in parenthesis next to Clear indicates the number of items selected. In this example, the "Sign In or Register" link does not have anything similar to it on the specified page, so "1" displays. Click Clear to remove selected 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 users click the "Sign In or Register" link.

170 Rules 170 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 our website. The difference between this example and the simple example discussed above is that the "Men's" tab has many similar elements on the page. 1. Access the CSS Selector widget within DTM by clicking the 2. Specify the website's URL, then click Load. icon while creating a rule. 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 in parenthesis 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 displays around the element.

171 Rules 171 When you click a page element that you want the selector to match, it turns green. The CSS Selector then generates a minimal CSS selector for that element. In addition, the selector highlights everything that matches that 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 this process of selection and rejection, you can come up with the perfect CSS selector for your needs. Pressing Shift while 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 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 track which link is clicked by dynamically populating an evar with the id of the element clicked.

172 Rules 172 Example Link: <a id='myfirstlink' href=' To accomplish this, create an event-based rule to trigger on the click of the links on the page. Then, within the Analytics 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, these links 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=' To accomplish this, create an event-based rule to trigger on the click of the links on the page. Then, within the Analytics 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 about standard HTML attributes. However, if in doubt, you can use the non-standard getattribute() format, which will work in either scenario. This functionality can be utilized in dynamic tag management rule fields, including: Analytics Variables Custom Script Analytics Variables Adobe Analytics:

173 Rules 173 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 page content 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.

174 Rules 174 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, without quotes. Watch an Adobe training video demonstrating how to set up a direct-call rule in dynamic tag management: DTM Basics: Direct Call Rules Time: 3:01 By then end of this video you should be able to: Understand what direct call rules 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, you must 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 can include Analytics events, third-party tags, and custom scripts. This example describes how to set up scripts or third-party tags. Beyond integrated tools like Adobe Analytics and Google Analytics, dynamic tag management can trigger any type of 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-site scripting (XSS) vulnerabilities (see OWASP s guide for more info). Using data elements within a script requires particular attention. Always assume data element values might come from an untrusted source. To set up actions for the condition to trigger

175 Rules Click JavaScript / Third Party Tags to add a new script to your rule. 2. Click Add New Script. 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.

176 Rules 176 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 Management Product 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 tool such 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 you want the rule to fire. Conditions and Functions The following table describes condition types, conditions, functions, and applicable notes: Condition Type Condition Function Notes URL Protocol Indicate rule to fire on HTTP or HTTPS.

177 Rules 177 Condition Type Condition Function Notes Subdomain Indicate rule to fire or not fire on specified subdomain(s). Enable regex on this condition to include multiple scenarios in a single condition. Path Indicate rule to fire or not fire on specified URL path(s). Enable regex on this condition to include multiple scenarios in a single condition. The path condition functions based on the _satellite.data.uri, which is inclusive of query params. Parameter Indicate rule to fire if specific URL parameter(s) with specific values are present. Enable regex on this condition to include multiple scenarios in a single condition. Technology Cookie Opt-out Indicate rule to fire only if user accepts cookies based on presence of sat_track cookie that is set to 'true' Requires data element setup. Cookie can be given custom name on the Edit Property page. Browser Indicate rule to fire only in specified browsers. Operating System Indicate rule to fire only in specified operating systems. Device Type Indicate rule to fire only on specified devices. Screen Resolution Indicate rule to fire within specified screen-resolution ranges. Window Size Indicate rule to fire within specified window-size ranges. Engagement Traffic Source Indicate rule to fire if visit came from specified source. Enable regex on this condition to include multiple scenarios in a single condition.

178 Rules 178 Condition Type Condition Function Notes Landing Page Indicate rule to fire if visit landed on specified page(s). Enable regex on this condition to include multiple scenarios in a single condition. New/Returning Visitor Indicate rule to fire only if new/returning visit. Sessions Indicate rule to fire if visitor has had >, =, or < specified number of sessions. Page Views Indicate rule to fire if visitor has had >, =, or < specified number of page views in this session or all sessions. Time on Site Indicate rule to fire if visit persists for specified # of minutes. Registered User Indicate rule to fire based on user registration status as indicated in data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value). Requires data element setup. Logged In Indicate rule to fire if user is / is not logged in as indicated in data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value). Requires data element setup. Previous Converter Indicate rule to fire if user is / is not a previous converter as indicated data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value). Requires data element setup. Cart Item Quantity Indicate rule to fire if user has certain number of items in cart as indicated in data element. Requires data element setup. Cart Amount Indicate rule to fire if user has certain dollar value in cart as indicated in data element. Requires data element setup. Data Cookie Indicate rule to fire if specified cookie with specified value is present. Enable regex on this condition to include

179 Rules 179 Condition Type Condition Function Notes multiple scenarios in a single condition. Data Element Value Indicate rule to fire if specified data element with specified value is present. Requires data element setup. Enable regex on this condition to include multiple scenarios in a single condition. Variable Set Indicate rule to fire if specified JS object with specified value is present. It may be necessary to prefix the object path with the appropriate scope depending on the scenario - 'this.', 'event.', 'target.', 'window.', or 'param.' Enable regex on this condition to include multiple scenarios in a single condition. Custom Opens a blank text box to input custom script.

180 Migrating to Dynamic Tag Management 180 Migrating to Dynamic Tag Management Dynamic tag management provides several options to migrate from a typical JavaScript implementation or a Tag Manager 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 to the site, but you can still go ahead and add rules and expand upon your implementation without having to wait for all 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 begin to deploy the Analytics page code to your site, allowing you to get the benefits of dynamic tag management right away without having to wait. Configure a Second Instance Dynamic tag management provides the means for you to have a completely separate Analytics implementation while leaving your original one intact, allowing you to run them in parallel. To do this, you can simply rename the main s object 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 one within 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. Step Step 1 Task Migrate your existing Adobe Tag Manager tags to dynamic tag management. Description Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping

181 Migrating to Dynamic Tag Management 181 Step Step 2 Task Deploy your dynamic tag management implementation to staging. Description In your staging environment, replace your Adobe Tag Manager page code, then validate your dynamic tag management implementation. Step 3 Plan and execute your production rollout. This involves replacing the Adobe Tag Manager page code with the header and footer code, and making sure that all changes are published. 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 Tag Manager 1.0 tag Custom Core JavaScript Dynamic Tag Management JavaScript / Third Party Tag Migration Instructions Custom JavaScript can be deployed directly into the JavaScript / Third Party Tags section of a rule. In most cases, you can paste the page code provided by the vendor directly into a tag with no additional configuration. If any product specific code was included in this section in Adobe Tag Management, it will need to be specifically migrated into the applicable tool in dynamic tag management. Product Code Tag Manager 1.0 Product Code Tag SiteCatalyst SiteCatalyst > Survey SiteCatalyst > Video Tracking SiteCatalyst > Genesis Integrations Dynamic Tag Management Adobe Analytics Tool Migration Instructions Follow the instructions in Add Adobe Analytics Tool to add an Adobe Analytics tool in dynamic tag management. Option 1 Host code using the Managed by Adobe option. This method leverages the base version of the AppMeasurement code and allows you to choose between the latest available code versions.

182 Migrating to Dynamic Tag Management 182 Tag Manager 1.0 Product Code Tag Dynamic Tag Management Migration Instructions With this option, above this line customization can be configured in the available 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 or if a legacy code version is used. 1. In Adobe Tag Management 1.0, click Edit next to the latest container 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 and ending with the first s.settagcontainer command. (Do not include this s.settagcontainer in this situation). Here is an example:

183 Migrating to Dynamic Tag Management 183 Tag Manager 1.0 Product Code Tag Dynamic Tag Management Migration Instructions Paste this code into the Custom editor in the Adobe Analytics tool in dynamic tag management. Then, from the same preview file in ATM, copy the below the line code. This code begins with: /************* DO NOT ALTER ANYTHING BELOW THIS LINE! **************/

184 Migrating to Dynamic Tag Management 184 Tag Manager 1.0 Product Code Tag Dynamic Tag Management Migration Instructions and ends with the second settagcontainer function. (In this case, include the settagcontainer function, because this code should not be altered). Ensure the code only in this block is included. Any code set in the Custom Code (after products) section is included after this code block in the preview file, so ensure that only the intended code block is included in the copy. For example:

185 Migrating to Dynamic Tag Management 185 Tag Manager 1.0 Product Code Tag Dynamic Tag Management Migration Instructions Paste the code into the same Custom editor in dynamic tag management after the above this line code. Note: Since mistakes can occur with copy / paste, please be sure to review the implementation in dynamic tag management thoroughly and test extensively in staging before publishing to production to ensure the expected behavior is accomplished. Demdex Adobe Audience Manager Tool Add and configure an audience management tool. Custom Code (after products) 1.0 Custom Code Tag HTML Dynamic Tag Management HTML Migration Instructions Create a rule with conditions mimicking the ATM firing rules. Copy all of the code into the JavaScript / Third Party Tags editor in the rule. Select between non-sequential and sequential HTML as applicable. JavaScript JavaScript Create a rule with conditions mimicking the ATM firing rules. Copy all of the code into the JavaScript / Third Party Tags editor in the rule. Select between non-sequential and sequential JavaScript as applicable. Image Beacon HTML Create a rule with conditions mimicking the ATM firing rules. Copy the image URL from the 1.0 tag into the JavaScript / Third Party Tags editor of the rule. Wrap the image url in <img> tags and configure as non-sequential or sequential HTML as applicable. For example: <img height="1" width="1" style="border-style:none;" alt="" src="imageurl"/> Remote Script HTML Create a rule with conditions mimicking the ATM firing rules. Copy the script URL from the 1.0 tag into the JavaScript / Third Party Tags editor of the rule. Wrap the script url in script tags and configure as non-sequential or sequential HTML as applicable. For example: <script type="text/javascript" src="scripturl"></script>

186 Migrating to Dynamic Tag Management Custom Code Tag IFrame Dynamic Tag Management HTML Migration Instructions Create a rule with conditions mimicking the ATM firing rules. Copy the iframe URL from the 1.0 tag into the JavaScript / Third Party Tags editor of the rule. Wrap the iframe url in iframe tags and configure as non-sequential or sequential HTML as applicable. 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 into a 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.0 Product Code Tag Dynamic Tag Management Migration Instructions SiteCatalyst Adobe Analytics Tool SiteCatalyst > Survey Option 1 Follow the instructions in Add Adobe Analytics Tool to add an Adobe Analytics tool in dynamic tag management. SiteCatalyst > Video SiteCatalyst > Integration Module Host code using the Managed by Adobe option. This method leverages the base version of the AppMeasurement code and allows you to choose between the latest available code versions.

187 Migrating to Dynamic Tag Management 187 Tag Manager 2.0 Product Code Tag Dynamic Tag Management Migration Instructions With this option, above this line customization can be configured in the available 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 or if 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 ending with the first s.settagcontainer command. (Do not include this s.settagcontainer in this situation). Here is an example: Paste this code into the Custom editor in the Adobe Analytics tool in dynamic tag management.

188 Migrating to Dynamic Tag Management 188 Tag Manager 2.0 Product Code Tag Dynamic Tag Management Migration Instructions "Then, from the same preview file in ATM, copy the below this line code. This is 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 management after the above this line code. Note: Since mistakes can occur with copy / paste, please be sure to review the implementation in dynamic tag management thoroughly and

189 Migrating to Dynamic Tag Management 189 Tag Manager 2.0 Product Code Tag Dynamic Tag Management Migration Instructions test extensively in staging before publishing to production to ensure the expected behavior is accomplished. Adobe Target Audience Management Adobe Target Tool Adobe Audience Manager Tool Configure Add Adobe Target Tool. Configure Add Adobe Audience Manager Tool. Custom Code 2.0 Custom Code Tag HTML Dynamic Tag Management HTML Migration Instructions Create a rule with conditions mimicking the ATM firing rules. Copy all of the code into the JavaScript / Third Party Tags editor in the rule. Select between non-sequential and sequential HTML as applicable. JavaScript JavaScript Create a rule with conditions mimicking the ATM firing rules. Copy all of the code into the JavaScript / Third Party Tags editor in the rule. Select between non-sequential and sequential JavaScript as applicable. Remote Script HTML Create a rule with conditions mimicking the ATM firing rules. Copy the script URL from the 2.0 tag into the JavaScript / Third Party Tags editor of the rule. Wrap the script url in script tags and configure as non-sequential or sequential HTML as applicable. For example: <script type="text/javascript" src="scripturl"></script> IFrame HTML Create a rule with conditions mimicking the ATM firing rules. Copy the iframe URL from the 2.0 tag into the JavaScript / Third Party Tags editor of the rule. Wrap the iframe url in iframe tags and configure as non-sequential or sequential HTML as applicable. For example: <iframe height="0" width="0" style="display:none;visibility:hidden" src="iframeurl"></iframe>

190 Migrating to Dynamic Tag Management 190 Note: If the conditions set in the firing rules are the same between each custom tag, they can be placed into a single rule in dynamic tag management.

191 Dynamic Tag Management Object Reference 191 Dynamic Tag Management Object Reference A basic object reference for _satellite. The _satellite object is the essential dynamic tag management (DTM) JavaScript object that is generated by the DTM libraries. Important: To ensure ongoing success of your implementation, do not configure custom code in your library to 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, as these 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()

192 Frequently Asked Questions 192 Frequently Asked Questions Frequently 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. Question How do I get started? Answer See Getting Started. How much does dynamic tag management cost? Dynamic tag management is free. Are there limitations on my use of dynamic tag management? You can create as many Web Properties as you want and write as many rules as you want. You can also use it to deliver any digital marketing service, even if you don t use it to deliver Adobe Digital Marketing solutions. There is no effective limitation on your use of the capability. Why is it an advantage for customers (over competitive offerings) to use dynamic tag management from Adobe? The dynamic tag management advantage is the control and flexibility of using rules. It is also the only market-leading tag management solution that supports all of your digital marketing services and is offered to customers at no additional cost. Who can help me with my dynamic tag management implementation? Adobe Global Services provides dynamic tag management implementation, as do several implementation partners. Contact your account manager for more information. With which Adobe Marketing Cloud solutions are dynamic tag management integrated? Dynamic tag management will support all of the Marketing Cloud solutions as well as any digital marketing service, regardless of vendor. How do I access dynamic tag management through the Adobe Marketing Cloud? Before you can start using dynamic tag management, someone from your company must request access. See Requesting Access to Dynamic Tag Management.

193 Frequently Asked Questions 193 Question Why am I getting an "Access Failed" error when I try to access the Marketing Cloud? Answer Make sure that your company has been provisioned to use the Marketing Cloud. See Access the Marketing Cloud in the Marketing Cloud Product Documentation. How do I assign my account to a Company name in the Marketing Cloud? You must add an organization to the Marketing Cloud Organizations & Product Access page and set it as the default organization. You add an organization if you have access to more than one company's Marketing Cloud accounts. See Organizations in the Marketing Cloud Product Documentation. How do I link my account to an Adobe ID? When you click Join Marketing Cloud, you can step through a wizard that helps you link your solution account credentials to your Adobe ID. Your Adobe ID becomes your single login for all of the Marketing Cloud solutions and services. See Join the Marketing Cloud from a Solution in the Marketing Cloud Product Documentation. How do I link solutions from within the Marketing Cloud? For more information, see Link Accounts in the Marketing Cloud in the Marketing Cloud Product Documentation. Do I need to remove my Analytics or other tags from my site to use dynamic tag management? No. You can leverage dynamic tag management without touching any of the existing tags on your site. Just place the embed code and start creating rules. Dynamic tag management can work with existing services tagged directly to the page. Does dynamic tag management work for apps as well as sites? For web apps (applications that run in the browser or for pages with many Ajax sequences), DTM provides excellent data collection and distribution capabilities. See Event Types. For mobile apps, there is a bit of misinformation out there regarding tag management capabilities on mobile devices. The answer depends 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 with responsive designs or mobile-optimized sites consisting of HTML, CSS, and JavaScript. For fully-native, compiled, Objective-C mobile applications where every piece of screen content comes from within the compiled code, there is no tag management system available today to adequately deal with tagging use cases in those environments. For those cases, Adobe recommends the full power, flexibility, and visitor context available 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

194 Frequently Asked Questions 194 Question Answer 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 a mobile application depends on how the app was built. What third-party tags are supported by dynamic tag management? Any third-party tag can be deployed through dynamic tag management. Our top-down, rules-driven approach leverages those third-party tags as fuel for power digital marketing use cases. Does dynamic tag management support HTML5 Yes, HTML5 is supported. Dynamic tag management does not yet support fully native applications. It can handle an application if it has an in-application browser or is essentially a website wrapped in an app container. Properties for the mobile and desktop sites should be able to be set up as normal. Which browser versions does DTM support? See Browser Support. FAQ - Dynamic Tag Management and the Adobe Marketing Cloud A FAQ about using dynamic tag management with the Adobe Marketing Cloud. Question With which Adobe Marketing Cloud solutions are dynamic tag management integrated? Answer Dynamic tag management will support all of the Marketing Cloud solutions as well as any digital marketing service, regardless of vendor. How do I access dynamic tag management through the Adobe Marketing Cloud? Before you can start using dynamic tag management, someone from your company must request access. See Requesting Access to Dynamic Tag Management. Why am I getting an "Access Failed" error when I try to access the Marketing Cloud? Make sure that your company has been provisioned to use the Marketing Cloud. See Access the Marketing Cloud in the Marketing Cloud Product Documentation. How do I assign my account to a Company name in the Marketing Cloud? You must add an organization to the Marketing Cloud Organizations & Product Access page and set it as the default organization. You add an organization if you have access to more than one company's Marketing Cloud accounts. See Organizations in the Marketing Cloud Product Documentation. How do I link my account to an Adobe ID? When you click Join Marketing Cloud, you can step through a wizard that helps you link your solution account credentials to your

195 Frequently Asked Questions 195 Question Answer Adobe ID. Your Adobe ID becomes your single login for all of the Marketing Cloud solutions and services. See Join the Marketing Cloud from a Solution in the Marketing Cloud Product Documentation. How do I link solutions from within the Marketing Cloud? For more information, see Link Accounts in the Marketing Cloud in the Marketing Cloud Product Documentation. How do I provision the Adobe Marketing Cloud ID service using DTM? See Marketing Cloud ID Services. How do I troubleshoot my account access when it is linked to the Marketing Cloud ID Service. For more information about troubleshooting issues that arise from account linking, see Troubleshooting Account Linking in the Marketing Cloud Product Documentation. How do I implement Adobe Experience Manager (AEM) using DTM? Contact Customer Care to get the required information and to get started. FAQ - Advanced A FAQ about performance, rules, loading, hosting, and so on. Question Can I manually implement s_code through dynamic tag management? Answer You can create and configure an Adobe Analytics tool automatically or manually. For more information about a manual (legacy) implementation, see Manually implement Adobe Analytics (legacy). Can I use dynamic tag management on pages with content type application/xhtml+xml or text + xhtml? Yes. The only potential issue is the use of document.write, because content type text + xhtml does not support document.write. However, this issue can be avoided because document.write is used by dynamic tag management only in the situations stated below. Loading of the staging library using the dynamic tag management switch plugin uses document.write. Workaround: Test in the staging environment by specifically referencing the staging library in the page code instead of using the dynamic tag management switch plugin to toggle between libraries. Synchronously loading JS and HTML scripts via dynamic tag management uses document.write.

196 Frequently Asked Questions 196 Question Answer Workaround: The synchronous loading of scripts via dynamic tag management cannot avoid document.write. Thus, when this content type is being used, all third-party scripts (JS and HTML) should be loaded asynchronously in dynamic tag management to avoid document.write. Please always consider and test all code dependencies to ensure the desired behavior is still accomplished with asynchronous loading. Will dynamic tag management reduce my website's performance? Dynamic tag management has never shown signs of negatively affecting page load time or execution speed. However, because dynamic tag management can be used as a delivery system (a way to deliver JavaScript, HTML, images, or other Web content), if you load a large file, or a large image at the wrong point during render time, you can slow down page load speed and increase code execution time on that page. If you lazy load images, and if you use asynchronous (non-sequential) scripts as much as possible, and you follow best practices regarding the code you add into dynamic tag management, you should not see negative performance impacts. The Embed code should be hard-coded in the <head> section of your templates. This is a synchronous JavaScript include. The dynamic tag management engine is designed to work in a modular way, so scripts that do not apply to a particular page, site section, or domain will not load or execute when they are not needed. Most users increase the use of asynchronous (non-sequential) methods when deploying third-party scripts. This generally improves the perceived page load speed for site visitors. While the dynamic tag management main library file itself is loaded synchronously, most clients load any code from within dynamic tag management using the built-in asynchronous methods. How do I remember which tags are in which rules? How do I keep track of my tags and make it easier to find certain rules? Adobe recommends using the rule Name, the Tag Name, and the Categories to label your rules in a way that helps you find things 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 rules respond to different Conditions, it might make sense to add an indicator about the Conditions in the rule Name, like Global Page Load." When working with Third Party Tags or custom JavaScript, you can add information into the Tag Name field. Later, when you are looking for all the rules with a certain tag, you can filter the list of rules by Tag Name to find all rules containing that tag.

197 Frequently Asked Questions 197 Question Answer Finally, each rule can be labeled with a Category and a value. The Category is also available when filtering your list of rules, so you can easily and quickly find the list of rules in a certain Category. For example, 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. Does dynamic tag management have features that help avoid errors due to asynchronous tag loading or rare cases of CDN unavailability? Adobe recommends the use of tag event callbacks provided by amc.on to wrap any code that depends on tags delivered by any tag management system. See amc.on Tag Event Callbacks. Can the dynamic tag management library files work with the version control system we use at my company? Adobe offers two options for self-hosting the library files: FTP Delivery and Library Download. When you choose one of these self-hosted options for the library, each time you make changes in dynamic tag management, those changes are written out by the system to the library files. Those files are typically then "pushed" or "pulled" to your architecture automatically. Once the updated library code is on your servers, you can add the files to your version control systems and processes however you like. If you use GitHub, SVN, or some other system to manage your web development code or content, that works fine with dynamic tag management. One note on version control: Ensure you do not overwrite the production version of the Embed code with the staging version of the 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 the production templates. Can I use dynamic tag management with our mobile applications? Currently, dynamic tag management can be used in any digital experience created with HTML, CSS, and JavaScript. This includes any mobile-optimized content or responsive designs. This also includes mobile applications created with wrappers like Cordova or PhoneGap. Unfortunately, at this time, dynamic tag management does not offer a separate SDK for use with completely native, compiled applications. You can still track your mobile applications using the Adobe Analytics SDK. Dynamic tag management can also be present on HTML documents pulled into your mobile app when desktop or responsive content is accessed within the native app experience, like in hybrid or crossover content situations.

198 Frequently Asked Questions 198 Question How do I set s.pagename without creating a separate rule for each of my web pages? Answer There are a number of ways to set s.pagename for each page, without creating a separate dynamic tag management Page Load rule for each page. In dynamic tag management, the conditions for your rules answer questions like: What s the visitor doing? Where are they doing it? When is it happening? You can set any number of variables, trigger different tags or tools, and execute any number of scripts from within the same rule, as long as you want all those things to happen in response to the same conditions. For example, if you want document.title to be the source for the value of the s.pagename variable, you could create a Data Element with a name of Page Name, a Type of JS Object, a Path of document.title, a Default Value of None, and Remember this value for Pageview. Then, you could create a global Page Load rule and assign that Data Element to s.pagename, either in the interface, or in the Custom Editor code window. It will then be dynamically populated with the value of document.title for each page that meets your conditions. How do I choose a hosting option? Dynamic tag management creates and uses various JavaScript files that contain all the code needed to run the system. These library files can be hosted by Adobe, or they can be hosted on your own servers, 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 Web Property. 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, or subdomains hosted by one of your agency partners. These options give you more flexibility to host the library files according to your specific needs. See Hosting Considerations (FAQ). Does the dynamic tag management code send any information back to Adobe? Dynamic tag management is a way to get JavaScript and HTML to your pages. It sends data only to the systems, tools, or tags that you specifically choose when using the system. In other words, dynamic tag management does not send any data anywhere, unless you specifically tell it what data should be collected, and then tell it when, where, and how it should be sent to any systems, tools, or tags.

199 Frequently Asked Questions 199 Question Answer You have control over the specific data points that only get sent to the places and technologies you designate. How do I handle multiple geo markets, business units, and subdomains? See Separating the DTM Environment for Multiple Entities. My data element setup does not seem to be working. How do I test it? Navigate to a page where the data element should be available on your site. Open your web console and type in _satellite.getvar( dataelementname ) and press enter. This action returns any value that is present for the noted data element on that page. If the value is undefined, the data element is likely setup incorrectly. If the value is null, then that data element may not have a value on that particular page. How can I tell if my site is in a live or staging environment? DTM Switch is a browser plugin for easy switching between debug mode and staging mode for dynamic tag management users. It is available for both Google Chrome and Mozilla Firefox. See Dynamic Tag Management Plugins. FAQ - Adobe Analytics Tool A FAQ about the automatic configuration of the Adobe Analytics deployment. The automatic configuration method manages the AppMeasurement code for you. Question Where do I put my plugins when implementing Adobe Analytics via DTM? Answer If using DTM to manually host the s_code, plugins can be added in the same editor as the hosted s_code, just as it would be in a typical Adobe Analytics implementation. However, it is also an option to place the plugins in the editor within the Customize Page Code section of the tool settings. Both implementation methods should be equally effective. See DTM Switch Plugins. If I make configuration changes in the new version of the tool, can I test in staging before publishing to production? Yes. All changes can be tested in staging just like you normally would before deploying to a production environment. If you choose not to publish, because you notice issues in staging, the production code will continue to function as it did before the new integration was released. If I switch from manual configuration (the default setting for existing tools) to automatic configuration, will my current settings be affected? No.

200 Frequently Asked Questions 200 Question If I switch from manual library management to Managed by Adobe, will my current settings or code be affected? Answer Any user code that you have specified is overwritten with the base AppMeasurement library.you must move this code to the new Custom Page Code section at the end of the tool configuration so that the code continues executing. This method allows the AppMeasurement library to be managed (and upgraded) separately from the user's custom code. Will the revision history for the Adobe Analytics tool be retained when the new integration is released? Yes. How do I configure persistence for a data element? See the Persistence section in Data Elements. 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 Question What is Launch? Answer Launch is the next-generation of the Adobe tag-management capability, built into the Adobe Cloud Platform. Launch enables clients to: Deploy client-side web products using integrations called extensions Consistently capture, define, manage, and share data between marketing and advertising products from other vendors and from Adobe Launch is an advanced JavaScript delivery system that evaluates conditions and executed actions to efficiently and effectively deploy client-side libraries and products. It provides a highly scalable approach to managing and building extensions, together with a robust set of APIs for programmatic interaction with the Adobe Cloud Platform. For more frequently asked questions about Launch, see Adobe Cloud Platform 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 logic in its core library file that delivers file assets only when needed. In addition to a focus on scenario-based logic and precise activation of vendor technologies, dynamic tag management provides a series of features that dramatically improve page speed. These include:

201 Frequently Asked Questions 201 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 dynamic tag management provides the best set of options that can be assembled to meet these challenges. There are also a 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 assets 2. Creating site pages from the server 3. Reducing the number of downloaded files 4. Reducing the size of downloaded files 5. Improving the connection speed to source files 6. 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 these areas can increase and decrease the time that it takes for a page to load. Because TMS vendors cannot directly address 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 approach that each TMS takes to accomplish those tasks might vary somewhat, but in the end they each provide some improvement to the final file weight that is delivered to the page.when evaluating a TMS it is important to understand the 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 size with some degree of success. The areas where TMS solutions can see appreciable speed differences on the page are in the areas of connection speed and file loading. All of the major TMS offerings provide the option of a globally distributed CDN to deliver their files. 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 cautionary questions 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 TMS vendors. Self-hosting of TMS assets prevents this situation from occurring because the files are delivered along with the rest of the client-hosted website assets either on their own architecture or an architecture of their choice.

202 Frequently Asked Questions 202 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 TMS have 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 asynchronous tag loading, conditional logic that determines what file assets will be delivered, and the placement of timeouts on tags provide ways to parallelize tag behavior and improve the loading of the page. Although the final tag weight may not be significantly different at the end of the page load, moving third-party vendor tags from a synchronous to asynchronous load allows multiple assets to load in parallel rather than one at a time. How much flexibility does the TMS provide regarding the timing and sequencing of vendor code? Does the TMS vendor provide best practices for optimizing page performance in relationship to file loading? Can third-party vendor code be easily changed from synchronous 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 addressed when evaluating a TMS. Critical questions need to be answered regarding workflow and governance, rule deployment methodologies, 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 performance record 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 Question What is Launch? Answer Launch is the next-generation of the Adobe tag-management capability, built into the Adobe Cloud Platform. Launch enables clients to: Deploy client-side web products using integrations called extensions Consistently capture, define, manage, and share data between marketing and advertising products from other vendors and from Adobe Launch is an advanced JavaScript delivery system that evaluates conditions and executed actions to efficiently and effectively deploy client-side libraries and products. It provides a highly scalable approach to managing and building extensions, together with a robust set of APIs for programmatic interaction with the Adobe Cloud Platform. When will Launch be released? Launch began a rolling release to production on November 7, This means that Launch will be released to customers incrementally over the course of a few months. Customers who wish to gain access to Launch may indicate their interest by providing their Company Name, Org ID, and a contact address in the Launch Release Form. Every two weeks, Adobe will

203 Frequently Asked Questions 203 Question Answer randomly select a number of these customers who will then be given access and receive a single notification of their access. Is Launch just an updated DTM? No. Launch is an entirely new product with a new code base. The system has been re-architected from scratch using modern front-end development practices and an API-first approach. Everything is built on a robust set of APIs, which makes the system very powerful and highly flexible. Will the current DTM product remain available? Yes, legacy DTM (the existing production version) will continue to be supported for the foreseeable future. Adobe will continue to fix any significant bugs and ensure consistent performance. At this time, no major feature enhancements are planned for legacy DTM. The Launch team is working to make the migration process from legacy DTM to Launch as easy as possible so customers can take advantage of more than twenty new features, extensions, and APIs that Launch provides. How much will Launch cost? There is no additional charge for Launch. It will be available for any Adobe Experience Cloud customer. Will I have to change the embed codes in my current DTM implementation? No, you won't have to change your Staging or Production embed codes if you're currently using the existing (legacy) DTM system. You can continue to work in your current DTM Company and Web Properties without worrying at all about changing those embed codes. The product team has not finalized the migration process just yet, but they are working to make it as easy and automated as possible. I heard there are plug-ins now. What's that about? Launch is built into the Adobe Cloud Platform and it is fully extensible. Customers, Adobe Partners, agencies, and marketing or advertising technology vendors will soon be able to build Launch extensions that add new functionality or modify existing functionality. The system allows partners and clients to build, manage, and update their own integrations. This is just one way Adobe is opening up the Adobe Cloud Platform so customers and partners can build products and businesses on the Platform, and so everyone can more easily connect Adobe technology to the marketing and advertising technologies from other vendors. Over time, this will be the place for customers to install and configure all of their client-side technologies. Will all third-party tools be available right away? Extensions will be available for all Adobe solutions and for a select group of independent vendors when Launch is released. The product team is working closely with several technology partners to ensure the availability of these extensions upon release. After that initial release of Launch, the product team will work to expand the number of extensions as quickly as possible. Because extensions can be built, managed, and updated by the Extension

204 Frequently Asked Questions 204 Question Answer developer, vendors won't have to wait for Adobe engineering to build them, so this should be a very rapid process going forward. When will clients or partners be able to build extensions? After general availability, Launch will open its virtually self-service portal that extension developers can use to build their own integrations with the Adobe Cloud Platform. Will Launch meet my company's security standards? Yes. Launch is SOC-2 and Gramm-Leach-Bliley Act ready. Launch also offers the capability of being self-hosted. The JavaScript libraries can be served from your own servers, or the CDN of your choice. For I.T. and security teams, this gives you the ability to run automated testing, to check the files into your own version control system, and to fully comply with any internal production migration processes, security-related or otherwise. I have a project coming up very soon. Should I wait for Launch? If you are already using legacy DTM, or are currently deploying DTM, you should continue to do so. Don't wait. Move your projects forward using the current DTM. Then, when you're ready to move to Launch, the migration process will make it as easy and automated as possible (no on-page embed code changes, and automated migration of Rules and Data Elements). Which capabilities exist in Launch that don't exist in legacy DTM? Launch will offer four major capabilities that aren't comparable to legacy DTM: Deploy non-adobe client-side browser technologies quickly and easily Using extensions, clients and partners can easily control in-browser technologies in the interface, without managing custom code. Enterprise-grade publishing Compartmentalize and control each piece of your libraries to deploy precisely what you need, where you need it, and when you need it. Robust approval workflows Flexible approval workflows allow custom processes to match your existing internal 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 certain users. Does Launch support single page apps and my favorite framework? Yes. Launch has capabilities to give users and extension developers flexibility in collecting, managing, and distributing data within single page application experiences or Ajax-heavy pages or sites. This applies regardless of your development framework preferences, whether that's Angular, React.js, Ember, Meteor, etc.

205 Frequently Asked Questions 205 Question Does Launch support dynamic data layers? Answer Yes. Launch includes an extension that specializes in listening for changes in dynamic data layers. Which event types does Launch support? Event types are available through extensions. The pre-loaded DTM extension includes 30 built-in event types. Other extensions could add additional event types. For example, the YouTube extension includes four video event types: play, pause, end, and time played. Through extensions, Launch can support any other browser event types or synthetic event types, such as specific visitor activity sequences. Will the new Launch speed up (or slow down) my web site? Launch is designed to deliver and run marketing and advertising technologies on your web site as efficiently as possible using today's best practices. When used properly, Launch has proven to improve performance of web sites over alternative methods of providing similar functionality. Which browsers will Launch support? Browser support in the Launch client-side libraries: 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 last few years, the percentage of overall web users with older, outdated browsers has dropped to a small segment for our clients. Most Adobe clients now leverage more modern web platform features in current browsers and create better user experiences, including single page applications and interactive Ajax-heavy web sites and pages. As most clients move to more modern approaches with their sites, they demand a solution like Launch that enables those approaches. Does the new Launch work on native mobile apps? Adobe continues to recommend the Mobile Services App SDK to implement data collection and delivery in a native mobile app environment. With Adobe mobile services, the process is streamlined with a single SDK that works with multiple Adobe Cloud Platform solutions. Going forward, you will see additional tag management-like functionality in the Mobile Services interface

206 Frequently Asked Questions 206 Question Answer as the Launch and Mobile teams continue working closely together for more seamless Cloud Platform access and user experiences. What if I have other questions? These are the questions we've received most often from customers and partners since the Launch announcement. If you have other questions, please ask in the Adobe Community on the main Launch page located at Launch is just one example of where our platform is headed: more open, more integrated and as always dedicated to customer success.

207 Resources 207 Resources Additional resources to help you get the most out of Dynamic Tag Management. Additional resources will be added to this list in the future. Resource How do I use DTM for a Single Page App? Details This post on the Digital Data Tactics blog is a great resource when using DTM on Single Page Apps (SPAs) Digital Data Tactics contains additional posts about DTM and other Adobe Marketing Cloud Solutions.

208 Troubleshooting 208 Troubleshooting Describes several troubleshooting scenarios and their solutions and provides a list of Frequently Asked Questions (FAQ). This section contains the following information: 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 export a list of all activities that take place within companies and web properties to which they have access. This feature is 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 click on 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 the page. 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/aaaabbbcccddddeeee /satellitelib-aaaabbbcccddddeeee 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 was expecting HTML, but you set the script to JavaScript or vice versa.

209 Troubleshooting 209 For example: if your script contains <script> tags, but you set the script up as JavaScript, you will receive this error when 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. Locate the element on your site where the desired event action occurs, right click and select Inspect element. Inspect the highlighted 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 load order of rules? It is important that rules fire in the correct order. Many problems with rules are the result of rules firing in the wrong order. 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 page loads.you need to check the box within the rule identifier indicating Delay link activation. This keeps the activated link 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 on a child or parent item, ensure the button indicating Allow events on child elements to bubble is checked. This ensures 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 or DOM 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, then the data element is likely not available yet when the rule fires. Try switching the rule to load at Bottom of Page or DOM Ready. If the data element still does not populate, refer to method for the previous question to ensure the data element 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 tag management users. It is available for both Google Chrome and Mozilla Firefox. For more information, see Dynamic Tag Management Plugins. Watch an Adobe training video that demonstrates how to debug a rule by using the DTM switch plugins:

210 Troubleshooting 210 DTM Basics: Introduction Time: 3:41 By then end of this video you should be able to: Use the DTM debugging plugin 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 set linktrackvars / 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 / events via 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 linker link? There is likely a code conflict with the linker link feature. Navigate to your analytics tool within your web property and 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 set it 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 JavaScript console, which says that Chrome might block document.write calls in the browser if the device has "poor network connectivity." Chrome specifically states they are currently targeting users on 2G networks. See "Intervening against document.write()" on the Google Developers website. Due to the limited usage of 2G network, the current 2G Google intervention should have a minimal impact on enterprise customers at this time. Adobe is proactively addressing future issues that might develop if Google continues to 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 includes allowing 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 continue to 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.

211 Troubleshooting 211 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 the page 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 who are 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.

212 Dynamic Tag Management Plugins 212 Dynamic Tag Management Plugins Adobe has partnered with Search Discovery and Disruptive Advertising to offer additional plugins to help you with debugging 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 help you set up and configure other products. Note: Search Discovery is the creator of the plugins mentioned in this topic. Contact Search Discovery for support issues for these plugins. This topic contains information about the plugins currently offered. See the Search Discovery website for an updated list. This section contains the following information: 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 management users. 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 with no additional support from Adobe. You can also manually set the debugger and switch between libraries via the dynamic tag management web console. This section contains the following information: 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.

213 Dynamic Tag Management Plugins 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.

214 Dynamic Tag Management Plugins 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 unpublished rules for Akamai hosting WordPress Plugin Easily set up and configure WordPress using dynamic tag management. This plugin installs the necessary DTM code 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.