Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Add support for Google instant


Level 2


It would be great if Omniture could collect the oq= parameter from the referer string passed over from Google.  oq= shows what the user typed into the box, as opposed to q= which shows the search query Google returned results for.


ideally, I'd love to look at a keyword report, click on one specific keyword, and then see all of the oq= variations that are associated with that keyword.


Also, it might be useful to just show all the oq= variations in their own report.



Level 2


The goal here is to use the data to learn how users refine their search terms.  One could then use that information to help guide their on-site content and SEO strategies.




This is a good suggestion. While we look at the best way to report on Google Instant, you can start by doing something like this:


if(document.referrer.indexOf('') > -1 && document.referrer.indexOf('oq=') > -1) {




This will grab the value of oq= out of the referrer and put it into s.propX (whichever Custom Traffic variable you want). Then you can correlate that variable with Search Keywords to see how users refined their search terms while using Google Instant.


Level 4


Hi Benjamin,

I test your advice, I insert into JS s_code.js your code, but the s.propX is empty, there's no data.

This happens because the query string parameter "oq" is not present in the referrer, it's only present when you are typing on your keyword, but when you click on a search result, the referrer does not contain the "oq" parameter (it contains only "q", the keyword suggested by google).







That's correct. The snippet of code I provided only executes if oq= is present. . . I believe Google has stated that it won't always be there, and may not even be related to Instant Search. Others believe that it is related to Google Instant. The point of my code snippet is that you can always capture query string parameters that are present in the referrer if you want to do so prior to official support for something like the oq= parameter.



Ben Gaines
Product Manager
Adobe Systems, Inc.