Show Menu
TOPICS×

Frequently asked questions

Frequently asked questions about Dynamic Tag Management.

FAQ -getting started

A FAQ answering common questions about your decision to use Dynamic Tag Management.
How do I get started?
How much does Dynamic Tag Management cost?
Dynamic Tag Management is free.
Are there limitations on my use of Dynamic Tag Management?
You can create as many Web Properties as you want and write as many rules as you want. You can also use it to deliver any digital marketing service, even if you don’t use it to deliver Adobe Digital Marketing solutions. There is no effective limitation on your use of the capability.
Why is it an advantage for customers (over competitive offerings) to use Dynamic Tag Management from Adobe?
The Dynamic Tag Management advantage is the control and flexibility of using rules. It is also the only market-leading tag management solution that supports all of your digital marketing services and is offered to customers at no additional cost.
Who can help me with my Dynamic Tag Management implementation?
Adobe Global Services provides Dynamic Tag Management implementation, as do several implementation partners. Contact your account manager for more information.
With which Adobe Experience Cloud solutions are Dynamic Tag Management integrated?
Dynamic Tag Management will support all of the Experience Cloud solutions as well as any digital marketing service, regardless of vendor.
How do I access Dynamic Tag Management through the Adobe Experience Cloud?
Before you can start using Dynamic Tag Management, someone from your company must request access. See Requesting Access to Dynamic Tag Management .
Why am I getting an "Access Failed" error when I try to access the Experience Cloud?
Make sure that your company has been provisioned to use the Experience Cloud. See Manage Experience Cloud users and products in the Experience Cloud Product Documentation .
How do I assign my account to a Company name in the Experience Cloud?
You must add an organization to the Experience Cloud Organizations & Product Access page and set it as the default organization. You add an organization if you have access to more than one company's Experience Cloud accounts. See Organizations in the Experience Cloud Product Documentation .
How do I link my account to an Adobe ID?
When you click Join Experience 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 Experience Cloud solutions and services. See Join the Experience Cloud from a Solution in the Experience Cloud Product Documentation .
How do I link solutions from within the Experience Cloud?
For more information, see Organizations and account linking in the Experience Cloud Product Documentation .
Do I need to remove my Analytics or other tags from my site to use Dynamic Tag Management?
No. You can leverage Dynamic Tag Management without touching any of the existing tags on your site. Just place the embed code and start creating rules. Dynamic Tag Management can work with existing services tagged directly to the page.
Does Dynamic Tag Management work for apps as well as sites?
For web apps (applications that run in the browser or for pages with many Ajax sequences), DTM provides excellent data collection and distribution capabilities. See Event Types .
For mobile apps, there is a bit of misinformation out there regarding tag management capabilities on mobile devices. The answer depends on how the mobile application is built and deployed.
DTM is fully compatible with any hybrid mobile apps using a wrapper, such as PhoneGap or Cordova. DTM is also fully compatible with responsive designs or mobile-optimized sites consisting of HTML, CSS, and JavaScript.
For fully-native, compiled, Objective-C mobile applications where every piece of screen content comes from within the compiled code, there is no tag management system available today to adequately deal with tagging use cases in those environments. For those cases, Adobe recommends the full power, flexibility, and visitor context available through the Analytics SDK.
If the apps are a hybrid of native code for their screen "shells" (header, footer, & sidebar) and the native app pulls in HTML and CSS content from the web to display on the mobile device screen, DTM can be useful for the web content.
In other words, the tag management functionality you can use in a mobile application depends on how the app was built.
What third-party tags are supported by Dynamic Tag Management?
Any third-party tag can be deployed through Dynamic Tag Management. Our top-down, rules-driven approach leverages those third-party tags as fuel for power digital marketing use cases.
Does Dynamic Tag Management support HTML5?
Yes, HTML5 is supported.
Dynamic Tag Management does not yet support fully native applications. It can handle an application if it has an in-application browser or is essentially a website wrapped in an app container. Properties for the mobile and desktop sites should be able to be set up as normal.
Which browser versions does DTM support?

FAQ - Dynamic Tag Management and Adobe Experience Cloud

A FAQ about using Dynamic Tag Management with Adobe Experience Cloud.
With which Adobe Experience Cloud solutions are Dynamic Tag Management integrated?
Dynamic Tag Management will support all Experience Cloud solutions as well as any digital marketing service, regardless of vendor.
How do I access Dynamic Tag Management through Adobe Experience Cloud?
Before you can start using Dynamic Tag Management, someone from your company must request access. See Requesting Access to Dynamic Tag Management .
Why am I getting an "Access Failed" error when I try to access Experience Cloud?
Make sure that your company has been provisioned to use Experience Cloud. See Activation in the Experience Cloud Product Documentation .
How do I assign my account to a Company name in Experience Cloud?
You must add an organization to the Experience Cloud Organizations & Product Access page and set it as the default organization. You add an organization if you have access to more than one company's Experience Cloud accounts. See Organizations in the Experience Cloud Product Documentation .
How do I link my account to an Adobe ID?
When you click Join Experience 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 Experience Cloud solutions and services. See Join the Experience Cloud from a Solution in the Experience Cloud Product Documentation .
How do I link solutions from within Experience Cloud?
For more information, see Organizations and account linking in the Experience Cloud Product Documentation .
How do I provision the Adobe Experience Cloud ID service using DTM?
How do I troubleshoot my account access when it is linked to the Experience Cloud ID Service.
For more information about troubleshooting issues that arise from account linking, see Troubleshooting Account Linking in the Experience Cloud Product Documentation .
How do I implement Adobe Experience Manager (AEM) using DTM?
Contact Customer Care to get the required information and to get started.

FAQ - advanced

A FAQ about performance, rules, loading, hosting, and so on.
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 content type application/xhtml+xml or text + xhtml ?
Yes.
The only potential issue is the use of document.write, because content type text + xhtml does not support document.write. However, this issue can be avoided because document.write is used by Dynamic Tag Management only in the situations stated below.
  • Loading of the staging library using the Dynamic Tag Management switch plugin uses document.write.
    Workaround: Test in the staging environment by specifically referencing the staging library in the page code instead of using the Dynamic Tag Management switch plugin to toggle between libraries.
  • Synchronously loading JS and HTML scripts via Dynamic Tag Management uses document.write.
    Workaround: The synchronous loading of scripts via Dynamic Tag Management cannot avoid document.write. Thus, when this content type is being used, all third-party scripts (JS and HTML) should be loaded asynchronously in Dynamic Tag Management to avoid document.write. Please always consider and test all code dependencies to ensure the desired behavior is still accomplished with asynchronous loading.
Will Dynamic Tag Management reduce my website's performance?
Dynamic Tag Management has never shown signs of negatively affecting page load time or execution speed.
However, because Dynamic Tag Management can be used as a delivery system (a way to deliver JavaScript, HTML, images, or other Web content), if you load a large file, or a large image at the wrong point during render time, you can slow down page load speed and increase code execution time on that page. If you lazy load images, and if you use asynchronous (non-sequential) scripts as much as possible, and you follow best practices regarding the code you add into Dynamic Tag Management, you should not see negative performance impacts.
The Embed code should be hard-coded in the section of your templates. This is a synchronous JavaScript include. The Dynamic Tag Management engine is designed to work in a modular way, so scripts that do not apply to a particular page, site section, or domain will not load or execute when they are not needed. Most users increase the use of asynchronous (non-sequential) methods when deploying third-party scripts. This generally improves the perceived page load speed for site visitors. While the Dynamic Tag Management main library file itself is loaded synchronously, most clients load any code from within Dynamic Tag Management using the built-in asynchronous methods.
How do I remember which tags are in which rules? How do I keep track of my tags and make it easier to find certain rules?
Adobe recommends using the rule Name, the Tag Name, and the Categories to label your rules in a way that helps you find things faster later on, when you need to come back and change a rule, or group of rules.
For example, because different Page Load and Event Based rules respond to different Conditions, it might make sense to add an indicator about the Conditions in the rule Name, like “Global Page Load."
When working with Third Party Tags or custom JavaScript, you can add information into the Tag Name field. Later, when you are looking for all the rules with a certain tag, you can filter the list of rules by Tag Name to find all rules containing that tag.
Finally, each rule can be labeled with a Category and a value. The Category is also available when filtering your list of rules, so you can easily and quickly find the list of rules in a certain Category. For example, using a Category like “3rd Party” with a value of “DoubleClick” lets you search for all rules in the “3rd Party” Category, or all rules with the value of “DoubleClick”.
Does Dynamic Tag Management have features that help avoid errors due to asynchronous tag loading or rare cases of CDN unavailability?
Adobe recommends the use of tag event callbacks provided by amc.on to wrap any code that depends on tags delivered by any tag management system.
Can the Dynamic Tag Management library files work with the version control system we use at my company?
Adobe offers two options for self-hosting the library files: FTP Delivery and Library Download . When you choose one of these self-hosted options for the library, each time you make changes in Dynamic Tag Management, those changes are written out by the system to the library files. Those files are typically then "pushed" or "pulled" to your architecture automatically. Once the updated library code is on your servers, you can add the files to your version control systems and processes however you like. If you use GitHub, SVN, or some other system to manage your web development code or content, that works fine with Dynamic Tag Management.
One note on version control: Ensure you do not overwrite the production version of the Embed code with the staging version of the Embed code when you commit and push code to production. The staging version of the Embed code has to stay in the staging (non-production, test, dev, QA, UAT, etc.) environment templates. The production version of the embed code has to stay in the production templates.
Can I use Dynamic Tag Management with our mobile applications?
Currently, Dynamic Tag Management can be used in any digital experience created with HTML, CSS, and JavaScript. This includes any mobile-optimized content or responsive designs. This also includes mobile applications created with wrappers like Cordova or PhoneGap.
Unfortunately, at this time, Dynamic Tag Management does not offer a separate SDK for use with completely native, compiled applications. You can still track your mobile applications using the Adobe Analytics SDK. Dynamic Tag Management can also be present on HTML documents pulled into your mobile app when desktop or responsive content is accessed within the native app experience, like in hybrid or crossover content situations.
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:
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.
Does the Dynamic Tag Management code send any information back to Adobe?
Dynamic Tag Management is a way to get JavaScript and HTML to your pages. It sends data only to the systems, tools, or tags that you specifically choose when using the system. In other words, Dynamic Tag Management does not send any data anywhere, unless you specifically tell it what data should be collected, and then tell it when, where, and how it should be sent to any systems, tools, or tags.
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?
My data element setup does not seem to be working. How do I test it?
Navigate to a page where the data element should be available on your site. Open your web console and type in _satellite.getVar(‘dataelementname’) and press enter. This action returns any value that is present for the noted data element on that page. If the value is undefined, the data element is likely setup incorrectly. If the value is null , then that data element may not have a value on that particular page.
How can I tell if my site is in a live or staging environment?
DTM Switch is a browser plugin for easy switching between debug mode and staging mode for Dynamic Tag Management users. It is available for both Google Chrome and Mozilla Firefox. See DTM Plugins .

FAQ - Adobe Analytics tool

A FAQ about the automatic configuration of the Adobe Analytics deployment. The automatic configuration method manages the AppMeasurement code for you.
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.
If I make configuration changes in the new version of the tool, can I test in staging before publishing to production?
Yes.
All changes can be tested in staging just like you normally would before deploying to a production environment. If you choose not to publish, because you notice issues in staging, the production code will continue to function as it did before the new integration was released.
If I switch from manual configuration (the default setting for existing tools) to automatic configuration, will my current settings be affected?
No.
If I switch from manual library management to Managed by Adobe, will my current settings or code be affected?
Any user code that you have specified is overwritten with the base AppMeasurement library. You must move this code to the new Custom Page Code section at the end of the tool configuration so that the code continues executing. This method allows the AppMeasurement library to be managed (and upgraded) separately from the user's custom code.
Will the revision history for the Adobe Analytics tool be retained when the new integration is released?
Yes.
How do I configure persistence for a data element?
See the Persistence section in Data Elements .
See Configure Adobe Analytics for configuration information.

FAQ - Adobe Experience Platform Launch

A FAQ about the new version of Dynamic Tag Management, announced in March 2017.
What is Launch?
Adobe Experience Platform Launch is the next-generation of the Adobe tag-management capability, built into the Adobe Cloud Platform. Launch enables clients to:
  • Deploy client-side web products using integrations called extensions
  • Consistently capture, define, manage, and share data between marketing and advertising products from other vendors and from Adobe
Launch is an advanced JavaScript delivery system that evaluates conditions and executed actions to efficiently and effectively deploy client-side libraries and products. It provides a highly scalable approach to managing and building extensions, together with a robust set of APIs for programmatic interaction with the Adobe Cloud Platform.
For more frequently asked questions about Launch, see Launch FAQ .
Will Launch replace DTM?
Adobe has released plans to sunset DTM by the end of 2020. For more information and scheduling, see DTM Plans for a Sunset in the Adobe community forums.