> 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/landing-page-criterion.md).

# Landing Page criterion

Landing 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 <a href="#h_01hhpygwdzt9fhcmk07n3wtz6n" id="h_01hhpygwdzt9fhcmk07n3wtz6n"></a>

The landing page criterion allows you to trigger your campaign depending on which page your visitor landed during their visit on your website.

## ⚙️ Configuration <a href="#h_01hhpygwdzt9fhcmk07n3wtz6n" id="h_01hhpygwdzt9fhcmk07n3wtz6n"></a>

First, you will have to choose which operator you want to use to identify a 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 operator chosen.

<figure><img src="/files/5yT4kuKuAQ531t4PUJcf" alt="" width="563"><figcaption></figcaption></figure>

## 🔎 How does it work? <a href="#h_01hhpyw4abkqmjd1yk9a78xfk5" id="h_01hhpyw4abkqmjd1yk9a78xfk5"></a>

The AB Tasty tag captures every session’ first URL and stores it at the beginning of the session inside one of our cookies: `ABTastySession`. This information is always stored, for each and every session.

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!

<img src="/files/Zq88Ca7RlS8Bwu4Y3r4c" alt="" width="146">


---

# 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/landing-page-criterion.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.
