title: Outbound link tracking - Google Analytics' _trackEvent() and Omniture's s.tl()
body: <p>We have a site that uses both Omniture and Google Analytics. Ideally, we want to report in both suites on clicks to outbound links. </p>
  
  <p>I'd like to do this the "right way," i.e. overcoming the race condition that occurs when requesting a site and the tracking pixel at the same time. See: <a href="http://www.gwotricks.com/test/2009/07/tracking-outbound-links-right-way.html" rel="nofollow noreferrer">http://www.gwotricks.com/test/2009/07/tracking-outbound-links-right-way.html</a></p>
  
  <p>I probably wouldn't use the "onclick" attribute, instead binding the trackEvent to the link's click event.</p>
  
  <p>Omniture's external link tracking overcomes the condition by hooking a 500ms delay into <code>s.tl()</code>:</p>
  
  <p>www. webmetric.org/white_paper/link_tracking.pdf</p>
  
  <p>Has anyone tried doing both on the same site? Ideally I'd like to call both tracking pixels with an appropriate amount of time before the page executes, but I'm not a big enough Omniture buff to really have gone in-depth with their code and hook trackEvent in before the delay.</p>