Note: After you choose which s.prop you are going to use to store/capture the data in, you will need to contact Omniture Client Care to get pathing enabled for that s.prop

Where does your path take you?

In a previous post, I went over how we capture the search terms from the Google Mini. So when I returned from the training, I contacted client care and had then enable pathing on the s.prop and "Shazam!". We now have pathing on the internal search terms.

This has been working great, and I've been really pleased with being able to see exactly how visitors refine their searches. Recently, I had the opportunity to chat with Susan Fariss, at the American Chemical Society (@soozantf) about search analytics and the questions came up on do we know where the user was on the site when they initiated the search and then what search result did they click on.. if any? Well... I did not have those answers, but I sure wanted to.

So the question was could the following be accomplished:

• Detect/capture where visitor was on the web site when the search was initiated
• Modify the google mini xslt to tag all of the search results so that the result clicked could be captured
• Would this provide the full search pathing expected

Detect/capture where visitor was on the web site when the search was initiated:
This was the easy part of the adventure for sure. I already had a JavaScript function handling the initial search, so I added another function call in that

			function recordInternalSearchOmniture(){
				var s = s_gi(s_account);
				s.linkTrackVars="prop1";
				s.prop1 = s.pageName;
				s.tl(document.location.href,'o','InternalSearch');
				s.linkTrackVars="";
			}

This code snippet simply pulls the s.pageName and puts it into the same s.prop used to store the actual search terms, creating the "entry point" of our search path.

Modify the google mini xslt to tag all of the search results so that the result clicked could be captured:
This proved to be the pesky part of the adventure. The challenge was to be able to add the jQuery function to tag the search results someplace where the Google xslt could access it. After a few missteps I added the jQuery to a main .js file (not the s_code.js) that I was able to link to inside the xslt. But first I needed to add a div with a specific Id to the xslt so that I would be able to tag the results with the tracking codes. So inside the xslt I did the following.

<!-- **********************************************************************
 Search results (do not customize)
     ********************************************************************** -->
.
.
.
<div id="googleSearch">
<!-- *** Customer's own result page header *** -->
.
.
<!-- *** HTML footer *** -->
</div>

So find the section that says "Search results (do not customize)" - I viewed this as more of a suggestion than a hard rule. Inside this section, wrap the header/footer items with a new div with the id of "googleSearch" (or some other id of your choosing). This is needed so that the jQuery function can find the elements that need the new tags. Once that div is in place add a jQuery function to find all results in that div and tag them. The first function below binds a function call to the a href tags in the search results. The second function does pulls in the location of the search results and records where the user clicked. This provides the "exit point" to our path.

$(document).ready(function(){
$('#googleSearch a').each(function(i) {
  var hrefval = $(this).attr('href');
  $(this).bind('click',function (event){
  	omniGoogleSearchResultClicked('Search Result Clicked',hrefval)
  	});
});
.
.
function omniGoogleSearchResultClicked(propTitle,hrefVal){
	var s = s_gi(s_account);
	s.linkTrackVars="prop1";
	s.prop1 = hrefVal;
	s.tl(document.location.href,'o',propTitle);
	s.linkTrackVars="";
}

Would this provide the full search pathing expected:
Yes! This does indeed provide a full search path.

I knew IE6 was evil!

Ok..  so maybe I changed the actual values, but this is the type of search pathing you can achieve with tracking the entry and exit points in the same s.prop as the search terms and having pathing enabled on that s.prop.

-Rudi

Share/Save

Here are the steps I took to integrate/capture the search terms into Site Catalyst.

Step 1.  Locate and backup your searchtemplate.xslt file.

Step 2.  In the section of the code that has the sections labeled "(can be customized)" add this code block.

<!-- **********************************************************************
 Omniture SiteCatalyst code (can be customized)
 ********************************************************************** -->

<xsl:template name="sitecatalyst">
 <xsl:param name="query"/>
 <xsl:param name="matches"/>
 <xsl:comment>
 SiteCatalyst : Google Mini Search Integration
 </xsl:comment>
 <script language="JavaScript" type="text/javascript" src="INSERT-DOMAIN-AND-PATH-TO-CODE/s_code.js"></script>
 <script language="JavaScript" type="text/javascript">
 <xsl:comment>
 s.eVar1="<xsl:value-of select='$query'/>"
 var s_code=s.t();if(s_code)document.write(s_code)
 </xsl:comment>
 </script>
 <script language="JavaScript" type="text/javascript">
 <xsl:comment>
 if(navigator.appVersion.indexOf('MSIE')>=0)
 document.write("unescape('%3C')+'!-'+'-'")
 </xsl:comment>
 </script>
 <xsl:comment>
 End SiteCatalyst : Google Mini Search Integration
 </xsl:comment>
</xsl:template>

NOTES:
1. Replace the"INSERT-DOMAIN-AND-PATH-TO-CODE" with the location where you uploadedthe s_code.js file:
2. Be sure to use an absolute path.  http://www.rudishumpert.com/subfolder/s_code.js
3. Code above assumes you are using s.prop1.  Change value as needed.

Step 3.  Next, locate the XSL template named, search_results.

<!-- **********************************************************************
Search results (do not customize)
 ********************************************************************** -->
<xsl:template name="search_results">
...
...
<body onLoad="resetForms()" dir="ltr">

and place the following code  opening <body> tag:

 <!-- *** Add Omniture SiteCatalyst code *** -->
 <xsl:choose>
 <xsl:when test="RES">
 <xsl:call-template name="sitecatalyst">
 <xsl:with-param name="query" select="Q"/>
 </xsl:call-template>
 </xsl:when>
 <xsl:otherwise>
 <xsl:call-template name="sitecatalyst">
 <xsl:with-param name="query" select="Q"/>
 </xsl:call-template>
 </xsl:otherwise>
 </xsl:choose>

Step 4.  Deploy code to test/production making sure to backup a copy of your existing XSLT template (just in case).

You should now be able to see the search terms being passed to Omniture using your debugging tool of choice.

-Rudi

EDIT:  changed the Omniture variable used from prop1 to evar1 so we could add sub relations to the element.

Share/Save