That looks good.

Thanks for the question,

Justin

Have a client with a site that does not pass the search term as a url parameter. It is an online classifieds site with subdomains for each city and every page has a search box.

We want to implement site search and also ensure that sub-domain tracking is unaffected.

Is this how the customized GATC would look?

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”);
document.write(unescape(“%3Cscript src=’” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”));

/script>

var pageTracker = _gat._getTracker(“UA-xxxxxxx-x”);
pageTracker._setDomainName(“.domain.com”);
pageTracker._initData();
pageTracker._trackPageview(‘/search?q=’);

Any help would be much appreciated.

Thanks,
Raina

Sorry, but without digging into your site and looking at the stricture I’m at a dead end. The most common problem is that the search term is not in the search results page (ie the search form is using a post to pass the search term to the server).

My lsat guess is that you’re passing a value to _trackPageview() that’s overwriting the q parameter in the URL.

Hope that helps,

Justin

Sorry if my post was not clear. Based on your URL you want to enter q into the ‘Query Parameter’ field in the site search settings. You can find Site Search settings in the Profile settings. You’ll need to enable site search first. Then you should see the ‘Query Parameter’ field.

Hope that helps,

Justin

I haven’t seen anything in GA when I use “q” as the parameter so what am I missing? My IT guy has way to much on his plate to give this any attention so any help would be greatly appreciated.

Is the site search located on a different sub domain that is included in the sub domain profile? I’m wondering if you’re excluding the search data by accident with the sub domain include filter.

Let me know if that helps,

Justin