Store Overview
Store integrations connect real money to player identity. Once connected, purchases appear in payments analytics and can be attributed to the campaign that brought the player in.
Supported providers
Section titled “Supported providers”| Provider | Integration |
|---|---|
| Tebex | Native webhook integration with purchase, refund, and decline events. |
| Custom | Signed webhooks from your own store backend. |
A tenant can have both connected at the same time. Other providers are added as they are built; this page lists only what is supported today.
Payment pages
Section titled “Payment pages”| Page | Shows |
|---|---|
| Overview | Gross revenue, take-home, transactions, revenue at risk, and refunds. |
| Revenue | Revenue over time and by source. |
| Methods | How players pay, and where checkout methods underperform. |
| Declines | Failed payments grouped by reason. |
| Chargebacks | Disputes and chargeback pressure. |
| Transactions | The full transaction ledger with filters. |
Revenue definitions
Section titled “Revenue definitions”| Value | Definition |
|---|---|
| Gross revenue | Completed payments plus gift-card value. |
| Net revenue | Gross minus taxes. |
| Take-home | Net minus gateway fees. |
Where a fee or tax cannot be determined from provider data, ShardAnalytics shows the amount as unavailable rather than estimating it.
Currency behaviour
Section titled “Currency behaviour”- Amounts are reported in the currency your store sends. No conversion is applied.
- A shop is expected to use one currency. If events arrive with mixed or unknown currencies, monetary values are withheld while counts (transactions, players) remain accurate.
- Where a single currency is known, you can select it and all monetary figures are constrained to it.
Player and campaign attribution
Section titled “Player and campaign attribution”- Purchases are matched to players through the identity fields in the provider payload.
- Transactions can carry a creator code, which links revenue to a campaign.
- Provider stores can be mapped to ShardAnalytics servers. Ingestion works without mappings; mapping enables per-server revenue analytics.
- Open Organization Settings → Payments.
- Choose Tebex or Custom.
- Set the secret and confirm the webhook URL with your provider.
- Wait for the test event, then the integration shows as active.
- Optionally map provider stores to your servers.