Support Menu

Coveo component ResultsFiltersPreferences

Coveo ResultsFiltersPreferences Component (CoveoResultsFiltersPreferences)

The ResultFiltersPreferences component allows end users to create custom filters to apply to queries. These filters are saved to local storage.

Only advanced end users who understand the Coveo query syntax should use this feature (see Coveo Query Syntax Reference).

This component is normally accessible through the Settings menu. Its usual location in the DOM is inside the PreferencesPanel element.

See also the ResultsPreferences component.


Component Options


filters: any

Specifies the default filters which all end users can apply.

End users cannot modify or delete these filters. These filters do not count as "user-made" filters, but rather as "built-in" filters created by the developer of the search page.


You cannot set this option directly in the component markup as an HTML attribute. You must either set it in the init call of your search interface (see Components - Passing Component Options in the init Call), or before the init call, using the options top-level function (see Components - Passing Component Options Before the init Call).

Filters should follow this definition:

filters : { [caption : string] : { expression : string, tab? : string[] } };


var myFilters = { "Only Google Drive Items" : { expression : "@connectortype == 'GoogleDriveCrawler'", tab : ["Tab1", "Tab2"] },

"Another Filter" : { expression : [ ... another expression ... ] },

[ ... ] };

// You can set the option in the 'init' call:
Coveo.init(document.querySelector("#search"), {
  ResultsFiltersPreferences : {
    filters : myFilters

// Or before the 'init' call, using the 'options' top-level function:
// Coveo.options(document.querySelector("#search"), {
//   ResultsFiltersPreferences : {
       filters : myFilters
// });

Default value is undefined.


includeInBreadcrumb: boolean

Specifies whether to display the active filter(s) in the Breadcrumb.

Default value is true.

Markup configuration example(s) :


showAdvancedFilters: boolean

Specifies whether to show the Create button that allows the end user to create filters.

If you set this option to false, only the pre-populated filters are available to the end user.

Default value is true.

Markup configuration example(s) :



  • debugInfo(): any


  • disable(): void
  • Disable the component. Normally this means that the component will not execute handlers for the framework events (query events, for example). Component are enabled by default on creation.

    Returns void


  • enable(): void
  • Enable the component. Normally this means that the component will execute handlers for the framework events (query events, for example). Components are enabled by default on creation.

    Returns void


Static get

  • get(element: HTMLElement, componentClass?: any, noThrow?: boolean): BaseComponent
  • Get the bound component to the given HTMLElement. Throws an assert if the HTMLElement has no component bound, unless using the noThrow argument.
    If there is multiple component bound to the current HTMLElement, you must specify the component class.


    • element: HTMLElement

      HTMLElement for which to get the bound component.

    • Optional componentClass: any

      Optional component class. If the HTMLElement has multiple components bound, you must specify which one you are targeting.

    • Optional noThrow: boolean

      Boolean option to tell the method to not throw on error.

    Returns BaseComponent



Allows the component to bind events and execute them only when it is enabled.




componentOptionsModel: ComponentOptionsModel

Contains the state of options for differents component. Mainly used by ResultLink.


componentStateModel: ComponentStateModel

Contains the state of different component (enabled vs disabled). Allows to get/set values. Trigger component state event when modified. Each component can listen to those events.


disabled: boolean

A disabled component will not participate in the query, or listen to ComponentEvents.




logger: Logger

Allows component to log in the dev console.


queryController: QueryController

Contains the singleton that allows to trigger queries.


queryStateModel: QueryStateModel

Contains the state of the query. Allows to get/set values. Trigger query state event when modified. Each component can listen to those events.


root: HTMLElement

A reference to the root HTMLElement (the SearchInterface).


searchInterface: SearchInterface

A reference to the root of every component, the SearchInterface.


usageAnalytics: IAnalyticsClient

A reference to the Analytics.client.

Static ID

ID: string

The static ID that each component need to be identified.
For example, SearchButton -> static ID : SearchButton -> className : CoveoSearchButton