Code version H.20.3 released

Analytics · By On · 8 Comments

Some of you may have noticed in the Code Man­ager within the Admin Con­sole that H.20.3 code is now avail­able. A num­ber of users have asked me about it on Twit­ter, so I’m mak­ing it a goal to briefly dis­cuss each code release as soon as it becomes avail­able right here. Over time, hope­fully this blog will become a great resource to help you deter­mine when it’s time to upgrade your implementation.

If you read my post on the Google refer­rer change, you may have noticed that the patch dis­cussed 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 prob­a­bly don’t need to upgrade to H.20.3, as the inclu­sion of the patch natively is the only dif­fer­ence between H.20.2 and H.20.3 code.

NOTE: The deploy­ment of an upgrade code base should never be done in haste. Always test code upgrades exten­sively in a devel­op­ment envi­ron­ment before deploy­ing on your pro­duc­tion site(s).

  • http://etrade.com.au Sam Potts

    Ben,

    Does this offer much over a H17 code implementation?

    Cheers
    Sam

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

      Sam: I don’t want to get into the specifics of com­par­ing past ver­sions of code with H.20.3 here, so I’ll say that the main dif­fer­ence between H.17 and H.20 is speed improve­ments and some addi­tional media track­ing func­tion­al­ity (e.g., s.Media.trackWhilePlaying).

  • Andy

    Hi Ben,

    Cur­rently I have H17 code imple­mented in my web­site. Is it nec­es­sary to upgrade to the lat­est H.20.3 ver­sion? Do I need to change my track­ing code in the website?

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

      Andy: I don’t pre­sume to under­stand the com­plex­i­ties and unique­ness of your Site­Cat­a­lyst imple­men­ta­tion, nor of your busi­ness needs and how they’re man­aged by your Site­Cat­a­lyst imple­men­ta­tion, so I can’t say with any degree of cer­tainty whether you should upgrade. It cer­tainly is not nec­es­sary; the main advan­tages of the newer code ver­sion are the Google refer­rer update dis­cussed in this post, speed improve­ments, and updated video mea­sure­ment func­tion­al­ity. You may want to con­sult with your Omni­ture Account Man­ager to help deter­mine whether now is a good time to upgrade, or whether wait­ing for a sub­se­quent code release is a bet­ter idea for your par­tic­u­lar needs.

  • Lnd­dMiles

    Pretty cool post. I just stum­bled upon your blog and wanted to say
    that I have really liked read­ing your blog posts. Any­way
    I’ll be sub­scrib­ing to your blog and I hope you post again soon!

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

      Lnd­dMiles: Thanks! I appre­ci­ate it. I’ll be post­ing as often as I can.

  • http://www.hotwire.com Jeff Reichen­berg

    You men­tioned speed improve­ments. Can you expand on that a lit­tle bit? We are using H.16 which seems to tax some browsers, espe­cially IE <= 7, dur­ing ini­tial load. Are the speed improve­ments of this release (or later ones) in ini­tial parse time or in actual func­tion exe­cu­tion after t() or tl() are called? We’d love to see major improve­ments in ini­tial parse time.

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

      Jeff,

      I checked in with Bret Gun­der­sen, Senior Prod­uct Man­ager on this. He reported that “Ini­tial parse time was reduced sig­nif­i­cantly by tak­ing advan­tage of faster native JavaScript func­tions and alter­ing the for­mat slightly. The calls to s.t() and s.tl() had major improve­ments as well, which pre­vents any vis­i­ble delays in page, RIA or video ren­der­ing when those func­tions are called.”

      I hope this helps!

      Thanks,
      Ben