Code version H.21.1 released

Analytics · By On · 6 Comments

Some of you may have noticed that code Site­Cat­a­lyst ver­sion H.21.1 is now avail­able in the Admin Con­sole. (Fewer of you die-hards may have even noticed that JavaScript ver­sion his­tory has been added to the release notes!) I have doc­u­mented some details around the last two JavaScript code updates that we have put out on this blog, and will con­tinue to do so going for­ward. When I was in our Client­Care orga­ni­za­tion, a com­mon ques­tion that we heard was, “Should I upgrade my imple­men­ta­tion to the lat­est code ver­sion, or am I okay to stay put?” Hope­fully these posts will help answer that ques­tion by explain­ing the changes clearly.

There were two minor updates in code ver­sion H.21.1:

  • We improved ClickMap data accu­racy in cases where multi-suite tag­ging is in use.
  • We improved the way URL encod­ing and decod­ing occur in the case of multi-byte char­ac­ters, in order to work around a bug in older browser ver­sions in the Android OS.

So, how do you know whether you should con­sider upgrad­ing to H.21.1? You should con­sider upgrad­ing if:

  • You use multi-suite tag­ging (see expla­na­tion here) and also rely heav­ily on ClickMap.
  • You have a mobile site that uses multi-byte char­ac­ters and receives traf­fic from Android devices.

There you have it. As always, please feel free to sub­mit JavaScript code sug­ges­tions at the Idea Exchange; we’re lis­ten­ing! And if you have any ques­tions about this code release or any­thing else related to the Adobe Online Mar­ket­ing Suite, leave me a com­ment or send me a tweet (@benjamingaines).

  • http://www.stauer.com Mitchell Teix­eira

    Hi — thanks for this info and insight! Is there a way to find a change his­tory for all tag ver­sions going back to the beginning?

    • http://blogs.omniture.com/author/bgaines Ben Gaines

      Mitchell,

      Going all the way back to 1996? :) Cur­rently, there isn’t a pub­licly avail­able sin­gle his­tory of JavaScript code updates going all the way back, but if you give me a sense of how far back you need to go, I’ll see what I can do. Your Account Man­ager should be able to pro­vide infor­ma­tion on this as well. Also note that the code his­tory sec­tion that we added to the release notes (as of this past release) shows his­tory for the last 10 code releases, I believe.

      Thanks,
      Ben

  • sibel

    Hi Ben,
    When I saw this post, I checked my ver­sion. Opppss it is H17. I felt like very old :)
    If I upgrade my code in JS file to this one, I sup­pose I will not need any change in my tags that I already col­lect. Do I sup­pose correct?

    Thanks

    • http://blogs.omniture.com/author/bgaines Ben Gaines

      Sibel,

      Cor­rect. You can swap out the s_code.js file to go from H.17 to H.21.1 with­out chang­ing your indi­vid­ual page tags.

      Thanks,
      Ben

  • Ste­fanie

    Hello
    Is upgrad­ing tags a sim­ple job of copy and paste or does it require more thought?
    Regards
    Stefanie

    • http://blogs.omniture.com/author/bgaines Ben Gaines

      Hi Ste­fanie,

      In most cases, you can upgrade to the lat­est ver­sion of code by copy­ing and past­ing any cus­tomiza­tions you’ve made in your s_code.js file into a newer ver­sion, then sav­ing and pub­lish­ing. (There are excep­tions to this rule, which I may cover in a future blog post.)

      We strongly rec­om­mend test­ing all JavaScript code upgrades prior to pub­lish­ing in a live envi­ron­ment, to ensure com­pat­i­bil­ity. We also typ­i­cally rec­om­mend not upgrad­ing unless there are features/fixes that are rel­e­vant to your busi­ness in the newer version.

      Thanks,
      Ben