Overview
Creator Statistics adds detail to the operational dashboard. It combines earnings, AI-attributed and other revenue, PPV activity, paying-fan metrics, daily trends, and top-spender context for the selected bot.
- Compare total earnings with AI-attributed and other revenue.
- Connect PPV sends and unlocks to daily revenue.
- Identify high-value and repeat buyers in the selected period.
Before you start
- Select the exact Telegram account you want to analyze in the dashboard top bar.
- Choose a date range that matches the business question you are answering.
- Allow real messages, paid sends, and purchases to occur before judging an empty report.
Step by step
- Open Creator Statistics and select the creator bot you want to review.
- Choose Today, Last 7 days, Last 30 days, or a custom date range before comparing metrics.
- Read Total Earnings, Revenue by AI, and Revenue by Others as parts of the same selected period.
- Compare the daily earnings chart with PPV activity and message-volume sections to locate changes in performance.
- Review Top spending fans and paying-fan metrics to understand who generated the recorded revenue.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Revenue by AI | Purchase revenue attributed to the AI sales path in the selected scope. |
| Revenue by Others | Recorded purchase revenue not included in Revenue by AI for that same scope. |
| Top spending fans | Fans ranked from native purchase data within the selected account and period. |
| Repeat buyers | Paying fans with repeat purchase activity, shown relative to the paying-fan population. |
Verify the result
- Revenue by AI never exceeds Total Earnings for the same scope.
- The period label remains unchanged while you compare revenue, PPV, and fan sections.
- Top-spender rows belong to the selected creator bot.
Troubleshooting
| If you see this | What to check |
|---|---|
| A report is empty | Confirm the selected bot, date range, and whether qualifying activity occurred during that period. |
| Two reports show different totals | Check that both reports use the same bot, dates, metric definition, and attribution scope. |
| The latest data did not load | Use Retry and keep the last visible report separate from a failed refresh. |
Best practice
Keep the bot, dates, and metric definition fixed while investigating a change, then compare one variable at a time.