This is part 2 of a multipart series on Getting Started with Adobe Dynamic Tag Management. If you missed part 1, you can get caught up here.

In part 2 of this series of Getting Started with Dynamic Tag Management, we will cover activating and configuring Adobe Analytics.

In the first post in this series, we covered creating your first web property and deploying the embed codes, so your DTM account should be prepped and ready to activate Adobe Analytics and begin collecting data.

Step 1: Login to your DTM account and select the property that you would like to activate Adobe Analytics in.

Step 2: Select the “Add A Tool” button:


Note: Dynamic Tag Management supports every single marketing tag and script in the marketplace today, and our open architecture ensures that any new or emerging scripts will be supported as well. We will cover these other tags in a future post.

Once you have select the “Add a Tool” button you will be presented with a modal to select which of the major tools that you are ready to activate.


Select the “Adobe Analytics” option and the modal will present you with the options for the initial setup for Adobe Analytics. You do not have to worry about getting this exactly right on the first try as you are always able to go back and adjust any of these settings at any time.


Step 3: Set the basic configuration for Adobe Analytics

Now that you have added an instance of a tool, specifically Adobe Analytics, into your DTM account we need to setup at least the basic configuration to get the default beacon to fire properly. To access the configuration screen for the newly added instance, click on the gear icon as indicated in the image below.


This will open the main Adobe Analytics Configuration options screen.


There are many options to work with and customize within in this section, but this blog post is going to stay focused on the minimum settings that you need to setup to get the initial data collection beacon to fire. In future posts, we will go deeper into the other options or you can refer to the additional resources links at the bottom of this post.

Expand the General section:


Select the “Open Editor” button

This will bring up an editor window that you are able to paste in either the main s_code file or the new app measurement library.


With either selection you must make sure that the tracking server information is either in the editor window or in the “cookies” section as shown below.


That’s it!


Save the changes and publish the changes to see your Adobe Analytics beacon executing on your site. This whole process should only have taken 10 to 15 minutes at most. There are many more settings available to you that handle the most complex of the large-scale enterprise scale implementations, but you are well on your way to leveraging the full power of DTM.

For detailed specifications for deploying Adobe Analytics, that covers every possible setting you can refer to the DTM help section here.

Or if you prefer you can watch this video on DTM Web Propertied on the Adobe’s Enterprise TV Site.

Next Steps

In part 3 of this series of Getting Started with Dynamic Tag Management, we will cover activating and configuring Google Analytics. (Yes, you read that correctly!) If you just can’t wait to progress further with DTM, take advantage of all the other resources below:

Additional Resources



@pujoljulia I have the same question. The DTM document is not clear whether the page code s.t() needs to be inserted in a page load rule. I do not have s.t() in the managed s_code and DTM auto-executed s.t() on every page.

I am looking for a  way stop atuo-executing s.t() on certain pages in DTM. However, I could not find any settings to prevent s.t() from firing. 

Any suggestions?

Paul Suman Raj Talari
Paul Suman Raj Talari

Rudi, Thanks for the Article, one quick question..where do you thing the best place for "s.t()" code? Should I copy it in the custom page code or create a global page load rule?


@rwong @pujoljulia: I will try my best to answer both of your questions below with my limited knowledge on DTM: 

1. No need to insert s.t() call in page load rule. The Tag loader code snippets (Header and Footer codes) takes care of that.

2. There is a known way in Adobe Analytics (SiteCatalyst) which let's you abort the image requests. You can try abort flag. 

Ex: s.abort= true;

Also note that you might have to build a logic around this flag to stop the image requests on certainly pages. Leverage this abort flag and you should be good to stop the auto-execution.

Hope this helps.


Harsh Kabra

**Disclaimer: The views given here are my personal and it has connection with my employer.