> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising_deprecated/recos-and-merch-analytics/evolution-metrics.md).

# Evolution metrics

To evaluate the effectiveness of your recommendations, the following metrics are available in the **Report tab**:

## Number of Impressions <a href="#h_01jdmhj2hj79jbpsqvzw02vpe0" id="h_01jdmhj2hj79jbpsqvzw02vpe0"></a>

The Number of Impressions represents the total times a recommendation has been displayed to users.

**How it works:** Every time a recommendation appears—whether on a product page, the homepage, or within an email—it is counted as an impression.\
**Why it matters:** This metric measures the overall exposure of your recommendations and helps you assess their visibility across your website or campaigns.

\
Number of Clicks <a href="#h_01jdmhjjsknvwf2tp5ye21gq3x" id="h_01jdmhjjsknvwf2tp5ye21gq3x"></a>
-----------------------------------------------------------------------------------------------

The Number of Clicks captures the total instances where users have clicked on a recommendation.

**Why it matters:** It shows the level of engagement generated by your recommendations and indicates whether they successfully attract user interest.

\
Number of Closures <a href="#h_01jdmhjxy4kv1cgtsarqf9xvny" id="h_01jdmhjxy4kv1cgtsarqf9xvny"></a>
-------------------------------------------------------------------------------------------------

The Number of Closures refers to the number of times users explicitly close or dismiss a recommendation.

**Examples:** This could include actions like clicking a "close" button or selecting an option to disable the recommendation.\
**Why it matters:** This metric identifies instances where recommendations may not resonate with users, providing insights into areas for improvement.

\
CTR (Click-Through Rate) <a href="#h_01jdmhkbtc8v4yxdhkp4v70f82" id="h_01jdmhkbtc8v4yxdhkp4v70f82"></a>
-------------------------------------------------------------------------------------------------------

The Click-Through Rate (CTR) is a key performance indicator that reflects how effectively recommendations encourage user interaction.

**How it’s calculated:** CTR (%) = (Number of Clicks / Number of Impressions) × 100\
**Why it matters:** A higher CTR indicates that your recommendations are relevant and engaging to your audience.

\
Closure Rate <a href="#h_01jdmhp5hsw15192m11ma3cwfz" id="h_01jdmhp5hsw15192m11ma3cwfz"></a>
-------------------------------------------------------------------------------------------

The Closure Rate measures the frequency at which recommendations are explicitly dismissed or rejected by users.

**How it’s calculated:** Closure Rate (%) = (Number of Closures/Number of Impressions)×100\
**Why it matters:** This metric highlights how often recommendations fail to capture user interest, helping you identify potential issues with content, targeting, or placement.\
\
![](/files/GhkDS6j4eFhbV7o5YtF5)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/recommendations-and-merchandising_deprecated/recos-and-merch-analytics/evolution-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
