This is part 2 of a mul­ti­part series on Get­ting Started with Adobe’s Dynamic Tag Man­age­ment Solu­tion. If you missed part 1, you can get caught up here.

In part 2 of this series of Get­ting Started with Dynamic Tag Man­age­ment, we will cover acti­vat­ing and con­fig­ur­ing Adobe Ana­lyt­ics.

In the first post in this series, we cov­ered cre­at­ing your first web prop­erty and deploy­ing the embed codes, so your DTM account should be prepped and ready to acti­vate Adobe Ana­lyt­ics and begin col­lect­ing data.

Step 1: Login to your DTM account and select the prop­erty that you would like to acti­vate Adobe Ana­lyt­ics in.

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


Note: Adobe’s Dynamic Tag Man­age­ment solu­tion sup­ports every sin­gle mar­ket­ing tag and script in the mar­ket­place today, and our open archi­tec­ture ensures that any new or emerg­ing scripts will be sup­ported as well. We will cover these other tags in a future post.

Once you have select the “Add a Tool” but­ton you will be pre­sented with a modal to select which of the major tools that you are ready to activate.


Select the “Adobe Ana­lyt­ics” option and the modal will present you with the options for the ini­tial setup for Adobe Ana­lyt­ics. You do not have to worry about get­ting this exactly right on the first try as you are always able to go back and adjust any of these set­tings at any time.


Step 3: Set the basic con­fig­u­ra­tion for Adobe Analytics

Now that you have added an instance of a tool, specif­i­cally Adobe Ana­lyt­ics, into your DTM account we need to setup at least the basic con­fig­u­ra­tion to get the default bea­con to fire prop­erly. To access the con­fig­u­ra­tion screen for the newly added instance, click on the gear icon as indi­cated in the image below.


This will open the main Adobe Ana­lyt­ics Con­fig­u­ra­tion options screen.


There are many options to work with and cus­tomize within in this sec­tion, but this blog post is going to stay focused on the min­i­mum set­tings that you need to setup to get the ini­tial data col­lec­tion bea­con to fire. In future posts, we will go deeper into the other options or you can refer to the addi­tional resources links at the bot­tom of this post.

Expand the Gen­eral section:


Select the “Open Edi­tor” button

This will bring up an edi­tor win­dow that you are able to paste in either the main s_code file or the new app mea­sure­ment library.


With either selec­tion you must make sure that the track­ing server infor­ma­tion is either in the edi­tor win­dow or in the “cook­ies” sec­tion as shown below.


That’s it!


Save the changes and pub­lish the changes to see your Adobe Ana­lyt­ics bea­con exe­cut­ing on your site. This whole process should only have taken 10 to 15 min­utes at most. There are many more set­tings avail­able to you that han­dle the most com­plex of the large-scale enter­prise scale imple­men­ta­tions, but you are well on your way to lever­ag­ing the full power of DTM.

For detailed spec­i­fi­ca­tions for deploy­ing Adobe Ana­lyt­ics, that cov­ers every pos­si­ble set­ting you can refer to the DTM help sec­tion here.

Or if you pre­fer you can watch this video on DTM Web Prop­er­tied on the Adobe’s Enter­prise TV Site.

Next Steps

In part 3 of this series of Get­ting Started with Dynamic Tag Man­age­ment, we will cover acti­vat­ing and con­fig­ur­ing Google Ana­lyt­ics. (Yes, you read that cor­rectly!) If you just can’t wait to progress fur­ther with DTM, take advan­tage of all the other resources below:

Addi­tional 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.