Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question for a subscription + one off business using LTVision #83

Open
fbahacker21 opened this issue Jan 4, 2025 · 1 comment
Open

Comments

@fbahacker21
Copy link

Summary

I was working on the "pLTV Opportunity Size Estimation" section of the model

and just curious an example for an ecommerce brand with 80% subscription revenue 20% one off purchase, would you recommend I use scenario 1 or scenario 2 to test the model ?

@fbahacker21 fbahacker21 changed the title Case for a Question for a subscription + one off business using LTVision Jan 4, 2025
@QiongWu-Q
Copy link
Contributor

QiongWu-Q commented Jan 10, 2025

Hi there~ Thanks for testing LTVision Module 1 and asking the very first question! :) Which scenario to use depends on when user identification happen in relation to 1st revenue event. We have worked with advertisers with hybrid business models like yours, from an insights perspective, if your eCommerce customers and Subscription customers share their PII data at different point in time in relation to their 1st revenue event (e.g. Subscription customers might share days before paying and eComm customers share during checkout), then you could have two separate datasets and run Module 1 twice to evaluate the opportunity size separately and then combine the two estimated incremental revenue; from a pLTV model perspective, you don't necessarily need to separate the two types of customers, because the end goal is the same: to acquire more long-term high-value customers, despite which engagement type they chose. Let me know your thoughts! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants