Multiple Search Criteria
When sites have multiple search criteria, you can put each item into a separate s.prop to understand which values are selected the most in each case. For example:

  • s.prop1 = “Search Term”;
  • s.prop2 = “Number of search Results”;
  • s.prop3 = “Scope of Search” (searched entire site or just a portion).
As you will see later in the chapter, you will then be able to relate these reports to each other and see how they break down by each other (i.e. “When the scope of the search is just section A of my site, what were the search terms?). Player Type Example:
Another example might be something like which media player people are using or which flash version they have. Again, you are not counting the pages that a RealPlayer user views, but rather just how many people have RealPlayer or Windows Media Player.
  • s.prop4 = “RealPlayer”;
  • s.prop4 = “Window Media Player”;
These values can just be populated ONCE whne something happens, like when the player in initiated. This would the result in a report that shows which player was used the most.

PURPOSE 2: MEASURING FOR A SPECIFIC SEGMENT
The other purpose of setting an s.prop is to see how much traffic comes from a segment. This entails placing a values on EVERY page that belongs to a segment. Some segment examples includes:
  • Page grouping (section, subsection).
  • Logged in traffic.
  • Register users.
  • Language pages.
Language Page Example
If your site attracts people who speck different languages, you may have several versions of pages that have translated for their convenience. You may then want to know which languages pages have the most traffic. In the following example, a visitor might start at a “choose your language” page and then go to different English and French pages ( which may actually be unlikely in one visit, but illustrates the point well).

Start Visit ->
Page 1: s.prop1 = “ ”; Page 2: s.prop1 = “EN”; Page 3: s.prop1 = “FR”;
Page 4: s.prop4 = ”FR”; Page 5: s.prop1 = “EN”; Page 5: s.prop6 = “EN”;
End Visit.

The property variable is set on every page that belongs to a segment, and the resultant report from the above visit would look something like this:
Page Language Report Page Views Search %
1 EN 3 60%
2 FR 2 40%
Additional Level of Page Grouping
As discussed previously, the channel variable is used to show traffic to major section of the site, and the channel values show up on the Most Popular Site Section report. But what if you have multiple levels of groupings, such as subsection and sub-subsections? This is perfect use of .props. If you use one s.prop for each level of page groupings, you will be able to see how much traffic goes to the different sections and subsections. This is similar to the hierarchies function, but with some key differences:
  • With hierarchies, you drill down through the structure to lower levels.
  • With s.props, you could see ALL of the the lower level grouping across the entire site.
  • With hierarchies, you get de-duplicated uniques to sub-levels.
  • With s.props, if you want to break them down by each other (discussed later in this chapter), you will be see only the page views metrics.