Retail provides metrics to help you determine how incorporating the Retail API is affecting your business.
View Retail metrics
You can view summary metrics for your project on the Analytics page in Google Cloud console. See Summary metrics for metrics definitions.
For serving config-specific metrics, go to the Serving Configs page. Click a serving config name and select the Analytics tab to see its metrics. See Configuration-specific metrics for metrics definitions.
For details about monitoring Retail API errors and other health-related metrics, see the Retail API Monitoring and troubleshooting documentation.
Metrics definitions
Summary metrics
Click the Recommendations, Search, or Browse tab to view metrics for that type of solution.
The sections below provide definitions of the site-wide metrics displayed on the Analytics page:
- Recommendations AI summary metrics: Metrics representing user engagement with recommendation results generated by Recommendations AI.
- Retail Search summary metrics:
- Text query search summary metrics: Metrics representing engagement with text-based query search results generated by Retail Search.
- Browse search summary metrics: Metrics representing engagement with category browse search results generated by Retail Search.
Recommendations AI summary metrics
The following metrics are displayed for Recommendations AI on the Recommendations tab.
Select a metric type from the Metric drop-down list to see its graph for the last month.
| Metric | Description |
| Total revenue |
The total revenue from all recorded purchase events. This value includes shipping and tax. |
| Recommender-engaged revenue |
The revenue for purchase events that include at least one product that was selected from a recommendation panel. This value includes shipping and tax and any discount applied. |
| Average order value (AOV) |
The average value of orders from all purchase events. Total revenue divided by the number of orders. |
| Recommender-engaged AOV |
The average value of orders that include at least one product selected from a recommendation panel. Recommender-engaged revenue divided by the number of orders with at least one product that was selected from a recommendation panel. |
Text search summary metrics
The following metrics for Retail Search text searches are displayed on the Search tab.
Select a metric type from the Metric drop-down list to see its graph for the last month.
| Metric | Description |
| Searches |
The total number of searches performed site-wide. |
| Click-through rate |
The number of clicks from search results divided by the total number of site-wide searches. The total number of searches includes paginated queries. |
| Conversion rate |
The number of purchase events occurring from search results divided by the total number of searches. The total number of searches includes paginated queries. |
| Add to cart rate |
The number of add-to-cart events occurring from search results divided by the total number of searches. |
| % of queries that are personalized |
The number of personalized searches divided by the total number of searches. |
Browse search summary metrics
The following metrics for Retail Search browse searches are displayed on the Browse tab.
Select a metric type from the Metric drop-down list to see its graph for the last month.
| Metric | Description |
| Browses |
The total number of browse searches performed site-wide. |
| Click-through rate |
The number of clicks from browse results divided by the total number of site-wide browse searches. The total number of browse searches includes paginated queries. |
| Conversion rate |
The number of purchase events occurring from browse results divided by the total number of browse searches. The total number of browse searches includes paginated queries. |
| Add to cart rate |
The number of add-to-cart events occurring from browse results divided by the total number of browse searches. |
| % of queries that are personalized |
The number of personalized browse searches divided by the total number of browse searches. |
Configuration-specific metrics
You can see metrics for a specific serving config on the Serving Configs page. For metric graphs, click a serving config name to go to its details page, then select the Analytics tab.
The table below provides definitions for configuration-specific metrics.
| Metric | Description | Details |
| Click-through rate (CTR) |
The number of product detail views from a serving config's
recommendation panel, divided by the total number of predict
queries for this serving config.
|
For example, if the serving config points to a Frequently Bought Together model, then the CTR would be the number of product detail pages viewed from the shopping cart recommendation panel divided by the number of predict queries on the shopping cart page. |
| Conversion rate (CVR) |
The number of add-to-cart events from a serving config's
recommendation panel divided by the total number of predict
queries for this serving config.
|
Similar to CTR, except that instead of product detail views, conversion rate uses add-to-cart events. |
| Recommender-engaged revenue | The total revenue from the recommendations for this serving config. | Similar to recommender-engaged revenue for summary metrics, but for this serving config only. |
To track clicks from a serving config, Retail aligns the
results in predict and search responses with ingested user events. If a
clicked item appears in the responses for the same visitor ID within a
one hour time window, the click/purchase is treated as a result of the
Retail API.
This process is fully automatic; you do not need to set anything up. However, when you configure your prediction and search requests for the first time, you should confirm that:
- Visitor IDs in the request are the same as the visitor IDs you used in event ingestions.
- The timestamp in the response roughly match the timestamp for that event.
When Retail API metrics are compared to the ideal expected result, or ground truth, the values might be lower, but the trends align.
A more direct alternative to the method above is to use attribution tokens. This requires significant instrumentation and is only recommended as an advanced tracking use case.