Omniture is case sensitive. So when you are passing values to an s.prop it records “Word” and “word” as two different values.
User input can be a mix of capitalisation. So when passing user input to an s.prop. Ensure to use the .toLowerCase();. option on the s.prop. Consider this option for areas such as internal site search keywords.
Syntax is :-
s.prop1=s.prop1.toLowerCase();.
Without planning the use of s.props it’s easy to find your self at the 50 s.prop limit. Complex sites require complex Sitecatalyst tracking. So to avoid using too many s.props consider the following example.
A story ID or page ID generated by a CMS, there’s typically quite a bit of associated data with story or a page. The quick and easy way to get this into Sitecatalyst is to pass the associated data into additional s.prop values on the page and correlate with the story ID or page ID. However consider the option of dumping the story id out to a SAINT file and assigning associated data such as author, published date, story title etc to the file. Using the SAINT import functionality this data will then be associated with the story ID And viewable in Omniture. The good news storing data on story ID, author, publish date, story title using classifications will only use 1 s.prop (story ID).
Recent Comments