Back to Guides
Revenue

Understanding Server-Side Payments and Revenue Analytics

June 7, 2026 • By LoopBreak • 2 min read
#Tebex #CraftingStore #Net Revenue

Maximizing network monetization requires deep insight into player purchasing behavior. ShardAnalytics integrates directly with payment systems like Tebex and CraftingStore, delivering server-side insights without requiring you to maintain custom webhook endpoints or listen to raw event feeds.

In this guide, we will cover how ShardAnalytics calculates payments analytics, maps gross to net revenue, and reports on checkout conversion health.

Why Server-Side Analytics?

Traditional webhook integration relies on your game server receiving HTTP posts, which is prone to delivery failure when your server is under high CPU load or during DDoS attacks.

ShardAnalytics reads payment events directly from store APIs at the server level:

  • Zero Webhook Failure Risk: If your game server crashes, transactions are still fully captured.
  • Unified Insights: Combines player login history, campaign attribution, and purchases in one analytics pipeline.
  • Secure Integration: No open inbound ports required on your server.

Key Revenue Metrics to Monitor

Once synced, your Payments Dashboard displays the following core metrics:

1. Gross Revenue

The total checkout amount paid by customers at the store level.

2. Take-Home (Net) Revenue

The estimated take-home revenue after platform fees (Tebex/CraftingStore cuts) and standard credit card processing rates (Stripe, PayPal). ShardAnalytics applies a configurable fee template to estimate your net profit margin automatically.

3. Transaction success Rate

The ratio of completed checkouts to total initiated carts. A sudden drop in success rate indicates issues with a payment processor, or localized currency problems.

4. Revenue at Risk

The amount of money currently tied up in chargeback disputes, refunds, or fraud blocks.

Categorized Decline Reasons

To prevent lost sales, ShardAnalytics categorizes failed checkouts by their API decline reasons:

  • Card Insufficient Funds: Indicates a need for lower-priced bundles or localized pricing adjustments.
  • Fraud/Risk Block: Indicates payment gateway rules might be too aggressive.
  • Gateway Timeouts: Signal-processing bottlenecks between the store and the bank.