> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/predictive-models/customer-lifetime-revenue-clr/customer-lifetime-revenue-clr-explanation.md). # Customer lifetime revenue (CLR) explanation ### Introduction Once we have established the recency, frequency, and monetary value summary statistics, we can input these into algorithms to estimate the total customer lifetime revenue. This encompasses the sum of their previous spending up until the time the model is run. Additionally, we forecast the customer's likelihood of re-engagement and repurchasing based on their behavioral patterns. The sum of these two estimates creates the customer lifetime value, representing the anticipated lifetime engagement and spending of a customer with the company. {% embed url="" %} This measure can be used to evaluate the ROI of customer acquisition costs, measure the overall increase or decrease in the company's customer lifetime revenue, and track changes in customer lifetime revenue over time. The customer lifetime revenue can further be used to determine the appropriate amount of investment in new customer acquisition. By analyzing each customer's data, we train models to identify patterns in their behavior and predict their likelihood of repurchasing. Our goal is to accurately identify customers who are likely to repurchase and those who are not and assign weights accordingly to assess the accuracy of our models. ### Probability re-engagement Calculating the probability of a customer's re-engagement or repurchase is a crucial aspect of customer lifetime value estimation. A representative customer who made multiple purchases from a store exemplifies this concept. The likelihood of their engagement with the store at the time of purchase is 100%, but as time passes, this probability diminishes. With increasing temporal distance from their last purchase, the likelihood of re-engagement also declines. {% embed url="" %} ### ### Example probability re-engagement usage An important aspect of customer lifetime value is determining the probability of a customer reengaging or repurchasing from a store. For instance, if a company scores the reengagement probability for all its customers, it can conduct a targeted campaign for customers with a moderate probability of reengagement, say 40% to 60%. This group can then be divided into an A/B component, with the treatment marketing campaign or email campaign only given to the A group while the B group is not engaged. {% embed url="" %} At the conclusion of the campaign, a causal difference can be measured between the two groups. It is expected that the A group's performance would be what was predicted, with the delta between the two groups representing the impact of the A/B group. The probability of reengagement is a powerful segmentation tool that can be spiced by different segments within the group. The general idea is to use it as a predictive tool, with a good idea of how the two buckets will perform in the test, and then evaluate the causal impact of the test by assessing the delta on the other side. --- # 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.chord.co/model-your-data/predictive-models/customer-lifetime-revenue-clr/customer-lifetime-revenue-clr-explanation.md?ask=&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.