Quick answer: A retention manager’s weekly reporting cadence should cover four areas: acquisition quality (cohort conversion, revenue per registration), engagement health (deposit frequency shifts, session decline, dormancy onset), monetization (GGR/RTP by game, bonus vs. real-money split, payment failure rates), and campaign performance (per-channel conversion, reactivation recovery, segment migration). The point isn’t to admire the numbers — it’s to surface the players and segments that need an intervention this week, before churn hardens.
The real problem: most retention teams report monthly and react too late
Ask a CRM manager at a growing operator how often they look at retention data, and the honest answer is usually “when the monthly deck is due.” That cadence is built around reporting to management, not around running the retention operation itself.
The problem is that player behavior doesn’t move on a monthly cycle. A high-value player who deposited twice a week for three months can go silent in seven days. A bonus campaign can quietly subsidize play on titles that were already profitable, burning margin you’ll only notice 30 days later. An acquisition channel can start delivering registrations that never reach first deposit — and by the time the monthly cohort report exposes it, you’ve spent another month’s budget on it.
Weekly reporting closes that gap. It’s not about producing more dashboards; it’s about running a small, fixed set of reads every week that each map to a decision — who to message, what to pause, where to shift budget. Below are the twelve reports that matter, organized by the operator question each one answers.
What counts as a “retention report” (and what doesn’t)
A retention report is any recurring data read that changes what your CRM team does next. That’s the operational test. A vanity chart that shows total registrations climbing is not a retention report. A cohort funnel that shows last week’s signups stalled before first deposit — so you reallocate spend away from the channel that produced them — is.
In iGaming specifically, a useful retention report shares three traits:
- It’s segment-aware. “Average LTV is up 4%” tells you nothing actionable. “VIP-tier LTV is up 9% but mid-value LTV dropped 6%” tells you exactly where to look.
- It separates real money from bonus. Blended GGR and RTP numbers hide the true cost of your promotional spend. The reports that matter let you isolate bonus-funded play.
- It’s available without a ticket to BI. If producing the report requires a data analyst and a two-day turnaround, it won’t get run weekly. The reports below are the ones a single CRM manager can pull and act on the same day.
Why generic tools make weekly retention reporting nearly impossible
Operators who run retention on a generic ESP (Mailchimp, Customer.io) or a horizontal CRM (HubSpot, Salesforce) hit the same wall. These tools were built for contacts and deals, not for players with deposits, wagering events, bonus wallets, and game sessions. So the metrics a casino actually needs — first-deposit conversion by cohort, GGR by provider, deposit-frequency decay — simply don’t exist as native reports. Teams end up exporting raw data to spreadsheets and rebuilding the same pivot tables every week, which is exactly the friction that kills a weekly cadence.
Enterprise iGaming platforms solve the data model but introduce a different problem: the reports live behind BI configuration, custom dashboards, and often a data team’s roadmap. A growth-stage operator with one or two CRM people can’t run a twelve-report weekly rhythm if half of them require an analyst to build.
The practical requirement is an iGaming-native CRM where the player data model and the reporting layer are the same system — so deposit, game, and campaign data are already structured the way a retention manager needs to read them. Platforms like InTarget are built around exactly this: behavior-based segmentation, lifecycle automation, and purpose-built iGaming analytics dashboards sit on one unified player record, so the reports below are filters-and-export operations, not data engineering projects.
The 12 weekly casino retention reports, by operator question
Acquisition quality — “Are the players we’re paying for actually worth keeping?”
1. Registration-to-first-deposit cohort conversion Group last week’s registrations by signup period and track what share reached first deposit. A healthy operation watches this weekly because a drop signals either a funnel problem (KYC friction, payment issues) or a channel-quality problem — and the two demand different fixes. This is the core read of a registration cohort report: of the players acquired in a given week, how many deposited, and how much they generated.
2. Revenue per registration by UTM source / refcode Registration volume is a vanity metric; revenue per registration is the truth. Block your cohort data by UTM campaign or affiliate refcode and you’ll see which channels deliver depositors versus tire-kickers. Run weekly, this is what lets you cut a bleeding channel mid-month instead of after.
3. Second- and third-deposit conversion (early-habit formation) First deposit is necessary but not sufficient. The players who deposit a second and third time within their first weeks are the ones forming a habit — your future retained base. A weekly read on repeat-deposit conversion by cohort tells you whether your onboarding and welcome-sequence automation is doing its job before the window closes.
Engagement health — “Which active players are quietly slipping?”
4. Deposit-frequency decay The single most important early-churn signal in iGaming. Build a segment of players whose deposit frequency dropped meaningfully versus their own prior pattern — e.g., from 3+ deposits a week to one. These players are still “active” by any monthly definition, but they’re on the way out. Catching them weekly is the difference between a reactivation nudge and a win-back campaign that costs three times as much.
5. Session / play-frequency decline Deposits lag behavior. A player often reduces session frequency before they reduce deposits. Tracking week-over-week session decline gives you the earliest possible churn warning — and a reason to trigger a re-engagement touch while the player is still on-platform.
6. New dormancy onset (the 7/14/30-day tripwire) Rather than one monolithic “inactive” list, run a weekly report on players crossing dormancy thresholds this week — newly hit 7 days no login, newly hit 14 days no deposit. Freshly dormant players reactivate far more cheaply than long-gone ones. The weekly cadence is what keeps the intervention early.
7. Segment migration (lifecycle stage movement) Each week, track how players moved between lifecycle stages — activation → habitual, habitual → at-risk, at-risk → reactivated. This is your retention scoreboard. If more players are sliding down than climbing up, your automation needs work, and this report tells you which transition is leaking.
Monetization & risk — “Where is margin actually coming from, and where is it leaking?”
8. GGR and RTP by game and provider A casino game metrics report ranks bet volume, GGR, and RTP across titles, providers, and game types. Weekly, this surfaces abnormal RTP (a possible bonus-abuse or configuration issue) and shows which studios are carrying revenue — directly informing the offers and game recommendations your retention campaigns push.
9. Bonus vs. real-money GGR split The report that protects your margin. By separating real-money play from bonus-funded play, you see the true cost of your promotional calendar. If a bonus drives most of its volume on high-RTP titles, the headline offer cost understates the real revenue hit. Run this weekly during any active promo cycle.
10. Payment-system performance and failure rates Deposit failures are silent churn. A transactions report blocked by payment system and filtered by status shows failure rates per provider and country. A spike in declines on one method — especially in a key market — is an emergency, not a monthly footnote. Weekly monitoring catches provider incidents before they cost you a week of deposits.
Campaign performance — “Is our retention work actually moving revenue?”
11. Per-channel campaign conversion (email vs. SMS vs. push) Opens and clicks are inputs; deposits are the outcome. With per-step conversion attribution, you can see revenue per message, per channel, per campaign — and compare email, SMS, and push effectiveness on the same scale. Weekly review tells you where to shift volume and which sequences to retire.
12. Reactivation campaign recovery rate Close the loop on your win-back work: of the dormant players entered into reactivation flows this week, how many returned and deposited? A weekly recovery-rate read tells you whether your reactivation offers and timing are working, and feeds directly back into report #6. This is the report that proves retention spend is generating return, not just activity.
A simple weekly cadence framework
You don’t need to run all twelve as twelve separate sit-downs. Group them by the decision rhythm:
| Day | Focus | Reports | Decision it drives |
|---|---|---|---|
| Monday | Engagement triage | 4, 5, 6 | Which players get an intervention this week |
| Monday | Lifecycle scoreboard | 7 | Where automation is leaking |
| Wednesday | Campaign performance | 11, 12 | What to scale, pause, or retire |
| Wednesday | Acquisition quality | 1, 2, 3 | Where to shift acquisition budget |
| Friday | Monetization & risk | 8, 9, 10 | Margin protection, payment incidents, offer tuning |
The logic: start the week by identifying who needs action (engagement and lifecycle), check mid-week whether your campaigns are working, and close the week on margin and risk so nothing structural is bleeding into the weekend. A single CRM manager can run this whole rhythm in a few hours a week when the reports live inside the CRM rather than in exported spreadsheets.
Where InTarget fits
Most of the reports above fail in practice not because operators don’t understand them, but because producing them weekly is too much work. That’s the constraint InTarget is built around. The three analytics dashboards — Registration Cohort Metrics, Transactions Metrics, and Casino Game Metrics — cover reports 1–3 and 8–10 directly, with filtering by UTM source, refcode, country, payment system, and money type, and one-click CSV export. The engagement and lifecycle reports (4–7) are built from behavior-based player segments that update in real time, and campaign performance (11–12) comes from per-step conversion attribution on every email, SMS, and push. Because it’s all one iGaming-native CRM — typically live within about a week with free data migration — a single retention manager can actually sustain a weekly reporting rhythm without a BI team behind them.
FAQ
How often should a retention manager actually run these reports? Weekly is the right default for a growing operator. Player behavior shifts within days, so a monthly cadence consistently catches churn signals too late to act on cheaply. Some reports — payment failures during a provider incident, or campaign performance during an active promo — justify a daily glance.
Can a single CRM manager handle twelve weekly reports? Yes, if the reports live inside the CRM rather than in exported spreadsheets. The work that makes weekly reporting unsustainable is rebuilding pivot tables, not reading the data. With purpose-built dashboards and behavior-based segments, the full cadence is a few hours a week.
Why separate bonus play from real-money play in reports? Blended GGR and RTP hide the true cost of promotions. Bonus-funded play on high-RTP titles can make an offer look cheaper than it actually is. Separating money types is the only way to evaluate the real margin impact of your retention and reactivation campaigns.
What’s the difference between these and the reports our BI team produces? BI reports are typically deep, custom, and slow — excellent for quarterly strategy, poorly suited to a weekly operating rhythm. Retention reports are fast, recurring reads that each trigger an immediate action. The two are complementary; this list is about the weekly operating layer.
Do generic CRMs or ESPs support this kind of reporting? Not natively. Tools built for contacts and deals lack the iGaming data model — deposits, wagering events, bonus wallets, GGR/RTP — so the metrics either don’t exist or require manual export and reconstruction every week, which is what breaks the cadence. An iGaming-specific CRM has these structures built in.