We’ve been get­ting a lot of ques­tions here at the Search Dis­cov­ery office about Adobe’s lat­est update to DTM. We’ve done a lot of test­ing with the prod­uct updates and are big fans of the tighter inte­gra­tion with Adobe Ana­lyt­ics in this lat­est 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 man­age your s_code/AppMeasurement library. This selec­tion can be made here in the Adobe Ana­lyt­ics tool set­up in DTM:

Library Management Screenshot

This is great because you no longer have to sep­a­rate­ly open Adobe Ana­lyt­ics, access the admin con­sole, and click through to the Code Man­ag­er to get the code; it’s auto­mat­i­cal­ly pop­u­lat­ed in the tool! It will make updat­ing the library sim­i­lar­ly as easy.

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

Caveat 1 – Don’t for­get to test before pub­lish­ing. This is a no-brain­er, but it’s always impor­tant to use our DTM Switch plu­g­in to ensure that changes you’ve made in DTM work prop­er­ly in pro­duc­tion.

Caveat 2 – Make sure you’ve got your Track­ing Serv­er (and SSL Track­ing Serv­er if nec­es­sary) pop­u­lat­ed in the Ana­lyt­ics tool set­up. The DTM tool doesn’t know how to pop­u­late this when library code is man­aged by Adobe.

Caveat 3 – Any cus­tom items you have in your code library need to be moved else­where in DTM. Tons of our clients are set­ting cus­tom items in their code library. These need to be done either in Data Ele­ments that are pulled into a Glob­al Page Bot­tom page-load rule, or else­where. One big ques­tion on everyone’s mind (and if you’ve got­ten this far into our blog post then it’s prob­a­bly on your mind too) is: what hap­pens to my cus­tom plu­g­ins and how do I man­age them? It’s such a big ques­tion it gets its own sec­tion:


Now that you don’t have access to update your code library, where do your plu­g­ins go? Fear not, Adobe has planned for this in the Cus­tomize Page Code sec­tion of your Ana­lyt­ics Tool set­up:

doPlugins Location

When you click Open Edi­tor, you can add any “plu­g­in” code you need, and then you can set vari­ables with­in the doPlu­g­ins func­tion. Just use the fol­low­ing steps:

Step 1: Add the fol­low­ing Plu­g­in con­fig code in the cus­tom page code sec­tion. This includes the doPlu­g­ins func­tion:


func­tion s_doPlugins(s) {
//Example: Set eVar3 using the time part­ing plu­g­in

//Example: Set val­ue to con­sole to con­firm doPlu­g­ins was called
satellite.notify(“doPlugins was called”,1);


Note that s.usePlugins is set to “true” pri­or to call­ing the func­tion itself. Also note that you set plu­g­in val­ues to vari­ables with­in doPlu­g­ins like has been done with lega­cy imple­men­ta­tions.

Step 2: Cre­ate a “plu­g­ins” sec­tion in the same page code that will con­tain all of your plu­g­ins you will call with­in doPlu­g­ins or your imple­men­ta­tion.


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

Now that you’ve got plu­g­ins han­dled, you should have no issue migrat­ing to this slick inte­gra­tion between Adobe DTM and Adobe Ana­lyt­ics! Please reach out in the com­ments with any ques­tions.