Migration from Old Code to New Appmeasurement.js | Community
Skip to main content
Mandeep5062
Mandeep5062
New Participant
October 16, 2015
Solved

Migration from Old Code to New Appmeasurement.js

HI All, 

We are trying to migrate to new appmeasurement.js and i want to know what are the steps, precautions and things to remember?

Please Help 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
zackbearlakeAccepted solution
Level 2
October 16, 2015

Here is a good reference to shift the implementation type: http://www.searchdiscovery.com/blog/adobe-dtm-update-let-adobe-manage-measurement-library/

This link shows what needs to happen in order to move your plugins to the custom code section. I would recommend implementing and testing one plugin at a time.

Also, you no longer need the s.getQueryParam plugin. This is built into the new appMeasurement code. You can call this with s.Util.getQueryParam();

The only thing they are missing from their code to implement plugins is you need to define "s"

View reply

4 replies

Nikhil_Bisne
Level 8
October 16, 2015

See if this doc helps : About AppMeasurement for JavaScript

 

Thanks

Nikhil

Translate
Mandeep5062
Mandeep5062Author
New Participant
October 16, 2015

Thanks Nikhil, 

 

I have already seen this document. But we are using dynamic account selection and which is not supported in new library. There are some plugins which are also not supported. 

What needs to be done in order to successfully migrate ?

Translate
Gigazelle
Gigazelle
Employee
October 16, 2015

Hi Mandeep,

Any precautions that need to be taken, you're already taking them. Some plug-ins are not yet supported, which I believe our consulting team is working on them. You're welcome to use custom rules in DTM to accomplish similar tasks the plug-ins do.

Translate
zackbearlakeAccepted solution
Level 2
October 16, 2015

Here is a good reference to shift the implementation type: http://www.searchdiscovery.com/blog/adobe-dtm-update-let-adobe-manage-measurement-library/

This link shows what needs to happen in order to move your plugins to the custom code section. I would recommend implementing and testing one plugin at a time.

Also, you no longer need the s.getQueryParam plugin. This is built into the new appMeasurement code. You can call this with s.Util.getQueryParam();

The only thing they are missing from their code to implement plugins is you need to define "s"

Translate
Terms & ConditionsAccessibility statement

Loading footer...