Overview dashboard

This is for:

Business Analyst System Administrator

The Overview dashboard on the Advanced Reports (platform-ca | platform-eu | platform-au) page provides a snapshot of your site’s overall performance over a specified period. It’s divided into several charts, each dedicated to a key metric that contributes to the overall performance. Furthermore, each chart contains a visual breakdown of the attribution that affects the metric.

The Overview dashboard | Coveo for Commerce

The Overview dashboard includes the following metric charts:

What is a session?

Although sessions aren’t specifically listed in the Overview 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.

Metrics attributed to Coveo

Most metrics in the Overview dashboard are the result of the combined value of the different Coveo product discovery solutions.

You can also see how much a specific solution contributed to a metric’s total value. For example, the revenue of a product within a transaction can be attributed to the Search, Product listings, or Recommendations solutions.

The attribution of a purchased product to a Coveo solution is determined by examining the visitor’s touchpoints before the purchase.

The general attribution mechanism is to track a unique identifier (UID) throughout the visitor’s journey leading up to the purchase. This UID is generated when a search query or request is made to the Commerce or Search APIs. It’s included in subsequent click actions on search results, product listings, or recommendations.

Coveo can track this UID to determine which touchpoint led to the purchase.

Total revenue chart

Expand the following sections to learn about the Total revenue chart, depending on the tracking method you use:

Event protocol

The Total revenue chart displays the sum of the gross revenue earned from all purchase events that occurred within the chosen filters.

This chart also displays the portion of the total gross revenue that’s earned through Coveo solutions.

The bar graph highlights the purchases attributed to the Search, Product listings, and Recommendations solutions.

Coveo UA

The Total revenue chart displays the sum of the gross revenue earned from all purchase events that occurred within the chosen filters.

This chart also displays the portion of the total gross revenue that’s earned through Coveo solutions.

The bar graph highlights the purchases attributed to the Search, Product listings, and Recommendations solutions.

How is total revenue calculated?

Expand the following sections to learn how the revenue metric is calculated based on the tracking method you use:

Event protocol

The sum of the gross revenue (from the transaction property) from every product sold in each purchase events.

SUM (gross revenue)
Coveo UA

The sum of the gross revenue (from the transaction property) from every product sold in each purchase events.

SUM (gross revenue)
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.

Total transactions chart

Expand the following sections to learn about the Total transactions chart based on the tracking method you use:

Event protocol

The Total transactions chart shows the total number of purchase events within the chosen filters. Each purchase event can contain multiple products and can be attributed to multiple solutions.

Coveo UA

The Total transactions chart shows the total number of purchase events within the chosen filters. Each purchase event can contain multiple products and can be attributed to multiple solutions.

The bar graph highlights the transactions attributed to the Search, Product listings, and Recommendations solutions.

How are transactions calculated?

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

Event protocol

The total number of purchase events.

For more information on how purchase events are logged and measured, see Capture a purchase event.

SUM (purchase events)
Coveo UA

The total number of commerce events that contain the purchase action.

For more information on how purchase events are logged and measured, see Capture a purchase event.

SUM (commerce events with action = purchase)
Important

When a single transaction contains multiple products, it’s attributed to each of the solutions that’s credited for one or more of the products in the transaction. However, Coveo attributes transactions based on the unique touchpoints involved, not the total number of products.

For example, a transaction contains four different products, each attributed to a specific solution:

  • Product 1: Search

  • Product 2: Product listings

  • Product 3: Product listings

  • Product 4: Recommendations

In this example, even though the Product listings solution is responsible for two products, only one transaction is attributed to the Product listings solution.

This means that the transaction is attributed as follows:

  • One transaction is attributed to the Search solution

  • One transaction is attributed to the Product listings solution

  • One transaction is attributed to the Recommendations solution

  • One transaction is attributed to Coveo

Conversion rate chart

The Conversion rate chart displays the sum of the completed sessions with at least one transaction, divided by the sum of the completed sessions, within the chosen filters.

The line graph shows the conversion rates for the Search, Product listings, and Recommendations solutions.

How is the conversion rate calculated?

The sum of the completed sessions with at least one transaction, divided by the total number of completed sessions.

SUM (completed sessions with at least one transaction) / SUM (completed sessions)
Notes

  • The Conversion rate with Coveo metric is the sum of the completed sessions that involved a Coveo solution (Search, Product listings, or Recommendations) with at least one transaction, divided by the total number of completed sessions that involved any Coveo solution.

    SUM (completed sessions involving a Coveo solution with at least one transaction) / SUM (completed sessions involving a Coveo solution)

  • The conversion rate for a specific Coveo solution, such as Search, is the sum of the completed sessions involving that solution with at least one transaction, divided by the total number of completed sessions in which that Coveo solution was used.

    SUM (completed sessions involving the solution with at least one transaction) / SUM (completed sessions involving that solution)

  • The Conversion rate without Coveo metric is the sum of the completed sessions that didn’t involve any Coveo solutions with at least one transaction, divided by the total number of completed sessions that didn’t involve any Coveo solutions.

    If Coveo solutions are used across the whole commerce experience, there will be few sessions that don’t involve a Coveo solution, so the denominator may be very small. As a result, the Conversion rate without Coveo may appear disproportionately high.

    SUM (completed sessions that didn't involve any Coveo solutions with at least one transaction) / SUM (completed sessions that didn't involve any Coveo solutions)

Average order value chart

The Average order value (AOV) chart displays the average gross revenue per transaction, within the chosen filters.

The line graph highlights how the AOV is attributed to the Search, Product listings, and Recommendations solutions.

How is the AOV calculated?

The sum of the gross revenue, divided by the total number of transactions.

SUM (total gross revenue) / SUM (transactions)

Average clickthrough rate chart

The Average clickthrough rate chart shows the proportion of times products were returned and followed by at least one related product click, within the chosen filters.

The line graph highlights how the clickthrough rate is attributed to the Search, Product listings, and Recommendations solutions.

How is the average clickthrough rate calculated?

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

Commerce API

The sum of the 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.

Requests must be either a search, a recommendations, or a listings request.

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

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

SUM (search events followed by a click event) / SUM (search events)

Average click rank chart

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

The line graph highlights how the average click rank is attributed to the Search, Product listings, and Recommendations solutions.

Tip

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

How is the average click rank calculated?

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

Commerce API

The sum of the position values for all click events that followed a request to the Commerce API, divided by the total number of click events that followed a request to the Commerce API.

Requests must be a search, recommendations, or listings request.

SUM (position values for all click events that followed a request to the Commerce API) / SUM (click events that followed a request to the Commerce API)
Search API

The sum of the documentPosition values for all click events that followed a search event, divided by the total number of click events that followed a search event.

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

Top selling products chart

The top ten products or product groups that generated the most net revenue, within the chosen filters.

How are top selling products determined?

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

Commerce API

The products or product groups included in click events that followed a request to the Commerce API and generated the most net revenue.

Requests must be either a search, recommendations, or listings request.

Search API

The products or product groups contained in click events that followed a search event to which a purchase was attributed 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.