I love the Google Analytics module and it's features, but for some reason I cant get my installation to pull search info!

I have my query parameter set to "productsearch/results/", as that is what precedes all of my search results (i'm using Faceted Search, is this possibly the problem?). I have also tried just using "search", and have no luck that way either. I've reviewed the documentation and have scanned the forums and can't find a whole lot of help.

Any advice or tips are appreciated!

Drupal Version 6.10
GA Version 6.x-2.2

Comments

hass’s picture

hass commented
Status: Active » Postponed (maintainer needs more info)

I'm not sure what "Faceted Search" does, but it should be the source of this issue. Try it with core internal search - it works well, but you need to configure "search" as the search query string in your GA account.

If you have a webpage showing the issue I can take a short look.

xdecibelx’s picture

xdecibelx commented

http://gtwantennas.com

I've read that faceted search can be used with GA, as it uses Drupal's core search module to function. But since it changes the path that lies before the search query in the address bar, I figured that was where the problem came from. Thanks for your time!

hass’s picture

hass commented
Project: Google Analytics » Faceted Search
Version: 6.x-2.2 » 6.x-1.x-dev
Component: User Interface » General
Category: support » task
Status: Postponed (maintainer needs more info) » Active

I'd like to move this to the project faceted search. This project should follow the core directory rules and then all should work as expected. I cannot add exceptions for every small search module that does not follow the core path's. If it would use search/product/* it would be much easier.

david lesieur’s picture

david lesieur commented
Title: Site Search/Query Parameter Issues » Faceted Search + Google Analytics integration

Faceted Search's base path is defined by site admins and could be set to "search/products", for example. I haven't tested whether such path would cause conflicts with core search, but it should not.

earthday47’s picture

earthday47
Location New York
commented

(ressurecting)
I just tried some parameters with Google Analytics, I'll know tomorrow if it worked.

I'm using Multisite Search which generates a search path like "search/multisite_search/". drupal.org's default search is "search/apachesolr_multisitesearch/". It'd be nice to track these local options.

Under Google's "Query Parameter" setting, I put in "search,search/multisite_search", we'll see if that works.

When Drupal translates paths, it uses the q var, like index.php?q=search/multisite_search/about .

hass’s picture

hass commented
Category: task » support
Status: Active » Fixed

Query param is search nothing else. If path starts with "search" - perfect. This must work with GA.

earthday47’s picture

earthday47
Location New York
commented

I just confirmed that my installation of Google Analytics correctly captured both search terms.
In summary:

www.example.com/search/
www.example.com/search/products/

GA's "Query Parameter" should be set to the following:
search,search/products

hass’s picture

hass commented

I have no clue why you configure "search/products" - this is wrong! Configure "search" only!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.