-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Feature Description
Grouping the customer based on their likes and dislikes on particular product using k-mean…
-
Hi,
I have the real e-commerce data. Firstly, I've used **"lifetimes"** library for expected transactions, and expected average revenue, and CLV prediction. However, the model overfits and it fails…
-
There are API inconsistencies in the CLV module. Standardization is a big task best broken down into multiple PRs:
## PRs to be Completed In-Order
- [x] 1. Update `BetaGeoModel` predictive methods…
-
-
In the table in frontend/src/components/CustomerData.js allow for sorting based on serviceTitanLifetimeRevenue. Other relevant files might be frontend/src/sections/@dashboard/client/ClientListHead.js,…
-
We are **Allowme**, a business unit from Tempest Security Intelligence, a cybersecurity company from Brazil, Latam, with more than 22 years in operation. Allowme's mission is to help companies protect…
-
I've been asked to investigate implementing some additional "Lifetime" fields, similar to the existing "Lifetime Sales Value" field. The fields the client requires seem quite generic and generally app…
-
Pra que serve
-
time_days = 126
time_months = int(math.ceil(time_days / 30.0))
#column-selection
summary = f_and_t[['customer_id', 'frequency_btyd', 'recency', 'T',
'monetary_btyd']]
…
-
[Unrealistically high CLV estimations](https://github.com/CamDavidsonPilon/lifetimes/issues/313) [have been a common complaint](https://github.com/ColtAllen/btyd/issues/73) with the legacy `lifetimes`…