Content generated with AI — it may contain mistakes.

ExyliaAnalytics/GuidesUpdated in v1.2.0

Track Tebex revenue

The Tebex integration and the Revenue and Creator codes pages. Payments reach the dashboard straight from Tebex, not through the agent.

Page 10 of 285 min read

In about ten minutes your Tebex store feeds the dashboard, so you can see what the server earns, who pays, which packages sell, and what a new player is worth. Revenue does not come from the agent: your Tebex store sends each payment to the dashboard as a signed webhook, and the dashboard matches it to a player by their Minecraft UUID. That is what lets revenue, lifetime value and campaign ROI use real payments.

Before you start#

  • A Tebex store and access to its creator panel.
  • A workspace member with Connect and disconnect integrations (manage_integrations) to connect it.
  • To read the page, Revenue (view_revenue); the Viewer role is seeded without it. See Team and settings.
  • Your store's currency set under Settings: amounts are shown in it.

Steps#

On Integrations, open Tebex.

Create a webhook endpoint in Tebex

In the Tebex creator panel, open Integrations → Webhooks → Endpoints, add an endpoint and copy its webhook secret. Enable payment.completed, payment.refunded, the payment.dispute.* events and, for subscriptions, recurring-payment.started, recurring-payment.renewed, recurring-payment.cancellation and recurring-payment.ended.

Paste the secret into the dashboard

Paste it into Webhook secret and click Connect Tebex. It is stored encrypted and never shown again.

Paste the endpoint URL into Tebex

The dashboard shows the URL to use. Tebex sends a validation request first; the status turns to Receiving with the first payment.

Import past payments (optional)

Under Import past payments (optional), add a Game server secret key (Tebex: Game Servers → your server → secret key) and click Import past payments. The dashboard imports every payment Tebex still lists. Importing again never duplicates a payment. Refunds imported this way are dated on the payment's day.

Buyer names, e-mail addresses, IPs and postal codes are dropped before anything is stored. Disconnect Tebex stops new payments; the ones already stored stay.

Check that it works#

Open Revenue (the Store tab). Once a payment has arrived, Revenue after refunds and Paying players fill in, and Every payment lists it with its player. If Integrations shows Waiting for Tebex, send a test event from the endpoint in Tebex, then run the check on the page again. Before you connect, the page shows Connect your Tebex store.

Going further#

The Revenue page#

SectionShows
Over timeRevenue over time per period with refunds and chargebacks below the line, the running total, and buyers and payments.
Subscriptions and one-off purchasesMoney from recurring payments against single purchases.
What a new player is worthLifetime value over a player's first 90 days, by cohort and by campaign.
Time to first purchaseDays from a player's first session to their first payment, with the typical wait.
Packages, Revenue by country, Creator codesRevenue after refunds by each. Packages show sales, buyers, refunded and the share of first purchases.
Revenue by kind of packagePackages sorted by Exylia AI from their names: Ranks, Crates and keys, Cosmetics, Currency, Bundles, Other, Unclassified.
Revenue by sourceMoney by the address each buyer first joined through; Not linked to a player is money from buyers who never joined the network.
Top payersThe players who spent the most in the range, after refunds.
SubscriptionsActive, cancelling, started and ended, and churn (Share cancelled). Counted only once the store also sends the recurring-payment end and cancellation events.
Every paymentEach transaction, newest first; search by player, package, source or id, filter by status (Linked, Not linked, Refunded, Chargeback, Free) and sort by newest or largest amount.
Free ordersOrders fully paid with a coupon or gift card. They are not sales and never make someone a paying player.

If you set a monthly goal in Settings › Menu, a line at the top says whether you are on pace.

Creator codes#

Open Revenue › Creator codes: the codes buyers typed at checkout. Revenue is after refunds: refunds and chargebacks are taken off the code that brought the payment. The page shows Revenue with a code and its Share of revenue, Codes used, the average Per transaction, revenue with and without a code over time, Top codes, and Every code with its payments, buyers, average and last payment. It has its own permission, Creator codes (view_creators).

Definitions

Amounts are in the workspace's currency (Settings). Refunds and chargebacks subtract on the day they happen.

MetricDefinition
Sales (gross revenue)Completed payments.
Revenue after refunds (net)Sales minus refunds and chargebacks.
What you keepNet revenue minus the tax and gateway fees Tebex reports per payment.
Buyers (payers)Unique players with a completed payment.
Players who paid (conversion)Buyers ÷ active players.
Spend per paying player (ARPPU)Net revenue ÷ buyers.
Yearly pace (run rate)Net revenue of the last 30 days × 12.
What a new player is worth (LTV)Net revenue a cohort brings within N days of its first day, per player.
Revenue per new playerNet revenue in the range from players whose first join is in the range, ÷ those players.
Cost per new player (CAC) and Return (ROI)See Campaigns.

A payment from a player never seen on the network is still revenue; it is simply Not linked to a player, so it counts in every total but belongs to no campaign, source or join-date group. Totals count the store currency only; payments in other currencies are listed apart.

Something missing on this page? Tell us on Discord