> 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/previous-page-criterion.md).
# Previous Page criterion
Previous page 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 previous page criteria allow you to trigger your campaign based on a specific “previous page” URL. That will allow you to capture your visitor in specific and determine the navigation context.
## ⚙️ Configuration
First, you will have to choose which operator you want to use to identify the page or a set of pages.
Once you do, you can proceed and enter the specific URL or piece of URL that will identify the page(s) to target, depending on the chosen operator.
## đź’ˇ Use case
Through the previous page criteria, you can trigger the campaign for the visitors that just left your cart process. To do that, you can go through the following steps:
1. Declare your cart URL as the previous page
2. Exclude the cart page and the following page (checkout, shipping, payment, confirmation) from the targeting, to avoid displaying your campaign to user that proceed with the normal checkout procedure
## 🔎 How does it work?
The ABTasty reads that information directly from the browser current page’ `document.referrer`. If there is no value in that object, the ABTasty tag gets the value from one of its specific resources (`window.ABTasty.urlHistory.previous`).
{% hint style="warning" %}
Be careful, the Back Button function of the browser does not change the `document.referrer` so the Previous Page criterion will not work if the visitors use this function.
{% endhint %}
**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/previous-page-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.