Ensure that search hubs are implemented

This is for:

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 for help.

In your solution, each search interface intended for a specific audience should have its own identifier, or search hub. Depending on your chosen authentication method, you can enforce the search hub through the search token or API key. You must also ensure that you set your search hub in your search interfaces.

Depending on how you choose to build your search interfaces, see:

Example

You have two search interfaces which specifically target two distinct audiences (customers and service agents). You set the following search hubs to personalize each audience’s search experience:

CommunitySearch

<atomic-search-interface id="search" search-hub="CommunitySearch">
  <!-- ... -->
</atomic-search-interface>

AgentPanel

<atomic-search-interface id="search" search-hub="AgentPanel">
  <!-- ... -->
</atomic-search-interface>

Setting search hubs based on your audiences allows Coveo Machine Learning (Coveo ML) to learn from the behavior of a particular segment of your users. You can also get insightful information about an audience that’s targeted by a specific search hub in Coveo Usage Analytics (Coveo UA).

In the Coveo Administration Console, your consumption dashboard lets you analyze logged queries per search hub.