'Searches' report is empty
It's possible that Analytics Reports for your collection have not yet been created. You can manually force an update of reports from the Administration Interface (Analyse > Update Analytics Now).
Not all collections are suitable for querying directly by end users, and their contents may be queried as part of a meta collection instead. It's possible that the component collection has never been queried directly.
'Searches' reports show test queries or complex syntax
During testing, debugging or monitoring, complex queries may be sent to your search index, logged, and appear in reports. Examples may look like the following:
!nullquery !showallresults polling query test +v:coriolanus f:key a:"william shakespeare" fun*
While these queries may be syntactically correct and valid, they may be adding unnecessary noise to your reports and prevent you from identifying real users' search behaviour.
Consider adding known test or polling queries to your
reporting-blacklist.cfg file. If a polling or monitoring service has been configured, it's IP address should also be added to
Consider separating system-generated queries and constraints from user-generated queries at query time with the use of the
squery syntax. System-generated queries and constraints are not displayed in search analytics reports.
'Searches' reports are visible, but 'Clicks' reports are empty
Depending on the integration method used to deploy search results, it's possible that click tracking is enabled, and displaying in the Funnelback data model, but not configured on the template used to display results.
Confirm that click tracking is enabled for your collection.
Confirm that your template is displaying the
clickTrackingUrl element for each result's
<a href> value. Note that this value will be distinct from
If click tracking cannot be enabled for a given template, consider using a supplementary source (e.g. third party web analytics tools) for extracting a view of data useful for converting to pseudo-click logs during collection update workflows.
'Locations' report shows only one location (or only a handful of locations)
This behaviour typically occurs when a CMS or proxy server is making requests of Funnelback on a remote user's behalf, and only the CMS or proxy server's IP address is recorded at query time.
Ensure your CMS or proxy server's requests to Funnelback are appending the remote user's IP address as part of the
X-Forwarded-For headers. Aditionally, ensure Funnelback is configured to ignore / log the appropriate IP address ranges from the list of forwarded IP addresses.