py-why / py-why/EconML

True TE estimates in customer segmentation example

Open
#720 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
4.8k
Forks
827
PR merge metrics
No merged PRs in 30d

Description

Hi, I have a couple of questions for Case Study - Customer Segmentation at An Online Media Company

  1. In the true te estimate part, why was it not just gamma_fn(X) but instead price*gamma_fn(X)/demand? Because I see the formula in DGP is Y = gamma(X).T + beta(X,W), then I presume gamma(X) is the CATE.
  2. How should we actually interpret the CATE(X) when the Y and T were log transformed? As I understand, The CATE(X) interpretation when using raw Y and T is for example CATE 0.3 means that on certain X value, the Y will change by 0.3 with the change in treatment. I'm not sure with the log transformation being used here.

I appreciate your responses. Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CustomerScenarios/Case Study - Customer Segmentation at An Online Media Company.ipynb notebook, especially the true TE estimate section and its DGP formula. Review how the notebook defines gamma_fn, price, demand, Y, and T, then clarify the rationale for the estimate and how to interpret CATE after log transformation. Done means the notebook answers both questions clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.