Features
Store analytics
Track store revenue, purchases, packages, categories, item-level recent purchases, and source breakdowns.
Store analytics turns purchases into a dashboard you can actually use. Instead of only seeing revenue as a stat on other pages, the Store page shows what players bought, which packages are working, and where purchases are coming from.
Store required
Store analytics needs a connected store integration such as Tebex or CraftingStore. See Connect your store if purchases are not showing yet.
What the Store page shows
Open Store from a Server or Network to see:
- Revenue in the selected time range
- Purchases in the selected time range
- Top packages ranked by revenue and purchase count
- Top categories so you can compare groups of products
- Revenue and purchase charts over time
- Package and category detail pages with recent purchases for that specific item
Use the time range selector to switch between short-term performance and all-time results.
Package pages
Open a package to answer:
- How much revenue did this package generate?
- How many times was it purchased?
- Which players bought it recently?
- Is demand increasing or falling over time?
This is useful for spotting packages that should be promoted, renamed, re-priced, or removed.
Category pages
Categories group related packages together. Open a category to see whether a whole part of your store is working, for example:
- Ranks
- Crates
- Cosmetics
- Boosters
- Seasonal bundles
If one category brings most of the revenue, it probably deserves the most polish. If a category gets traffic but no purchases, the offer may be unclear or overpriced.
Revenue breakdowns
Store analytics also connects revenue back to acquisition. Depending on the page and workspace, you can see purchase performance by:
- Server
- Network
- Domain
- Hostname
- Campaign
- Creator code
This is what lets you separate "players who join" from "players who join and buy".
Store analytics on Networks
Network Store pages roll up purchases across the Servers in that Network. Use this when you want to compare gamemodes or understand the store as one product instead of one Server at a time.
For example, if Skyblock drives more total revenue but Lifesteal has higher revenue per player, that changes where you put development time and creator spend.
Tips
- Review top packages weekly. If a package is carrying revenue, make sure it is easy to find and clearly explained.
- Watch purchases, not just revenue. One expensive sale can spike revenue. Purchase count shows whether demand is broad.
- Compare by source. A Campaign with fewer players can still win if those players buy more.
- Use categories for decisions. It is easier to improve "Ranks" or "Cosmetics" than to stare at every package one by one.