We’ve been getting a lot of questions here at the Search Discovery office about Adobe’s latest update to DTM. We’ve done a lot of testing with the product updates and are big fans of the tighter integration with Adobe Analytics in this latest release. Of course, with updates, comes a requirement for training and learning what has changed.

One of the big updates is that you can now have Adobe DTM manage your s_code/AppMeasurement library. This selection can be made here in the Adobe Analytics tool setup in DTM:

Library Management Screenshot

This is great because you no longer have to separately open Adobe Analytics, access the admin console, and click through to the Code Manager to get the code; it’s automatically populated in the tool! It will make updating the library similarly as easy.

With major update like these comes caveats, and here’s what we’ve found:

Caveat 1 – Don’t forget to test before publishing. This is a no-brainer, but it’s always important to use our DTM Switch plugin to ensure that changes you’ve made in DTM work properly in production.

Caveat 2 – Make sure you’ve got your Tracking Server (and SSL Tracking Server if necessary) populated in the Analytics tool setup. The DTM tool doesn’t know how to populate this when library code is managed by Adobe.

Caveat 3 – Any custom items you have in your code library need to be moved elsewhere in DTM. Tons of our clients are setting custom items in their code library. These need to be done either in Data Elements that are pulled into a Global Page Bottom page-load rule, or elsewhere. One big question on everyone’s mind (and if you’ve gotten this far into our blog post then it’s probably on your mind too) is: what happens to my custom plugins and how do I manage them? It’s such a big question it gets its own section:


Now that you don’t have access to update your code library, where do your plugins go? Fear not, Adobe has planned for this in the Customize Page Code section of your Analytics Tool setup:

doPlugins Location

When you click Open Editor, you can add any “plugin” code you need, and then you can set variables within the doPlugins function. Just use the following steps:

Step 1: Add the following Plugin config code in the custom page code section. This includes the doPlugins function:


function s_doPlugins(s) {
//Example: Set eVar3 using the time parting plugin

//Example: Set value to console to confirm doPlugins was called
satellite.notify(“doPlugins was called”,1);


Note that s.usePlugins is set to “true” prior to calling the function itself. Also note that you set plugin values to variables within doPlugins like has been done with legacy implementations.

Step 2: Create a “plugins” section in the same page code that will contain all of your plugins you will call within doPlugins or your implementation.


Step 3: Save and test in your staging environment.

Now that you’ve got plugins handled, you should have no issue migrating to this slick integration between Adobe DTM and Adobe Analytics! Please reach out in the comments with any questions.