omniture fake page load tracking for scrolling / achored content

Question

Looking through my business requirements, the web analytics team wants to make s.T() 'page load' calls when a user navigates to different sections on the same long ass page. This is also supposed to happen when they scroll to or through this content. I feel like this should perhaps be completed with a link tracking call, is that correct? Is there a recommended approach for handling this scenario? Are there any well document drawbacks to faking pageload omniture calls?

Answer 1

There's absolutely no issues calling s.t() multiple times, as long as you want each of those calls treated as a page view.

Really the only differences between s.t() and s.tl() are as such:

• s.t() calls increment page views while s.tl() calls do not
• s.t() calls collect pageName and pageURL while s.tl() calls do not
• s.t() calls send all defined variables while s.tl() calls only send variables defined in s.linkTrackVars

Based on your business requirements, if you want additional page views to be incremented as they scroll through it, by all means use s.t(). If you want page views to only increment on actual page loads, consider using s.tl() calls.