Dynamic Tag Manager (DTM) - Appmesaurment custom code section (No Customize page Code) + Module codes on UI

[julià_pujol_ar1]

Hi colleagues,

Since DTM's Team added the possibility that deployed Adobe codes, like Appmesaurment and Visitor API natively through DTM UI, I was thinking that would be well if all code (Heartbeat, Module integrate,...) may be deployed natively as well. That arises because I would want that new Appmesuement versions or whatever code are installing by default, and on the other hand, to have a section for customize my Appmesaument code.

I try do it through Customize page Code, but unfortunately seems that this section was not thought for do it, and we cannot executed this section before Appmesaurment code (for then can add into it custom code and then activate Code Managed by Adobe). Some idea for do it?

Finally, as I cannot do that, I suggest in Idea Exchange a method for:

    1. Possibility to add other code modules, like right now Appmesurment, be managed automatically by Adobe updates.

    2. Section (Or Customize page Code checkbox) through it to can add custom Appmesaurment Code.

Please, if actually somebody have any idea to do it, I really will appreciate if shared it, if not please vote my suggested idea:

                                http://adobe.ly/1m8a03b

[Rudi_Shumpert]

Julia,

The heartbeat modules and the others should work fine with this new deployment method.   Do you have a site/DTM property that we can look at?

-Rudi

[julià_pujol_ar1]

Hi Rudi,

I'm only able to see the Appmesaurment.js code when I select  "Managed by Adobe" option, another modules seems that hasn't been added. In my last post, I was trying say that would be good if we can add those modules managed by Adobe as we do with Appmesaurement, for 1.Automatically updates and  2.Have a section where add a custom code, for example where make the do_plugins function. Whith this, we not need be attentive of Adobe updates and also we would have a section to costumize our Appmesaument.

I'm trying to do this through "Costumize Page Code", I mean, selecting "Managed by Adobe" option and then add a custom do_plugins + Modules on Costumize page code, but cannot execute it before Appmesaument, and also I imagine that this section wasn't thought for this purpose. Also when "Managed by Adobe" has been selected, the object by default becomes "s", and I use for example the "smetrics" object, I think that this not should if so :(

I hope this make sense for you. If actually we cannot do it and your team are planing offer this in a future, let me know,

Many thanks for your feedback,

Julià.

[julià_pujol_ar1]

Hi Rudi,

It make sense for you? Maybe I wasn't explained well, if you need more details just tell me,

Julià.

[salomepb]

Hi Julià,

You should be able to execute your plug-ins in the 'Customize Page Code' section of the installed analytics tool when using the 'Managed by Adobe' option. If you need them to execute first, have you tried changing the setting in the 'Customize Page Code' section to ' Execute - Before UI settings'? If you already tried this and still encountered issues, can you provide an example we can specifically troubleshoot? Additionally, you also always have the option of loading any other desired third party tags / modules in a top of page, page load rule to ensure availability as well. 

Regarding changing the tracker variable from 's' when using 'Managed by Adobe', I don't believe this is possible. Since modifying the default ’s’ variable name is essentially a customization to the configuration, you would need to select the 'Custom' option for your code configuration to indicate this variable change in the 'Tracker Variable Name' UI field in DTM.

I hope this helps! Just let me know if you still have questions.

Best,

Anna

[julià_pujol_ar1]

Hi Anna,

Before all thank you for your attention, and allow me to say that I'm excited that adobe provide us this tool,

So, I'll try to explain my idea, and the problems which I was encountering when I wanted do that. Also I would like to left clear that with "Custom" option I'm able to do that, but the idea is improving my process, and maybe all other users's process as well.

So, first doing some test I saw that the execution's order of AA deployment section (leaving part Data Elements and Rules) is like this:

[img]Screen Shot 2014-08-21 at 14.50.55.png[/img]

When I realised that the order is these, I thought that customize page is this part of code that we only want to be triggered once page is charged, and only once. Legacy implementations without DTM, used a little trick with true/false variable into do_plugins section:

[img]Screen Shot 2014-08-21 at 15.06.10.png[/img]

With this we get split a s.tl() (interactions) code with the s.t() (page loading) as do_plugins is called each time that those functions are called. So is exactly this that I miss in deployment UI AA, one part where we can do that.

Certainly, you can say me, welcome the event rules Julià! True, but unfortunately some plugins are created for to be fired into it, and also implementers can take advantage that do_plugins to be called each time that user's interactions take place, and use it as a "generall event rule".

So for solve that, I'm thinking that the best would be that "Managed by Adobe Section", should allow customize some code before that Appmeasurement has been executed. With this we got:

• Free us to make updates when Adobe update your core codes, Appmesaurement and modules (for this I published it on Idea Exchange that modules should have an option for be managed by Adobe as well), because them will be updates automatically.
• Have a section where we can costumize our do_plugins section, as a legacy implementations, and to can use as a general s.tl(); rule
• Use Costumize page code for make custom code once page is loaded, and only once (as works right now).

With this DTM executing as well as do a customized implementations:

1. Marketing Cloud Service ID (as a tool)
2. Customized code when Appmesaument and modules hasn't been executed (with suposed new feature)
3. Execution of Appmesurment and Modules (like Heartbeat)
4. Costumized code when Appmesaurment has been executed (with Costumize page code).

Under my point of vision, with this we respect legacy implementations and allow us more advantages in terms of implementation, and especially liberate us to actualize core codes if want costumize our Appmesaument code before it has been executed. Finally, and it is a personal opinion, "Managed by Adobe" should allow change the "s" object name, can trust me that many tools use the same object, like for example Sophus, and when we work with a big companies whose using a lot of third party tools, that's a problem.

PS: If you try to Execute Costumize page Code before UI, you'll realized that always Appmesaurement is executed before :(

Hope this make sense for you. If really exists on option for solve the gap which I commented, please let me know,

Julià.

[salomepb · Accepted solution]

Hi Julià,

Thanks for the detailed feedback; I've submitted this information / your request to the DTM product team for their review. We're actively working on making improvements to make this process more intuitive and effective for users, so we appreciate your feedback. 

However, for now, the best option if you're encountering timing issues with some of your plugins via the 'Customize Page Code' section is as follows:

1) First setup 'Managed by Adobe' to get the most recent code version

2) Switch to 'Custom' - this will retain the current code acquired by the 'Managed by Adobe' option but will make it editable

3) Add your plugins to the code editor. This will ensure the desired load order is accomplished.

Again, I know this isn't the most ideal method, but it should solve your immediate needs. Also, please rest assured we're working on a more complete solution like the one you're describing. Keep an eye on the product release notes here for more information on upcoming DTM product updates.

I hope this helps! Just let me know if you still have questions.

Best,

Anna

[julià_pujol_ar1]

Hi Anna,

Many thanks for your reply, right now I'm using solution that you described but I'm only testing DTM, my company will release new site and new implementation at the end of year, but I would like that at arrived this moment, implementation be as more stable as possible.

Always I'm attentive to DTM releases, so it's more important for us that this tool be as robust as possible, and I'll continue providing feedback in order to improve it. So finally, and as a summary of our proposals:

• Other modules like Heartbeat o module connection can be managed by Adobe.
• Enable a section where we can customize AppMesaurment code before it has been executed.
• Possibility to change Analytics object (by default "s") even code be managed by Adobe.

Many thanks for hearing my feedback and thanks for improving this tool,

Julià.