> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/sales-insights/set-up-and-manage-sales-insights/change-the-customer-segmentation-period.md).

# Change the customer segmentation period

Choose how much purchase history Sales Insights uses to segment customers, so the segmentation better reflects your customers’ buying cycle.

{% hint style="info" %}
**Early access:** This feature is available to participating Sales Insights customers.\
**User permissions:** Administration.
{% endhint %}

By default, customer segmentation uses purchase activity from the last **12 months**. You can change this to a rolling period from **6 to 60 months (5 years)**.

If your customers purchase less frequently, a longer period such as 24 or 36 months might better reflect their buying cycle. When choosing a period, consider seasonal buying patterns and how much purchase history is available in your database.

### Change the segmentation period

You can choose the segmentation period when you first set up customer segmentation or change it later.

<div align="left"><figure><img src="https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FTeGj9Vb8FkHkpeXzX369%2FScreenshot%202026-09-28%20at%2016.30.41.png?alt=media&amp;token=310972cd-c849-45a4-85f4-a189ff00e312" alt="" width="375"><figcaption></figcaption></figure></div>

To change the period for an existing configuration:

1. Open the database in Sales Insights.
2. Open the three-dot administration menu and select **Edit configuration**.
3. On the **Data** step, under **Include customers who purchased in the last**, enter a period from 6 to 60 months.
   * If additional threshold sets are configured for the database, an alert displays. These threshold sets are not updated automatically when you change the segmentation period.
4. Select **Next** and continue through the setup.
5. Review the **Frequency**, **Monetary**, and **Recency** thresholds.
6. On the final step, select **Done** to save your changes.

#### See how the period affects segmentation

The new period recalculates the thresholds in the setup. It is also reflected in the Frequency and Monetary steps, so you can review the thresholds against the purchase history being analyzed.

<div align="left"><figure><img src="https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2F4B8sHWX8psDYHeGp5bS1%2FScreenshot%202026-09-25%20at%2016.04.56.png?alt=media&amp;token=7940229f-d154-4645-a76d-d77269c7c67f" alt="" width="563"><figcaption></figcaption></figure></div>

Customer counts, purchase totals, and segment membership might change because Sales Insights is assessing purchasing behavior over a different period.

The selected period applies to the database, so everyone using that database sees customer segmentation based on the same period.

### Review additional threshold sets

Changing the segmentation period does **not** automatically recalculate additional threshold sets for specific customer groups.

After you save the new period, open **Edit threshold sets** and review each additional set to make sure its thresholds are still appropriate.

<div align="left"><figure><img src="https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FP6ZYrbnIHkHgjDNglshL%2FScreenshot%202026-09-28%20at%2016.26.03.png?alt=media&amp;token=1e7c60d4-fae1-46e1-bab7-7ed25343d63d" alt="" width="563"><figcaption></figcaption></figure></div>

The Frequency and Monetary headings show the current segmentation period. Select **Recalculate** to generate thresholds based on the new period, then adjust them if needed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/sales-insights/set-up-and-manage-sales-insights/change-the-customer-segmentation-period.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
