So we are using a version of the analytics code which is 7 yrs and 26 versions old. I've tried to get an update to the code briefed in to the product teams as it seems like it should be the right thing to do.
However I'm being asked why we need to do this. And honestly from reading the Adobe documentation on the releases I'm still not sure myself. I know it will unlock ClickMap capabilities, but essentially that's just representation of data we are already receiving so probably isn't valuable enough on its own.
I wondered if anybody would be able to help me with genuine business benefits of updating the code used
(i.e. you can't track visitors properly as oppose to, renames this tag).
I'd like everything to be as up to date as possible, but in the prioritisation process I'm going to need stronger reasons than that.
Or I wondered if anyone had any examples where not having updated code has hampered their use of Adobe Analytics?
Thanks for any help you can give
1. New version of Adobe Analytics AppMeasurement contains:
4. As website as made mobile friendly nowadays, making sure your website loads faster is a priority. Using old libraries might affect the rendering performance.
5. If you are in the process to update your tracking libraries I will strongly encourage you to investigate using a Tag Management System . Adobe has 2 at the moment, DTM and Launch (new one, will replace DTM ultimately I believe)
Using a TMS, has loads of benefits (faster deployments, easy deployments, keeps libraries up to dates, allows to load libraries to specific site sections, leverage data layers etc..)
Thanks Alexis, this is really usedful.
Gaming Web Analyst