> 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/assets-library/creating-and-managing-triggers/list-of-trigger-criteria/minimum-pages-viewed-criterion.md).
# Minimum Pages viewed criterion
The Minimum pages viewed criterion is a triggering criterion that enables defining a [segment](/assets-library/creating-and-managing-segments.md).
To learn how to create a segment, please refer to this [article](/web-experimentation-and-personalization/targeting-step/how-to-create-a-segment-who-section.md).
## đź“– Definition
The minimum pages viewed is a criterion that allows you to trigger your campaign based on a specific number of pages viewed by your visitors. It helps build your strategy around visitors' engagement wherever our tag can count those visited pages.
## ⚙️ Configuration
You have to first select the right operators. You have two solutions, either:
* `is equal to or greater than`
* `is equal to or lower than`
In the value field, you just have to declare the right number of pages that will fit your use cases.
## đź’ˇ Use case
Let’s imagine you want to target visitors that wander on your website. You could set a trigger based on your average number of visited pages’ number to identify visitors that spend more time than average. If that number is `5`, you could set the configuration to `6` to display the campaign to visitors that exceed that number.
## 🔎 How does it work?
ABTasty gets this information from our main `ABTasty` cookie. We have a specific key `pvis` (that stands for “Pages viewed in Session”) that stores this information. Every time a visitor visits a new page, this number is incremented.
**Need additional information?**
Submit your request at
Always happy to help!
---
# 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/assets-library/creating-and-managing-triggers/list-of-trigger-criteria/minimum-pages-viewed-criterion.md?ask=&goal=
```
`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.