alteryx / alteryx/predict-customer-churn
Potential data leakage due to some features?
- Ngôn ngữ chính
- Jupyter Notebook
- Star
- 427
- Fork
- 216
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Mô tả
Firstly, thanks for the detailed notebooks! Learnt a lot from it.
In https://github.com/Featuretools/predict-customer-churn/blob/main/churn/3.%20Feature%20Engineering.ipynb,
I assume that the features `num_25, num_50, num_75, num_985, num_100, and num_unq, etc` represent the number of specific types of transactions (e.g., number of songs played with 25% completion, 50% completion, etc.) for each customer.
Wouldnt using these features (and various transformations/aggregations on it) in the windows lead to data leakage?
Because basically we are using the information from the future or outside the given time window to create features or train a model.
I have a similar use-case where we have few customer columns like `ltv`, `nr_orders` etc which reflect value "as of today". I am not sure how to handle these in the windows that are created.
Hướng dẫn đóng góp
Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này
Đánh giá
Issue này chưa được đánh giá.