Search dashboard

This is for:

Business Analyst System Administrator

The Search dashboard on the Advanced Reports (platform-ca | platform-eu | platform-au) page provides an in-depth view of the attribution that’s specific to the Search product discovery solution. It’s divided into several charts, each dedicated to a key metric.

The Search dashboard | Coveo for Commerce

The Search dashboard includes the following metric charts:

What is a session?

Although sessions aren’t specifically listed in the Search dashboard, they’re often used to calculate the metrics listed there.

At Coveo, a session starts with the first event a visitor generates and ends after 30 minutes of inactivity. For a given visitor, if a new event is generated after 30 minutes of inactivity, it results in a new session with a new visit ID.

To be considered Coveo-related, the session must contain search, product listing, or recommendation actions.

What is search attribution?

A click action on a search result | Coveo for Commerce Coveo attributes a product in a transaction to the Search product discovery solution if the visitor's last registered click action before purchasing the product was selecting it from the search results that were returned after performing a query in the search box.

For more details about how attribution is tracked for the Search solution, see About search attribution.

The Search dashboard shows how Coveo-powered searches have contributed to your key commerce metrics.

Revenue from searches chart

The Revenue from searches chart displays the sum of the gross revenue influenced by Coveo-powered searches (coming from the search bar) that occurred within the chosen filters.

The line graph delineates the revenue variance over a specific period of time.

How is the revenue from searches calculated?

Expand the following sections to learn how the revenue from searches is calculated, based on whether you’re tracking events using the Coveo Event protocol or the Coveo UA protocol:

Event protocol

The sum of the gross revenue (from the transaction property) from every product sold in each purchase event that was attributed to Coveo searches.

SUM (gross revenue attributed to Coveo searches)
Coveo UA

The sum of the gross revenue from every product sold in each purchase event that was attributed to Coveo searches.

SUM (gross revenue attributed to Coveo searches)
Note

Revenue is reported in USD and calculated as either net or gross revenue:

  • Net revenue excludes taxes, shipping costs, and discounts.

  • Gross revenue includes taxes, shipping costs, and discounts.

The Top selling products metric displays net revenue figures. All other reported revenue metrics use gross revenue, unless otherwise stated.

See About revenue for more information on how the revenue metrics are calculated.

Transactions from searches chart

Expand the following sections to learn about the Transactions from searches chart based on the tracking method you use:

Event protocol

The Transactions from searches chart displays the total number of purchase events influenced by Coveo-powered searches (coming from the search bar) that occurred within the chosen filters.

The line graph delineates the variance of the purchase events over a specific period of time.

Coveo UA

The Transactions from searches chart displays the total number of purchase events influenced by Coveo-powered searches (coming from the search bar) that occurred within the chosen filters.

The line graph delineates the variance of the purchase events over a specific period of time.

How are transactions from searches calculated?

Expand the following sections to learn how transactions from searches are calculated, based on the tracking method you use:

Event protocol

The total number of purchase events attributed to Coveo searches.

See Capture purchase events for more information on how purchase events are logged and measured.

SUM (purchase events attributed to Coveo searches)
Coveo UA

The total number of commerce events that contain the purchase action and are attributed to Coveo searches.

See Capture a purchase event for more information on how purchase events are logged and measured.

SUM (commerce events with action = purchase attributed to Coveo searches)

Conversion rate from searches chart

The Conversion rate from searches chart displays the sum of the completed sessions that involved Coveo-powered searches (coming from the search bar) with at least one transaction, divided by the sum of completed sessions that involved Coveo-powered searches (coming from the search bar), within the chosen filters.

The line graph delineates the variance of the rate over a specific period of time.

How is the conversion rate from searches calculated?

The sum of the completed sessions involving Coveo-powered searches (coming from the search bar) with at least one transaction, divided by the sum of the completed sessions with at least one search event triggered by a search query, multiplied by 100.

SUM (completed sessions involving Coveo searches with at least one transaction) / SUM (completed sessions involving Coveo searches) * 100

Average order value influenced by searches chart

The Average order value influenced by searches chart displays the average gross revenue per transaction influenced by Coveo-powered searches (coming from the search bar) that occurred within the chosen filters.

The line graph delineates the variance of the average over a specific period of time.

How is the average order value influenced by searches calculated?

The sum of the gross revenue attributed to Coveo searches, divided by the total number of transactions attributed to Coveo searches.

SUM (gross revenue attributed to Coveo searches) / SUM (transactions attributed to Coveo searches)

Average clickthrough rate chart

Expand the following sections to learn how the average clickthrough rate is calculated, based on the tracking method you use:

Commerce API

The Average clickthrough rate chart displays the ratio between the number of search requests to the Commerce API that were followed by at least one related click event, out of the total number of search requests to the Commerce API, within the chosen filters.

The line graph delineates the variance of the average clickthrough rate over a specific period of time.

Search API

The Average clickthrough rate chart displays the ratio between the number of search events influenced by Coveo-powered searches (coming from the search bar) that were followed by at least one related click event, out of the total number of search events influenced by Coveo-powered searches, within the chosen filters.

The line graph delineates the variance of the average clickthrough rate over a specific period of time.

How is the average clickthrough rate calculated?

Expand the following sections to learn how the average clickthrough rate is calculated, based on the Coveo API your implementation targets:

Commerce API

The sum of search requests to the Commerce API that were followed by at least one click event (with a matching unique identifier value), divided by the total number of search requests to the Commerce API.

SUM (search requests to the Commerce API followed by a click event) / SUM (search requests to the Commerce API)
Search API

The sum of search events influenced by Coveo-powered searches (coming from the search bar) that were followed by at least one click event (with a matching unique identifier value), divided by the total number of search events influenced by Coveo-powered searches.

SUM (search events influenced by Coveo-powered searches followed by a click event) / SUM (search events influenced by Coveo-powered searches)

Average click rank chart

Tip

A lower click rank is better, because it means that the product was well positioned.

The Average click rank chart displays the average position of clicked products searches, within the chosen filters.

The line graph delineates the variance of the average click rank over a specific period of time.

How is the average click rank calculated?

Expand the following sections to learn how the average click rank is calculated, based on the Coveo API your implementation targets:

Commerce API

The average position value for all click events that followed a search request to the Commerce API.

SUM (position values for all click events that followed a Coveo search) / SUM (click events that followed a Coveo search)
Search API

The average position value for all click events that followed a search event triggered by a search query.

SUM (documentPosition values for all click events that followed a search event) / SUM (click events that followed a search event)

Top queries and search events chart

This chart displays a list of the top user queries (Query expressions) organized by the attributed number of Coveo searches and their respective total revenue, within the chosen filters.

How are top queries and search events calculated?

Expand the following sections to learn how the top queries and search events are calculated, based on the Coveo API your implementation targets:

Commerce API

The expressions that appear in the query property of search requests to the Commerce API the most often.

Search API

The expressions that appear in the queryText property the most often in search events triggered by a search query.

When purchases are attributed to the Search solution, the sum of the revenue of related purchase events is used to calculate the total revenue generated by that specific query.

Total search events chart

The Total search events chart displays the total number of search events.

The total is broken down into manual, refinement, automatic, or unclassified search events:

  • A manual search event happens when a visitor takes a manual action that causes products to be displayed, like sending a query from the search box.

  • A refinement search event typically happens after a manual search, when a visitor takes an action that refines a search, like interacting with facets or sort options.

  • An automatic search event happens when a search event is triggered automatically by a Coveo-powered feature, such as when:

    • The query correction (also known as Did You Mean) feature automatically corrects a user’s query.

    • The search-as-you-type feature triggers search events when a user types a query in the search box.

    • A Coveo-powered interface loads without any user interaction, such as when a user lands on a page where search results are automatically displayed.

  • An unclassified search event, depending on whether your implementation targets the Commerce API or Search API, is:

    • Commerce API: Any search event that doesn’t fall into the manual, refinement, or automatic categories.

    • Search API: Any search event for which the actionCause value isn’t recognized.

How are total search events calculated?

Expand the following sections to learn how total search events are calculated, based on the Coveo API your implementation targets:

Commerce API

The total number of search requests made to the Commerce API.

SUM (search requests to the Commerce API)
Note

Requests to the Commerce API don’t need to specify the actionCause value, as this is automatically inferred by the Coveo platform.
Search API

The total number of search events triggered by a search query. The actionCause value is used to determine whether it’s a manual, refinement, automatic, or unclassified search event.

SUM (search events triggered by a search query)

Top selling products chart

A list of the top ten products or product groups in search results that generated the most net revenue, within the chosen filters.

How are top selling products calculated?

Expand the following sections to learn how the top selling products are calculated based on the Coveo API your implementation targets:

Commerce API

The products or product groups contained in click events that followed a search requests made to the Commerce API to which a purchase was attributed and that generated the most net revenue.

Search API

The products or product groups contained in click events that followed a search event influenced by Coveo-powered searches (coming from the search bar) to which a purchase was attributed and that generated the most net revenue.

Discrepancies between reports

Figures shown for metrics in the Commerce Advanced Reports may differ from those for the same metrics in the Reports (platform-ca | platform-eu | platform-au) page of the Coveo Administration Console and Coveo Merchandising Hub (CMH) reports.

These discrepancies typically occur because different reports use distinct filters and processing rules when calculating figures for the same metric.

Here are the most common reasons for differences between reports:

  • Inclusion of searchBoxAsYouType events:

    By default, reports from the Reports (platform-ca | platform-eu | platform-au) page include search events where the event cause is searchBoxAsYouType. This can result in higher query figures compared to the Commerce Advanced Reports or CMH reports, which exclude these events by default.

  • Time zone differences:

    CMH reports use Coordinated Universal Time (UTC), while the reports of the Reports page and Commerce Advanced Reports use the user’s browser time zone. This difference can lead to a few hours of offset in event timestamps, which may affect metric calculations.

  • Case sensitivity in query metrics:

    For query-related metrics, CMH reports treat queries as case-sensitive, while Commerce Advanced Reports and the reports on the Reports page consider queries case-insensitive. This means that identical queries with different casing are treated as separate queries in CMH reports, but are counted as the same query on the Commerce Advanced Reports and on the Reports page.

    For example, the queries coveo and Coveo are counted as separate queries in CMH reports, but as the same query on the Commerce Advanced Reports and on the Reports page.