Analyse
FeaturesRevenue

Features

Revenue

Every purchase linked back to the player, the campaign that brought them, and the creator code they used.

Revenue in Analyse is connected to the rest of your analytics. Once your store is connected, every purchase flows into the Store dashboard and also shows up on the pages where it is useful: Overview, Campaigns, Creator Codes, Domains, Countries, and Networks.

Where revenue shows up

On the Overview

The Server's Overview dashboard shows your revenue stat cards:

  • Total revenue in the selected time window

This is the page you open daily to see "are we up or down".

On the Store page

The Store page is the main revenue workspace. It shows:

  • Revenue and purchases over time
  • Top packages
  • Top categories
  • Package detail pages
  • Category detail pages
  • Breakdowns by Server, Domain, and source where available
  • Recent purchases on package and category detail pages

Use it when the question is about what players bought, not just which creator sent them.

On each Campaign page

Open any Campaign and you get its own revenue view, attributed to the players who joined through that tracking link:

  • Total attributed revenue in the selected window
  • Revenue over time
  • Average revenue per attributed player

This is how you compare creators: "did pewds' audience actually spend, or just click"?

On each Creator Code page

Open a Creator Code and you see:

  • Total sales driven by the code
  • Commission earned and discount given
  • Usage over time and recent purchases

This is how you work out what to pay a creator you have a rev-share deal with.

How purchases get attributed

When a connected store sends a purchase webhook:

  1. The player is looked up by the Minecraft username on the purchase (case-insensitive). If that player has ever joined the Server, the purchase is linked to them.
  2. The purchase inherits the Campaign the player originally joined through (first-touch attribution).
  3. If the player used a Creator Code at checkout, the purchase is linked to that code too.
  4. Any refund or chargeback webhook subtracts the amount from the attributed totals.

All of this is automatic. You don't need to tag purchases yourself.

Plan

Revenue attribution requires a connected store integration such as Tebex, CraftingStore, a custom webhook, or the fallback purchase command. Campaign-level and creator-code-level breakdowns depend on those features being available in your workspace.

Refunds and chargebacks

  • Payment Refunded (Tebex webhook type) subtracts the refunded amount from totals and marks the purchase as refunded.
  • Payment Chargeback does the same but marks it as a chargeback (so you can spot abuse patterns).

Tips

  • Watch revenue-per-Campaign weekly. It's the single fastest way to spot a creator that's stopped delivering.
  • Compare Creator Code revenue to flat-fee spend. If the code's revenue is lower than what you're paying the creator, you're losing money.
  • Check refund rate per package. If one specific package refunds over 3% it's usually a gameplay problem (broken, over-promised, or priced wrong).

Related