> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/analytics/metrics.md).
# Metrics
Understand how Crobox metrics are calculated, find definitions for the default metrics, and create your own.
Metrics are the numbers behind every dashboard widget, from sessions and revenue to conversion rates. Every container comes with a set of default metrics, and you can create your own for the questions that matter to your business.
You'll find them in **Analytics** → **Metrics**. The **Metrics** tab lists every metric with its format, a readable formula, and its performance over the last three days, so you can sanity-check a metric before you add it to a dashboard.
Create a metric
Build custom metrics, from simple counts to calculated rates.
Group by aliases
Combine group by keys that mean the same thing into one.
### How metrics are built
Every metric is one of two types:
* **Simple** - Counts or sums a single value, like sessions, transactions, or revenue. Filters narrow it down, for example to sessions where a visitor added a product to their cart.
* **Calculated** - Combines other metrics with an operator: plus, minus, divided by, or multiplied by. For example, Average Order Value is Revenue ÷ Transactions.
In the **Formula** column, filters appear in brackets. For example, **Sessions (Cart)** means sessions that include an add to cart.
{% hint style="info" %}
The Formula column doesn't show brackets for nested calculations, so a metric built as (A − B) ÷ C displays as A − B ÷ C. Open the metric to see exactly how it's built.
{% endhint %}
### Where metric data comes from
Your analytics data comes from:
* **JavaScript tracking** installed on your site pages
* **Experience interactions** from Product Finder, Campaigns, and other Crobox tools
* **E-commerce events** captured through your implementation
* **Cross-session tracking** that follows customer journeys over time
The depth and accuracy of your metrics depend on which Crobox experiences you have installed and how they're configured on your site.
{% hint style="warning" %}
Missing expected metrics? Check that your Crobox implementation covers all relevant pages and events. Contact your technical team or Crobox support if you need help expanding your tracking coverage.
{% endhint %}
## Default metrics
Default metrics are available in every container and can't be removed. Find the exact formula for each one in **Analytics** → **Metrics**.
#### Core Site Metrics
| Metric | Definition | Use Case |
| ------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| **Actions** | Total interactions customers make on your site - clicks, adds to cart, custom actions, and more | *Monitor overall site engagement and activity levels* |
| **Pageviews** | How many pages visitors view during their time on your site | *Track content consumption and popular pages* |
| **Sessions** | Individual visits to your site, from arrival to departure | *Understand traffic volume and visitor patterns* |
| **Users** | Unique individuals visiting your site (removing duplicate visits) | *Measure your actual audience size and reach* |
#### Performance Metrics
| Metric | Definition | Use Case |
| ----------------------- | ------------------------------------------- | ------------------------------------------------------------------- |
| **Revenue** | Total money earned from completed purchases | *Track financial performance and business growth* |
| **Transactions** | Number of completed purchases on your site | *Monitor sales volume and conversion success* |
| **Conversion Rate** | Percentage of visitors who make a purchase | *Measure how effectively your site turns visitors into customers* |
| **Average Order Value** | Average amount customers spend per purchase | *Understand spending patterns and identify upselling opportunities* |
#### Cross-Session Performance Metrics
| Metric | Definition | Use Case |
| ----------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Revenue (cross-session)** | Total money earned from customers within 30 days of their initial interaction | *Understand the full revenue impact of customer discovery journeys, including delayed purchases* |
| **Transactions (cross-session)** | Number of purchases completed by customers within 30 days of their initial interaction | *Measure true conversion impact beyond single-session purchases* |
| **Conversion Rate (cross-session)** | Percentage of initial visitors who make a purchase within 30 days of first interaction | *Evaluate the long-term effectiveness of customer acquisition and engagement* |
{% hint style="success" %}
**Cross-session metrics** provide a more complete picture of customer behavior by tracking the full customer journey, not just immediate conversions. These metrics are especially valuable for understanding the impact of discovery experiences on customers who need time to research before purchasing.
{% endhint %}
#### Engagement Metrics
| Metric | Definition | Use Case |
| ---------------------- | ------------------------------------------------------------- | ------------------------------------------------------ |
| **Product Clicks** | Number of product clicks by visitors | *Identify which products generate the most interest* |
| **Product Carts** | Number of products added to shopping carts | *Track purchase intent and product appeal* |
| **Product Boughts** | Products that customers actually purchased | *See which products convert from interest to sales* |
| **Add-to-Cart Rate** | Percentage of sessions where visitors add items to their cart | *Measure how well products appeal to shoppers* |
| **Click-through Rate** | How often products generates clicks from visitors | *Measure content impressions and click event tracking* |
| **Buy-to-Detail Rate** | Percentage of product page visits that result in purchases | *Identify your most effective product pages* |
#### Product Finder Specific Metrics
| Metric | Definition | Use Case |
| --------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------- |
| **Finder Completion Rate** | Percentage of customers who complete your Product Finder | *Measure how engaging and useful your guided selling tools are* |
| **Product Finder Products Bought** | Items purchased directly through Product Finder recommendations | *Track the sales impact of your guided selling experiences* |
| **Product Finder Products Recommended** | Products suggested by your Product Finder experience | *Monitor recommendation volume and system performance* |
#### Recommender Specific Metrics
| Metric | Definition | Use Case |
| ------------------------ | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **Recommenders Shown** | Number of times your Product Recommender experience is displayed to users | *Track recommendation reach and impression volume across your site* |
| **Recommenders Clicked** | Number of times customers click on recommended products | *Measure engagement with your recommendations and identify product suggestions* |
{% hint style="info" %}
Recommender specific metrics apply only to Recommender experiences active on your site.
{% endhint %}
{% hint style="warning" %}
Recommender specific metrics should be used with the group bys: **Action** **Recommender ID** and **Action Product ID,** for accurate results. Contact Support for best practice recommender template dashboards.
{% endhint %}
#### Analyzing Recommender Data
Recommender analytics support multiple grouping dimensions to help you understand performance from different angles:
* Group by **Action** **Recommender ID:** Evaluate individual Recommender campaigns independently
* Group by **Action Product ID:** Evaluate individual products recommended within a Recommender
* Group by ***additional dimensions***
* Segment data by other product or context attributes available in your implementation (e.g; Product Title, Region Country). This helps organize and filter your data to focus on specific subsets of your Products and Recommender performance.
* Multiple grouping levels combine grouping dimensions for deeper analysis. For example, group by both Recommender ID and Product to see which products are recommended by each campaign, then add another dimension to slice the data further.
* Connecting Recommender Analytics to commercial performance: For deeper insights, cross-reference Recommender metrics with your site's core metrics
## FAQ
Is bot traffic included in my Crobox analytics?
No. Crobox identifies known bots, crawlers and automated traffic, and excludes those sessions from your metrics, so your analytics reflect real visitors.
Automated testing tools (such as Selenium or Playwright) are also excluded. The Crobox snippet does not run in these sessions, so they don't appear in your data.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.crobox.com/how-to-guides/analytics/metrics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.