Integrate Coveo components in an Experience Cloud site

This is for:

In this article

Prerequisites
Adding the Coveo Community Search component
Adding the Coveo standalone search box
Adding the Coveo Page View Tracker component
Adding the Coveo Case Deflection component
Adding missing Content Security Policy trusted sites
What’s next?

Coveo for Salesforce comes with multiple Lightning components which can be easily added to your Experience Cloud site (formerly Lightning community). This page shows you how to add the default Coveo Lightning components to your Experience Cloud site using the Salesforce Experience Builder.

Leading practice

You should always duplicate Coveo components instead of using the default ones. This keeps the original component configurations intact for reference and re-use (see Integrating Coveo components in a custom Lightning component).

Prerequisites

Enable Digital Experiences for your organization.
Assign the View Global Header permission to internal users who need access to the Experience Cloud site to allow them to see the global menu.
Select the Customer Service template to create your Experience Cloud site.

Important

The only supported template is Customer Service. If you select another template, you may experience unexpected behavior with certain components.

Adding the Coveo Community Search component

The Coveo Community Search component lets you insert a complete search results page in your Experience Cloud site, including features such as facets, tabs, sorting, and pagination.

To add the Coveo Community Search component

Access the Salesforce Experience Builder.
In the left sidebar, select Components.
In the Components dialog, under Custom Components, drag the Coveo Community Search component and drop it onto the page region where you want the search interface to appear, typically in the Content section.

When you create a Community Search component for the first time, the Interface Creator (This search page isn’t configured yet.) dialog is displayed:

Click Preview in the upper-right corner of the Experience Builder to switch to preview mode.

Important

In a newly created Experience Cloud site, you must either publish your site and create or edit your search page via the published Experience Cloud site URL. Otherwise, to continue in Preview mode, you must add the following Content Security Policy (CSP) trusted sites:

After adding these sites, you must refresh the page to use the Interface Creator. You should also set the CSP security to Allow Inline Scripts and Script Access to Any Third-Party Host.

In the Coveo Search component region, click Set up a Search Page.
Follow the onscreen steps, and then click Create page.

Important

If an error message appears after clicking Create page, you must add missing Content Security Policy trusted sites to your Salesforce organization.

You should now have a functional search page connected to the Salesforce search box, returning results from your Coveo organization index. You can also test your search page at this time.

When you’re satisfied with your search page, in the upper-right corner of the Experience Builder, click Publish to make your changes available to your site users (see Publish Your Experience Builder Site Customizations).

Important

Be aware that publishing Interface Editor changes immediately affects your Experience Cloud site in production.
Make sure that the appropriate users are members of your Experience Cloud site so that they can view your search page.

You can use the Coveo Community Searchbox component to add a standalone search box to your Experience Cloud site. The standalone search box offers advanced features such as Coveo Machine Learning (Coveo ML) query suggestions, typo correction, and facet value suggestions.

To add the Coveo Community Searchbox component

Access the Salesforce Experience Builder.
In the left sidebar, select Theme > Theme Settings.
Under Search Component, in the dropdown menu, select Coveo Community Searchbox.

Important

If you don’t see the Coveo Community Searchbox option, you may not be using the right template. Ensure that your Theme is set to Customer Service.

Note

If you’re using a previous version of the Coveo for Salesforce package, the component name will be Searchbox (before v2.51) and Coveo Searchbox (before v3.25).
Close the Theme Settings menu.

Your search page now uses the Coveo standalone search box.

Additional considerations

Ensure that the value for the Search Url option is set to global-search/%40uri (see Customizing the standalone search box).
When you have the default Headline component from Salesforce integrated into your Experience Cloud site, you won’t notice that it always shows the query is @uri. You’re encouraged to remove this component, as it’s incompatible with the standalone search box.
With your current configuration, both the standalone search box and the search component are injecting their query to the search component. If you prefer to only inject the relevant query, you can disable the Auto inject basic query setting of your search component.
The Coveo standalone search box doesn’t support site branding. However, using custom CSS to override the template elements should still work as expected.

You can now use the options panel to customize your Coveo standalone search box.

Adding the Coveo Page View Tracker component

Coveo for Salesforce 3.10

The Coveo Page View Tracker component can be added to your Experience Cloud site to send usage analytics data to Coveo. The data gathered by the component can later be used to recommend pages to your users using a Content Recommendation (CR) model.

To add the Coveo Page View Tracker component

Access the Salesforce Experience Builder.
In the left sidebar, select Components.
Under Custom Components, drag and drop the Coveo Page View Tracker component in the header of your page.

Leading practice

We recommend adding the Coveo Page View Tracker on every page of your Experience Cloud site to ensure that all your page views are recorded.

Adding the Coveo Case Deflection component

Coveo for Salesforce 3.29

You can add the Coveo Case Deflection component to your Experience Cloud site to provide recommended solutions to users before they submit a case to your support agents (see Integrate a Coveo Case Deflection component).

Adding missing Content Security Policy trusted sites

Following changes in the Salesforce framing policies, you may need to manually add URIs to your Content Security Policy (CSP) Trusted Sites to access the Interface Creator and Interface Editor.

To know which URIs to add to your CSP trusted sites

In the Can’t Access Resources error message that appears after clicking Create page in the Interface Creator, copy the URI address displayed next to Blocked URI, and then add the URI to your CSP Trusted Sites.
Back in the Preview mode of the Experience Builder, open your browser developer tools, and then access the Console tab.
In the Coveo Search component region, click Set up a Search Page, and then follow the onscreen steps.
Click Create page and then, in the Console tab of your browser developer tools, you should see an error message.
In the error message, copy the last URI that appears (the one displayed in red), and then add the URI to your CSP Trusted Sites.

Note

After adding these sites, you must refresh the page to use the Interface Creator.

What’s next?

Learn how to access the Interface Editor.
When you need to securely add mandatory filters or inject identities, consider defining a server-side configuration for your Coveo Lightning component.