Tebex

The Tebex integration receives store events over a webhook, so purchases are captured by ShardAnalytics even when your game server is offline.

What it captures

Event	Effect
payment.completed	Adds revenue and links the purchase to the player.
payment.declined	Feeds decline analysis and checkout health.
payment.refunded	Adjusts revenue and refund reporting.
validation.webhook	Confirms the endpoint during setup.

Connect Tebex

1. Open Organization Settings → Payments and choose Tebex.

2. Copy the webhook URL shown in the dashboard. It has the form:

   https://api.shardanalytics.com/v1/webhooks/<tenantId>/tebex

3. In Tebex, create a webhook pointing at that URL and enable the completed, declined, and refunded payment events.

4. Enter the webhook secret in ShardAnalytics. The secret is stored encrypted and is never returned by the API.

5. Trigger a test event from Tebex. When it is received, the integration moves to Active.

Player matching

Tebex payloads include the buyer identity. ShardAnalytics matches purchases to players using the identifiers available in the event (for example username or UUID). Purchases that cannot be matched are still counted in revenue but are not attributed to a player profile.

If a creator code is present on the transaction, it is stored for campaign attribution.

Server mapping

If your Tebex store routes purchases to specific servers, map those stores to ShardAnalytics servers in the payments settings. Mapping enables per-server revenue analytics. Unmapped purchases still appear in organization-level revenue.

Managing the connection

From the same settings panel you can:

• Rotate the webhook secret.
• Disable the integration without deleting its configuration.
• Delete the integration and its stored secret.

Troubleshooting

Symptom	Check
Integration stays pending	The test event has not arrived. Confirm the webhook URL and event selection in Tebex.
Purchases counted but not matched to players	The payload identity did not match a known player. Check the identifiers Tebex sends.
Revenue missing for one server	The provider store is not mapped to that server.

See Store Overview for revenue definitions and currency behaviour.