This is a response rewriting stage that helps “de-bias” results by swapping the search results at any two positions, such as positions 1 and 2, positions 3 and 4, and so on. This stage must be used after the Solr Query stage in your pipeline. This stage is especially useful when combined with experiments, where a small percentage of traffic is given swapped results to minimize position bias when using click signals for ranking. The Response Shuffle stage provides an another method for minimizing this bias.

​
Query pipeline stage condition examples

Stages can be triggered conditionally when a script in the Condition field evaluates to true. Some examples are shown below. Run this stage only for mobile clients: 
params.deviceType === "mobile"
Run this stage when debugging is enabled: 
params.debug === "true"
Run this stage when the query includes a specific term: 
params.q && params.q.includes("sale")
Run this stage when multiple conditions are met: 
request.hasParam("fusion-user-name") && request.getFirstParam("fusion-user-name").equals("SuperUser");
!request.hasParam("isFusionPluginQuery")
The first condition checks that the request parameter “fusion-user-name” is present and has the value “SuperUser”. The second condition checks that the request parameter “isFusionPluginQuery” is not present.

​
Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.