Adobe Marketing Cloud Dynamic Tag Management Product Documentation

140 

Full text

(1)

Dynamic Tag Management Product

Documentation

(2)

Dynamic Tag Management Product Documentation...5

Release Notes for Dynamic Tag Management...7

Dynamic Tag Management Overview...9

Getting Started...11

Planning for Dynamic Tag Management...13

Managing Users and the Publish Workflow...13

Web Properties...15

Create a web property...17

Users and Permissions...20

Invite a user...20

Create and Manage Groups...20

Add Users to Groups...21

Create a New Group...22

Edit a Group...24

Delete a Group...25

Embed Code and Hosting Options...26

Hosting Considerations (FAQ)...28

Akamai...29

Migrate from Amazon S3 to Akamai...30

FTP...31

Library Download...32

Header and Footer Code...33

Add header and footer code...34

Verify header and footer code...34

Dynamic Tag Management Product Documentation Last updated 9/2/2015

(3)

Tools...35

Add Adobe Analytics Tool...35

General...39

Library Management...39

Global Variables...42

Page Views and Content...44

Link Tracking...45

Referrers and Campaigns...46

Cookies...46

Customize Page Code...47

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

Manually implement Adobe Analytics (legacy)...49

Add Adobe Audience Manager Tool...51

Add Adobe Media Optimizer Tool...52

Media Optimizer Rule Example...54

Add Adobe Target Tool...55

Library Management - Adobe Target...57

Global Parameters - Adobe Target...58

FAQ for Adobe Target Deployment - Released October 28 2014...59

Mbox rule example for DTM...60

Marketing Cloud ID Service Settings...62

Add Google Analytics Tool...64

Add Google Universal Analytics Tool...67

Insert third-party tags...70

Object References to Handle Cookies...70

Data Elements...71

Create a data element...76

Rules...77

Event-Based Rules Example...79

EnterpriseTV Videos: Event-Based Rules...82

Dynamic Tag Management Product Documentation Last updated 9/2/2015

(4)

Page Load Rules - Advanced...85

EnterpriseTV Videos: Page-Load Rules...87

Load Order for Rules...87

Create new rule...90

Create conditions for event-based rules...90

Create conditions for page-load rules...94

Create conditions for direct-call rules...95

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

Test unpublished rules for Akamai hosting...97

Test rules for Library Download or FTP...97

Rule Conditions and Functions...98

Migrating to Dynamic Tag Management...101

Migrating from Adobe Tag Management...101

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

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

Dynamic Tag Management Object Reference ...111

Architecture...112

Troubleshooting...113

DTM Plugins...116

Documentation Updates...121

Previous Release Notes...125

Contact and Legal Information...140

Dynamic Tag Management Product Documentation Last updated 9/2/2015

(5)

Dynamic Tag Management Product Documentation

Dynamic tag management (DTM) lets you manage your Adobe Marketing Cloud solutions and other tags across all of your sites, regardless of your number of domains.

Last Updated: September 3, 2015

Videos Getting Started & Popular Topics

• In EnterpriseTV, click Dynamic Tag Management.Request access

Deploy Adobe Analytics

Plugins

Deploy Adobe Target (New)

Deploy Media Optimizer(New) DTM Plugins

Frequently asked questions

Community Resources

Troubleshooting

Solution Overview What's New and Release Notes

Marketing Cloud Forum

Release Notes for Dynamic Tag Management Adobe Marketing Cloud Community

Current release notes and known issues for dynamic tag management.

Idea Exchange

Adobe Training and Tutorials

Featured Solutions Center

Marketing Cloud ID Service

Digital Marketing Blog

Learn how to deploy the Marketing Cloud ID Service (Visitor

ID) using dynamic tag management. •#Dynamic Tag Management

Twitter

Deploy Adobe Analytics

Learn how to let dynamic tag management automatically manage your report suites accounts and AppMeasurement code.

• If you have questions about dynamic tag management you can also tweet us at @AdobeMktgCare with the hashtag

#DTM. •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

(6)

Search and browse for help across all product documentation topics.

Contact Adobe Global Services for help with an implementation.

Contact your Adobe Account Manager to find out more about professional services.

(7)

Release Notes for Dynamic Tag Management

Release notes and known issues for dynamic tag management. This section contains the following information:

Current Release Notes

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

Current Release Notes

September 3, 2015

Adobe has deprecated the use of Amazon S3 as a DTM library hosting option.

Adobe will no longer support Amazon S3. Your dynamic tag management libraries on Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made in dynamic tag management will no longer be reflected in these files.

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

The September 3, 2015 dynamic tag management release includes the following changes:

New Features

Description Feature

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

Group management

For more information, see: •Create and Manage Groups

Add Users to Groups

Create a New Group

Edit a Group

Delete a Group

Fixes and Enhancements:

• Improved the deployment of the satellite library (2-5 times speed increase). Customers with many rules or who are deploying many third-party tags will greatly benefit from these changes.

• Improved the upload speed to Akamai (up to 5 times faster). • Improved the load speed (2 times faster) for all rule listing pages.

• Fixed an issue that prevented some pages from loading in Internet Explorer (users received a pop-up error message).

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

(8)

Description Resource

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

Documentation Updates

View information about new features and enhancements in previous releases of Adobe Social.

Previous Release Notes

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

(9)

Dynamic Tag Management Overview

Dynamic tag management lets marketers quickly and easily manage tags and provides innovative tools for collecting and distributing data across digital marketing systems. Dynamic tag management also enables responsive delivery of user-specific content —providing new levels of agility and control to companies seeking to thrive in today’s fast paced digital marketplace. This section contains the following information:

Business ChallengeSolutionBenefitsKey FeaturesOverview Video Business Challenge

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

In addition, as the technologies and tools used by marketers to implement digital strategies and deliver consumer experiences become more sophisticated, the technical requirements associated with installing and managing these tools continues to grow. These factors are hampering marketers’ ability to quickly adapt to the fast-paced, dynamic digital marketplace and compromising the effectiveness of the very tools that are designed to make digital marketers successful.

Solution

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

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

Benefits

Dynamic tag management provides the following benefits:

• Improved Site Speed: Optimize loading of multiple analytics and marketing tags, proven to slow page loads. • Quicker Implementations: Significantly reduce deployment time.

(10)

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

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

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

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

Key Features

Dynamic tag management provides the following key features: • Unmatched rule-driven data collection

• Site-centric rather than tag-centric user interface • Robust process and workflow management • Lightweight, meta-based library

• Ability to host anywhere • Built-in collaborative tools • Management of multiple sites

Overview Video

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

(11)

Getting Started

Information for new users of dynamic tag management. This section contains the following information: •Requesting Access to Dynamic Tag Management

Logging In

Getting Started Tasks

EnterpriseTV Training Videos

Requesting Access to Dynamic Tag Management

Before you start using dynamic tag management, someone from your company must request access. Your request will be fielded by our provisioning team and you should receive your login credentials within one to two business days.

To request access to dynamic tag management, visit the Adobe Marketing Cloud > Dynamic Tag Management page.

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

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

Logging In

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

Getting Started Tasks

The steps in the following table help you get up and running with dynamic tag management:

Description Location

Getting Started Tasks Step

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 Web Properties

tab on the Dashboard Create a web property.

subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template and you want to track the same assets on all of these websites. You can apply one web property to multiple domains. For general information about web properties and best practices, see

Web Properties.

(12)

Description Location

Getting Started Tasks Step

Dynamic tag management provides a number of options to host the required JavaScript files:

Embed tab Configure your hosting

options.

• Akamai

• Self-hosting: FTP Delivery • Self-hosting: Library Download See Embed Code and Hosting Options.

Dynamic tag management allows you to precisely time the loading of JavaScript and page content in your page. You can choose to run Embed tab

Add header and footer code to each managed page.

rules at the beginning or end of a page. This allows you to implement testing tools and other technologies, while retaining full control over tracking your pages.

Adobe provides staging and production embed code so you can test your changes in your staging environment before pushing changes to your production environment.

See Header and Footer Code.

Tools let you quickly integrate Adobe Marketing Cloud solutions on your site. Tools go beyond a basic tag, because they provide additional Overview tab

Deploy tools for solutions.

configuration options. A tool corresponds to Adobe solutions like Analytics and Target, as well as Google Analytics. After you add a tool to a property, it is available for inclusion in a rule.

See Tools.

Data elements are the building blocks for rules. Data elements let you create a data dictionary (or data map) of commonly used items Rules tab

Create data elements. And

on a page, regardless of where they originate (query strings, URLs, Create rules, conditions,

and actions.

or cookie values) for any object that is contained on your site. You use data elements to build a data layer that can be used in rules for Analytics and other data collection tools.

Rules can be triggered at page load or when a specific event occurs. Dynamic tag management provides a powerful conditioning interface that provides granular control of when tags fire.

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

For more information, see Data Elements and Rules.

After a rule is created, it is funneled through a multi-step approval process before it is published to a production environment. Publish tools and rules to

the production server.

(13)

EnterpriseTV Training Videos

In EnterpriseTV, click Dynamic Tag Management.

Planning for Dynamic Tag Management

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

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

Planning Ahead

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

Managing Users and the Publish Workflow

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

Description Role

Create and test rules. Users

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

(14)

Description Role

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

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

Publishing Workflow

1. A rule is saved.

2. The rule is automatically pushed to your staging site where you can perform testing.

3. The saved rule is funneled into the approval queue, where the details of the rule can be viewed in summary. 4. The Approver, Approver & Publisher, or Administrator level user approves the rule.

5. The rule goes into the publishing queue.

6. In the publishing queue, the Admin, Publisher, or Approver & Publisher level user must publish the rule before it goes live. If you make changes to a published rule, the changes are not published to the site until they have been funneled through the approval process.

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

(15)

Web Properties

A web property is a library of rules and one embed code. A web property can be any grouping of one or more domains and subdomains. You can manage and track these assets similarly. For example, suppose that you have multiple websites based on one template, and you want to track the same assets on all of them. You can apply one web property to multiple domains. This section contains the following information:

Best Practices for Planning Web Properties

How Web Properties Compare to Analytics Report Suites

Separating the DTM Environment for Multiple Entities

Best Practices for Planning Web Properties

Considering the following when planning web properties:

Best Practice Consideration

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

Data

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

If your data collection needs are unique for each site, it might make sense to separate those sites in their own web properties. This method lets you control the data collection more specifically for each site, without using large amounts of conditional logic in custom scripts. For example, if 80 percent of the data you are collecting across your sites is the same, or similar, it makes sense to group those sites together into the same web property. If the data is unique for each site, it makes sense to put each site into its own web property.

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?

Variables

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.

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

Tools, Tags, and Systems

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

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

(16)

Best Practice Consideration

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.

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?

People

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

Each implementation can be very different in dynamic tag management, with a wide variety of data-collection needs, variable usage, tools, third-party tags, other systems and technologies, people, teams, geographic regions, and so on. Using the flexible User Management features and web properties, you can create a configuration that matches your workflow and processes. If the scenarios you are tracking, the data you are collecting, the tools you are deploying, and the variables you are setting are similar across all or some of your domains and subdomains, it is easier to have those domains and subdomains grouped into the same web property in dynamic tag management. If those are unique for each domain and subdomain, it is easier to have those domains and subdomains in their own web property. If you choose to group domains and subdomains in a single property now, you can always change your mind and later create several web properties.

How Web Properties Compare to Analytics Report Suites

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

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

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

If you want to send data to a particular report suite based on conditional logic, you would add your logic in the Editor, in the

General section of the Adobe Analytics Global Settings page. Separating the DTM Environment for Multiple Entities

There are a few ways to handle multiple geo markets, business units, domains, and subdomains in dynamic tag management. First, you can have one or several dynamic tag management Company accounts. Companies contain web properties. You can have one or several or any number of web properties within a Company account. Within a web property, you can have one or any number of domains or subdomains.

(17)

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

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

Note: Each web property requires its own Embed Codes in your page templates. Any domains or subdomains you want

included in a particular web property would have the same Embed Codes in the page templates when dynamic tag management is first installed on your site.

Can we use separate instances for each?

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

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

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

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

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

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

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

Create a web property

Create a web property in dynamic tag management.

Before beginning, review the Best Practices for Planning Web Properties for web properties. 1. Navigate to your company page, then click Add Property.

(18)

2. Fill in the fields:

Description Element

The name of your property.

Name

The base URL of the property.

URL

You can add and remove domains if you want visitor data to persist between domains.

This site spans multiple 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.

Description Element

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

Allow Multi-Rule Approvals

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

(19)

Description Element

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.

Tracking Cookie Name

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

Tag Timeout

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

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.

Anchor Delay

Longer delays improve tracking accuracy. We recommend anything under 500 milliseconds, which the user will not perceive.

4. Click Create Property.

The new property will be created in a "pending" state within your Web Properties tab until an administrator approves and activates the property. After activation, the property status changes from Pending Approval to Active.

(20)

Users and Permissions

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

Note: You must have administrative privileges to invite a new user in dynamic tag management. Administrators are

automatically granted permissions to a new property. This section contains the following information:

Watch an Adobe EnterpriseTV video demonstrating how to create a user in dynamic tag management and set permissions:

Adobe EnterpriseTV Training Video: https://outv.omniture.com/?v=UzeXU2bDr5I4UoMp0vClap7AF_Rr2QRV

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.

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

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

5. Click Invite User.

An email message 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.

Create and Manage Groups

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

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

Watch an Adobe EnterpriseTV video explaining the benefits of using groups and how to set them up:

Adobe EnterpriseTV Training Video: https://outv.omniture.com/?v=tscGszdzqiW5D70hAYtMeMfIJX6YMKD5

This section contains the following information: •Default Roles

Migrated Groups for Existing Customers

Default Roles

(21)

The following table illustrates the permissions that each default role inherits: Create Property Create/Edit Users Publish Rules Approve Rules Test Rules Edit Rules Create Rules User Role Yes Yes Yes User Yes Yes Yes Yes Approver Yes Yes Yes Yes Publisher Yes Yes Yes Yes Yes

Approver and Publisher

Yes Yes Yes Yes Yes Yes Yes Admin

Migrated Groups for Existing Customers

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

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

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

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

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

Add Users to Groups

(22)

1. From your company dashboard, click Groups. 2. Click Edit next to an existing group.

You can also invite users while creating new groups as explained in Create a New Group. 3. From the Add User drop-down list, select a user's email address, then click Add User to Group.

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

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

4. Add additional users as needed. 5. Click Save Group.

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

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

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

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

Create a New Group

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

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

1. From your company dashboard, click Groups. 2. Click Create New Group.

(23)

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

Description: Specify an optional description for the group. The description displays on the Groups page and can help you

locate a specific group and determine its purpose.

Default Role: (Optional) Select a default role. All newly created properties going forward inherit this role. Create Property Create/Edit Users Publish Rules Approve Rules Test Rules Edit Rules Create Rules User Role Yes Yes Yes User Yes Yes Yes Yes Approver Yes Yes Yes Yes Publisher Yes Yes Yes Yes Yes

Approver and Publisher

Yes Yes Yes Yes Yes Yes Yes Admin

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

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

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

(24)

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

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

Note: Be aware that if you collapse the Default Role section by clicking Define Role per Property again, all roles are

set to the default role, regardless of how they were set before collapsing the section.

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

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

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

6. Add additional users as needed. 7. Click Save Group.

Edit a Group

(25)

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

1. From your company dashboard, click Groups. 2. Click Edit next to the desired group.

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

Delete a Group

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

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

1. From your company dashboard, click Groups. 2. Click Edit next to the desired group.

3. Click Delete.

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

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

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

(26)

Embed Code and Hosting Options

Information about the various hosting options in dynamic tag management: Akamai, self-hosting FTP delivery, and self-hosting library download.

Important: For a successful implementation, it is critical that you follow these instructions as they appear in Adobe Help.

Specifically, you must place the header code in the <head> section of your document templates. Also, you must place the footer code just before the closing </body> tag. Placing either of these embed codes elsewhere in your markup, or using asynchronous methods to append the embed codes, are not a supported implementation of dynamic tag management. An unsupported implementation will yield unexpected results and prevent Customer Care and Engineering from assisting with your implementation.

This section contains the following information: •Hosting Workflow

Hosting Options

EnterpriseTV Video - Library Hosting Options

Hosting Workflow

(27)

Hosting Options

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

Implementation Description

Hosting Option

The simplest hosting option to implement. Akamai (migrated

from Amazon S3)

1. Dynamic tag management generates custom JavaScript libraries.

Globally distributed delivery network. 2. Dynamic tag management exports the custom

JavaScript libraries to Akamai. Adds additional third-party infrastructure

dependencies (DNS lookup, Akamai availability). 3. The target website references the Akamai-hosted dynamic tag management libraries directly at the page level.

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.

A push approach, whereby dynamic tag management exports custom JavaScript libraries directly to the web content server host via the FTP protocol. Self-hosting: FTP

Delivery 1. Dynamic tag management generates custom

JavaScript libraries.

2. Dynamic tag management exports the custom JavaScript libraries to host server via FTP. This solution requires an FTP server and credentials

to be available on the web content server to publish

3. The target website locally references the custom dynamic tag management libraries.

changes to the custom dynamic tag management libraries.

A pull approach, whereby the application exports custom JavaScript libraries to Amazon S3. There, the Self-hosting:

Library Download 1. Dynamic tag management generates custom

JavaScript libraries.

2. Dynamic tag management exports the custom JavaScript libraries to Akamai.

libraries can be accessed by a hosted server-side process.

3. Custom dynamic tag management libraries are manually or programmatically moved to the web content server.

Additionally, the libraries are available via web download directly from the dynamic tag

management interface. 4. The target website locally references the custom

dynamic tag management libraries. This solution requires either a manual retrieval and

(28)

Implementation Description

Hosting Option

or the creation of an automated process that pulls the libraries from Akamai onto the web content server.

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

To check if the latest version of your library file is being referenced, use the command

_satellite.publishDate in the web console. This will return the date and time of publish for the library file currently being referenced. Compare this to the time and date of your latest publish shown in the History tab of your property to determine if the file has been updated.

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:

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 How do I choose a hosting option?

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

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

(29)

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

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.

What is your current policy regarding website content sources?

Akamai

FTP delivery

Library download

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

Can I use more than one dynamic tag management library hosting option at once?

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

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

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 your current website content

deployment process?

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.

What is the current page-level markup and structure of the website?

Key items to identify include:

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

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

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

Akamai

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

(30)

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

Note: After July 31, 2015 Adobe will no longer support Amazon S3. Your dynamic tag management libraries on Amazon

S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made in dynamic tag management will no longer be reflected in these files.

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

Why Choose Akamai Hosting for Library Files?

Can I Avoid Errors in Case of Akamai Unavailability?

Why Choose Akamai Hosting for Library Files?

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

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

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

Can I Avoid Errors in Case of Akamai Unavailability?

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

Migrate from Amazon S3 to Akamai

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

Note: After July 31, 2015 Adobe will no longer support Amazon S3. Your dynamic tag management libraries on Amazon

S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made in dynamic tag management will no longer be reflected in these files.

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

1. Navigate to the Embed tab.

2. Replace your existing Amazon S3 header codes with the new Akamai header codes. No change is necessary in the footer code.

(31)

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

Note: After you disable Amazon S3, you can no longer use Amazon S3 hosting. Ensure that you no longer need Amazon

S3 before turning it off.

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

FTP

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

The FTP Delivery hosting option lets you self-host the library files. When an authorized dynamic tag management user makes a change in the software, dynamic tag management writes those changes to the library files. When you 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.

(32)

3. Provide the required FTP information for the staging and production servers, then click Save FTP Information. 4. Toggle the switch in the top right corner to ON.

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

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

Note: The staging code should go only into your staging or development environment. Production code should be placed

on the live production site.

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

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

Library Download

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

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

You must be an administrator to deploy using the Library Download. 1. In the web property, click the Embed tab.

2. Click Library Download in the left navigation.

(33)

Description Option

Encrypts the dynamic tag management library during download.

Shared Secret

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

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.

Deploy Hook URL

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

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

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

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

6. Click the Header Code and Footer Code sections.

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

Note: The staging code should go only into your staging or development environment. Production code should be placed

on the live production site.

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

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

Header and Footer Code

You can add header and footer code that determines the loading of JavaScript and page content on your site. You must install both the header and footer code on every page of your site, regardless of the hosting option used.

Important: For a successful implementation, it is critical that you follow these instructions as they appear in Adobe Help.

Specifically, you must place the header code in the <head> section of your document templates. Also, you must place the

footer code just before the closing </body> tag. Placing either of these embed codes elsewhere in your markup, or using

asynchronous methods to append the embed codes, or wrapping the embed codes in any way, are not a supported implementations of dynamic tag management. The embed codes must be implemented exactly as provided.

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

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

(34)

Add header and footer code

Add header and footer code in dynamic tag management.

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

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

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

2. Copy the production footer code and place it in the BODY section of your site HTML. Place the code as close to the </body> tag as possible.

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

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

Verify header and footer code

Verify that your dynamic tag management library is loading properly on your site. 1. Open your site in your browser.

2. Open the Developer Console by right-clicking and choosing Inspect Element > Console. 3. Type the following command into the console:

_satellite.settings.notifications = true;

4. Press Enter.

If the code was properly installed, you will see true display in the console. If the code was not properly installed, you will see the reference error:

_satellite is not defined

If you receive this error, ensure that:

• You have included the full header code on every page of the site in the HEAD section, as close to the <head> tag as possible. • You do not have unexpected characters appearing in the code snippet, potentially as a result of copying and pasting from

(35)

Tools

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

Dashboard > Company > Web Property Name > Overview Description

Element

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

Installed Tools

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

Adobe Analytics

Adobe Audience Management

Adobe Media Optimizer

Adobe Target

Marketing Cloud ID Service (Analytics Visitor ID) •Google Analytics

Google Universal Analytics

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.

Add a Tag

See Rules.

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

Assigned Users

See Users and Permissions.

Add Adobe Analytics Tool

You can deploy Adobe Analytics (Standard and Premium) using dynamic tag management by creating the Adobe Analytics tool and configuring the page code either automatically or manually. The automatic method is recommended for most users. This section contains the following information:

Add an Adobe Analytics Tool

Edit an Existing Adobe Analytics Tool

Enabling Adobe Analytics Premium

EnterpriseTV Video - Add Adobe Analytics Tool

Add an Adobe Analytics Tool

(36)

2. Fill in the fields:

Description Element

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

A descriptive name for this tool. This name displays on the Overview tab under Installed

Tools.

Tool Name

Manual: Manually manage the AppMeasurement code. You can download the

AnalyticsAppMeasurement code from Admin Tools > Code Manager. Configuration Method

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

Fill in the fields specific to a manual configuration:

• Production Account ID: (Required)) A number for your production account for data collection. Dynamic tag management automatically installs the correct account in the production and staging environment.

• Staging Account ID: (Required) A number used in your development or test environment. A staging account keeps your testing data separate from production. • Tracking Server: Specify the information for your tracking server.

The Tracking Server and SSL Tracking Server variables are used for first-party cookie implementation to specify the domain at which the image request and cookie is written. For more information, see the Correctly Populate the trackingServer and

trackingServerSecure Variable article.

Note: These fields are required when using a manual configuration with multiple

(37)

Description Element

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

Automatic: Use dynamic tag management to manage the configuration. This method

enables automatic synchronization of Adobe Analytics report suites via a Marketing Cloud login or Web Services ID, and manages the AppMeasurement code.

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

Note: You must choose the Automatic option if you are an Adobe Analytics Premium

customer. See Enabling Adobe Analytics Premium below.

Fill in the fields specific to automatic configuration:

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

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

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

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

3. Click Create Tool to create the tool and display it for editing. Tools are displayed on the Overview tab, under Installed Tools.

4. (Conditional) Configure the tool further as necessary by following the directions in the links below (General, Library

Management, Global Variables, Pageviews & Content, Link Tracking, Referrers & Campaigns, Cookies, and Customize Page Code).

See for additional information about this tool.

Edit an Existing Adobe Analytics Tool

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

Click the icon next to an installed tool from the Overview tab. 2. Edit the fields as desired.

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

Description Element

Enable Automatic Configuration

Note: Enabling this setting changes a manually configured implementation to the

(38)

Description Element

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

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

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

3. (Conditional) Configure the tool further as necessary by following the directions in the links below (General, Library

Management, Global Variables, Pageviews & Content, Link Tracking, Referrers & Campaigns, Cookies, and Customize Page Code).

4. Click Save Changes.

Enabling Adobe Analytics Premium

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

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

Adobe Analytics Premium Adobe Analytics (Standard)

Adobe Analytics (Point Product) 250 100 75 eVars 1,000 1,000 100 Events

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

• Use the Automatic configuration method (explained above).

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

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

Note: If you downgrade to standard Analytics in the future, the added premium eVars that are out of the standard range

will be grayed out in both tools/rules. You can view any configured variables that are now out of range and make any necessary changes to an in-range variable. You cannot add or edit any of these out-of-range variables, but you will be able to view them and delete them.

EnterpriseTV Video - Add Adobe Analytics Tool

Watch an Adobe EnterpriseTV video demonstrating how to add Adobe Analytics as a dynamic tag management tool:

(39)

General

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

Property > Edit Tool > General

Description Element

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

When a page is loaded, the system checks to see if a cookie 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");

Displays the available character encoding sets. Character Set

Displays the supported currency codes for selection. Currency Code

The domain at which the image request and cookie is written. Tracking Server

See trackingServer.

The domain at which the image request and cookie is written. Used for secure pages. If not defined, SSL data goes to trackingServer.

SSL Tracking Server

See trackingServerSecure.

The Adobe data center used for data collection. Data Center

Library Management

Figure

Updating...

References

  1. In https://outv.omniture.com/
  2. .http://www.adobe.com/video/solutions/digital-marketing/dynamic-tag-management/overview-dynamic-tag-mgmt.modaldisplay._s_content_s_dotcom_s_en_s_solutions_s_digital-marketing_s_dynamic-tag-management.html
  3. page.
  4. Administrators, see
  5. Browse to
  6. Click
  7. For more information, see the
  8. Developers, see
  9. additional eVars and events. For more information, see
  10. See http://microsite.omniture.com/t2/help/en_US/sc/implement/?f=trackingServer
  11. See http://microsite.omniture.com/t2/help/en_US/sc/implement/trackingServerSecure.html
  12. .http://microsite.omniture.com/t2/help/en_US/sc/implement/dynvars_overview.html
  13. If you are unsure if the desired attribute is standard or non-standard, reference
  14. .http://microsite.omniture.com/t2/help/en_US/sc/implement/channel.html
  15. Se http://microsite.omniture.com/t2/help/en_US/sc/implement/hierN.html
  16. See http://microsite.omniture.com/t2/help/en_US/sc/implement/trackInlineStats.html
  17. See http://microsite.omniture.com/t2/help/en_US/sc/implement/trackDownloadLinks.html
  18. See http://microsite.omniture.com/t2/help/en_US/sc/implement/linkDownloadFileTypes.html
  19. See http://microsite.omniture.com/t2/help/en_US/sc/implement/trackExternalLinks.html
  20. See http://microsite.omniture.com/t2/help/en_US/sc/implement/linkLeaveQueryString.html
  21. .http://microsite.omniture.com/t2/help/en_US/sc/implement/referrer.html
  22. .http://microsite.omniture.com/t2/help/en_US/sc/implement/campaign.html
  23. See http://microsite.omniture.com/t2/help/en_US/sc/implement/?f=visitorid
  24. See http://microsite.omniture.com/t2/help/en_US/sc/implement/visitorNamespace.html
  25. See http://microsite.omniture.com/t2/help/en_US/sc/implement/cookiedomainperiods.html
  26. See http://microsite.omniture.com/t2/help/en_US/sc/implement/fpCookieDomainPeriods.html
  27. See http://microsite.omniture.com/t2/help/en_US/sc/implement/?f=transactionid
  28. See http://microsite.omniture.com/t2/help/en_US/sc/implement/cookielifetime.html
  29. Click
  30. Marketing Cloud services and features, such as
Related subjects :