> For the complete documentation index, see [llms.txt](https://academy.gopersonal.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.gopersonal.ai/en/admin-ui/segmentation/audiences/predictive-rules.md).

# Predictive Rules

* **Affinity:**

  Customer affinity with specific product properties such as color, size, category, or brand. For example, customers whose highest affinity is with the color red.
* **Likehood to purchase:**  Probability or likelihood that a customer will make a purchase considering their behavior. The options are Normal, High or Low. 
* **Customer Lifecycle status:** Current stage or status of a customer within the customer lifecycle. The options for this status Active, Inactive and Churn. 
  1. **Active:** Customers who are currently engaged, making regular purchases, and actively participating with the brand.
  2. **Inactive:** Customers who were once active but have not engaged with the brand recently. They may not have made a purchase or interacted with the platform within a specified timeframe.
  3. **Churn:** Customers who have disengaged entirely and are considered lost or churned. These customers have ceased their relationship with the brand, and efforts may be needed to re-engage them.


---

# 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:

```
GET https://academy.gopersonal.ai/en/admin-ui/segmentation/audiences/predictive-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.