# Metrics based on pageviews
A metric is based on an event and helps to **analyze the number of collected events** (or their mean/average) and compare it to a baseline, generally the total number of unique visitors or the total number of sessions. For more information about definitions, please refer to the following [article](/reporting-and-performances/reporting/data--reports-generalities-and-definitions.md).
## The event “pageview”
This event is sent via our tag from every page where the tag is displayed.
**This event is universal and automatically sent:** You don’t have to set up anything in your campaign to use a metric based on pageviews because these events are stored in the session history in our database.
**This event is sent by the tag:** The higher the generic tag is placed on the page, the faster the event is sent to our database. It means that some events can be sent even if the visitor changes their mind and doesn’t wait for the end of the load of the page (goes back, click elsewhere, or closes the tab)
* It’s displayed as “**unique**” in the column “unique conversions” in the reports, conversions meaning “click done” when the *type of data* is “visitor”
In this case, it represents the number of visitors who have visited **at least one time a certain page** (if a unique visitor have seen it three times, the total number of pageviews will still be one)
* It’s displayed as “**total**” in the reports, conversions meaning “click done” when the *type of data* is “session”.
In this case, it represents **the total number of visits to a certain page** (if a unique visitor visits three times the same page, the total number of pageviews will be three).
### What’s inside a page view event setup?
It can be composed of:
* A single page (e.g. homepage, basket page), declared with a specific and unique URL
* Several pages (e.g. three specific product pages), declared with the three specific URLs
* A series of equivalent pages (e.g. all the product pages), declared by a specific rule (regex or other)
* etc.
## Pageview conversion rate
### **Visitor scope**
The pageview conversion rate represents the percentage of unique visitors who have visited a specific page at least one time, versus the total traffic on the variation.
#### Calculation
#### Example
88 unique visitors have seen the page
Total traffic is 880
Conversion rate = 88 / 880 \* 100 = 10%
### **Session scope**
The pageview conversion rate represents the percentage of pageviews (total of impressions of the page) versus the total number of sessions on the variation.
#### Calculation
#### Example
100 impression has been performed
The total number of sessions is 900
Pageviews conversion rate = 100 / 900 \* 100 = 11.11%
## Pageview conversion rate growth
In a testing campaign, this metric compares two pageview conversion rates (at a visitor level or a session level) and helps to identify the best performer between the two variations (the variation is compared to the baseline, which is the original version).
The growth metrics are always displayed on all variations except on the one which is used as the ***baseline***. See this [***article***](/reporting-and-performances/reporting/campaign-reporting.md) to learn how to change the baseline in a report.
---
# Agent Instructions: 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:
```
GET https://docs.abtasty.com/reporting-and-performances/reporting/metrics/metrics-based-on-pageviews.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.