We’ve been getting a lot of ques­tions 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 inte­gra­tion with Adobe Analyt­ics in this latest release. Of course, with updates, comes a require­ment for train­ing and learn­ing what has changed.

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

Library Management Screenshot

This is great because you no longer have to sepa­rately open Adobe Analyt­ics, access the admin console, and click through to the Code Manager to get the code; it’s auto­mat­i­cally popu­lated in the tool! It will make updat­ing the library simi­larly as easy.

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

Caveat 1 – Don’t forget to test before publish­ing. This is a no-brainer, but it’s always impor­tant to use our DTM Switch plugin to ensure that changes you’ve made in DTM work prop­erly in produc­tion.

Caveat 2 – Make sure you’ve got your Track­ing Server (and SSL Track­ing Server if neces­sary) popu­lated in the Analyt­ics tool setup. The DTM tool doesn’t know how to popu­late this when library code is managed by Adobe.

Caveat 3 – Any custom items you have in your code library need to be moved else­where 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 else­where. One big ques­tion on everyone’s mind (and if you’ve gotten this far into our blog post then it’s prob­a­bly on your mind too) is: what happens to my custom plugins and how do I manage them? It’s such a big ques­tion 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 Analyt­ics Tool setup:

doPlugins Location

When you click Open Editor, you can add any “plugin” code you need, and then you can set vari­ables within the doPlu­g­ins func­tion. Just use the follow­ing steps:

Step 1: Add the follow­ing Plugin config code in the custom page code section. This includes the doPlu­g­ins func­tion:


func­tion s_doPlugins(s) {
//Example: Set eVar3 using the time parting plugin

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


Note that s.usePlugins is set to “true” prior to calling the func­tion itself. Also note that you set plugin values to vari­ables within doPlu­g­ins like has been done with legacy imple­men­ta­tions.

Step 2: Create a “plugins” section in the same page code that will contain all of your plugins you will call within doPlu­g­ins or your imple­men­ta­tion.


Step 3: Save and test in your staging envi­ron­ment.

Now that you’ve got plugins handled, you should have no issue migrat­ing to this slick inte­gra­tion between Adobe DTM and Adobe Analyt­ics! Please reach out in the comments with any ques­tions.