We haver query logging enabled but although its logging query words and terms its not logging best bet clicks. We know the best bets are being used (as we ourselves are using them). Do we need to change something in the search script?
thanks.
Niamh
p.s. our nightly walk type is refresh
It would appear that there's the possibility of some clickovers of any type to not get logged. It all depends on how quickly the browser follows the redirect compared to how quickly the clickover is logged.
There's a fix for the search script in the pipeline for release. You can fix your search script by adding
<vxcp connreset 39>
after the <init> line in the "redir" function so you end up with:
<a name=redir public>
<init>
<vxcp connreset 39>
<doredir u=$u>
Hi,
We've added the above to the script and now the query log for best bet clicks is 1 which could not be correct as we have done multiple best bet clicks ourselves.
any other ideas?
Double check that query logging is on.
That the url you're clicking on has "redir" before the actual page's url.
That you've clicked on best bets since the last "new" walk which will clear the log.
Check your vortex.log to make sure you're not getting any errors when clicking best bets.
query logging is on. there is a redir before the page's url. best bets have been clicked (and the walk is refresh). vortex logs show no errors for best bet (at least no errors that can be identified).
To eliminate the possiblity of disconnect issues try moving
<doredir u=$u>
to between
</if>
and
</a>
so that the logging occurs before the user is redirected.
I am having the same problem. I have best bets set, query logging is on, but whenever I click on a best bets link nothing is written into the query log or the Best Bets Click report.
I have made the changes as specifed above into the search script, reran the profile walk and still nothing.
So, you have query logging on and the queries are getting logged? Are regular clickovers getting logged? Do the best bet urls have "redir.html" in them?
Maybe try the latest scripts from the Webinator support page.
Rerunning the walk will have no affect on query logging issues except to clear the query log if it's a new walk.