--- title: Inspect your query pipeline and rules slug: mc2g0358 canonical_url: https://docs.coveo.com/en/mc2g0358/ collection: project-guide source_format: adoc --- # Inspect your query pipeline and rules A [query pipeline](https://docs.coveo.com/en/180/) is a set of [rules](https://docs.coveo.com/en/236/) that modifies user [queries](https://docs.coveo.com/en/231/) before they reach the [index](https://docs.coveo.com/en/204/). You can manage query pipelines on the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). If you have multiple [search interfaces](https://docs.coveo.com/en/2741/) to serve distinct users and purposes, your [Coveo organization](https://docs.coveo.com/en/185/) may contain several query pipelines. > **Leading practice** > > Have a separate query pipeline for every search interface. This article provides testing guidelines for the most common query pipeline components in a Coveo-powered search implementation. > **Important** > > This guide provides guidelines to analyze, review, and test different aspects of a Coveo-powered implementation. > > It shouldn't be considered an official, definitive guide to testing an implementation before it goes live, but rather a guide showcasing the basic components that Coveo implementations typically include. > > Every Coveo implementation is different and may require custom configuration. > > Therefore, you may notice discrepancies between the components and features listed in this guide and those you're using in your actual implementation. > > If you encounter issues, or have any questions related to this article, contact [Coveo Support](https://connect.coveo.com/s/case/Case/Default) for help. ## Access your browser's network monitoring tool . Open your web browser's developer tools. > **Note** > > The examples in this article use the **Google Chrome** developer tools. > For browser-specific information, see: > > * [Google Chrome](https://developers.google.com/web/tools/chrome-devtools/open) > > * [Mozilla Firefox](https://developer.mozilla.org/en-US/docs/Tools) > > * [Safari](https://support.apple.com/en-ca/guide/safari/sfri20948/mac) . Select the **Network** tab. ## Query routing You should ensure that queries [are directed to the right query pipeline](https://docs.coveo.com/en/1666/) for every search interface. . Access the search interface in which you want to test query routing. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search box, perform a query. . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Find the `pipeline` property. Its value should correspond to the name of the query pipeline to which queries originating from this search interface must be routed. ![Query routing in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/query-pipeline-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the pipeline is displayed under **Query pipeline selection** (the second step in the **Query journey**). Click **See details** for more information about the pipeline through which the query was routed. ![Query routing in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/query-pipeline-in-relevance-inspector.png) ## Thesaurus Query pipeline [thesaurus](https://docs.coveo.com/en/2742/) rules let you define lists of synonyms to help users find relevant results when they search for specific terms. If a query pipeline contains [thesaurus rules](https://docs.coveo.com/en/3405/), review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review thesaurus rules configuration . On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review thesaurus rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Search terms** tab, and then click **Thesaurus**. . Validate the thesaurus rules' configuration and associated conditions. ### Test thesaurus rules in a search interface . Access the search interface in which you want to test a thesaurus rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search box, perform a query that would trigger a thesaurus rule. . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Find and expand the `executionReport` property, and then expand the `children` sub-property. . Expand the `PreprocessQueryExpression` property, and then expand the `children` sub-property. . Check for a `ApplyThesaurusFeature` value. If you see a value for the `applied` sub-property, this means that a thesaurus rule was applied and modified the query. . Expand the `applied` sub-property to see the definition of the rule that was applied. ![Thesaurus rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/thesaurus-rule-in-developer-tools.png) . By expanding the `result` property, you can also see both the query that was initially sent (`in`) and the query modified by the thesaurus rule (`out`). ![Thesaurus result in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/thesaurus-result-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the thesaurus rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Thesaurus rule details in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/thesaurus-rule-in-relevance-inspector.png) ## Stop words Query pipeline [stop word rules](https://docs.coveo.com/en/3406/) let you remove terms from a query before it's sent to the index. If a query pipeline contains stop word rules, review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review stop word rules configuration . On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review stop word rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Search terms** tab, and then click **Stop words**. . Validate the stop word rules' configuration and associated conditions. ### Test stop word rules in a search interface . Access the search interface in which you want to test a stop word rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search box, perform a query that would trigger a stop word rule. . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab, and then find the `basicExpression` property. . The value of the `basicExpression` property should reflect the stop word rule (in other words, the stop word terms shouldn't be present in the query). In the following capture, the term `mass` was removed by a stop word rule: ![Stop word rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/stop-word-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the stop word rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Stop word rule in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/stop-word-rule-in-relevance-inspector.png) ## Ranking expressions Query pipeline [ranking expression](https://docs.coveo.com/en/1472/) rules let you modify the score of specific search results when certain conditions are met. If a query pipeline contains [ranking expression rules](https://docs.coveo.com/en/3375/), review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review ranking expression rules configuration . On the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review ranking expression rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Result Ranking** tab, and then click a ranking expression rule. . In the Action bar, click **Edit**. . Validate the ranking expression rule's configuration and associated condition. ### Test ranking expression rules in a search interface . Access the search interface in which you want to test a ranking expression rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search box, perform a query that would trigger a ranking expression rule. . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Find and expand the `rankingExpressions` property, and then validate whether the `expression` and `modifier` behave as expected. ![Developer tools showing a ranking expression rule configuration | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/ranking-expression-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the ranking expression rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Ranking expression rule details in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/ranking-expression-rule-in-relevance-inspector.png) ## Featured results Query pipeline [featured result rules](https://docs.coveo.com/en/3376/) let you display content at the top of the results list when specific conditions are met. If a query pipeline contains featured result rules, review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review featured result rules configuration . In the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review featured result rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Result Ranking** tab, and then click a featured result rule. . In the Action bar, click **Edit**. . Validate the featured result rule's configuration and associated condition. ### Test featured result rules in a search interface . Access the search interface in which you want to test a featured result rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search box, perform a query that would trigger a featured result rule. . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . Check whether the first item in the result list is the one that the rule must boost. . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Find and expand the `results` property. . Find the property that corresponds to the item that the rule must boost. . Validate that the item has the `isTopResult` property with the `true` value. In the following capture, the **Use the Coveo Atomic Library** item is boosted by a featured result rule: ![Featured result rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/featured-result-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the featured result rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Featured result rule details in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/featured-result-rule-in-relevance-inspector.png) ## Triggers Query pipeline [triggers](https://docs.coveo.com/en/2792/) define actions to execute in a search interface. If a query pipeline contains [trigger rules](https://docs.coveo.com/en/3413/), review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review trigger rules configuration . In the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review trigger rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Advanced** tab, and then select **Triggers**. . Validate the trigger rules`' configuration and associated conditions. ### Test trigger rules in a search interface The [Coveo Platform](https://docs.coveo.com/en/186/) offers different types of trigger actions. The procedure to test them differs depending on the type of action the trigger rule leverages: * [Notify](#notify) * [Query](#query) * [Execute](#execute) * [Redirect](#redirect) #### Notify A **Notify** trigger rule displays a message in the search interface. . Access the search interface in which you want to test a trigger rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search interface, reproduce the conditions that would launch a trigger rule (for example, performing a query). . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . Verify that the message is displayed as expected in the search interface. . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab, and then find and expand the `triggers` property. . Validate the values of the `triggers` property. In the following capture, the **Notify** trigger displays the text `You searched for "atomic".`: ![Notify trigger rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/notify-trigger-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the trigger rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Notify trigger rule details in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/notify-trigger-rule-in-relevance-inspector.png) #### Query A **Query** trigger rule forces the search interface to perform a new search using the query specified in the rule. . Access the search interface in which you want to test a trigger rule. . In the search box, perform a query that would launch a trigger rule. . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab, and then find the `basicExpression` property. . Verify that the value of the `basicExpression` property matches the query defined in the **Query** trigger rule. In the following capture, the **Query** trigger rule performed the query `atomic` when the user entered the query `quantum`: ![Query trigger rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/query-trigger-rule-in-developer-tools.png) > **Note** > > You can't validate a **Query** trigger rule in the Relevance Inspector. #### Execute An **Execute** trigger rule lets you specify JavaScript functions to execute in the user's browser. . Access the search interface in which you want to test a trigger rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search interface, reproduce the conditions that would launch a trigger rule (for example, performing a query). . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab, and then find and expand the `triggers` property. . Validate the values of the `triggers` property. ![Execute trigger rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/execute-trigger-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the trigger rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Execute trigger rule in Relevance Inspector interface | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/execute-trigger-rule-in-relevance-inspector.png) #### Redirect A **Redirect** trigger rule redirects the user to a specific URL. . Access the search interface in which you want to test a trigger rule. . In the search interface, reproduce the conditions that would launch a trigger rule (for example, performing a query). . Validate that you are redirected to the expected URL. . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab, and then find and expand the `triggers` property. . Validate the values of the `triggers` property. ![Redirect trigger rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/redirect-trigger-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the trigger rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Redirect trigger rule in Relevance Inspector interface | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/redirect-trigger-rule-in-relevance-inspector.png) ## Query parameter rules Query parameter rules can override [query parameter](https://docs.coveo.com/en/13#tag/Search-V2/operation/searchUsingPost) values for every query that matches a condition. If a query pipeline contains [query parameter rules](https://docs.coveo.com/en/3411/), review its configuration and test several entries in a search interface to ensure that the rules work as expected. ### Review query parameter rules configuration . In the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review query parameter rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Advanced** tab, and then select **Query parameters**. . Validate the query parameter rules`' configuration and associated conditions. ### Test query parameter rules in a search interface . Access the search interface in which you want to test a query parameter rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search interface, reproduce the conditions that would trigger a query parameter rule (for example, performing a query). . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Find and expand the `executionReport` property, and then expand the `children` sub-property. . Expand the `ApplyQueryParamOverrideFeature` property. If you see a value for the `applied` sub-property, this means that a query parameter rule was applied for this query. . Expand the `applied` sub-property to see the definition of the rule that was applied. In the following capture, the rule overrides the `enableQuerySyntax` query parameter: ![Query parameter rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/query-parameter-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the query parameter rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Relevance Inspector showing query parameter rule with override query and enableQuerySyntax set to false | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/query-parameter-rule-in-relevance-inspector.png) ## Filters Query pipeline [filter](https://docs.coveo.com/en/2736/) rules define the scope of the search results displayed to your users. If a query pipeline contains [filter rules](https://docs.coveo.com/en/3410/), review its configuration and test several entries in a search interface to ensure that the rules work as expected. > **Important** > > Filters, by themselves, don't prevent the exposure of filtered content. > We strongly advise against creating a source whose content is [accessible to everyone](https://docs.coveo.com/en/1779#everyone) and using a pipeline filter to exclude sensitive information. > > In the following cases, sensitive content from a source whose content is [accessible to everyone](https://docs.coveo.com/en/1779#everyone) could be exposed: > > * A filter rule based on the [`aq`](https://docs.coveo.com/en/13#operation/searchUsingPost-aq) query parameter is set on a query pipeline that contains an [ART](https://docs.coveo.com/en/1013/) [model](https://docs.coveo.com/en/1012/) for which the [**Match the advanced query**](https://docs.coveo.com/en/l1ca1038#match-the-advanced-query) option is disabled. > > * Using other pipelines not having a similar filter from other search interfaces or directly from the API. > > * A colleague not understanding the reason for the filter could modify or remove the filter. > > You can ensure security by enforcing the [search hub](https://docs.coveo.com/en/1342/) at the [search token](https://docs.coveo.com/en/1346/) level (see [Search token authentication](https://docs.coveo.com/en/56/)). > Moreover, search hubs defined on the client-side that are used as conditions in pipelines **don't** safeguard the security of the filtered content. ### Review filter rules configuration . In the [**Query Pipelines**](https://platform.cloud.coveo.com/admin/#/orgid/search/pipelines/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/pipelines/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/pipelines/)) page of the Administration Console, select the query pipeline for which you want to review filter rules configuration. Then, in the Action bar, click **Edit components**. . Select the **Advanced** tab, and then select **Filters**. . Validate the filter rules`' configuration and associated conditions. ### Test filter rules in a search interface . Access the search interface in which you want to test a filter rule. . [Access your browser's network monitoring tool](#access-your-browsers-network-monitoring-tool). . In the search interface, reproduce the conditions that would trigger a filter rule (for example, performing a query). . Enable debugging mode by appending `&debug=true` to the current URL. ![Enable debugging mode | Coveo](https://docs.coveo.com/en/assets/images/debugging-mode-url.png) . In the network monitoring tool, under the **Name** column, select the latest request to the Search API. The request path should contain `/rest/search/v2`. . Select the **Preview** tab. . Filter rules can take effect on the [basic query expression (`q`)](https://docs.coveo.com/en/178/), [advanced query expression (`aq`)](https://docs.coveo.com/en/175/), [constant query expression (`cq`)](https://docs.coveo.com/en/179/), [disjunction query expression (`dq`)](https://docs.coveo.com/en/190/), or [large query expression (`lq`)](https://docs.coveo.com/en/214/). Verify that the expression associated to this property matches the rule. In the following capture, the filter rule affects `cq` so that the search interface only displays items for which the value of the `language` field is `english`: ![Filter rule in developer tools | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/filter-rule-in-developer-tools.png) . Access the Relevance Inspector: -- .. If your search interface leverages the [Atomic library](https://docs.coveo.com/en/lcdf0264/), select and hold Alt (Windows) or Option (Mac) and double-click any search interface element. .. In the modal that appears, select `Open`, and you'll be redirected to the [Coveo Administration Console](https://docs.coveo.com/en/183/). You may have to wait for your query to load. -- > **Note** > > You can go directly to the [**Relevance Inspector**](https://platform.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/search/relevanceInspector/)) page of the [Coveo Administration Console](https://docs.coveo.com/en/183/). > If you do, you'll need to rerun the query in the Relevance Inspector using the query's `SearchUid`. > You can find this value on the **Preview** tab of your network monitoring tool: > > ![Find the Search UID](:https://docs.coveo.com/en/assets/images/find-search-uid.png) . In the Relevance Inspector, the filter rules are displayed under **Query pipeline rules** (the third step in the **Query journey**). Click **See details** for more information about the rule that was applied. ![Filter rule in Relevance Inspector | Coveo](https://docs.coveo.com/en/assets/images/implementation-guide/filter-rule-in-relevance-inspector.png)