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...5 Release Notes for Dynamic Tag Management...7 Dynamic Tag Management Overview...9 Getting Started...11 Planning for Dynamic Tag Management...13 Managing Users and the Publish Workflow...13 Web Properties...15 Create a web property...17 Users and Permissions...20 Invite a user...20 Create and Manage Groups...20 Add Users to Groups...21 Create a New Group...22 Edit a Group...24 Delete a Group...25 Embed Code and Hosting Options...26 Hosting Considerations (FAQ)...28 Akamai...29 Migrate from Amazon S3 to Akamai...30 FTP...31 Library Download...32 Header and Footer Code...33 Add header and footer code...34 Verify header and footer code...34 Last updated 9/2/2015 Dynamic Tag Management Product Documentation

3 Contents Tools...35 Add Adobe Analytics Tool...35 General...39 Library Management...39 Global Variables...42 Page Views and Content...44 Link Tracking...45 Referrers and Campaigns...46 Cookies...46 Customize Page Code...47 FAQ for Adobe Analytics Release - July Manually implement Adobe Analytics (legacy)...49 Add Adobe Audience Manager Tool...51 Add Adobe Media Optimizer Tool...52 Media Optimizer Rule Example...54 Add Adobe Target Tool...55 Library Management - Adobe Target...57 Global Parameters - Adobe Target...58 FAQ for Adobe Target Deployment - Released October Mbox rule example for DTM...60 Marketing Cloud ID Service Settings...62 Add Google Analytics Tool...64 Add Google Universal Analytics Tool...67 Insert third-party tags...70 Object References to Handle Cookies...70 Data Elements...71 Create a data element...76 Rules...77 Event-Based Rules Example...79 EnterpriseTV Videos: Event-Based Rules...82 Last updated 9/2/2015 Dynamic Tag Management Product Documentation

4 Page Load Rules Example...83 Page Load Rules - Advanced...85 EnterpriseTV Videos: Page-Load Rules...87 Load Order for Rules...87 Create new rule...90 Create conditions for event-based rules...90 Create conditions for page-load rules...94 Create conditions for direct-call rules...95 Set up actions for the condition to trigger...96 Test unpublished rules for Akamai hosting...97 Test rules for Library Download or FTP...97 Rule Conditions and Functions...98 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 Architecture Troubleshooting DTM Plugins Documentation Updates Previous Release Notes Contact and Legal Information Last updated 9/2/2015 Dynamic Tag Management Product Documentation

5 Dynamic Tag Management Product Documentation 5 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: September 3, 2015 Getting Started & Popular Topics Request access Deploy Adobe Analytics Deploy Adobe Target (New) Deploy Media Optimizer (New) Frequently asked questions Troubleshooting What's New and Release Notes Release Notes for Dynamic Tag Management Current release notes and known issues for dynamic tag management. Marketing Cloud ID Service 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) Videos In EnterpriseTV, click Dynamic Tag Management. Plugins DTM 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 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. 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

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

7 Release Notes for Dynamic Tag Management 7 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, Historical Release Notes, and Marketing Cloud Release Notes Current Release Notes September 3, 2015 Adobe has deprecated the use of Amazon S3 as a DTM library hosting option. 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. The September 3, 2015 dynamic tag management release includes the following changes: New Features Feature Group management 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 properties. For more information, see: Create and Manage Groups Add Users to Groups Create a New Group Edit a Group Delete a Group Fixes and Enhancements: Improved the deployment of the satellite library (2-5 times speed increase). Customers with many rules or who are deploying many third-party tags will greatly benefit from these changes. Improved the upload speed to Akamai (up to 5 times faster). Improved the load speed (2 times faster) for all rule listing pages. Fixed an issue that prevented some pages from loading in Internet Explorer (users received a pop-up error message). Documentation Updates, Historical Release Notes, and Marketing Cloud Release Notes In addition to the notes for each release, the following resources provide additional information:

8 Release Notes for Dynamic Tag Management 8 Resource Documentation Updates 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 Adobe Social. 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 Video 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. Quicker Implementations: Significantly reduce deployment time. Increased Efficiencies: Reclaim substantial amounts of time spent managing analytics and media tags.

10 Dynamic Tag Management Overview 10 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 Video 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. Watch the overview video.

11 Getting Started 11 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 EnterpriseTV Training Videos Requesting Access to Dynamic Tag Management Before you start using dynamic tag management, someone from your company must request access. Your request will be fielded by our provisioning team and you should receive your login credentials within one to two business days. To request access to dynamic tag management, visit the Adobe Marketing Cloud > Dynamic Tag Management page. 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 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.

12 Getting Started 12 Step Getting Started Tasks Location 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. 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.

13 Getting Started 13 EnterpriseTV Training Videos In EnterpriseTV, click Dynamic Tag Management. 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. 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 Approvers Create and test rules. Review and approve rules, making approved states of rules publishable.

14 Getting Started 14 Role Publishers Administrators 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.

15 Web Properties 15 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. 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 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? 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.

16 Web Properties 16 Consideration Best Practice 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. 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.

17 Web Properties 17 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? 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. Create a web property Create a web property in dynamic tag management. Before beginning, review the Best Practices for Planning Web Properties for web properties. 1. Navigate to your company page, then click Add Property.

18 Web Properties Fill in the fields: Element Name URL This site spans multiple domains 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 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.)

19 Web Properties 19 Element Tracking Cookie Name Tag Timeout 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. We recommend anything under 500 milliseconds, which the user will not perceive. 4. Click Create Property. The new property will be created in a "pending" state within your Web Properties tab until an administrator approves and activates the property. After activation, the property status changes from Pending Approval to Active.

20 Users and Permissions 20 Users and Permissions You can invite users to dynamic tag management and assign user roles and add users to groups.. Note: You must have administrative privileges to invite a new user in dynamic tag management. Administrators are automatically granted permissions to a new property. This section contains the following information: Watch an Adobe EnterpriseTV video demonstrating how to create a user in dynamic tag management and set permissions: Adobe EnterpriseTV Training Video: Invite a user Invite a user to dynamic tag management. 1. From your company dashboard, click Users. 2. Click Invite User. 3. Enter the user's address. 4. (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. 5. 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. Create and Manage Groups 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. Watch an Adobe EnterpriseTV video explaining the benefits of using groups and how to set them up: Adobe EnterpriseTV Training Video: 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:

21 Users and Permissions 21 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.

22 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. 3. Fill in the fields:

23 Users and Permissions 23 Name: (Required) Specify a descriptive name for the group. : 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. 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."

24 Users and Permissions 24 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. Edit a Group Edit an existing user group to change its name, description, default role, or add users to the group.

25 Users and Permissions 25 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.

26 Embed Code and Hosting Options 26 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. This section contains the following information: Hosting Workflow Hosting Options EnterpriseTV Video - Library Hosting Options Hosting Workflow The following illustration shows the hosting workflow in dynamic tag management:

27 Embed Code and Hosting Options 27 Hosting Options You can deploy dynamic tag management using one or more of the following options, found on the Embed tab: Hosting Option Implementation Akamai (migrated from Amazon S3) Amazon S3 The simplest hosting option to implement. Globally distributed delivery network. 1. Dynamic tag management generates custom JavaScript libraries. 2. Dynamic tag management exports the custom JavaScript libraries to Akamai. Adds additional third-party infrastructure dependencies (DNS lookup, Akamai availability). 3. The target website references the Akamai-hosted See Akamai for information about migrating from Amazon S3 to Akamai. 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. dynamic tag management libraries directly at the page level. 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. 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. Additionally, the libraries are available via web download directly from the dynamic tag 1. Dynamic tag management generates custom JavaScript libraries. 2. Dynamic tag management exports the custom JavaScript libraries to Akamai. 3. Custom dynamic tag management libraries are manually or programmatically moved to the web content server. management interface. 4. The target website locally references the custom dynamic tag management libraries. This solution requires either a manual retrieval and publication of the dynamic tag management libraries

28 Embed Code and Hosting Options 28 Hosting Option 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. To check if the latest version of your library file is being referenced, use the command _satellite.publishdate in the web console. This will return the date and time of publish for the library file currently being referenced. Compare this to the time and date of your latest publish shown in the History tab of your property to determine if the file has been updated. Implementation 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. EnterpriseTV Video - Library Hosting Options Watch an Adobe EnterpriseTV video explaining the different library hosting options you can use with dynamic tag management: Adobe EnterpriseTV Training Video: 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 change is made in dynamic tag management, the files you re hosting on your servers can be updated in an automated manner.

29 Embed Code and Hosting Options 29 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. 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.

30 Embed Code and Hosting Options 30 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. 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.

31 Embed Code and Hosting Options 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 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.

32 Embed Code and Hosting Options Provide the required FTP information for the staging and production servers, then click Save FTP Information. 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. 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:

33 Embed Code and Hosting Options 33 Option 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. 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. 8. Copy the header code and place it within the HEAD section of the site HTML, on every page of the website. Place it as close to the beginning <head> tag as possible. 9. Copy the footer code and place it within the BODY section of the site HTML, on every page of the website. Place it as close to the closing </body> tag as possible Header and Footer Code 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. 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.

34 Embed Code and Hosting Options 34 Add header and footer code Add header and footer code in dynamic tag management. 1. Copy the production header code and place it within the HEAD section of your site HTML. Place the code as close to the <head> tag as possible. This code snippet should be placed on every page 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. Type the following command into the console: _satellite.settings.notifications = true; 4. 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.

35 Tools 35 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 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 Service (Analytics Visitor ID) Google Analytics Google Universal Analytics 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 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. This section contains the following information: Add an Adobe Analytics Tool Edit an Existing Adobe Analytics Tool Enabling Adobe Analytics Premium EnterpriseTV Video - Add Adobe Analytics Tool Add an Adobe Analytics Tool 1. Click Web Property Name > Overview > Add a Tool > Adobe Analytics.

36 Tools Fill in the fields: Element Tool Type Tool Name Configuration Method The type of tool, such as Adobe Analytics. A descriptive name for this tool. This name displays on the Overview tab under Installed Tools. Manual: Manually manage the AppMeasurement code. You can download the AnalyticsAppMeasurement 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)) A number for your production account for data collection. Dynamic tag management automatically installs the correct account in the production and staging environment. Staging Account ID: (Required) A number used in your development or test environment. 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. Note: These fields are required when using a manual configuration with multiple report suites.

37 Tools 37 Element SSL Tracking Server: Specify the information for your SSL tracking server. Automatic: 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. 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. 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 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. Element Enable Automatic Configuration Note: Enabling this setting changes a manually configured implementation to the automatic configuration method described in Configuration Method.

38 Tools 38 Element 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. EnterpriseTV Video - Add Adobe Analytics Tool Watch an Adobe EnterpriseTV video demonstrating how to add Adobe Analytics as a dynamic tag management tool: Adobe EnterpriseTV Training Video:

39 Tools 39 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 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. Library Management s of the fields and options in the Library Management settings in dynamic tag management.

40 Tools 40 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 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. Managed by Adobe 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. 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 AppMeasurment code when manually deploying dynamic tag management in Adobe Analytics.

41 Tools 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. 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 = new AppMeasurement(); s.account = "[insert account name]"; Alternatively, if you prefer to set s.account dynamically, based on the environment (staging or production), follow these steps: 1. Add this function to the top of the AppMeasurement file: s = new AppMeasurement(); function getanalyticsaccount() { for(var toolid in _satellite.tools) { if(_satellite.tools[toolid].settings.engine == "sc") { return _satellite.tools[toolid].settings.account; } } } 2. Replace the second line of code (s.account = "[insert account name]";) mentioned as a minimum requirement in the preceding step with s.account = getanalyticsaccount();. For example:

42 Tools 42 These steps will force s.account to set dynamically, based on the account IDs indicated in the Account Numbers fields in the dynamic tag management: Note: This method works only for the first Adobe Analytics tool that is installed in a given web property. If there are multiple Analytics tool instances installed in a single web property, the function returns only the account value for the first tool. 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. Global Variables - Field s Dynamically Populate Variables

43 Tools 43 Global Variables - Field s Property > Element Server Edit Tool > Global Variables 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. Dynamically Populate Variables You can assign element attributes to variables dynamically by using 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. 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.

44 Tools 44 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 Adobe Analytics: 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. 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 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.

45 Tools 45 Element 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. Property > Edit Tool > Link Tracking Element Enable ClickMap 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 you 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 the query strings.

46 Tools 46 Element See linkleavequerystring. Referrers and Campaigns Field descriptions in dynamic tag management for referrers and campaign options when deploying dynamic tag management in Adobe Analytics. Property > Edit Tool > Referrers & Campaigns Element 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. Cookies Field descriptions for the Cookies global settings used for deploying dynamic tag management in Adobe Analytics. Property > Element Visitor ID Edit Tool > Cookies 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. FP Domain Periods 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.

47 Tools 47 Element 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 Field descriptions in dynamic tag management for customizing page code when deploying Analytics. Property > Element Open Editor Edit Tool > Customize Page Code 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

48 Tools 48 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. Do I have to do anything to get the new functionality? No. The existing tool automatically becomes available. You can then view the configuration for your Adobe Analytics tool to see the new configuration options. 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 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 my current settings or code be affected? 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.

49 Tools 49 Question Will the revision history for the Adobe Analytics tool be retained when the new integration is released? Answer Yes. 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.

50 Tools 50 d) Configure the following fields: Element Tool Type Tool Name Production Account ID Staging Account ID 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.

51 Tools 51 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 Load audience management page code at (Page Top or Page Bottom) Audience management page code already present Code version Integrate with Modules: Adobe Analytics Google Analytics Open Editor Add a Note You can name this instance of audience manager. A unique alphanumeric identifier assigned by audience manager. You can control where and when to load the page code. The recommended location is selected by default. 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.

52 Tools 52 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 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 to add to your existing advertising management implementation, rather than starting a new implementation.

53 Tools 53 Setting 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. SKU 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

54 Tools 54 Setting 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. 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.

55 Tools 55 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. 4. Enable Load Adobe Media Optimizer for this rule. 5. Configure the settings you want to apply in this rule. All of the settings are optional, because global configurations from the installed Adobe Media Optimizer tool 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

56 Tools 56 The following potential implications exist regarding the Target tool: If you currently load mbox.js through a global page load rule in dynamic tag management, adding a new Adobe Target tool to the property, or changing the configuration of an existing Target tool, could break this implementation method. This occurs because the tool deploys another instance of the mbox.js when using either of the available Automatic configuration options or the Manual > Hosted by Adobe configuration option. Presently, auto-loading the mbox.js code via the integrated Target tool could break scripts currently being deployed later in the <head> as they may be pushed down into the <body/> section of the page. If you encounter this conflict, there is always the option of reverting to manual code configuration (your hosted code is retained but becomes editable in the editor). You can move the createglobalmbox() function out of the mbox.js and into a page load rule to avoid sequencing issues. Global parameters configured in the new dynamic tag management interface takes effect only if you are using TNT.createGlobalMbox(). If you created your mboxes using mboxcreate(), these parameters will have no effect. Important: Adobe strongly suggests that you thoroughly test the new Adobe Target integration in your staging library before publishing the new tool configuration to your production library. Testing allows you to fully vet the new integration and mitigate conflicts with your current implementation before it is implemented on your production site. This update will be automatically added to all accounts but will not be activated on your staging library until you make a change to the staging library (any rules or tool edit). Likewise it will not be activated in your production library until you publish changes to your production library. Additionally, any current Adobe Target tools in dynamic tag management will maintain their current functionality and will default to the Manual > Custom configuration option and all currently included code will be maintained. Field s - 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 The type of tool, such as Adobe Target.

57 Tools 57 Setting 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 mbox.js file from the Target solution interface as follows: Target Classic: Configuration- > mbox.js > Download Target Standard: Setup > Implementation > Download mbox.js 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 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 s of the fields and options in the Adobe Target Library Management settings in dynamic tag management. Property > Edit Tool > Library Management

58 Tools 58 Element Load Adobe Target Library synchronously This option ensures the 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 mbox.js code in this way. Once the accounts are connected, dynamic tag management pulls the Adobe Targetmbox.js code into the tool and optimizes the configuration process. This process increases consistency between the two solutions. Code Configuration Managed by Adobe: 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 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. At URL: If your 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 s 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. 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.

59 Tools 59 Property > Edit Tool > Library Management Element Name Indicate the name of the additional parameter(s) you wish to pass to the global mbox. Adobe Target does not accept the usage of and in this field. Using it leads to errors on the web page. Parameters here take effect only if you use TNT.createGlobalMbox(). If you created your mboxes using mboxcreate(), these parameters have no effect. Value Indicate the value of the additional parameter(s) you want to pass to the global mbox. FAQ for Adobe Target Deployment - Released October Frequently asked questions for the Adobe Target deployment using dynamic tag management. This content is relevant only to the Target tool updated on October Important: Adobe recommends that you thoroughly test this Adobe Target integration in your staging library before publishing the new tool configuration to your production library. Testing the new integration mitigates potential conflicts with your current implementation before it is implemented on your production site. Question Is this a new Adobe Target tool or a change to the existing tool? Answer A change to the existing tool. If you currently have an implementation of Adobe Target in dynamic tag management, it will continue to function as is unless you make a change. Please review the following questions for more details on avoiding potential issues. Do I have to do anything to get the new functionality? No. The existing tool automatically becomes available. You can then view the configuration for your Adobe Target tool to see the new configuration options. 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.

60 Tools 60 Question If I switch from manual configuration (the default setting for existing tools) to automatic configuration, will my current settings be affected? Answer No. How does changing from manual library management to Managed by Adobe affect my current settings or code? The code previously hosted in the manual editor is replaced by the mbox.js code supplied by the linked Adobe Target account. See Library Management - Adobe Target Will the revision history for the Adobe Target tool be retained when the new integration is released? Yes. I currently load Adobe Target through a page load rule. Should I be aware of anything as I migrate to the built-in tool? If you currently load mbox.js through a global page load rule, adding a new Target tool to the property, or changing the configuration of an existing Target tool, could break this implementation method. This occurs because the tool deploys another instance of the mbox.js when utilizing either of the available automatic configuration options, or the Manual > Hosted by Adobe configuration option. To avoid this issue, test the deployment in staging to ensure you are only deploying a single mbox.js code on your site before deploying a new tool configuration to production. What pitfalls should I be aware of as I migrate to the Adobe Target tool? With the present functionality of the mbox.js code, auto-loading the mbox.js code via the integrated Target tool could break scripts currently being deployed later in the <head> as they may be pushed down into the <body/> section of the page. If you encounter this conflict, revert to the Manual code configuration (your hosted code is retained and becomes available in the Custom editor), and move the createglobalmbox() function out of the mbox.js code. Place it in a page load rule to avoid sequencing issues. Mbox rule example for DTM 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.

61 Tools 61 Configure the rule so that it fires only on the pages where you want to deploy the mbox. 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.

62 Tools 62 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. 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. Marketing Cloud ID Service Settings Deploy the Marketing Cloud visitor ID service using dynamic tag management. This enables Important: The Marketing Cloud ID Service tool integrates only with Adobe Analytics and the Adobe Marketing Cloud. This service must be the first code that loads on a page. It must load synchronously, and it cannot be edited. Additionally, to avoid conflicts, use only one method of deploying the Marketing Cloud ID Service (either the dynamic tag management deployment, or manually using your own code). <Web Property Name> > Overview > Add a Tool > Marketing Cloud ID Service

63 Tools 63 You can automate the deployment of the Marketing Cloud ID Service using dynamic tag management. This service enables Marketing Cloud services and features, such as Audiences, where you can publishing an Analytics audience segment. Field - Marketing Cloud ID Service Settings Validating Deployment of the Marketing Cloud ID Service Field - Marketing Cloud ID Service Settings Field descriptions for options found on the Marketing Cloud ID Tool and on the Marketing Cloud ID Service Settings page. Element Tool Type Tool Name The type of tool, such as Adobe Analytics, Adobe Target, or Marketing Cloud ID Service. The name for this tool. This name displays on the Overview tab under Installed Tools. Marketing Cloud Organization ID (Required) The ID associated with your provisioned Marketing Cloud company. An Organization is the entity that enables an administrator to configure groups and users, and to control single sign-on in the Marketing Cloud. This ID is a 24-character alphanumeric string, followed by (and must Marketing Cloud administrators can find this ID in Marketing Cloud > Tools. Automatically Request Visitor ID Enabling this option causes dynamic tag management to automatically call the getmarketingcloudvisitorid() method before loading any of the Adobe solutions that use the Marketing Cloud ID service. See Library Reference in Marketing Cloud Visitor ID help for information about getmarketingcloudvisitorid() Tracking Server (Required for Adobe Analytics) The tracking server used for Adobe Analytics data collection. It is the domain at which the image request and cookie is written. (For example, site.omtrdc.net). See trackingserver. Tracking Server Secure (Optional) If you use a secure Adobe Analytics tracking server, specify it here. This specifies 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. Marketing Cloud Server (Optional) If your company uses first-party data collection (CNAME) to utilize first-party cookies in a third-party context, enter the tracking server here. For example, metrics.company.com.) Marketing Cloud Server Secure (Optional) If you use a secure Analytics tracking server for first-party data collection, specify the server here. (For example, s.metrics.company.com.)

64 Tools 64 Element Library Version The version of the AppMeasurement Library you want to use. This code is not editable for the Marketing Cloud ID Service. (For example, s.metrics.company.com.) Settings The name-values pairs defined in these fields are available as Visitor ID instance properties. Customer ID The Visitor API accepts multiple Customer IDs for the same visitor along with a Customer type identifier, to separate the scope of the different Customer IDs. Validating Deployment of the Marketing Cloud ID Service Ensure the library being used in other solutions is up-to-date to support the Marketing Cloud ID Service. The dynamic tag management engine does not validate this for you. Important: To avoid conflicts, do not attempt multiple deployments of the Marketing Cloud ID Service: Use only one deployment method: either the dynamic tag management deployment, or manually, using your own code. The getinstance() function, as well as any other related visitorapi.js, should be removed from the AppMeasurement file when deploying the Marketing Cloud ID Service in dynamic tag management. See Verify Marketing Cloud ID Service Implementation to verify that the Analytics request contains a mid (Marketing Cloud Visitor ID) parameter. See Visitor ID Service Requirements for information about specific code versions and other Visitor ID service requirements. 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 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.

65 Tools 65 Setting Enable EU compliance for Google 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"); 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 Load Google Analytics page code at Page Top or Page Bottom 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). You can control where and when to load the page code (on a rule-by-rule basis).

66 Tools 66 Setting 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. 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 Classify the following referrers as direct Clear Keywords & Referrers from User Cookies Open Editor 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. 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

67 Tools 67 Setting command and write your own to customize page names, be sure to "return false;" at the end of the script. 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 Production Account ID Staging Account ID The name of this instance of Google Analytics. 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 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:

68 Tools 68 Element 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. Tracker Name 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).

69 Tools 69 Element 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 Cookie Name Cookie Path Cookie Domain Control how long a cookie lasts for a visitor to count as a repeat visitor. The default value is two years. 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 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.

70 Tools 70 Element Open Editor 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;" Insert third-party tags Deploy third-party tags from vendors, using dynamic tag management. As a general rule, tags that depend on page elements should be defined as sequential tags. 1. 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)

71 Data Elements 71 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. 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 EnterpriseTV Video - Data Elements Types of Data Elements The following table describes the types of data elements. Type JavaScript Object Any available JavaScript object or variable can be referenced using the path field. Example document.title CSS Selector Any element value can be retrieved, such as a div or H1 tag. CSS Selector Chain: id#dc logo img Get the value of:

72 Data Elements 72 Type Cookie Any available domain cookie can be referenced in the cookie name field. Example src cookiename URL Parameter 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 contenttype Custom Script 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. 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 Protocol Used in rule: %protocol% Returns document.location.protocol

73 Data Elements 73 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.

74 Data Elements 74 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.

75 Data Elements 75 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:

76 Data Elements 76 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. EnterpriseTV Video - Data Elements Watch an Adobe EnterpriseTV video explaining the benefits of using data elements and how to set them up: Adobe EnterpriseTV Training Video: 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 Name Type The data element friendly name that a marketer can recognize. For example, Product ID. 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. Note: Unknown is returned when you use a data element and no object exists, and there is no default value in the data element definition. 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.

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

78 Rules 78 Type of Rule 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.

79 Rules 79 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 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. Note: When using event-based rules, it helps to have some knowledge of CSS selectors so that you can identify elements on the page. The following links are useful resources to learn about CSS: CSS Selector Pattern Matching Syntax CSS Selector Reference

80 Rules 80 Set up how to track this click in Adobe Analytics.

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

82 Rules 82 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. EnterpriseTV Videos: Event-Based Rules Watch Adobe EnterpriseTV videos that explain event-based rules on a conceptual basis and demonstrate how to create and configure them. Event-Based Rules (Part 1) Conceptual information about event-based rules and information to help you set up dynamic tag management rules based on specific events occurring on a page: Adobe EnterpriseTV Training Video: Event-Based Rules (Part 2) Continued review of dynamic tag management event-based rules, including additional configuration options: Adobe EnterpriseTV Training Video: Event-Based Rules (Part 3) Final review of dynamic tag management event-based rules, including the creation of a rule based on view ports, or the area you see on the site. Adobe EnterpriseTV Training Video:

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

84 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 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.

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

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

87 Rules 87 EnterpriseTV Videos: Page-Load Rules Watch Adobe EnterpriseTV videos that explain page-load rules on a conceptual basis and demonstrate how to create and configure them. Page-Load Rules (Part 1) Conceptual information about page-load rules and information to help you set up dynamic tag management rules based on specific conditions occurring when a page loads. Adobe EnterpriseTV Training Video: Page-Load Rules (Part 2) Continued review of dynamic tag management page-load rules, including specific conditions you can use while building a rule. Adobe EnterpriseTV Training Video: 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.

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

89 Rules 89 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 you recognize that the timing on the page is somewhat questionable and

90 Rules 90 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. 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 Create conditions for event-based rules. Conditions determine when event rules are triggered. 1. Select the type of interaction you want to track, such as mouse clicks, or submitting a form.

91 Rules 91 For more information, see Event Types. 2. Enable the following options as necessary: Element Delay Link Activation 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.

92 Rules 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. Category Mouse Event click Definition A pointing device button is pressed and released on an element.

93 Rules 93 Category Event mouseover Definition 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. zoomchange When a pinch or spread gesture is performed on a mobile device. 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.

94 Rules 94 Category Event Definition 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. For more information about using hashchange, see Hashchange on the Mozilla Developer Network. 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.

95 Rules 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. 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. Watch an Adobe EnterpriseTV video demonstrating how to set up a direct-call rule in dynamic tag management: Adobe EnterpriseTV Training Video:

96 Rules 96 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. To set up actions for the condition to trigger 1. 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.

97 Rules Click Save Code, and the script will be added to the queue for the rule. Test unpublished rules for Akamai hosting Test unpublished rules from your console if you use Akamai hosting. 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. 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.

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

99 Rules 99 Condition Type Condition Function Notes 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. 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.

100 Rules 100 Condition Type Condition Function Notes 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 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.

101 Migrating to Dynamic Tag Management 101 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. Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping

102 Migrating to Dynamic Tag Management 102 Step Step 2 Task Deploy your dynamic tag management implementation to staging. 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.

103 Migrating to Dynamic Tag Management 103 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:

104 Migrating to Dynamic Tag Management 104 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! **************/

105 Migrating to Dynamic Tag Management 105 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:

106 Migrating to Dynamic Tag Management 106 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> IFrame HTML 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.

107 Migrating to Dynamic Tag Management Custom Code Tag Dynamic Tag Management Migration Instructions 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. 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.

108 Migrating to Dynamic Tag Management 108 Tag Manager 2.0 Product Code Tag Dynamic Tag Management Migration Instructions 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.

109 Migrating to Dynamic Tag Management 109 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 test extensively in

110 Migrating to Dynamic Tag Management 110 Tag Manager 2.0 Product Code Tag Dynamic Tag Management Migration Instructions 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> 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.

111 Dynamic Tag Management Object Reference 111 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()

112 Architecture 112 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. Watch an Adobe EnterpriseTV video that explains the basic elements of dynamic tag management's architecture: Adobe EnterpriseTV Training Video:

113 Troubleshooting 113 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= //s3.amazonaws.com/searchdiscovery-satellite-production/[client specific path]/satellitelib-[client specific path].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.

114 Troubleshooting 114 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 Watch an Adobe EnterpriseTV video that demonstrates how to troubleshoot a rule by inspecting the selector syntax: Adobe EnterpriseTV Training Video: 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 DTM Plugins. Watch an Adobe EnterpriseTV video that demonstrates how to debug a rule by using the DTM switch plugins:

115 Troubleshooting 115 Adobe EnterpriseTV Training Video: 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.

116 DTM Plugins 116 DTM 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.

117 DTM 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.

118 DTM Plugins Click the DTM Switch icon. 2. Toggle the buttons on or off, as desired. 3. Refresh the page to see the changes. EnterpriseTV Video - Debugging Watch an Adobe EnterpriseTV video that demonstrates how to debug a rule by using the DTM switch plugins: Adobe EnterpriseTV Training Video: 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.