> 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-segments/list-of-segment-criteria/purchase-frequency-criterion.md).
# Purchase Frequency criterion
The Purchase Frequency criterion is a segmentation 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 Purchase frequency targeting criterion enables you to create a segment of visitors based on the frequency of the purchases they made within a defined period of time.\
The Purchase frequency criterion is based on the transaction tag, which enables you to collect specific information on the buying patterns of users.
## ⚙️ Configuration
To configure the Purchase frequency criterion, apply the following steps:
1. Select the type of interval from the first drop-down list: `more than` (strictly higher) or `less than` (strictly lower).
2. In the *Time(s)* field, manually enter the number of desired purchases.
3. Select the type of interval from the first drop-down list: `within`, `beyond` or `between`.
4. In the *Day(s)* field, manually enter the value(s) depending on the chosen interval.
{% hint style="warning" %}
For data confidentiality reasons, you cannot target visitors who made their last purchase over a year (365 days) ago.\
Keep in mind that this duration is depending on your browser settings and policy.
{% endhint %}
You can also refine targeting by adding advanced conditions, thus defining the last purchase based on:
* payment method;
* delivery method;
* SKU code of the product;
* product category;
* transaction amount;
* coupon used.
## đź’ˇ Use case
Example: a segment with people that have made more than 5 purchases within the last 30 days using an American Express card.\
All the values that need to be filled in are your websites’ variables. **You have to enter the exact string (without quotes)**: `Paypal`, `clickandcollect` etc. and match the spaces and special characters.\
However, you don’t need to match lowercase and uppercase letters. For example, `Paypal` and `paypal` will both work. You don’t need to specify the currency, just enter the amount in your website’s currency.
## 🔎 How Does It Work?
Within the tag, we created an object called **`ABTastyData`** that contains information about your visitors’ journey. Inside this object, we store transactional data in locations called **transaction** and **items**.
This is performed when you integrate the transaction tag on your website. With that integration, the generic tag receives [***hits***](https://developers.abtasty.com/docs/data/universal-collect/uc-hits#transaction) from the transactional tag when your visitor validates a transaction.
**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-segments/list-of-segment-criteria/purchase-frequency-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.