> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/fr/cas-dusage/data-activation/retain-customers/identify-a-churn-risk-with-rfm-segmentation.md).

# Identifier un risque d'attrition avec la segmentation RFM

## Description du cas d’usage

🎯 Objectif :

Détectez les clients présentant un risque de churn et activez-les.

Utilisez la segmentation RFM pour créer un segment d’audience présentant un risque de churn et lui envoyer une campagne dédiée (campagne « Vous nous manquez », enquête…).

🔧 Complexité : 2/5

💰 ROI : faible

## Configuration du cas d’usage

Étape 1 : créez un segment avec des conditions représentant un risque de churn (utilisez la fonctionnalité Augmented User Attributes pour créer un score, un ratio, un indicateur ou une valeur booléenne représentant le churn, par exemple le nombre de commandes au cours des 6 derniers mois, le nombre de visites, de clics…)

Étape 2 : créez un flux pour envoyer les utilisateurs du segment créé précédemment vers une solution d’emailing


---

# 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://doc.commandersact.com/fr/cas-dusage/data-activation/retain-customers/identify-a-churn-risk-with-rfm-segmentation.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.
