alteryx / alteryx/predict-customer-churn

Potential data leakage due to some features?

Aberta
#27 0 comentários 0 reações 0 responsáveis Ver no GitHub
Linguagem predominante
Jupyter Notebook
Estrelas
427
Forks
216
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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.

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.