Retention & Heatmaps
Retention & Heatmaps
Section titled “Retention & Heatmaps”Retention metrics and time-based heatmaps help you understand how often users return and when they’re most active. Use this data to optimize release timing, support hours, and engagement strategies.
Heatmap
Section titled “Heatmap”The dashboard displays a heatmap of execution activity across time dimensions (e.g., hour of day, day of week). Use it to visualize when executions occur most frequently.
Retention Metrics
Section titled “Retention Metrics”The dashboard shows retention metrics for each project. Typical metrics include:
| Metric | Description |
|---|---|
| Day 1 retention | % of users who execute again within 24 hours of first use |
| Day 7 retention | % of users who return within 7 days |
| Day 30 retention | % of users who return within 30 days |
| Cohort view | Retention by first-use date |
Report Generation
Section titled “Report Generation”The dashboard allows you to generate exportable reports for a project:
| Format | Description |
|---|---|
| CSV | Comma-separated values for spreadsheets |
| JSON | Structured JSON for programmatic use |
Use reports for:
- Offline analysis
- Sharing with stakeholders
- Archiving historical data
Keysystem Funnel
Section titled “Keysystem Funnel”The dashboard tracks the keysystem conversion funnel with metrics such as:
- Checkpoint page views
- Ad completions
- Key generations
- Conversion rates between steps
Use this to optimize your keysystem flow and ad placement.
Revenue Dashboard
Section titled “Revenue Dashboard”The dashboard displays revenue metrics from ad providers and keysystem monetization. Use this to understand earnings and optimize ad configuration.
Time-Based Heatmaps
Section titled “Time-Based Heatmaps”Heatmaps visualize when executions occur across time dimensions:
Dimensions
Section titled “Dimensions”| Dimension | Description |
|---|---|
| Hour of day | Executions by hour (0–23) |
| Day of week | Executions by weekday (Mon–Sun) |
| Hour × Day | Heatmap grid: rows = day, columns = hour; color = execution count |
Example Heatmap Reading
Section titled “Example Heatmap Reading” Mon Tue Wed Thu Fri Sat Sun00:00 ░░ ░░ ░░ ░░ ▒▒ ▒▒ ▒▒12:00 ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒18:00 ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓Darker cells = more executions. This example suggests peak usage in evening hours (18:00) and higher weekend activity.
Interpreting Patterns
Section titled “Interpreting Patterns”Common Patterns
Section titled “Common Patterns”| Pattern | Interpretation |
|---|---|
| Evening peaks | Users are home from school/work; typical for Roblox audience |
| Weekend spikes | More free time; good for releases and announcements |
| Flat distribution | Global audience or 24/7 usage (e.g., automation) |
| Single peak | Concentrated in one timezone; consider expansion |
Actionable Insights
Section titled “Actionable Insights”- Release timing — Launch updates during peak hours for maximum visibility
- Support — Staff support during high-activity windows
- Maintenance — Schedule downtime during low-activity periods
- Marketing — Target ads or Discord announcements before peak times
Retention vs. Heatmap Use Cases
Section titled “Retention vs. Heatmap Use Cases”| Use Case | Best Tool |
|---|---|
| ”Do users stick around?” | Retention metrics |
| ”When should I release an update?” | Heatmap (hour × day) |
| “Which cohort is most engaged?” | Cohort retention |
| ”When is the best time for Discord announcements?” | Heatmap |
| ”Is my script a one-time or recurring use?” | Retention (Day 1 vs. Day 7) |
Script-Level Analytics
Section titled “Script-Level Analytics”Retention and heatmaps can be viewed per script as well as per project when supported.
| Level | Use |
|---|---|
| Project | Overall engagement across all scripts |
| Script | Individual script performance; compare scripts |
Script-level retention helps identify which scripts drive repeat usage. Script-level heatmaps show when each script is used most.
Next Steps
Section titled “Next Steps”- Dashboard Stats — Overview stats and execution tracking
- Geo Analytics — Country breakdown and execution distribution