Working with Omniture?
Data not going through? Try adding a call to s.tl() to flush things out and make sure they’re sent to Omniture. It seems to not want to send certain custom events by default.
I'm Reading…
- Paul Irish and I enjoy a good web geek debate.
- Tom Kershaw is a diamond geezer.
Search This Site
Archives
- August 2010
- February 2010
- May 2009
- March 2009
- February 2009
- January 2009
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
Categories
- adobe air (2)
- browser bugs (3)
- code (49)
- cross browser (17)
- css (37)
- design (28)
- development (14)
- dhtml (30)
- interaction design (3)
- javascript (58)
- learn (34)
- personal (3)
- projects (4)
- ruby on rails (10)
- usability (11)
- user experience (5)
- ux week (17)
- yak (9)
- yui (6)
May 13th, 2009 at 9:46 am
I’ve noticed that with s.tl(), you’ll need to open it up with trackLinkVars before setting custom props:
// reset the s variable
var s=s_gi(s_account);
// for the tl() calls you need to specify what vars you want to pass it.
s.linkTrackVars=”prop18,eVar17,events”;
s.linkTrackEvents=”event13″;
s.prop18 = ‘foo’;
s.eVar17 = ‘bar’;
May 13th, 2009 at 1:45 pm
Yep. I’m queuing up props/events/eVars separately first, then calling transmitting them with s.tl() when I’m done constructing them.
May 14th, 2009 at 5:25 pm
Also: set events and props to null if you want to clear them out and prevent them from being reported.