An independent analysis inspired by the Lift × Lottomart case, with a reusable monetization-first operating framework.
<aside> 🚀 🚀 FREE STRATEGY CALL Want to grow your product through viral reach? We help teams across iGaming, mobile apps, AI products, and SaaS build creator-led organic distribution generating tens of millions of views at CPMs starting from $0.03.
<aside> 🚀 Book a free strategy call
</aside>
On the call you'll receive:
Use the published Lift × Lottomart case as a starting point for a practical acquisition-readiness review. This framework helps you define the right events, locate conversion leaks and decide when your own cohort results support the next budget increase.
Lift describes starting with retention and retargeting, optimizing for first and recurring deposits, and expanding acquisition after monetization stabilized. It reports 4.5× registration growth, roughly 65% registration-to-FTD conversion, a $5–$15 blended CPA, 75–85% of events as monetizing actions (FTD plus recurring deposits), and about 8.5 deposits per returning user.
For your own reporting, separate first-time depositors, returning depositors and recurring transactions. Define the cost scope and denominator beside each CPA, then compare cohorts at the same age. This gives you a consistent basis for deciding whether to fix the funnel or expand acquisition.
Source: Lift × Lottomart case study
PROBLEM: A large count of repeat transactions can conceal poor new-customer acquisition. A registration can be counted multiple times, a failed payment can look like an attempt, and yesterday's cohort may not have had time to convert.
FRAMEWORK: measurement integrity → first-value completion → mature-cohort economics → controlled expansion.
| Event | Definition | Deduplication | Required dimensions |
|---|---|---|---|
| Landing session | Eligible arrival with a stable session ID | Session ID | Market, source, asset, offer, timestamp |
| Registration | First completed account registration | Customer ID | Signup cohort and acquisition source |
| Verification complete | Required verification passed | Customer ID + state transition | Failure reason, time to complete |
| Deposit attempt | Payment submitted for processing | Payment-attempt ID | Method, amount band, response |
| FTD | First successful eligible real-money deposit | Customer ID, once | Success time, market, source |
| Returning depositor | Existing FTD customer with a later successful deposit | Customer ID in fixed window | Original FTD cohort |
| Recurring deposit | Successful deposit after the first | Transaction ID | Customer ID, date, net value |
Use only eligible adult users in permitted markets, with operational exclusions respected. Keep self-excluded or restricted users out of acquisition and reactivation audiences. Marketing reports should use aggregate or pseudonymous records.
| Metric | Formula | What it answers |
|---|---|---|
| Registration → FTD | Unique new FTD customers / eligible registrations in same mature cohort | Does signup lead to first value? |
| Attempt success | Successful payment attempts / valid submitted attempts | Is payment processing working? |
| Returning depositor rate | Original FTD users depositing again / original FTD cohort | How many people return? |
| Deposits per returning user | Recurring transactions / unique returning depositors | How frequently returning users transact? |
| New-FTD CAC | Defined acquisition costs / unique new FTD customers | What does a new depositor cost? |
| Cohort contribution | Recognized net revenue less relevant variable costs | Does the cohort support growth? |
Set cohort windows before comparison. A seven-day acquisition cohort may require a later conversion cutoff. Align geographies, attribution and cost inclusion before comparing channels. Deposit amount is not revenue or profit.
Ignore as scale criteria: raw registration totals, total event counts, the cheapest click and a blended action CPA whose denominator mixes new and returning users. Keep them as diagnostics if useful, but do not substitute them for new-customer economics.
Work from the last reliable event backward. If registration-to-FTD falls, split it into verification completion, payment initiation and payment success. Compare platform, market, payment method, source and offer only where sample sizes support a decision.
| Symptom | First check | Action owner | Repair before scale |
|---|---|---|---|
| Visits without registrations | Destination load and message match | Growth + product | Correct broken pages or misleading promise |
| Registrations without verification | Error and abandonment reasons | Product + operations | Clarify steps and repair failures |
| Verified users without attempts | Offer clarity and payment availability | Product + payments | Make eligible methods and terms understandable |
| Attempts without successful deposits | Processor response codes | Payments | Fix technical failures and routing |
| FTDs without healthy later value | Cohort mix and experience | Analytics + product | Diagnose quality; avoid blindly buying more |
| Report drops but source events do not | Event pipeline and reconciliation | Data owner | Repair measurement before campaign cuts |