Funnelback logo

Documentation

Related Information (Classic UI)

Introduction

Funnelback's "related information" mechanism supports the presentation of additional information relating to a specific query and result URLs. The information available includes:

Related queries
Information about how queries are related to other queries.
Result related queries
Information about which queries were used when clicking on a given result URL.
Related locations
Information about the locations from which certain queries were received.

Presentation

Related information can be presented in search forms using the following form tags.

API Access

All related information can also be accessed via related.cgi in JSON format for display of this information in external systems.

Configuration

The following configuration files control the related information system:

related.cfg
Manual specification / override of related queries.
reporting-blacklist.cfg
Query terms to be ignored by the reporting system.
reporting-stop-words.cfg
Terms to be eliminated from publicly visible reports.
related.api_enabled in Collection.cfg
Enables/disables API access to related information via related.cgi
analytics.data_miner.range_in_days in Collection.cfg
Specify a time range for query and click logs to mine data for related information.

NB: You will need to update the Query reports for any configuration changes to take effect.

Generation

The different types of related information are generated as follows:

Related queries

The most popular query for a result URL is considered the root query. A list of other queries used for that result URL (sorted by popularity) is then associated with that query.

For example, if the most popular query used when clicking on the URL www.example.com/careers/ is "careers" and other queries used are "jobs", "graduates", and "employment" then those queries will be associated e.g.

careers=jobs,graduates,employment

NB: The relation is currently only stored for the root query i.e. the reverse mapping is not stored. You could use the related.cfg file to enforce the reverse mapping if required.

Result related queries

Here we store a list of the most popular queries associated with a specific result URL. This can be seen as a set of query "tags" associated with that URL.

For example, if the queries "home loan", "mortgage rates" and "fees" were used when clicking on the URL www.example.com/loans/ then we would store the mapping:

http://www.example.com/loans/=home loan,mortgage rates,fees

If the ResultRelatedQueries plugin was being used in the search form then that list of queries could be displayed as "tags" for that URL when it appears in a result list.

Related locations

We use the MaxMind GeoLiteCity Database to look up query request IP addresses and store a list of city locations associated with that query, sorted by request frequency.

So for a specific query we might store the mapping:

mining=perth,brisbane,melbourne,canberra

and this information would be displayed in the standard query reports.

top ⇑