Categories

Authors

Pages

Recent posts

Recent comments

Archives

Code version H.20.3 released

Tuesday, 26 May 2009 @ 13:49, by Ben Gaines

Some of you may have noticed in the Code Manager within the Admin Console that H.20.3 code is now available. A number of users have asked me about it on Twitter, so I’m making it a goal to briefly discuss each code release as soon as it becomes available right here. Over time, hopefully this blog will become a great resource to help you determine when it’s time to upgrade your implementation.

If you read my post on the Google referrer change, you may have noticed that the patch discussed there is included in the H.20.3 release—no need to add it to H.20.3 code. If you’ve already added the patch to your H.20.2 (or older) code, then you probably don’t need to upgrade to H.20.3, as the inclusion of the patch natively is the only difference between H.20.2 and H.20.3 code.

NOTE: The deployment of an upgrade code base should never be done in haste. Always test code upgrades extensively in a development environment before deploying on your production site(s).

  • on  
  • Bookmark at  

respond to post

responses

  1. Sam Potts2009/5/26 @ 8:38 pm

    Ben,

    Does this offer much over a H17 code implementation?

    Cheers
    Sam
  2. Ben Gaines2009/5/27 @ 9:49 am

    Sam: I don’t want to get into the specifics of comparing past versions of code with H.20.3 here, so I’ll say that the main difference between H.17 and H.20 is speed improvements and some additional media tracking functionality (e.g., s.Media.trackWhilePlaying).
  3. Andy2009/6/18 @ 4:34 am

    Hi Ben,

    Currently I have H17 code implemented in my website. Is it necessary to upgrade to the latest H.20.3 version? Do I need to change my tracking code in the website?
  4. Ben Gaines2009/6/18 @ 11:08 am

    Andy: I don’t presume to understand the complexities and uniqueness of your SiteCatalyst implementation, nor of your business needs and how they’re managed by your SiteCatalyst implementation, so I can’t say with any degree of certainty whether you should upgrade. It certainly is not necessary; the main advantages of the newer code version are the Google referrer update discussed in this post, speed improvements, and updated video measurement functionality. You may want to consult with your Omniture Account Manager to help determine whether now is a good time to upgrade, or whether waiting for a subsequent code release is a better idea for your particular needs.
  5. LnddMiles2009/7/21 @ 10:51 am

    Pretty cool post. I just stumbled upon your blog and wanted to say
    that I have really liked reading your blog posts. Anyway
    I’ll be subscribing to your blog and I hope you post again soon!
  6. Ben Gaines2009/7/22 @ 2:37 pm

    LnddMiles: Thanks! I appreciate it. I’ll be posting as often as I can.
  7. Jeff Reichenberg2010/4/28 @ 4:01 pm

    You mentioned speed improvements. Can you expand on that a little bit? We are using H.16 which seems to tax some browsers, especially IE <= 7, during initial load. Are the speed improvements of this release (or later ones) in initial parse time or in actual function execution after t() or tl() are called? We’d love to see major improvements in initial parse time.
  8. Ben Gaines2010/4/28 @ 11:51 pm

    Jeff,

    I checked in with Bret Gundersen, Senior Product Manager on this. He reported that “Initial parse time was reduced significantly by taking advantage of faster native JavaScript functions and altering the format slightly. The calls to s.t() and s.tl() had major improvements as well, which prevents any visible delays in page, RIA or video rendering when those functions are called.”

    I hope this helps!

    Thanks,
    Ben