Dynamic Tag Management Product Documentation

Dynamic Tag Management Product Documentation
Adobe® Marketing Cloud
Dynamic Tag Management Product
Documentation
Contents
Dynamic Tag Management Product Documentation....................................................5
Release Notes for Dynamic Tag Management...............................................................7
Getting Started.................................................................................................................8
Planning for Dynamic Tag Management..................................................................................................................9
Managing Users and the Publish Workflow...........................................................................................................10
Web Properties...............................................................................................................11
Create a web property...................................................................................................................................................13
Data Elements.................................................................................................................16
Create a data element...................................................................................................................................................21
DTM Switch Plugins........................................................................................................22
Tools for Deployment - Overview Tab..........................................................................24
Adobe Analytics Settings.............................................................................................................................................24
FAQ for Adobe Analytics Release - July 24 2014............................................................................................................................26
General.........................................................................................................................................................................................................28
Library Management...............................................................................................................................................................................29
Global Variables.........................................................................................................................................................................................32
Page Views and Content........................................................................................................................................................................34
Link Tracking...............................................................................................................................................................................................35
Referrers and Campaigns.......................................................................................................................................................................35
Cookies.........................................................................................................................................................................................................36
Customize Page Code.............................................................................................................................................................................36
Manually implement Adobe Analytics (legacy).............................................................................................................................37
Marketing Cloud ID Service Settings........................................................................................................................39
Adobe Audience Management Settings................................................................................................................41
Last updated 2/19/2015
Dynamic Tag Management Product Documentation
Contents
Adobe Media Optimizer Settings..............................................................................................................................41
Media Optimizer Rule Example...........................................................................................................................................................43
Adobe Target Settings...................................................................................................................................................45
Library Management - Adobe Target................................................................................................................................................47
Global Parameters - Adobe Target.....................................................................................................................................................48
FAQ for Adobe Target Deployment - Released October 28 2014...........................................................................................48
Mbox rule example for DTM.................................................................................................................................................................50
Google Analytics Settings............................................................................................................................................52
Google Universal Analytics Settings.........................................................................................................................54
Insert third-party tags....................................................................................................................................................57
Object References to Handle Cookies......................................................................................................................58
Rules................................................................................................................................59
Event-Based Rules Example.........................................................................................................................................61
EnterpriseTV Videos: Event-Based Rules..........................................................................................................................................64
Page Load Rules Example.............................................................................................................................................65
Page Load Rules - Advanced.................................................................................................................................................................67
EnterpriseTV Videos: Page-Load Rules..............................................................................................................................................69
Load Order for Rules.......................................................................................................................................................69
Create new rule................................................................................................................................................................72
Create conditions for event-based rules..........................................................................................................................................72
Create conditions for page-load rules...............................................................................................................................................74
Create conditions for direct-call rules...............................................................................................................................................75
Set up actions for the condition to trigger......................................................................................................................................76
Test unpublished rules for Akamai hosting....................................................................................................................................77
Test rules for Library Download or FTP.............................................................................................................................................77
Rule Conditions and Functions..................................................................................................................................78
Hosting - Embed Tab......................................................................................................80
Hosting Considerations (FAQ)....................................................................................................................................82
Akamai.................................................................................................................................................................................83
Migrate from Amazon S3 to Akamai..................................................................................................................................................84
FTP........................................................................................................................................................................................85
Last updated 2/19/2015
Dynamic Tag Management Product Documentation
Library Download............................................................................................................................................................86
Header and Footer Code..............................................................................................................................................87
Add header and footer code................................................................................................................................................................88
Verify header and footer code.............................................................................................................................................................88
Users and Permissions...................................................................................................89
Invite a user.......................................................................................................................................................................89
Migrating to Dynamic Tag Management......................................................................91
Migrating from Adobe Tag Management..............................................................................................................91
Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping.........................................................................................92
Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping.........................................................................................97
Dynamic Tag Management Object Reference ...........................................................101
Architecture..................................................................................................................102
Frequently Asked Questions.......................................................................................103
How Do Tag Management Systems Improve Page Load Speed?...............................................................110
Troubleshooting...........................................................................................................112
Documentation Updates..............................................................................................116
Previous Release Notes................................................................................................120
Contact and Legal Information...................................................................................132
Last updated 2/19/2015
Dynamic Tag Management Product Documentation
Dynamic Tag Management Product Documentation
5
Dynamic Tag Management Product Documentation
Dynamic tag management (DTM) lets you manage your Analytics, Target, and other tags across all of your sites, regardless of
your number of domains.
Last Updated: 02/19/2015
Getting Started & Popular Topics
Videos
• Request access
• Deploy Adobe Analytics
• Deploy Adobe Target (New)
• Deploy Media Optimizer (New)
• Frequently asked questions
• Troubleshooting
In EnterpriseTV, click Dynamic Tag Management.
What's New and Release Notes
• Release Notes for Dynamic Tag Management
(release notes)
Current release notes and known issues for dynamic tag
management.
• Marketing Cloud ID Service
Plugins
DTM Switch 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
Learn how to deploy the Marketing Cloud ID Service (Visitor
Twitter
ID) using dynamic tag management.
• Deploy Adobe Analytics
Learn how to let dynamic tag management automatically
manage your report suites accounts and AppMeasurement
code.
• Manually implement Adobe Analytics (legacy)
Learn how to manually deploy an Adobe Analytics tool. This
procedure describes a manual (legacy) implementation.
• Deploy Adobe Target
Learn now to automatically deploy Adobe Target.
• Google Universal Analytics
Settings for deploying Google Universal Analytics.
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
If you have questions about dynamic tag management you can
also tweet us at @AdobeMktgCare with the hashtag #DTM.
Dynamic Tag Management Product Documentation
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.
6
Release Notes for Dynamic Tag Management
7
Release Notes for Dynamic Tag Management
Release notes and known issues for dynamic tag management.
February 10 2015
Fixes:
• Added a deprecation warning message for all company administrators using Amazon hosting for their JavaScript library.
• Improved the error handling for instances where document.write is not available.
• Addressed various localization issues to increase the user experience for supported languages.
• Fixed an issue where the Channel field wasn’t included in rules specifying a s.tl() call in Adobe Analytics.
• Fixed an issue where copied rules weren’t automatically added to the staging library until a change was made to the rules.
• Fixed an issue where Regex was firing for rules using the “parameters” condition option, even if the parameter wasn’t present.
Additional Information
• See Previous Release Notes for information about new features and enhancements in previous releases of dynamic tag
management.
• See Documentation Updates for detailed information about updates to this guide that might not be included in these release
notes.
Getting Started
8
Getting Started
Information for new users of dynamic tag management.
• Requesting Access to Dynamic Tag Management
• Logging In
• Getting Started Tasks
Videos
In EnterpriseTV, click Analytics > Dynamic Tag Management.
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.
Request Access to Dynamic Tag Management
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 https://dtm.adobe.com.
Getting Started Tasks
The steps in the following table help you get up and running with dynamic tag management.
Step
Getting Started Tasks
Location
Description
Installation: Create a web
property.
Web Properties
tab on the
Dashboard
A web property is a single site, a collection of subdomains, a 3rd-party
site, or multiple domains that you want to manage together.
To get started, create a web property in your dynamic tag management
account and download the embed code in the header and footer of
your web site.
Adobe provides staging and production embed code so you can test
your changes in your staging environment. After you install the
embed code, add tools and create rules.
Getting Started
Step
Getting Started Tasks
9
Location
Configure your deployment Embed tab
options.
Description
Dynamic tag management provides a number of options to host the
required JavaScript files.
See Hosting - Embed Tab.
Add header and footer code Embed tab
to each managed page.
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.
See Header and Footer Code.
Deploy Tools for solutions.
Overview tab
This configuration step sets up the basic information required to use
Marketing Cloud solutions. These configurations are used when
defining rules.
(Google Analytics users, see Google Universal Analytics Settings or
Google Analytics Settings.)
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.
Publish tools and rules to
the production server.
After a rule is created, it is funneled through a multi-step approval
process before it is published to a production environment.
See Rules.
Planning for Dynamic Tag Management
Dynamic tag management is an evolution of tag management, designed around the mapping of user interactions to marketing
technologies. Your tags and marketing tools are best used when reacting to visitors (or segments of your visitors) and their
activity on your site in precise ways.
By starting with user interactions as the stimulus for marketing tool response, you can know how those interactions result in
data collection, testing, or engagement with tools like chat, surveys, and more.
Getting Started
10
Planning Ahead
To make the most of dynamic tag manager, 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:
Users
Create and test rules.
Approvers
Review and approve rules, making approved states of rules publishable.
Publishers
Publish rules to the production site. Only approved rules are published.
Administrators
Create and manage users, as well as inheriting rights from the three preceding roles.
Publishing Workflow
1.
2.
3.
4.
5.
A rule is saved.
The saved rule is funneled into the approval queue, where the details of the rule can be viewed in summary.
The Approver, Approver & Publisher, or Admin level user approves the rule.
The rule goes into the publishing queue.
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 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.
Web Properties
11
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.
• 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
Adobe recommends considering the following when planning Web Properties:
Item
Best Practice
Data
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 into 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, & 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, then 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.
Web Properties
Item
12
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 an Admin 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, and the data you are collecting, and 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.
Web Properties
13
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 may 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 in Web Properties.
1. Navigate to your company page, then click Add Property.
Web Properties
14
2. Fill in the fields:
Element
Name
URL
This site spans multiple
domains
Description
The name of your property.
The base URL of the property.
You can add and remove domains if you want visitor data to persist between domains.
This setting lets you specify how you would like to track traffic moving between your associated
subdomains or domains.
Note: If you do not intend to integrate an analytics tool, this step is unnecessary and
does not affect processing.
3. (Optional) Configure Advanced Settings.
Element
Allow Multi-Rule Approvals
Enable Selective Publish
Description
Allows multiple rules for this property to be approved at one time. (The default approval
allows only single-rule approval.)
Specifies whether to allow users to selectively publish approved rules. (The default workflow
is to publish all approved rules at one time.)
Web Properties
Element
Tracking Cookie Name
Tag Timeout
15
Description
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 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 admin approves and activates
it. Upon activation, the property status changes from Pending Approval to Active.
Watch an Adobe EnterpriseTV video demonstrating how to set up web properties in dynamic tag management:
Adobe EnterpriseTV Training Video: https://outv.omniture.com/?v=VweXU2bDr9reKRQrltiQ3Mpqe2-MvWuf
Data Elements
16
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
Description
Example
JavaScript Object
Any available JavaScript object or variable can be
referenced using the path field.
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:
Data Elements
Type
17
Description
Example
src
Cookie
Any available domain cookie can be referenced in
the cookie name field.
URL Parameter
Specify a single URL parameter in the URL
Parameter field.
cookieName
contentType
Only the name section is necessary and any special
designators like "?" or "=" should be omitted
Custom Script
var pageType =
$('div.page-wrapper').attr('class').split('
')[1];
if
(window.location.pathname ==
'/'){return 'homepage';
The final value produced by the code is set as the }
data element value. Therefore, a return value is not else
{
necessary in the editor window, unlike the Rule
return pageType;
Identifier custom code editor.
}
Custom JavaScript can be entered into the UI by
clicking Open Editor and inserting code into the
editor window.
Persistence
Page view
• Available only while the page persists.
• Can be created and set in scripts using _satellite object syntax:
_satellite.setVar('data_element_name')
Session
• Sets a session-level cookie in the browser.
• Available throughout the site visit.
Visitor
• Sets a 2-year cookie.
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
Data Elements
Hostname
18
• 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.
Data Elements
19
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.
Data Elements
20
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:
Data Elements
21
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: https://outv.omniture.com/?v=VmeXU2bDqrTZ6nZTPZ5XmfPlJ7O1DjZT
Create a data element
Create a data element in dynamic tag management.
1.
2.
3.
4.
Create a web property.
In the web property, click Rules > Data Elements.
Click Create New Data Element.
Complete the following fields and options:
Option
Description
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.
DTM Switch Plugins
22
DTM Switch Plugins
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:
• Install and Use the Chrome Plugin
• Install and Use the Firefox Plugin
• Use the Debugger Via the DTM Web Console
Install and Use the 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.
1. Click the DTM icon.
2. Toggle the buttons on or off, as desired.
3. Refresh the page to see the changes.
Install and Use the Firefox Plugin
Add the Adobe DTM Switch add-on from the Mozilla Add-Ons page.
DTM Switch Plugins
23
You should see the DTM Switch icon on the right side of your address bar.
1. Click the DTM Switch icon.
2. Toggle the buttons on or off, as desired.
3. Refresh the page to see the changes.
Use the Debugger Via the DTM Web Console
It is also an option to manually set the debugger and switch between libraries via the web console. See Test unpublished rules for
Akamai hosting.
Tools for Deployment - Overview Tab
24
Tools for Deployment - Overview Tab
Tools let you quickly integrate 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.
Dashboard > Company > Web Property Name > Overview
Element
Description
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 are:
• 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, email addresses, and roles. Click Manage Users to add additional users and
define their roles.
See Users and Permissions.
Adobe Analytics Settings
You can deploy Adobe Analytics 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.
Web Property Name > Overview > Add a Tool > Adobe Analytics
Tools for Deployment - Overview Tab
25
This section contains the following information:
• Field Descriptions - Add a Tool (Adobe Analytics)
• EnterpriseTV Video - Add Adobe Analytics Tool
Field Descriptions - Add a Tool (Adobe Analytics)
The following table describes the fields and options on the Add a Tool page (and the tool edit page) for Adobe Analytics. This
table provides information for the automatic and manual configuration settings.
See FAQ - Adobe Analytics Tool for additional information about this tool.
Element
Tool Type
Tool Name
Description
The type of tool, such as Adobe Analytics.
The name for this tool. This name displays on the Overview tab under Installed Tools.
Enable Automatic Configuration This option allows dynamic tag management to 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.
Note: This setting displays when you edit an existing tool by clicking the
icon next
to an installed tool from the Overview tab. Enabling this setting changes a manually
configured implementation to the automatic configuration method described in
Configuration Method.
Tools for Deployment - Overview Tab
26
Element
Description
Configuration Method
Valid values:
• Manual: Manually manage the AppMeasurement code. You can download the
AnalyticsAppMeasurement code from Admin Tools > Code Manager.
Click JavaScript (new) to download the code locally, so that you can copy and paste the
code in the Edit Code field in Library Management.
• 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.
Authenticate via
Displays when you select Automatic as from the Configuration Method menu. Valid values:
• Marketing Cloud: (Default) Uses Marketing Cloud single sign-on.
• Web Services: 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.
Update Credentials
You can refresh the API, for example, to update report suites associated with a user.
Note: This setting displays when you edit an existing tool by clicking the
to an installed tool from the Overview tab.
icon next
Production Account ID
(Required for Manual configuration) 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 for Manual configuration) A number used in your development or test
environment. A staging account keeps your testing data separate from production.
Create Tool
Creates the tool and displays it for editing. Tools are displayed on the Overview tab, under
Installed Tools.
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: https://outv.omniture.com/?v=Nqa2N4cDr_VkfyRwcWI3bj2hGZDhCi79
FAQ for Adobe Analytics Release - July 24 2014
Dynamic tag management feature information and FAQ for Adobe Analytics released on July 24, 2014.
• New Features
Tools for Deployment - Overview Tab
27
• 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
Frequently Asked Questions
Question
Answer
Is this a new Adobe Analytics tool, or a A change to the existing tool. If you currently have an implementation of Adobe
change to the existing tool?
Analytics in dynamic tag management, it will continue to function.
Do I have to do anything to get the new No.
functionality?
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 Yes.
new version of the tool, can I test in
All changes can be tested in staging just like you normally would before deploying to
staging before publishing to production?
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.
Tools for Deployment - Overview Tab
Question
28
Answer
If I switch from manual configuration No.
(the default setting for existing tools) to
automatic configuration, will my current
settings be affected?
If I switch from manual library
Any user code that you have specified is overwritten with the base AppMeasurement
management to Managed by Adobe, will 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.
Will the revision history for the Adobe Yes.
Analytics tool be retained when the new
integration is released?
Potential Pitfalls
There is a small chance that the new integration could cause data collection issues if you currently use Adobe Analytics. These
issues could arise only if you publish your library to production subsequent to the release. (Production code remains intact until
publishing occurs.)
To avoid these issues, ensure that:
• Report suite IDs are correctly entered in the tool.
• Report suite IDs in the tool match the IDs in the AppMeasurement code.
• The currency code, character set, tracking server, and SSL tracking server configuration fields are correctly set with supported
values.
• Custom code is defined in Library Management.
General
Field descriptions for the General settings in dynamic tag manager, for deploying Adobe Analytics.
Property >
Edit Tool > General
Element
Description
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.
Tools for Deployment - Overview Tab
29
Element
Description
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
Descriptions of the fields and options in the Library Management settings in dynamic tag management.
Property >
Edit Tool > Library Management
Note: If more than one Adobe Analytics tool is used in a single web property, each tool must have a unique tracker variable
name. Duplicative object variable names between Adobe Analytics tools within a single web property will cause conflicts.
Element
Description
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.
Tools for Deployment - Overview Tab
Element
30
Description
Load library at <Page Top or Page Specifies where and when to load the page code.
Bottom>
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 Adobe Analytics
Settings.
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.
1. On the Adobe Analytics tool page, expand the General section, then click Open Editor.
2. Unzip the AppMeasurement_JavaScript*.zip file you downloaded in deploy Adobe Analytics.
3. Open AppMeasurement.js in a text editor.
4. Copy and paste the contents into the Edit Code window.
Tools for Deployment - Overview Tab
31
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:
Tools for Deployment - Overview Tab
32
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 Descriptions
• Dynamically Populate Variables
Tools for Deployment - Overview Tab
33
Global Variables - Field Descriptions
Property >
Edit Tool > Global Variables
Element
Description
Server
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='www.exampleLink.com'>
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.
Tools for Deployment - Overview Tab
34
Example link: <a id='myFirstLink' loc='top' href='www.exampleLink.com'>
To accomplish this, create an event-based rule to trigger on the click of the links on the page. Then, within 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 >
Edit Tool > Page Views & Content
Element
Page Name
Description
The name of each page on your site.
See pageName.
Page URL Override
Overrides the actual URL of the page.
See pageURL.
Channel (Site Section)
Identifies a section of your site.
See channel.
Tools for Deployment - Overview Tab
Element
35
Description
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
Description
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.
Keep URL Parameters
Preserves the query strings.
See linkLeaveQueryString.
Referrers and Campaigns
Field descriptions in dynamic tag management for referrers and campaign options when deploying dynamic tag management
in Adobe Analytics.
Property >
Edit Tool > Referrers & Campaigns
Element
Referrer Override
Description
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.
Tools for Deployment - Overview Tab
Element
36
Description
See campaign.
Cookies
Field descriptions for the Cookies global settings used for deploying dynamic tag management in Adobe Analytics.
Property >
Edit Tool > Cookies
Element
Description
Visitor ID
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.
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 >
Edit Tool > Customize Page Code
Element
Description
Open Editor
You can insert any JavaScript call that must be triggered before the final s.t() call, which is contained
in the s_code.
Tools for Deployment - Overview Tab
37
Element
Description
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.
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 Adobe Analytics Settings.
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.
Tools for Deployment - Overview Tab
38
d) Configure the following fields:
Element
Description
Tool Type
The Marketing Cloud solution, such as Analytics, Target, Social, and so on.
Tool Name
The name for this tool. This name displays on the Overview tab under Installed Tools.
Production Account ID
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
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.
Tools for Deployment - Overview Tab
39
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.
Marketing Cloud ID Service Settings
Deploy the Marketing Cloud visitor ID service using dynamic tag management.
Important: The Marketing Cloud ID Service tool integrates only with Adobe Analytics. 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
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 Audience Services.
• Field Description - Marketing Cloud ID Service Settings
• Validating Deployment of the Marketing Cloud ID Service
Field Description - 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
Marketing Cloud Organization
ID
Description
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.
(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 include) @AdobeOrg.
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.
Tools for Deployment - Overview Tab
Element
40
Description
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.)
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.
Tools for Deployment - Overview Tab
41
Adobe Audience Management Settings
Information about deploying Adobe audience management using dynamic tag management.
<Web Property Name> > Overview > Add a Tool > Adobe Audience Management
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
Description
You can name this instance of audience management.
A unique alphanumeric identifier assigned by audience management.
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.
Google Analytics
Open Editor
Add a Note
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.
Adobe Media Optimizer Settings
Information about deploying Adobe Media Optimizer using dynamic tag management.
<Web Property Name> > Overview > Add a Tool > Adobe Media Optimizer
Setting
Tool Name
User ID
Description
A descriptive name for this implementation.
Your advertising management account has an associated numeric user ID. It is displayed
in the JavaScript generated for a pixel.
Tools for Deployment - Overview Tab
Setting
42
Description
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)
Determines where and when the page code loads. The recommended location is selected
by default.
Media Optimizer page code already
Prevents dynamic tag management from installing advertising management code if the
present
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.
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.
Tools for Deployment - Overview Tab
Setting
43
Description
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
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.
Tools for Deployment - Overview Tab
44
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.
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.
Tools for Deployment - Overview Tab
45
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.
Adobe Target Settings
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
The following potential implications exist regarding the Target tool:
Tools for Deployment - Overview Tab
46
• 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 Descriptions - Add a Tool (Adobe Target)
The following table describes the fields and options on the Add a Tool page (and the tool edit page) for Adobe Target. This
table provides information for the automatic and manual configuration settings.
Setting
Description
Tool Type
The type of tool, such as Adobe Target.
Tool Name
The name for this tool. This name displays on the Overview tab under Installed Tools.
Library retrieval
method
Specifies whether Adobe should manage your Adobe Target code automatically, or whether you would
like to provide your own custom code manually.
Manual Configuration Method
You can manually manage the Adobe Target code. You can download the 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
Tools for Deployment - Overview Tab
Setting
47
Description
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 (Automatic method) A code unique to your Adobe Target account. It is required for your code to be
method
provided and managed automatically by Adobe. If you chose the Automatic method, you must either be
logged in via the Marketing Cloud, or provide your Client Code value after selecting Manual as the
retrieval method.
Client Code
(Automatic method) The Client Code value can be retrieved from the Adobe Target solution interface
as follows:
• Target Classic: Configuration > mbox.js > Edit > copy value for Client.
• Target Standard: Setup > Implementation > Download mbox.js > copy value for Client from within
mbox.js file.
Library Management - Adobe Target
Descriptions of the fields and options in the Adobe Target Library Management settings in dynamic tag management.
Property >
Edit Tool > Library Management
Element
Description
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.
Tools for Deployment - Overview Tab
Element
48
Description
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
Descriptions of the fields and options in the Global Parameters settings in dynamic tag management for an Adobe Target Tool.
Global parameters let you pass additional data to the global Adobe Target mbox, and also on a per-page basis via page load rules.
The parameters configured in dynamic tag management do not override parameters already defined on the page, but instead
appends and sequences to create maximum flexibility and customization on a per page basis.
Property >
Edit Tool > Library Management
Element
Description
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 28 2014
Frequently asked questions for the Adobe Target deployment using dynamic tag management. This content is relevant only to
the Target tool updated on October 28 2014.
Tools for Deployment - Overview Tab
49
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
Answer
Is this a new Adobe Target tool or a change to the A change to the existing tool.
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.
If I make configuration changes in the new
version of the tool, can I test in staging before
publishing to production?
Yes.
The existing tool automatically becomes available. You can then view the
configuration for your Adobe Target tool to see the new configuration
options.
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 No.
setting for existing tools) to automatic
configuration, will my current settings be affected?
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.
Will the revision history for the Adobe Target
tool be retained when the new integration is
released?
Yes.
See Library Management - Adobe Target
I currently load Adobe Target through a page load If you currently load mbox.js through a global page load rule, adding a
rule. Should I be aware of anything as I migrate new Target tool to the property, or changing the configuration of an existing
to the built-in tool?
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.
Tools for Deployment - Overview Tab
Question
50
Answer
What pitfalls should I be aware of as I migrate to With the present functionality of the mbox.js code, auto-loading the
the Adobe Target tool?
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.
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.
Tools for Deployment - Overview Tab
51
Specify the element to wrap with the mbox using a CSS selector, name the mbox, then configure the timeout if needed. (It
is generally recommended to leave this at the default 1500 ms).
4. Configure the parameters you want to add to the Target mbox or to the global Target mbox.
In this example, this rule deploys an mbox named Hero that wraps a div element with an id of hero and includes an mbox
parameter named Page Name with a value of homepage. It also includes a parameter named Path with a value of home
that it passes to the global mbox.
Tools for Deployment - Overview Tab
52
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.
Google Analytics Settings
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
Description
The name of this instance of Google Analytics.
You can point to production or staging accounts for data collection. Your staging account
number is used in your development or test environment. It keeps your testing data separate
from production. Dynamic tag management automatically installs the correct account in each
environment.
Enable if you are a Google Analytics Premium customer.
Google Analytics page code is
Check this box to prevent dynamic tag management from installing Google Analytics code if
already present
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.
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");
Tools for Deployment - Overview Tab
Setting
Tracker Name
Google Analytics Code
53
Description
The tracker name you want to use for your Google Analytics installation. If you specified that
Google Analytics is already installed on your site's pages, you must use the same name here for
proper data collection. The default tracker name for Google Analytics is blank.
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.
Sample Defaults - Data Sample
Sample Defaults - Site Speed
Social - Track Facebook like,
unlike, and share
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.
Social - Track official Twitter
Enables automatic link tracking on the Twitter button on your site.
button use
Force lowercase on all
pageview, event, and custom
variable calls
Force all page views, events, and custom variables sent to GA to be in all lowercase letters (a
best-practice recommendation).
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.
Element Tag or Selector to
INCLUDE
Specify the name of the tag you would like to track. Examples: A, IMG, INPUT, DIV, etc.
Element Tag or Selector to
EXCLUDE
Specify the name of any tags or selectors you do not wish to track.
Example: a[target="_blank"]
Session Cookie Timeout
Visitor Cookie Timeout
Cookie Path
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.
Tools for Deployment - Overview Tab
Setting
Cookie Domain
Set # as a query string
delimiter
Campaign Keys in URL
Parameters
54
Description
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.
Enable campaign tracking for
Allows you to set campaigns around cookies.
cookies
Campaign Cookie Timeout
Classify the following
keywords as direct
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.
Classify the following referrers
Create a list of referral sources that are automatically classified as direct traffic, comma separated.
as direct
This is most often used to classify affiliate or in-network searches as direct. Adobe does not
recommend this practice.
Clear Keywords & Referrers
from User Cookies
Open Editor
Removes keyword and referrer data from the Google Analytics user cookies set from your site.
Use the editor to customize the page code. This code is inserted into every page immediately
before the call to track the page view. If you want to cancel the initial default _trackPageview
command and write your own to customize page names, be sure to "return false;" at the
end of the script.
Google Universal Analytics Settings
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
Tools for Deployment - Overview Tab
55
Add a Tool
Setting
Tool Name
Production Account ID
Staging Account ID
Description
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
Description
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 Prevents dynamic tag management from installing Google Analytics page code if it
already present
is already present on your site. This feature allows you to use dynamic tag management
to add to your existing implementation, rather than starting from scratch. Ensure
that you properly set your tracker name when checking this box.
Enable EU compliance for Google
Universal Analytics
Enables or disables tracking based on the EU privacy cookie.
When a page is loaded, the system checks to see if a cookie called sat_track is set
(or the custom cookie name specified on the Edit Property page). Consider the
following information:
• If the cookie does not exist or if the cookie exists and is set to anything but true,
the loading of the tool is skipped when this setting is enabled. Meaning, any portion
of a rule that uses the tool will not apply.
If a rule has analytics with EU compliance on and third-party code, and the cookie
is set to false, the third-party code still runs. However, the analytics variables will
not be set.
• If the cookie exists but it is set to true, the tool loads normally.
You are responsible for setting the sat_track (or custom named) cookie to false
if a visitor opts out. You can accomplish this using custom code:
_satellite.setCookie(“sat_track”, “false”);
You must also have a mechanism to set that cookie to true if you want a visitor to be
able to opt in later:
_satellite.setCookie(“sat_track”, “true");
Anonymize IP addresses
Ensures that IP addresses are never recorded.
Force SSL
Forces the use of HTTPS.
Tools for Deployment - Overview Tab
56
Element
Description
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 Enables automatic link tracking on the above social buttons on your site.
share
Social - Track official Twitter button use Enables automatic link tracking on the Twitter button on your site.
Force lowercase on all pageview, event,
Force all page views, events, and custom variables sent to GA to be in all lowercase
and custom variable calls
letters (a best-practice recommendation).
Always send HTTP referrer URL
Typically, HTTP referrals come from outside the domain on which you implemented
Google Universal Analytics. Enable this setting if you have many subdomains and
want all URLs to be sent.
Load Google Analytics page code at Page You can control where and when to load the page code (on a rule-by-rule basis).
Top or Page Bottom
Global Settings - Enable automatic linker Automates the tracking of cross-domain property. Google Analytics customers need
link tracking
to implement JavaScript codes for links to different but internal domains, so that
cookies are shared across internal domains.
For more information from Google, click here.
Cookies
Element
Visitor Cookie Timeout
Description
Control how long a cookie lasts for a visitor to count as a repeat visitor. The default
value is two years.
Tools for Deployment - Overview Tab
Element
57
Description
Cookie Name
Name of the cookie used to store analytics data.
Cookie Path
You can restrict whether a Google Analytics cookie only functions with a specific
folder on your site.
Cookie Domain
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
Description
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.
Element
Description
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.
Tools for Deployment - Overview Tab
58
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)
Rules
59
Rules
Dynamic tag management is a rule-based system. It looks for user interaction and associated data. When the criteria outlined
in your rules are met, the rule triggers the tool, script, or HTML you identified.
A rule consists of two parts:
Identifier
The identifier is what you want the rule to look for. The identifier you specify depends on the type of
rule.
Trigger
Triggers occur after a rule's conditions are met. A rule in dynamic tag management can trigger as many
discrete actions as you want.
For example, a single rule for an e-commerce Thank You page can trigger your analytics tools and
third-party tags from a single rule. There is no need to create separate rules for each tool or tag.
• Types of Rules
• New vs Existing Rules
Types of Rules
There are three types of rules in dynamic tag management as well as several default rules:
Type of Rule
Event-based
Description
Events are where the majority of interactions on sites take place. You can measure and react to
these interactions in real-time, without the need for JavaScript.
Event-based rules are executed when visitors interact with on-page elements.
By leveraging in-page interactions and page-level tagging, you can optimize based on things like
social media sharing, video interactions, tabbed interfaces, image galleries, and product sorting
and filtering.
Rules
Type of Rule
60
Description
See Event-Based Rules Example for an example of how to set your condition to look for clicks on
the various tabs on your product pages.
See EnterpriseTV Videos: Event-Based Rules to watch videos about event-based rules.
Page load
Let you target by URL, site section, or set up scenarios that are independent of the site structure.
For example, a page-load rule can load a survey on the fifth page view or in the seventh minute
of a visitor’s session.
Advanced page-load rules let you, for example, target specific user segments in rules.
See Page Load Rules Example.
See EnterpriseTV Videos: Page-Load Rules to watch videos about page-load rules.
Direct call
Designed to bypass dynamic tag management event detection and lookup systems.
Direct call rules are ideal for situations where you want to tell dynamic tag management exactly
what is happening. Also, they are ideal when dynamic tag management cannot detect an event in
the DOM, such as with Adobe Flash.
See Create conditions for direct-call rules for more information and to watch an EnterpriseTV
video about direct-call rules.
Default rules
When you activate a property, dynamic tag management includes several default rules.
These rules track common interactions with your site and can help you analyze opportunities
throughout your site.
Dynamic tag management includes the following default rules:
• Dead Header: Tracks any clicks on "dead" (i.e. unlinked) header items.
• Dead Image: Tracks any clicks on "dead" (i.e. unlinked) images.
• Download Link: Tracks any clicks on downloadable site content.
• Email Link: Tracks any clicks on linked emails.
• Orientation Changed: Tracks any page orientation change (mobile relevant).
• Outbound Link: Tracks any clicks on links driving off site.
• Telephone Dial: Tracks any click on a phone number.
• Zoom Changed: Tracks any change in page zoom.
New vs Existing Rules
You can create a new rule or add your script to an existing rule.
In each rule, you might notice that the screens look very similar: the Conditions section is listed first, then any 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.
Rules
61
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
Rules
Set up how to track this click in Adobe Analytics.
62
Rules
63
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.
Rules
64
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: https://outv.omniture.com/?v=5vbXY2bDqppvhP0Vf2y3q7H7KiK95WO6
Event-Based Rules (Part 2)
Continued review of dynamic tag management event-based rules, including additional configuration options:
Adobe EnterpriseTV Training Video: https://outv.omniture.com/?v=UxeXU2bDp-k8CFt0nMmQJFX3CAbTMDyl
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: https://outv.omniture.com/?v=VoeXU2bDpSlkZYzdBgzK1ZZhi6A_wyBD
Rules
65
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
http://www.mysite.com/form/thank-you.html
Here is how you can set up this scenario in dynamic tag management:
1. Create a new page load rule.
2. In the rule conditions, specify the page where this rule will be triggered.
3. Paste the tag your vendor gave you directly into the Third-Party Tags section.
Because dynamic tag management does not rely on templates, marketers can use any tag within a rule, even in formatted HTML.
Rules
66
4. Give your rule a name that describes the user interaction like “Forms: User submits form.”
You can also add descriptive metadata to your rule.
This description will help you and others identify this rule if they want to use it for their tags or tools later.
5. Save your rule, and you are ready to test it in a staging environment, request rule approval, and publish to 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.
Rules
67
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.
Rules
3. Click Save, configure your test in Adobe Target and your test is running.
68
Rules
69
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: https://outv.omniture.com/?v=V5eHU2bDrTveUoEqZVEiDoSAUYiVCeM_
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: https://outv.omniture.com/?v=VieXU2bDp7TO0AXgWi81Ki_FMP97L6Fd
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.
Rules
70
Note: Red text on the above diagram represents non-sequential activity. Green text represents sequential activity.
Rules
71
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
Rules
72
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.
2.
3.
4.
5.
6.
Create a web property.
In the web property, click the Rules tab.
Select the type of rule you wish to create from the left navigation pane, such as Event Based Rules or Page Load Rules.
Click Create New Rule.
Name the rule and select a category, if you wish.
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
Create conditions for event-based rules
Page Load rule
Create conditions for page-load rules
Direct Call rule
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.
Rules
73
2. Enable the following options as necessary:
Element
Description
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.
Rules
74
4. Select and set up any additional criteria or condition types you wish to bind to the rule.
5. Indicate your preference regarding event bubbling.
Event bubbling is one way of event propagation in HTML DOM.
If you...
Want related interactions on child elements of the rule selector you
identified to fire the rule.
Want to prevent bubbling when the child element already triggers
its own event.
Check this option
Allow events on child elements to bubble
Do not allow if child element already triggers event.
Don't want the events of the rule selector you identified to go beyond Do not allow events to bubble upwards to parents
the element itself in the event hierarchy
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.
Rules
75
2. Specify for which condition you would like the rule to fire.
For example, you can select Path to identify specific pages for which you want the rule to fire.
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: https://outv.omniture.com/?v=50eXU2bDoVZvrT_pqT1THgX85eeCs2TD
Rules
76
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.
Rules
77
5. 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.
Rules
78
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, and functions:
*Note: Enable regex on these conditions to include multiple scenarios in a single condition.
Condition
Type
Condition
Function
URL
Protocol
Indicate rule to fire on HTTP or HTTPS
Subdomain*
Indicate rule to fire or not fire on specified subdomain(s)
Path*
Indicate rule to fire or not fire on specified URL path(s)
Parameter
Indicate rule to fire if specific URL parameter(s) with specific values are present
Technology Cookie Opt-out
Indicate rule to fire only of user accepts cookies
Browser
Indicate rule to fire only in specified browsers
Operating System
Indicate rule to fire only in specified operating systems
Device Type
Indicate rule to fire only on specified devices
Screen Resolution
Indicate rule to fire within specified screen resolution ranges
Window size
Indicate rule to fire within specified window size ranges
Engagement Traffic Source*
Indicate rule to fire if visit came from specified source
Landing Page*
Indicate rule to fire if visit landed on specified page(s)
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 indicated in data element
(requires setup)
Logged In
Indicate rule to fire if user is / is not logged in as indicated in data element
(requires setup)
Previous Converter
Indicate rule to fire if user is / is not previous converter as indicated in data
element (requires setup)
Cart Item Quantity
Indicate rule to fire if user has certain number of items in cart as indicated in
data element (requires setup)
Rules
Condition
Type
Data
79
Condition
Function
Cart Amount
Indicate rule to fire if user has certain dollar value in cart as indicated in data
element (requires setup)
Cookie*
Indicate rule to fire if specified cookie with specified value is present
Data Element Value*
Indicate rule to fire if specified data element with specified value is present
Variable Set*
Indicate rule to fire if specified JS object with specified value is present
Custom
Opens a blank text box to input custom script
Hosting - Embed Tab
80
Hosting - Embed Tab
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:
Hosting Options
You can deploy dynamic tag management using one or more of the following options, found on the Embed tab:
Hosting - Embed Tab
81
Hosting Option
Description
Implementation
Akamai (migrated
from Amazon S3)
The simplest hosting option to implement.
1. Dynamic tag management generates custom
JavaScript libraries.
2. Dynamic tag management exports the custom
JavaScript libraries to Akamai.
3. The target website references the Akamai-hosted
dynamic tag management libraries directly at
the page level.
Globally distributed delivery network.
Adds additional third-party infrastructure
dependencies (DNS lookup, Akamai availability).
See Akamai for information about migrating from
Amazon S3 to Akamai.
Amazon S3
Note: After July 31, 2015 Adobe will no longer
support Amazon S3. Your dynamic tag
management libraries on Amazon S3 will
continue to be served until December 31, 2015,
but in a read-only state. Any changes made in
dynamic tag management will no longer be
reflected in these files.
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.
Self-hosting: FTP
Delivery
A push approach, whereby dynamic tag management 1. Dynamic tag management generates custom
JavaScript libraries.
exports custom JavaScript libraries directly to the
2.
Dynamic tag management exports the custom
web content server host via the FTP protocol.
JavaScript libraries to host server via FTP.
This solution requires an FTP server and credentials 3. The target website locally references the custom
to be available on the web content server, to publish
dynamic tag management libraries.
changes to the custom dynamic tag management
libraries.
Self-hosting:
Library Download A pull approach, whereby the application exports 1. Dynamic tag management generates custom
JavaScript libraries.
custom JavaScript libraries to Amazon S3. There, the
2.
Dynamic tag management exports the custom
libraries can be accessed by a hosted server-side
JavaScript libraries to Akamai.
process.
3. Custom dynamic tag management libraries are
Additionally, the libraries are available via web
manually or programmatically moved to the web
content server.
download directly from the dynamic tag
4. The target website locally references the custom
management interface.
dynamic tag management libraries.
This solution requires either a manual retrieval and
publication of the dynamic tag management libraries
or the creation of an automated process that pulls
the libraries from Akamai onto the web content
server.
Hosting - Embed Tab
Hosting Option
82
Description
Implementation
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.
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: https://outv.omniture.com/?v=VqeXU2bDrF2pWBT3-0fc7oyrgvzVChBp
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.
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,
Hosting - Embed Tab
83
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
Yes, you can turn on and use any number of the hosting options and use different
management library hosting option at once? Embed codes for different domains or subdomains.
For example, you may want to use the Akamai option for your lower-level,
non-production environments like staging, dev, test, or UAT. At the same time,
you may 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, like 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.
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.
Hosting - Embed Tab
84
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. They run 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, they run more than 137,000 servers in 87 countries within more than 1,150 networks. In terms of redundancy, they
do not just route from one server to another, they route 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. The other
boxes in the node take over. If a node goes down, they serve 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.
Hosting - Embed Tab
85
4. Click the Amazon S3 option to the Off position.
Note: After you disable Amazon S3, you can no longer use Amazon S3 hosting. Ensure that you no longer need Amazon
S3 before turning it off.
Akamai hosting in dynamic tag management functions independently of any Akamai hosting you currently use for your
website.
FTP
Steps to deploy dynamic tag management using FTP (the push methodology).
The FTP Delivery hosting option allows you to self-host the library files. When an authorized dynamic tag management user
makes a change in the software, dynamic tag management writes those changes out 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.
Hosting - Embed Tab
3.
4.
5.
6.
86
Provide the required FTP information for the staging and production servers, then click Save FTP Information.
Toggle the switch in the top right corner to ON.
Click Header Code and Footer Code to expand those sections.
Click the appropriate Copy Embed Code button to copy header and footer codes to 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 allows you to self-host the library files. When an authorized dynamic tag management
user makes a change in the software, dynamic tag management writes those changes out 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:
Hosting - Embed Tab
87
Option
Description
Shared Secret
Encrypts the dynamic tag management library during download.
If you enter a shared secret, we will aes-256 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 will 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 to 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.
Hosting - Embed Tab
88
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.
Preferably, 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.
Preferably, 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 if 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.
Users and Permissions
89
Users and Permissions
You can invite users to dynamic tag management and assign user roles.
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:
• User Roles and Permissions
• EnterpriseTV Video - User Administration
• Creating User Groups
User Roles and Permissions
Dynamic tag management has five different user roles with varying sets of permissions.
User Role
Create
Rules
Edit Rules
Test Rules
Approve
Rules
Publish Rules Create/Edit
Users
User
Yes
Yes
Yes
Approver
Yes
Yes
Yes
Publisher
Yes
Yes
Yes
Approver and
Publisher
Yes
Yes
Yes
Yes
Yes
Administrator
Yes
Yes
Yes
Yes
Yes
Create
Property
Yes
Yes
Yes
Yes
EnterpriseTV Video - User Administration
Watch an Adobe EnterpriseTV video demonstrating how to create a user in dynamic tag management and set permissions:
Adobe EnterpriseTV Training Video: https://outv.omniture.com/?v=UzeXU2bDr5I4UoMp0vClap7AF_Rr2QRV
Creating User Groups
A user in dynamic tag management is basically an email address. If you want everyone in your Marketing department to be a
user, you can create a group email address for the Marketing team, then add that email address as a User. Each member of the
Marketing team would share a common password.
While there are some companies that do this, Adobe recommends assigning User roles to individuals, not to teams. This approach
offers the best security and user management experience, but you are free to create users in whatever way meets your needs.
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 email address.
Users and Permissions
90
4. Select the default role for the user.
5. (Optional) Click Define Role per Property.
Roles, by default, are chosen at a company level. Define Role per Property lets you define a user's role at the property level.
6. Click Invite User.
An email with a link is sent to the user. This email 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.
Migrating to Dynamic Tag Management
91
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
Task
Description
Step 1
Migrate your existing Adobe Tag Manager tags Adobe Tag Manager 1.0 to Dynamic Tag Management Mapping
to dynamic tag management.
Adobe Tag Manager 2.0 to Dynamic Tag Management Mapping
Migrating to Dynamic Tag Management
92
Step
Task
Description
Step 2
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
Dynamic Tag
Management
Custom Core JavaScript 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 Dynamic Tag
Code Tag
Management
SiteCatalyst
SiteCatalyst > Survey
SiteCatalyst > Video
Tracking
SiteCatalyst > Genesis
Integrations
Migration Instructions
Adobe Analytics Tool Follow the instructions in Adobe Analytics Settings 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.
Migrating to Dynamic Tag Management
Tag Manager 1.0 Product Dynamic Tag
Code Tag
Management
93
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:
Migrating to Dynamic Tag Management
Tag Manager 1.0 Product Dynamic Tag
Code Tag
Management
94
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!
**************/’
Migrating to Dynamic Tag Management
Tag Manager 1.0 Product Dynamic Tag
Code Tag
Management
95
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:
Migrating to Dynamic Tag Management
Tag Manager 1.0 Product Dynamic Tag
Code Tag
Management
96
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 Dynamic Tag Management Migration Instructions
HTML
HTML
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.
Migrating to Dynamic Tag Management
97
1.0 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
Dynamic Tag
Product Code Tag Management
Migration Instructions
SiteCatalyst
Follow the instructions in Adobe Analytics Settings to add an Adobe Analytics tool
in dynamic tag management.
SiteCatalyst >
Survey
SiteCatalyst > Video
SiteCatalyst >
Integration Module
Adobe Analytics
Tool
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.
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.
Migrating to Dynamic Tag Management
Tag Manager 2.0
Dynamic Tag
Product Code Tag Management
98
Migration Instructions
1.
2.
3.
4.
In Adobe Tag Management 2.0, click Edit next to the latest container file.
Click Preview to view the generated file.
Locate the sitecatalyst JS file and click See content.
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.
Migrating to Dynamic Tag Management
Tag Manager 2.0
Dynamic Tag
Product Code Tag Management
99
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
Migrating to Dynamic Tag Management
Tag Manager 2.0
Dynamic Tag
Product Code Tag Management
100
Migration Instructions
staging before publishing to production to ensure the expected behavior is
accomplished.
Adobe Target
Audience
Management
Adobe Target
Tool
Configure Adobe Target Settings.
Adobe Audience
Manager Tool
Configure Adobe Audience Management Settings.
Custom Code
2.0 Custom Code Tag Dynamic Tag Management Migration Instructions
HTML
HTML
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.
Dynamic Tag Management Object Reference
101
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()
Object Model Reference (PDF)
Architecture
102
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: https://outv.omniture.com/?v=VkeXU2bDqaHvnK08mDs3-8zFZXvjAYm9
Frequently Asked Questions
103
Frequently Asked Questions
Frequently asked questions about dynamic tag management.
• FAQ - Getting Started: Covers initial questions about your decision to use dynamic tag management.
• FAQ - Dynamic Tag Management and the Adobe Marketing Cloud: Covers using dynamic tag management with the Adobe
Marketing Cloud.
• FAQ - Advanced: Covers performance, rules, loading, hosting, and so on.
• FAQ - Adobe Analytics Tool: Covers questions about the automatic configuration feature of the Adobe Analytics tool.
FAQ - Getting Started
A FAQ answering common questions about your decision to use dynamic tag management.
Question
Answer
How do I get started?
See Getting Started.
How much does dynamic tag management cost?
Dynamic tag management is free.
Are there limitations on my use of dynamic tag
management?
You can create as many Web Properties as you want and write as many
rules as you want. You can also use it to deliver any digital marketing service,
even if you don’t use it to deliver Adobe Digital Marketing solutions. There
is no effective limitation on your use of the capability.
Why is it an advantage for customers (over
competitive offerings) to use dynamic tag
management from Adobe?
The dynamic tag management advantage is the control and flexibility of
using rules. It is also the only market-leading tag management solution
that supports all of your digital marketing services and is offered to
customers at no additional cost.
Who can help me with my dynamic tag
management implementation?
Adobe Global Services provides dynamic tag management implementation,
as do several implementation partners. Contact your account manager for
more information.
What if I am using Adobe TagManager (ATM)?
Do I have to migrate?
Not for a while. Adobe supports TagManager until October 2015.
Starting August 1, 2015, you will no longer be able to edit your tags or
containers in ATM. You will still be able to log into the application to view
and export existing tags and containers, and your tags will continue to be
served, but if you wish to make any changes you will need to deploy DTM
on your site(s) and transition these tags to DTM.
Starting October 1, 2015, the ATM application will become unavailable
entirely and your tags will no longer be served. If you have not transitioned
your sites away from ATM by this date, it is possible that your website
visitors may experience errors, so it is critical that you transition prior to
this date. We will begin sending periodic reminders between now and this
date to help you remember to begin the migration process as soon as
possible.
Frequently Asked Questions
Question
104
Answer
For help in creating a strategy to implement dynamic tag management,
please contact your account manager.
With which Adobe Marketing Cloud solutions are Dynamic tag management will support all of the Marketing Cloud solutions
dynamic tag management integrated?
as well as any digital marketing service, regardless of vendor.
How do I access dynamic tag management through Before you can start using dynamic tag management, someone from your
the Adobe Marketing Cloud?
company must request access. See Requesting Access to Dynamic Tag
Management.
Why am I getting an "Access Failed" error when I Make sure that your company has been provisioned to use the Marketing
try to access the Marketing Cloud?
Cloud. See Access the Marketing Cloud in the Marketing Cloud Product
Documentation.
How do I assign my account to a Company name You must add an organization to the Marketing Cloud Organizations &
in the Marketing Cloud?
Product Access page and set it as the default organization. You add an
organization if you have access to more than one company's Marketing
Cloud accounts. See Organizations in the Marketing Cloud Product
Documentation.
How do I link my account to an Adobe ID?
When you click Join Marketing Cloud, you can step through a wizard that
helps you link your solution account credentials to your Adobe ID. Your
Adobe ID becomes your single login for all of the Marketing Cloud solutions
and services. See Join the Marketing Cloud from a Solution in the Marketing
Cloud Product Documentation.
How do I link solutions from within the Marketing For more information, see Link Accounts in the Marketing Cloud in the
Cloud?
Marketing Cloud Product Documentation.
Do I need to remove my Analytics or other tags
from my site to use dynamic tag management?
No. You can leverage dynamic tag management without touching any of
the existing tags on your site. Just place the embed code and start creating
rules. Dynamic tag management can work with existing services tagged
directly to the page.
Does dynamic tag management work for apps as Dynamic tag management currently only delivers JavaScript. However, we
well as sites?
have integrations on the roadmap for delivering app configuration files for
Adobe Mobile in 2015.
Also, we are planning integrations with PhoneGap so that dynamic tag
management is available to any app built on that platform.
What third-party tags are supported by dynamic Any third-party tag can be deployed through dynamic tag management.
tag management?
Our top-down, rules-driven approach leverages those third-party tags as
fuel for power digital marketing use cases.
Frequently Asked Questions
Question
105
Answer
Does dynamic tag management support HTML5 Yes, HTML5 is supported.
Dynamic tag management does not yet support fully native applications.
It can handle an application if it has an in-application browser or is
essentially a website wrapped in an app container. Properties for the mobile
and desktop sites should be able to be set up as normal.
FAQ - Dynamic Tag Management and the Adobe Marketing Cloud
A FAQ about using dynamic tag management with the Adobe Marketing Cloud.
Question
Answer
With which Adobe Marketing Cloud solutions are Dynamic tag management will support all of the Marketing Cloud solutions
dynamic tag management integrated?
as well as any digital marketing service, regardless of vendor.
How do I access dynamic tag management through Before you can start using dynamic tag management, someone from your
the Adobe Marketing Cloud?
company must request access. See Requesting Access to Dynamic Tag
Management.
Why am I getting an "Access Failed" error when I Make sure that your company has been provisioned to use the Marketing
try to access the Marketing Cloud?
Cloud. See Access the Marketing Cloud in the Marketing Cloud Product
Documentation.
How do I assign my account to a Company name You must add an organization to the Marketing Cloud Organizations &
in the Marketing Cloud?
Product Access page and set it as the default organization. You add an
organization if you have access to more than one company's Marketing
Cloud accounts. See Organizations in the Marketing Cloud Product
Documentation.
How do I link my account to an Adobe ID?
When you click Join Marketing Cloud, you can step through a wizard that
helps you link your solution account credentials to your Adobe ID. Your
Adobe ID becomes your single login for all of the Marketing Cloud solutions
and services. See Join the Marketing Cloud from a Solution in the Marketing
Cloud Product Documentation.
How do I link solutions from within the Marketing For more information, see Link Accounts in the Marketing Cloud in the
Cloud?
Marketing Cloud Product Documentation.
FAQ - Advanced
A FAQ about performance, rules, loading, hosting, and so on.
Frequently Asked Questions
106
Question
Answer
Can I manually implement s_Code through
dynamic tag management?
You can create and configure an Adobe Analytics tool automatically or
manually. For more information about a manual (legacy) implementation,
see Manually implement Adobe Analytics (legacy).
Can I use dynamic tag management on pages with Yes.
content type application/xhtml+xml or text
The only potential issue is the use of document.write, because content
+ xhtml?
type text + xhtml does not support document.write. However,
this issue can be avoided because document.write is used by dynamic
tag management only in the situations stated below.
• Loading of the staging library using the dynamic tag management switch
plugin uses document.write.
Workaround: Test in the staging environment by specifically referencing
the staging library in the page code instead of using the dynamic tag
management switch plugin to toggle between libraries.
• Synchronously loading JS and HTML scripts via dynamic tag management
uses document.write.
Workaround: The synchronous loading of scripts via dynamic tag
management cannot avoid document.write. Thus, when this content
type is being used, all third-party scripts (JS and HTML) should be loaded
asynchronously in dynamic tag management to avoid
document.write. Please always consider and test all code
dependencies to ensure the desired behavior is still accomplished with
asynchronous loading.
Performance: Will dynamic tag management
reduce my website's performance?
Dynamic tag management has never shown signs of negatively affecting
page load time or execution speed.
However, because dynamic tag management can be used as a delivery
system (a way to deliver JavaScript, HTML, images, or other Web content),
if you load a large file, or a large image at the wrong point during render
time, you can slow down page load speed and increase code execution time
on that page. If you lazy load images, and if you use asynchronous
(non-sequential) scripts as much as possible, and you follow best practices
regarding the code you add into dynamic tag management, you should not
see negative performance impacts.
The Embed code should be hard-coded in the <head> section of your
templates. This is a synchronous JavaScript include. The dynamic tag
management engine is designed to work in a modular way, so scripts that
do not apply to a particular page, site section, or domain will not load or
execute when they are not needed. Most users increase the use of
asynchronous (non-sequential) methods when deploying third-party scripts.
This generally improves the perceived page load speed for site visitors.
Frequently Asked Questions
Question
107
Answer
While the dynamic tag management main library file itself is loaded
synchronously, most clients load any code from within dynamic tag
management using the built-in asynchronous methods.
How do I remember which tags are in which rules? Adobe recommends using the rule Name, the Tag Name, and the Categories
How do I keep track of my tags and make it easier to label your rules in a way that helps you find things faster later on, when
to find certain rules?
you need to come back and change a rule, or group of rules.
For example, because different Page Load and Event Based rules respond
to different Conditions, it might make sense to add an indicator about the
Conditions in the rule Name, like “Global Page Load."
When working with Third Party Tags or custom JavaScript, you can add
information into the Tag Name field. Later, when you are looking for all
the rules with a certain tag, you can filter the list of rules by Tag Name to
find all rules containing that tag.
Finally, each rule can be labeled with a Category and a value. The Category
is also available when filtering your list of rules, so you can easily and quickly
find the list of rules in a certain Category. For example, using a Category
like “3rd Party” with a value of “DoubleClick” lets you search for all rules
in the “3rd Party” Category, or all rules with the value of “DoubleClick”.
Does dynamic tag management have features that Adobe recommends the use of tag event callbacks provided by amc.on
help avoid errors due to asynchronous tag loading to wrap any code that depends on tags delivered by any tag management
or rare cases of CDN unavailability?
system.
See amc.on Tag Event Callbacks.
Can the dynamic tag management library files work Adobe offers two options for self-hosting the library files: FTP Delivery
with the version control system we use at my
and Library Download. When you choose one of these self-hosted options
company?
for the library, each time you make changes in dynamic tag management,
those changes are written out by the system to the library files. Those files
are typically then "pushed" or "pulled" to your architecture automatically.
Once the updated library code is on your servers, you can add the files to
your version control systems and processes however you like. If you use
GitHub, SVN, or some other system to manage your web development
code or content, that works fine with dynamic tag management.
One note on version control: Ensure you do not overwrite the production
version of the Embed code with the staging version of the Embed code when
you commit and push code to production. The staging version of the Embed
code has to stay in the staging (non-production, test, dev, QA, UAT, etc.)
environment templates. The production version of the embed code has to
stay in the production templates.
Can I use dynamic tag management with our
mobile applications?
Currently, dynamic tag management can be used in any digital experience
created with HTML, CSS, and JavaScript. This includes any
Frequently Asked Questions
Question
108
Answer
mobile-optimized content or responsive designs. This also includes mobile
applications created with wrappers like Cordova or PhoneGap.
Unfortunately, at this time, dynamic tag management does not offer a
separate SDK for use with completely native, compiled applications. You
can still track your mobile applications using the Adobe Analytics SDK.
Dynamic tag management can also be present on HTML documents pulled
into your mobile app when desktop or responsive content is accessed within
the native app experience, like in hybrid or crossover content situations.
How do I set s.pageName without creating a
separate rule for each of my web pages?
There are a number of ways to set s.pageName for each page, without
creating a separate dynamic tag management Page Load rule for each page.
In dynamic tag management, the conditions for your rules answer questions
like: What’s the visitor doing? Where are they doing it? When is it
happening? You can set any number of variables, trigger different tags or
tools, and execute any number of scripts from within the same rule, as long
as you want all those things to happen in response to the same conditions.
For example, if you want document.title to be the source for the value
of the s.pageName variable, you could create a Data Element with a name
of Page Name, a Type of JS Object, a Path of document.title, a Default
Value of None, and Remember this value for Pageview.
Then, you could create a global Page Load rule and assign that Data Element
to s.pageName, either in the interface, or in the Custom Editor code window.
It will then be dynamically populated with the value of document.title
for each page that meets your conditions.
How do I choose a hosting option?
Dynamic tag management creates and uses various JavaScript files that
contain all the code needed to run the system. These “library files” can be
hosted by Adobe, or they can be hosted on your own servers, within your
own Web architecture. Hosting options are:
• Akamai
• FTP delivery
• Library download
You can use one or more of these hosting options for a Web Property. Do
not use more than one Embed code in any single page. For example, you
could use Akamai in your staging environments, and one of the self-hosted
options in your production environments. Or, you could use the Akamai
option for any sites, domains, or subdomains hosted by one of your agency
partners. These options give you more flexibility to host the library files
according to your specific needs.
See Hosting Considerations (FAQ).
Does the dynamic tag management code send any Dynamic tag management is a way to get JavaScript and HTML to your
information back to Adobe?
pages. It sends data only to the systems, tools, or tags that you specifically
Frequently Asked Questions
109
Question
Answer
choose when using the system. In other words, dynamic tag management
does not send any data anywhere, unless you specifically tell it what data
should be collected, and then tell it when, where, and how it should be sent
to any systems, tools, or tags.
You have control over the specific data points that only get sent to the
places and technologies you designate.
How do I handle multiple geo markets, business
units, and subdomains?
See Separating the DTM Environment for Multiple Entities.
My data element setup does not seem to be
working. How do I test it?
Navigate to a page where the data element should be available on your site.
Open your web console and type in
_satellite.getVar(‘dataelementname’) and press enter. This
action returns any value that is present for the noted data element on that
page. If the value is undefined, the data element is likely setup incorrectly.
If the value is null, then that data element may not have a value on that
particular page.
FAQ - Adobe Analytics Tool
A FAQ about the automatic configuration of the Adobe Analytics deployment. The automatic configuration method manages
the AppMeasurement code for you.
Question
Answer
Where do I put my plugins when
implementing Adobe Analytics via
DTM?
If using DTM to manually host the s_code, plugins can be added in the same editor
as the hosted s_code, just as it would be in a typical Adobe Analytics implementation.
However, it is also an option to place the plugins in the editor within the Customize
Page Code section of the tool settings. Both implementation methods should be equally
effective.
See DTM Switch Plugins.
Do I have to do anything to get the new No.
functionality?
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 Yes.
new version of the tool, can I test in
All changes can be tested in staging just like you normally would before deploying to
staging before publishing to production?
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.
Frequently Asked Questions
Question
110
Answer
If I switch from manual configuration No.
(the default setting for existing tools) to
automatic configuration, will my current
settings be affected?
If I switch from manual library
Any user code that you have specified is overwritten with the base AppMeasurement
management to Managed by Adobe, will 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.
Will the revision history for the Adobe Yes.
Analytics tool be retained when the new
integration is released?
See Adobe Analytics Settings for configuration information.
How Do Tag Management Systems Improve Page Load Speed?
Information about effective solutions to the issues affecting page load speed.
Adobe dynamic tag management provides a number of effective solutions to the issues affecting page load speed. Dynamic tag
management approaches the page differently from most other solutions, by providing conditional logic in its core library file
that delivers file assets only when needed. In addition to a focus on scenario-based logic and precise activation of vendor
technologies, dynamic tag management provides a series of features that dramatically improve page speed. These include:
• Self-hosted static file delivery that eliminates the dependency on third-party hosting and DNS
• Parallelization of tag loading through asynchronous delivery
• Tag killing options with timeouts that can be modified by the client
• Dramatically reduced file size through the optimized dynamic tag management library schema - over 90% smaller than
competitors
• Enhanced file compression and delivery
• Optimized timing and delivery sequencing that can be modified by the client
• Client-side delivery of file assets that eliminates any additional server-side processing
Each tag management system (TMS) vendor must deal with the challenges of page load speed and Adobe dynamic tag management
provides the best set of options that can be assembled to meet these challenges. There are also a number of guiding questions
that should be answered when evaluating page load speed and TMS options.
Page Load Speed
There are essentially six areas that affect page load speed:
1.
2.
3.
4.
5.
6.
Caching of site assets
Creating site pages from the server
Reducing the number of downloaded files
Reducing the size of downloaded files
Improving the connection speed to source files
Converting sequential file loading to parallel file loading
Frequently Asked Questions
111
The caching of site assets occurs at the browser level and is not something that TMS vendors can directly address. The same is
true of the time that it takes for servers to create site pages and prepare them for delivery. Both of these areas can increase and
decrease the time that it takes for a page to load. Because TMS vendors cannot directly address the first two page load issues,
this overview focuses on the remaining four areas.
All major TMS options attempt to reduce the number of downloaded files and also optimize their size. The approach that each
TMS takes to accomplish those tasks might vary somewhat, but in the end they each provide some improvement to the final file
weight that is delivered to the page. When evaluating a TMS it is important to understand the architecture involved in the
packaging and deployment of the individual files to the client web browser.
• Are the files assembled server-side on each request or delivered from pre-published static files?
• If files are assembled dynamically, how long does file assembly take for each request?
• Is there a server-side-only management of a portion of the files, and if so, what are the limitations of that architecture?
• What compression techniques are used in the generation of the files?
• Are optimizations provided in the TMS file generation that might help mitigate browser errors?
In the final analysis, each major TMS vendor reduces the number of downloaded files and optimizes the file size with some
degree of success.
The areas where TMS solutions can see appreciable speed differences on the page are in the areas of connection speed and file
loading. All of the major TMS offerings provide the option of a globally distributed CDN to deliver their files. Hosting files on
any infrastructure is also available as an option when using Adobe dynamic tag management. In most cases a CDN provides an
efficient means to deliver the TMS files. However, there are several cautionary questions that must be answered relating to the
hosting methodology that is provided by the TMS.
• What happens if the host CDN or regional DNS service fails?
A number of enterprise-level failures have occurred in these areas during critical delivery times for some TMS vendors.
Self-hosting of TMS assets prevents this situation from occurring because the files are delivered along with the rest of the
client-hosted website assets either on their own architecture or an architecture of their choice.
• What are the response times for file retrieval?
• Are international response times significantly different for regional visitors?
• How responsive are the vendors of the third-party code that the TMS manages like Facebook, Google, Foresee, etc.?
Each of these third-party connections can cause delays even if the TMS files are delivered quickly. Does the TMS have
client-adjustable tag timeouts that mitigate vendor delays?
File loading also has an effect on page speed, but more specifically, on the user experience. The use of asynchronous tag loading,
conditional logic that determines what file assets will be delivered, and the placement of timeouts on tags provide ways to
parallelize tag behavior and improve the loading of the page. Although the final tag weight may not be significantly different at
the end of the page load, moving third-party vendor tags from a synchronous to asynchronous load allows multiple assets to
load in parallel rather than one at a time. How much flexibility does the TMS provide regarding the timing and sequencing of
vendor code? Does the TMS vendor provide best practices for optimizing page performance in relationship to file loading? Can
third-party vendor code be easily changed from synchronous to asynchronous loading and vice-versa?
Adobe dynamic tag management excels in each of these four page speed areas and, in certain cases like hosting, provides a better
solution than other vendors. However, page load speed is only one area that needs to be addressed when evaluating a TMS.
Critical questions need to be answered regarding workflow and governance, rule deployment methodologies, the user interface,
implementation, migration, maintenance, and user segmentation capabilities. These are areas that make Adobe dynamic tag
management stand out as a system with a proven performance record that clients enjoy using over the long-term.
Troubleshooting
112
Troubleshooting
Describes several troubleshooting scenarios and their solutions and provides a list of Frequently Asked Questions (FAQ).
This section contains the following information:
•
• Implementation Issues
• Rule Issues
• Tool Issues
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.
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
Troubleshooting
113
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.
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.
Glossary
114
Glossary
Terms used in dynamic tag management.
Term
Adobe Analytics
Definition
Adobe's hosted, subscription-based solution for real-time website reporting and analysis. You
can deploy Adobe Analytics using dynamic tag management by creating the Adobe Analytics
Tool and configuring the page code either automatically or manually.
Approvals
Audience management
Campaign
ClickMap
Cookie
Customize Page Code
Data Center
Data Element
Direct Call Rule
Data elements are the building blocks for rules. Data elements let you create a data dictionary (or
data map) for any object that is contained on your site. They can be JavaScript objects, cookie
values, and query strings.
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.
DTM Switch
DTM Switch is a browser plugin for easy switching of debug mode and staging mode for DTM
users. It is available for both Chrome and Firefox.
Embed
Global Variables
Google Analytics
Page Load
Link Tracking
Marketing Cloud
The Marketing Cloud is an integrated family of digital marketing solutions, as well as an intuitive
interface for new resources and capabilities, called core services, for your business.
Glossary
Term
Property
115
Definition
A Web Property is a library of rules and one embed code. It can be any grouping of one or more
domains and subdomains. You can manage and track these assets similarly.
Publish
Referrer
Rules
Staging
Tag
Target
Tool
Tracking Server
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.
Documentation Updates
116
Documentation Updates
Information about updates to the dynamic tag management help.
Date
Description
Location
02/18/2015
Added information explaining how the different
JavaScript/third-party tags script options are
utilized within the four page-load phases.
02/18/2015
Updated FAQ with information about using
dynamic tag management with the Adobe
Marketing Cloud.
Frequently Asked Questions
01/28/2015
Updated information about enabling EU
compliance.
Google Universal Analytics Settings
Load Order for Rules
Google Analytics Settings
General
01/28/2015
Updated topic.
DTM Switch Plugins
12/15/2014
Updated migration from Adobe Tag Manager 1.0 Migrating from Adobe Tag Management
and 2.0 to dynamic tag management.
12/08/2014
Updated the advanced FAQ with content regarding FAQ - Advanced
VisitorAPI.js breaks in text+html.
11/21/2014
Updated Adobe Media Optimizer tool settings.
Adobe Media Optimizer Settings
11/7/2014
Updated the Important note regarding the
wrapping of embed codes.
Header and Footer Code
10/23/2014
Updated the Object Reference landing
Dynamic Tag Management Object Reference
10/23/2014
Added feature content for Adobe Target
deployment.
Adobe Target Settings
10/23/2014
Added plug-in information to the Analytics FAQ. FAQ - Adobe Analytics Tool
08/27/2014
Added and important note in the Hosting section Hosting - Embed Tab and Header and Footer Code
about the risks of unsupported implementations.
08/26/2014
Added external links to resources for learning
about CSS.
Event-Based Rules Example
Documentation Updates
117
Date
Description
Location
08/08/2014
Added Load Adobe Target Library Synchronously Adobe Target Settings
field description.
08/07/2014
Added content for the Marketing Cloud ID Service Marketing Cloud ID Service Settings
tool.
07/24/2014
Updated the Adobe Analytics configuration with FAQ for Adobe Analytics Release - July 24 2014
new feature content for automatically managing
your configuration.
07/24/2014
Added FAQ information for the automatic
configuration for Adobe Analytics deployment
tool. Separated other FAQ information into
beginner and advanced sections.
Frequently Asked Questions
07/09/2014
Added information about handling multiple geo
markets, business units, and subdomains.
Separating the DTM Environment for Multiple
Entities in Web Properties
06/16/2014
Updated the Enable EU compliance for Google
Analytics field description.
Google Analytics Settings
05/06/2014
Added bets practices for Web Properties.
Web Properties
05/06/2014
Added queue processing information after the
Load Order diagram.
Load Order for Rules
04/22/2014
Added external link to plugins in the table of
contents.
DTM Switch Plugins
04/04/2014
Added Google Universal Analytics content
Google Universal Analytics Settings
03/20/2014
Added topic with information about how tag
management systems improve page load speed.
How Do Tag Management Systems Improve Page
Load Speed?
03/19/2014
Added Why Choose Akamai Hosting for Library
Files?
Akamai
03/19/2014
Added How Web Properties Compare to Adobe
Analytics Report Suites.
Web Properties
Added Domain Planning.
03/19/2014
Added a section How to Collect Values from
JavaScript Variables in a data element.
Data Elements
Documentation Updates
118
Date
Description
Location
03/18/2014
Updated the FAQ
Frequently Asked Questions
03/05/2014
Added information about dynamically populating Dynamically Populate Variables in the Global
Variables section.
variables (%this.attributeName%).
02/27/2014
Added the following note:
Note: Adobe supports the dynamic tag
management implementations only as
outlined on the pages in this section of Adobe
Help. Asynchronous or other deployment
methods are not supported.
02/07/2014
Added the following text to the s_code field
description.
Hosting - Embed Tab
Header and Footer Code
General
Dynamic tag management supports any H versions
of legacy s_code.
01/29/2014
Added new steps to insert core AppMeasurement Insert core AppMeasurement code
code.
01/17/2014
Added information about migrating from Amazon Akamai Hosting
S3 to Akamai hosting.
01/16/2014
Release notes update
12/16/2013
Added information in the FAQ about supporting Frequently Asked Questions
HTML5
12/09/2013
Reauthored help.
11/20/2013
Added a link to the Community Forum to the table Table of Contents.
of contents.
11/13/2013
11/07/2013
Release Notes for Dynamic Tag Management
All topics.
Added information to the Enable EU Compliance
Google Analytics Settings
field.
Manually implement Adobe Analytics (legacy)
Added the Object Model Reference.
Object Model Reference
11/06/2013
Updated procedures for adding header and footer
Header and Footer Code
code, and verifying code.
11/06/2013
Updated the Data Elements topic with new
content.
Data Elements
Documentation Updates
119
Date
Description
Location
10/30/2013
A process graphic showing the DTM load order
in relation to the JavaScript load order.
Rules > Load Order for Rules
Previous Release Notes
120
Previous Release Notes
Historical release notes for dynamic tag management.
See Current Release Notes for the latest release information.
January 13 2015
Fixes:
• Dynamic tag management no longer overrides global variables with the name window.t.
• Fixed an issue where Firefox was incorrectly trapping the right-click event handler in the browser and causing click-based
rules to fire.
November 13 2014
Feature
Description
Adobe improved our dynamic tag
management integration with Adobe
Media Optimizer, including.
• Default delivery of the latest (v3) Media Optimizer tag
• Support for a data-element based SKU
• Suppression of unneeded beacons
• Minor enhancements
See Adobe Media Optimizer Settings
Fixes and Improvements
• Fixed an issue where rule copying did not work after the release of the Adobe Media Optimizer integration on 10/30/2014.
• Added the ability to specify name/value pairs for general settings and customer-specified IDs in the Marketing Cloud ID tool.
• Added option for the Marketing Cloud ID tool to trigger the initial API call. This call enables support for Adobe solutions that
do not currently trigger this call already in your own code.
• Fixed an issue where the browser version tracked by dynamic tag management for certain versions of Internet Explorer was
returned as Unknown instead of Internet Explorer.
• Adobe tools will now be displayed first in the listing of installed tools on a given web property.
October 30 2014
Adobe improved our dynamic tag management integration with Adobe Media Optimizer, including:
• Default delivery of the latest (v3) Media Optimizer tag
• Support for a data-element based SKU
• Suppression of unneeded beacons
• Minor enhancements
October 28 2014
New features in dynamic tag management released on October 28, 2014:
Feature
Description
Adobe Target integration
Updated the Adobe Target tool to enable automatic deployment via dynamic tag
management.
See Adobe Target Settings for configuration information.
Previous Release Notes
121
Feature
Description
Enable support for Google Universal
Analytics Premium features
Added a checkbox for premium Google Universal Analytics features in the tool
(General group). This option enables the max dimensions and metrics increase
from 20 to 200.
Fixes and Improvements
• Fixed an issue where the Tracking Server value automatically determined by dynamic tag management for the Adobe Analytics
tool sometimes set an incorrect value.
• Fixed an issue where a restored data element had the name appended with "(Restored)," which caused previous references to
that data element to be broken. (The appended value is now added only if restoring the data element would create a naming
conflict with an existing data element.)
• Fixed an issue caused when triggering an event-based rule on a click event. If the click event had a delay link activation on an
anchor tag with no HREF, the issue forced the browser to attempt to navigate to a blank HREF location.
• Fixed an issue where dynamic tag management was no longer saving global variables configured in an Analytics tool when
changes to that tool had been rejected and then restored.
• Implemented significant performance improvements in the library generation process, which should result in a shorter wait
for changes to appear in production, especially during peak usage hours.
• Fixed an issue where company administrators were unable to export their activity log to CSV when there was a large amount
of data present.
• Added the ability to use custom HTML data attributes with CSS selector-based data elements.
August 21 2014
Fixes and improvements:
• The help landing for dynamic tag management is now at:
https://marketing.adobe.com/resources/help/en_US/dtm/
Please update your bookmarks accordingly.
• Fixed an issue where re-enabling a previously disabled property caused all approved items to be immediately published. A
property will now be enabled, but published assets will not be affected until a publish request is explicitly requested by a user
with appropriate permissions.
• Fixed an issue where custom code editors in dynamic tag management were truncating the last few lines of displayed code.
• Fixed an issue where reverting a tool to a previous version did not revert all settings for that tool.
• Users can now force a data element's value to be automatically converted to lowercase before it is returned and used.
• Fixed issue where a race condition in the dynamic tag management engine prevented data from being sent correctly to audience
management.
August 7 2014
New features:
Feature
Description
Marketing Cloud ID Service
You can automate the deployment of the Marketing Cloud ID Service using dynamic
tag management.
See Marketing Cloud ID Service in Dynamic Tag Management Help.
Fixes and improvements:
Previous Release Notes
122
• The help landing for dynamic tag management is now at:
https://marketing.adobe.com/resources/help/en_US/dtm/
Please update your bookmarks accordingly.
• Fixed an issue where reverting an Analytics account to a previous version resulted in a 404 error.
• Fixed an issue where Approvers trying to view details on a previous version, while reviewing an approvable item, were unable
to expand the appropriate sections.
• Added support in Adobe Analytics tool configuration for visitor namespace.
• Upgraded the code editor used throughout dynamic tag management, which provides additional features, including support
for extra-long lines of code.
• Fixed an issue where events set in the Analytics rule UI were not being sent as part of data collection when the rule was set to
use s.t().
• Fixed an issue where the Force Lowercase option was not working in Google Universal Analytics.
• Fixed an issue where the default value was not returned when specifying a DOM element that did not have the attribute defined
as specified in the CSS selector for the data element.
• Fixed an issue where reverting an Analytics tool to a previous version did not revert all elements of that account, resulting in
a mixture of old and new settings for the tool.
July 24 2014
New features:
Feature
Description
Adobe Analytics account and report Report suites are automatically synchronized via a Marketing Cloud login or Web Services
suite synchronization.
ID.
Once 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.
Adobe managed measurement
library option.
You can let dynamic tag management loads and manage the base library directly. You no
longer need to cut and paste library code from the Adobe Analytics administration tools.
This feature also makes upgrades to new versions of AppMeasurement easier, because
the base code and custom code are stored separately.
Custom Code timing.
You can now select whether you want the code in the Adobe Analytics code panel to fire
before or after the interface settings for more implementation flexibility.
Interface improvements.
The groups (General, Library Management, and so on) on the Tools page for Adobe
Analytics has been reorganized and streamlined to simplify configuration.
Latest Links
See FAQ for Adobe Analytics Release - July 24 2014 for questions and answers.
See Adobe Analytics Settings for configuration information.
July 10 2014
Features and fixes:
Previous Release Notes
123
Feature
Description
Audit Log for Administrator
Click Log in the left-hand rail to view the Audit Log page.
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.
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, and more.
You can also export the log data to .csv.
Language Selector
Dynamic tag management is now available in the same languages (English, French,
Spanish, German, Korean, Portuguese, Japanese, Traditional Chinese, and Simplified
Chinese) as the rest of the Marketing Cloud.
In Account Settings, click the Languages menu to specify the language.
Synchronous loading of the Adobe
Target tool.
To enable this feature:
1. Navigate to the Target tool configuration page.
2. Enable Load Adobe Target Library synchronously.
Note: This value is enabled by default for new instances of the Adobe Target tool,
and disabled by default for existing instances of the tool.
Existing instances of the Adobe Target tool will continue to load asynchronously until
you change the setting to synchronous.
Fixes
• Fixed an issue where disabling and then enabling a property caused the items in the approvals queue to be automatically
published by the system when the property was re-enabled.
• Added a message to the Embed tab for company administrators. This message is a reminder that no code is published to the
production environment until someone explicitly clicks Publish. This fix was done to help avoid confusion by some users who
were seeing 404 Not Found errors on the production library, because they had not yet published.
• Fixed an issue where duplicate registrations were possible for the same user using a differing case. (For example,
[email protected] vs [email protected]).
• Fixed an Adobe Analytics issue that prevented you from re-adding or editing an eVar or prop value after deleting that specific
variable or property.
• Fixed an issue where rejecting an approved or published tool, and then updating that tool, did not cause a new entry to be
generated in the approvals queue.
• Fixed an issue where the Adobe Analytics tool configuration options for Always Track and Never Track did not emit the correct
values to the library and therefore did not have any effect on data collection.
• Fixed an issue where entering invalid regular expressions caused a broken interface and required you to reload the page.
Previous Release Notes
124
• Google Analytics event tag: Fixed an issue where a Fill in all fields error appeared on a rule, but you were unable to save the
rule or make any additional edits and was required to reload the page.
May 15 2014
Fixes and improvements for May 15, 2014:
• Fixed an issue where variables set in custom code were not being set on direct call or event-based rules using s.t(). The code
contained within the custom code area for direct call or event-based rules using s.t() was not correctly adding any variables
set to the beacon before an image request was being fired.
• Fixed and issue where the command bar was sticking to the bottom of the Approvals page. The persistent bar with the Edit
and Reject commands on the Approvals page was sticking to the bottom of the page rather than following the page view upon
scroll.
• Fixed an issue on the Rule List page, where a newly created rule showed Adobe Analytics in use, even if those rules were not
using Adobe Analytics.
• Fixed layout issues on Selective Publish queue page. We cleaned up the layout so that it is not truncated or stretching beyond
the boundary of the content area of the page.
• Data elements now display in alphabetical order in the Data Element Value criteria of a rule. They have now been alphabetized
for easier viewing.
• The items on the publish history are now paginated to improve performance and user experience.
• Added password security enhancements. To ensure the security for dynamic tag management accounts, we have implemented
a number of enhancements to our authentication system:
• New passwords must meet specific criteria (minimum 7 characters, at least one number, at least one letter, at least one symbol,
not one of the last 5 passwords).
• Company admins can now see how long it has been since a user last changed their password.
• Company admins can now force users to reset their password.
• Users attempting to log in 5 times unsuccessfully will be locked out for 30 minutes to prevent brute force attacks (the user
or their company admin can reset the password to re-enable access immediately).
May 8 2014
Fixes for May 8, 2014:
• Fixed an issue where trackingServer value was not being applied consistently. The value for s.TrackingServer should be used
consistently for all types of calls throughout dynamic tag management, and the value should be pulled either from the custom
code or from the UI, depending on the configuration of a specific web property. (The UI value takes precedence if set in both
locations.)
• Fixed an issue where properties with a large number of items awaiting approval was causing 500 errors and timeouts. We
optimized the queries for the approvals workflow to ensure that properties with a large number of items awaiting approval
would load quickly and not result in timeouts, errors, or broken pages.
• Fixed an issue where pages with an existing object called 's' would cause errors in dynamic tag management. Dynamic tag
management tries to initialize an 's' object on the page for Adobe Analytics tracking, and this was causing a conflict if Analytics
was implemented via dynamic tag management and the Page code already exists box was not checked. The object is now locally
scoped within dynamic tag management, so it will work in any custom code scenarios but will not conflict with any on-page
code.
• We made a number of improvements to the way that hierarchies are managed in Adobe Analytics tools and rules, including
ensuring that non-sequential hierarchies could be used together in a tool or rule, and ensuring that the same hierarchy could
not be set more than once in a tool or rule.
April 28 2014
Fixes for April 28, 2014
• Fixed an issue where direct call and event-based rules that were configured to send a page view (using s.t()) were not
executing custom code.
Previous Release Notes
125
April 17 2014
Fixes for April 17, 2014
• Fixed an issue in which an error displayed when you delete data elements that were associated with rules that had already been
deleted.
• Fixed an issue in which deleted data elements were still shown in the menu when you add a condition to a rule based on a data
element.
• Fixed an issue where fields and values for Google Universal Analytics rules were showing as modified in the Approval view,
even if the rules had not been changed. This issue also occurred on new rules.
• Fixed an issue where the Google Universal Analytics tool configuration allowed you to configure the cookie timeout in
milliseconds, even though Google Universal Analytics does not support this.
• Changed AdLens to Media Optimizer.
• Users can now use the % syntax to view the pop-up list of data elements when sending values to Media Optimizer.
• Modified styling on tool lists to better accommodate tools with long names, and to improve readability.
April 8 2014
Fixes for April 8, 2014
• Fixed the styling on the Forgot Password page to improve appearance.
• Fixed an issue where approved/published rule conditions were being removed from production library upon deletion in staging.
• Fixed an issue where the Actions menu on the Rule List page was being cut off at the bottom, if there were less than three
rules being displayed.
• Fixed alignment for the Create Data Element button on the Data Elements page.
• Fixed alignment for the Create New Schedule button on the Scheduling page.
• Fixed an issue where long rule names were breaking the Selective Publish page.
• Fixed an issue where deleting Adobe Analytics variable values would, in certain cases, result in a broken UI that required a
page refresh to fix.
April 3 2014
Features for April 3, 2014
Feature
Description
Google Universal Analytics support.
Added native support for Google Universal Analytics.
Upgrade from Google Analytics to Google Universal Integrated the Airlock JS library to perform automatic translation of all
Analytics
existing GA calls to Google Universal Analytics.
Fixes for April 3, 2014:
• Fixed an issue where clicks were not being tracked in certain scenarios when the Page code is already present box was enabled
in the Adobe Analytics tool configuration.
• Fixed an issue where all approvables were being deployed in staging, rather than just the ones that were added or modified.
This issue potentially resulted in delays to seeing staging updates.
• Fixed an issue where linkTrackVars and linkTrackEvents were being overwritten by rules, rather than appending to existing
values (such as those set in s_code).
• Fixed an issue where use of special characters (such as brackets) in data element names caused exceptions when you edited
the data element.
• Fixed an issue where a lengthy shared secret for library download bundles caused exceptions (showed as a 500 Server Error).
• Fixed an issue where the cookieLifetime variable was being emitted to the library with incorrect capitalization, causing the
corresponding setting from the interface to be disregarded when the page was loaded.
Previous Release Notes
126
March 11 2014
Fixes for the March 11, 2014 release:
• Fixed issue where test files (ftp_test.txt) were being left on FTP/SFTP servers after upload was complete. This file is
now deleted once the upload is complete as it is only used to test the ability to validate user credentials and is not actually
needed by dynamic tag management.
• Fixed issue where custom port for FTP/SFTP was not being saved.
March 6 2014
Features and fixes for the March 6, 2014 release:
Feature
Description
Added support for SFTP.
Dynamic tag management now supports transmitting published files
to a client's server via secure FTP (SFTP).
Added support for hierarchy delimiters.
A delimiter can now be specified when hierarchies are used in a rule
that sends data to Adobe Analytics. (Previously, the behavior was that
all hierarchies were comma-delimited, and any other delimiter required
use of custom code.)
Fixes
• Fixed issue with SVG images in older IE browsers. SVG images that were clicked in older IE browsers (prior to IE version 9)
caused errors and would sometimes cause the browser to crash.
• Fixed issue with custom links in direct call rules. Using custom links in direct call rules would generate a JavaScript error in
the browser.
• Fixed issue with data element rule conditions referencing the wrong name. If a user renamed a data element, and the data
element was being referenced in a rule condition, the rule would try to use the most recently specified name for that data
element. This issue occurred even if the name change had not yet been published.
• Fixed issue where elements without an HREF attribute caused errors when clicked. This issue is regarding the "linker link"
functionality in the dynamic tag management engine, which attempts to automatically track any clicked elements on the page.
Elements without an HREF were generating errors. The "linker link" code now checks that the element is an anchor tag before
attempting to track clicks on it.
February 4 2014
Fixes for the February 4 2014 release:
Fixed Issue
Description
Fixed issue with invalid URLs being accepted in web Users were able to enter invalid URLs on a web property. Valid URLs
property configurations.
are now required.
Fixed issue with port being stripped from deploy hook The deploy hook URLs containing a non-default port would have the
URL.
port removed before the HTTP call was made. This issue resulted in
deploy hook notifications being sent to the wrong URL.
January 28 2014
Fixes for the January 28 2014 release:
Previous Release Notes
127
Fixed Issue
Description
Fixed an issue with Adobe Analytics variables
overwriting one another in the interface.
A user attempting to set multiple Adobe Analytics variables would see
variables being overwritten unintentionally. (For example, a user sets
prop22, then sets prop2. Prop22 disappears and prop2 contains wrong
value.)
Note: This issue was visible in the interface but did not affect
existing code or data collection. In other words, if you did not see
the variable being overwritten before you saved the rule or tool
configuration, then you were not affected by this issue.
Fixed an issue with long account IDs causing tools list Having a long account ID for one or more tools on a web property
to be truncated on right side.
would cause the tools list to be truncated, making it impossible to then
edit that tool.
January 21 2014
Fixes for the January 21 2014 release:
Fixed Issue
Description
Fixed UI bugs with Scheduling feature.
The Scheduling feature had a number of UI bugs relating to element
styling, etc. which have now been fixed.
User can now correctly set global campaign in Adobe Fixed issue where campaign values set in the Adobe Analytics tool were
Analytics tool.
not being retained when the tool was saved.
Fixed formatting of tool-tips.
Fixed display formatting issues relating to tool-tips.
January 16 2014
Fixes for the January 16 2014 release:
Fixed Issue
Description
Akamai hosting is the default embed option for new Dynamic tag management is migrating from Amazon S3 to Akamai as
web properties.
the primary external hosting option in efforts to provide dynamic tag
management customers a more reliable hosting experience. We
encourage all current customers utilizing Amazon S3 hosting to
transition to Akamai as soon as possible, so that they may take advantage
of increased performance due to Akamai's globally distributed network.
All new companies created after January 15, 2014 will have Akamai as
their external hosting option by default.
Companies created prior to January 15, 2014 will be able to choose
between Akamai and Amazon S3 until this option is deprecated on
December 31, 2014. Any new properties created within dynamic tag
Previous Release Notes
Fixed Issue
128
Description
management companies that existed prior to January 15, 2014 will also
have the option of choosing between Amazon S3 and Akamai.
For information about migrating from Amazon S3 to Akamai, see
Akamai Hosting
Paginated user lists.
User lists for companies and web properties are now paginated (if the
company or web property has more than 25 users). This change was
done to improve both user experience and platform performance.
Company administrators may delete web properties. Use caution when taking this action, because deleting the web property
removes all tools, rules, and settings and cannot be undone.
Multiple rules containing custom Adobe Analytics
code now fire correctly.
Previously, if multiple page load rules fire and they all had custom code
for Adobe Analytics, only one of the rules would take effect.
Batch deactivation of rules now working.
Fixed an issue that was causing batch deactivation of rules to show as
having taken effect in the UI, but were not actually deactivated in the
library.
Login page reskin.
Login via Adobe ID now looks identical to the login page for
marketing.adobe.com.
Opt-out of nonessential emails.
Users will now see an option on their Account Settings page to opt out
of non-essential emails, such as approval and publish notifications, note
creations, and so on. Essential emails, such as invitations to new
companies, properties, and password resets are still sent.
November 19 2013
The following table provides information about release notes and fixes for this release.
Fixed Issue
Description
Data elements not working correctly in Target rules Fixed an issue where a data element reference in a Target rule was
rendering the literal value (e.g. "%FirstName%") on the request instead
of the substituted value returned from the data element.
Invalid regex causing library save to fail
Fixed an issue where an invalid regular expression used in rule criteria
would cause the library updates to not be successfully saved.
New property for engine: isStaging
Added a new property to the engine (_satellite.isStaging).
This property indicates whether the staging library is the library loaded
on the current page.
True indicates staging library loaded.
False indicates production library loaded.
Previous Release Notes
129
November 12 2013
The following table provides information about release notes and fixes for this release.
Fixed Issue
Description
Deleted tools are no longer visible in rules.
Fixed an issue where tools that had been deleted were still showing up in
the Rules tab.
Time On Site criteria now allows for conditional Previously, the Time On Site criteria allowed you to specify only an exact
operators.
number of minutes to match. Time on Site now supports greater than (<)
and less than (>) for increased control over time based scenarios.
Adobe Analytics rules may now use events 76 100.
New Analytics installed tools with no s_code
will not show error.
Previously, the interface showed events 1 - 75. Now, support is available
for events 76 - 100 to match the capabilities available in Analytics.
Previously, when creating a new Analytics tool instance, if you did not add
s_code to the tool, you would see a 403/Forbidden error displayed in the
console. This error occurred because dynamic tag management was
requesting a file that did not exist.
Now whenever an Analytics tool is created, the s_code is pre-populated
with helpful comments and a call to the Satellite engine notification system.
The result displays a message in the console, which instructs you to install
s_code to complete the implementation.
October 30 2013
The following table provides information about release notes and fixes for this release.
Fixed Issue
Description
Interaction required to save a rule.
A user must click in a field or make a change to a rule before the Save
button is activated. Otherwise, to leave a rule without making changes,
you must click Cancel.
Errant text appearing on selective publish UI in
Firefox.
Fixed an issue where text was being displayed (when it shouldn't have
been) at the end of each row in the selective publish UI in Firefox only.
Buttons for approval modal are not centered.
Centered the Yes/No buttons in the approval confirmation modal
window.
Sidebar collapse icon not appearing correctly in
Firefox.
The icon that appears to the left of the breadcrumbs allowing a user to
collapse/expand their sidebar was not displaying correctly in Firefox.
It should now be displaying correctly.
Company admin can see who invited a user.
Administrators can now see the name of the person who invited a
particular user to their company (if the person who invited the user is
an Adobe employee, the admin will simply see DTM Admin in place of
the name).
Adding Target arguments breaks rule formatting.
Fixed an issue where a user adding arguments to a rule containing an
Adobe Target tool would see an incorrectly formatted/broken UI
October 23 2013
The following table provides information about release notes and fixes for this release.
Previous Release Notes
130
Fixed Issue
Description
Timestamps embedded in the _satellite object for Whenever a new version of the library is published, the _satellite
publish and build.
object will now contain two new properties:
publishDate: The user requested the publish to happen (the same
date/time that appears in the History section of the UI).
buildDate: The file was created by our server processes. The difference
between the two can be used to troubleshoot potentially processing
latency issues.
New tools and data elements can be created with the Previously when a tool or data element was deleted, you could not create
same name as those of deleted tools and data elements. a new tool or data element with that same name. Now, after a tool or
data element has been deleted, a new one can be created with the same
name.
If the original is later restored, "(restored)" is appended to the name to
avoid naming conflicts.
Left navigation sidebar is now collapsible
An icon appears next to the breadcrumb header at the top of the page
allowing the user to toggle the left navigation sidebar on and off. The
interface remembers the your preference.
Adding Target arguments breaks rule formatting.
Fixed an issue where a user adding arguments to a rule containing an
Adobe Target tool would see an incorrectly formatted/broken UI.
October 15 2013
The following table provides information about release notes and fixes for this release.
Fixed Issue
Description
Breadcrumb wrapping incorrectly The breadcrumb display at the top of the page was wrapping incorrectly in Chrome on
in Chrome
certain types of pages.
Rule page pagination
Rule pages will now show only 25 rules per page and will require users to "page through"
to see the full list. This is being done both for user experience and for performance reasons
(it's less stressful on the server to produce a list of 25 rules vs. several hundred in the case
of some of our clients).
Rule page filtering
A user can now filter the rule page by the name of the rule or the name of third party tags
contained within a rule.
Tool approvals
Tools in dynamic tag management (Analytics, Target, AdLens, Audience Manager, Google
Analytics, etc.) are now part of the approval workflow. New tools, modifications to existing
tools, or removals of tools will require approval before they are published to production.
Users can now add/modify/delete tools (previously users of type "user" were not able to
do this).
Previous Release Notes
Fixed Issue
131
Description
Engine shows Analytics instead of When looking at debug messages from the dynamic tag management engine, it now says
SiteCatalyst
"Adobe Analytics" instead of "SiteCatalyst" for any messages relating to the Analytics
product and its associated rules.
See Also
Previous Release Notes for historical dynamic tag management release notes.
September 30 2013
The following table provides information about release notes and fixes for this release.
Fixed Issue
Description
New properties do not require
approval
New web properties used to require approval by a superadmin. In order to expedite
provisioning of new accounts, we have removed the requirement for this approval so that
new properties are automatically approved and instantly available.
User views dashboard
This pertains to the above story about automating new property approval. Superadmins
used to have a section called "Pending Activation" on their dashboard; this story was to
remove that section since it's no longer needed.
Enable rule copy for all company
admins
Company admins now have the same ability as superadmins to copy rules across any
companies/properties they have access to.
Changing type of data element
retains previous values
When changing the type of a data element previously, it used to retain some of the old
parameters specified by the user. We're now clearing all parameters and ensuring that the
library only contains whatever parameters are relevant to the currently selected type.
company admin resends invitation Added the ability to click a "Resend" link in the Users tab for a company in case a user
email
didn't receive their invitation e-mail for some reason. (Previously this required revoking
the invite and recreating it from scratch)
Default selector for linker link rule The "linker link" rule for Google Analytics was not emitting a selector to the library by
not being emitted to library
default, so it was trying to attach linker link functionality to all clicked page elements.
We're now correctly defaulting it to "a" (all links).
Contact and Legal Information
132
Contact and Legal Information
Information to help you contact Adobe and to understand the legal issues concerning your use of this product and documentation.
Help & Technical Support
The Adobe Marketing Cloud Customer Care team is here to assist you and provides a number of mechanisms by which they
can be engaged:
• Check the Marketing Cloud help pages for advice, tips, and FAQs
• Ask us a quick question on Twitter @AdobeMktgCare
• Log an incident in our customer portal
• Contact the Customer Care team directly
• Check availability and status of Marketing Cloud Solutions
Service, Capability & Billing
Dependent on your solution configuration, some options described in this documentation might not be available to you. As
each account is unique, please refer to your contract for pricing, due dates, terms, and conditions. If you would like to add to
or otherwise change your service level, or if you have questions regarding your current service, please contact your Account
Manager.
Feedback
We welcome any suggestions or feedback regarding this solution. Enhancement ideas and suggestions for the Analytics suite
can be added to our Customer Idea Exchange.
Legal
© 2015 Adobe Systems Incorporated. All Rights Reserved.
Published by Adobe Systems Incorporated.
Terms of Use | Privacy Center
Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States
and/or other countries. A trademark symbol (®, ™, etc.) denotes an Adobe trademark.
All third-party trademarks are the property of their respective owners. Updated Information/Additional Third Party Code
Information available at http://www.adobe.com/go/thirdparty.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement