# Browsing metrics

The navigation metrics are available for tests and personalizations and must be selected in the [Goals step](https://docs.abtasty.com/web-experimentation-and-personalization/campaign-flow-goals-step) of the campaign flow to appear in the reports.

{% hint style="info" %}
**Good to know:** these metrics are retroactive. If you forget to add them at the Goals step, you can add them after the start of your campaigns, and the data will be displayed all the way back to the beginning, without any loss.
{% endhint %}

## Bounce metric <a href="#id-01gqj84yc10ykggyry0t83m11b" id="id-01gqj84yc10ykggyry0t83m11b"></a>

### **The event bounce** <a href="#h_01jbv33p8w657vypw9qm8phgb5" id="h_01jbv33p8w657vypw9qm8phgb5"></a>

A “bounce” is recognized and sent via our tag each time a visitor lands on a targeted page and decides to leave the website immediately after having seen the tested page.

**A visitor can only bounce once.**

This event is sent via our tag from every targeted page(s).

### **The bounce rate** <a href="#id-01jbv34q6ggmr8d907x505nkah" id="id-01jbv34q6ggmr8d907x505nkah"></a>

The bounce rate represents the **percentage of unique visitors** who have bounced in a campaign.

It's available on the *type of data: session* only.

#### Calculation <a href="#h_01jbv35hqaw90jywhv9xc7689e" id="h_01jbv35hqaw90jywhv9xc7689e"></a>

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-f9884a55cdd7d78f880e5c85e14edcf507feb2a3%2Febf16065048b2e58254469e4ef9e4677.png?alt=media)

#### Example <a href="#h_01jbv35c40kd6eqrzgs309sscw" id="h_01jbv35c40kd6eqrzgs309sscw"></a>

100 visitors have bounced on the targeted page(s) during their session(s).

Total number of unique visitors in the test variation is 1,000

Bounce rate = 100 / 1,000 \* 100 = 10%

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-22cd4348deb180b26addea1d9d3f728283b8c74b%2Fa8c12e7aeb342fd943a4bd23f8905e31.png?alt=media)

## Exit rate metric

The Exit Rate metric lets you measure how often users leave your site during or after exposure to a campaign. This helps you assess the real impact of your A/B tests on user retention and engagement.

It helps you:

* Spot variations that drive users to exit prematurely
* Monitor exit behavior on key pages like /cart, /pricing, or landing pages.
* Add behavioral depth to your A/B test results — beyond conversions.

#### Calculation

$$
Exit Rate = (Pageviews with isExit = true) ÷ (Total Pageviews matching the condition)
$$

* A pageview is counted **each time a tracked page is viewed** (based on your setup using contains, exact match, or regex).
* A pageview is flagged as isExit = true **when the user leaves the website from that page**, without navigating to another internal page.

#### Example

Let’s say you create an Exit Rate tracker with the condition:

`URL contains /cart`

Then the following happens:

* You visit the /cart page **3 times** during different sessions
* You leave the site from that page **once**

The result will be:

$$
Exit Rate = 1 exit / 3 total pageviews = 33.33%
$$

Later, if you return directly to /cart and exit again, it becomes:

$$
Exit  Rate = 2  exits / 4  total  pageviews = 50%
$$

This gives you a clear view of how likely users are to abandon the site from a critical page like the cart — which is particularly useful for e-commerce optimization.

{% hint style="info" %}
To use the Exit rate, read [How to set up an Exit Rate tracker](https://docs.abtasty.com/assets-library/trackers-page/how-to-set-up-an-exit-rate-tracker) article.
{% endhint %}

## Number of pages viewed metric <a href="#h_01jbv7b0x6jzqd3ejx43ym2hts" id="h_01jbv7b0x6jzqd3ejx43ym2hts"></a>

### **The event pages viewed** <a href="#h_01jbv7b0x6acahz5r3aqb16jem" id="h_01jbv7b0x6acahz5r3aqb16jem"></a>

Each time a page is loaded on the visitor's browser, AB Tasty counts it. All the browsing data are stored in the [AB Tasty cookie session](https://docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy).

### **The metric average number of pages viewed** <a href="#id-01gtvvvqgd726516dxac83e7bg" id="id-01gtvvvqgd726516dxac83e7bg"></a>

The metric average number of viewed pages per visit is the average quantity of pages that have been viewed per session on the entire perimeter where the AB Tasty tag is placed, **starting from when the visitor is assigned to a campaign**.<br>

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-e3c7c4ebd81794e7618d1ffb746bcf8dae894028%2F7c309f1fcc600fff56d8ad319a45c474.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### Calculation <a href="#h_01jbv7mmsbsddvynfna5c4hfv1" id="h_01jbv7mmsbsddvynfna5c4hfv1"></a>

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-44078725c162db1d576d1707eeaa53c67671d8db%2F03e3b3adfb8db42108f2772a7ce3bb0f.png?alt=media)

#### Example <a href="#h_01jbv7mxxrpp5w2zj4yra3k73w" id="h_01jbv7mxxrpp5w2zj4yra3k73w"></a>

Visitor A has visited the website 3 times during the campaign: session #1 for 5 viewed pages, session #2 for 6 viewed pages, and session #3 for 7 viewed pages.

Visitor B has visited the website 2 times during the campaign: session #1 for 10 viewed pages, session #2 for 12 viewed pages

Average viewed pages = (5+6+7+10+12) / 5 = 8<br>

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-87333037dd2373a38cf784c808f2e2f0c914a70c%2Fd10b0cb8eeb9290e8e696c563344b5e6.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

In a campaign, this metric compares two amounts of average viewed pages and helps to identify the best performer between 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*** ](https://docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting)to learn how to change the baseline in a report.

#### Calculation <a href="#h_01jbv7r0wa03ga9bjeg7knryh9" id="h_01jbv7r0wa03ga9bjeg7knryh9"></a>

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-7f791d775ca0ae31a2f01d97a2f8956a86bc0548%2Ff67b2fd09d17b2a1f29364db9038516e.png?alt=media)

## Revisit metric <a href="#id-01gqj84yc1y5ev5a7d74h1gxb2" id="id-01gqj84yc1y5ev5a7d74h1gxb2"></a>

#### **Revisit event** <a href="#id-01gtxtxcsf279q039wjbxztgp2" id="id-01gtxtxcsf279q039wjbxztgp2"></a>

The number of revisits represents the number of unique visitors who have triggered the campaign **at least two times** in **at least two distinct sessions**.

#### **Metric revisit rate** <a href="#id-01gtvvvqgdkt8qqv1t86y1dek2" id="id-01gtvvvqgdkt8qqv1t86y1dek2"></a>

The revisit rate is the **percentage of unique visitors who have triggered the campaign at least two times** in at least two unique sessions.

#### Calculation <a href="#h_01jbv957vmx2235dp4x1tngabd" id="h_01jbv957vmx2235dp4x1tngabd"></a>

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-f3a41723493226569bd06f38fb92c6aab1775bd2%2F11e782c079b244674df233a4e790f983.png?alt=media)

#### Example <a href="#h_01jbv95cwmsq5d74x2seqspvwp" id="h_01jbv95cwmsq5d74x2seqspvwp"></a>

100 unique visitors have visited the targeted page(s)

80 unique visitors have visited the targeted page(s) only once

20 unique visitors have visited the targeted page(s) at least two times

Revisit rate = 20 / 100 \* 100 = 20%

In a campaign, this metric compares two percentages of revisit rates to help identify the best performer between 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*** ](https://docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting)to learn how to change the baseline in a report.
