Query Pipeline Routing Mechanisms and Rules

All queries sent to your Coveo Cloud organization go through a query pipeline (see What Is a Query Pipeline?). You can use different mechanisms to determine into which query pipeline queries are routed.

The choice of the mechanism depends essentially on how easily you can get a developer to change code in your Coveo setup and if you want to take advantage of the routing flexibility that query pipeline conditions offer. The following table summarizes the main routing mechanism selection criteria.

Selection criteria   Query pipeline routing mechanisms
Query pipeline conditions Search token1 Hard-coded in search interface1
Routing priority 3 1 2
Implementation by Coveo Cloud administrator Developer Developer
Implementation in Coveo Cloud administration console Search token Search interface code
Applies to all queries Matching a condition With the token From the search interface
Dynamic routing Yes No No
Client-side modification No No Yes

Note 1: You cannot perform A/B tests with hardcoded pipelines or pipelines included in search tokens.

When using a search token, the pipeline query parameter value (if specified) takes precedence over the possible output of all other query pipeline routing mechanisms (see pipeline).

For instance, the pipeline searchHub value you specified in the same search token would be bypassed even if you linked the hub to the query pipeline with a condition (see Search Hub Condition).

Review the following leading practices and rules to better understand how queries are routed to a given query pipeline and which mechanism is the best for your needs.