Required to Start using Monetization
Our monetization dashboard tracks your game's revenue from all your in-game monetized sources. Requisites for using monetization will depend on how you monetize in your game. See the table below for requirements based on how you monetize:
| Monetization Channels | Required Integrations |
|---|---|
| App monetizes with both In-App Purchases & In-Game Ads | 1. Integrate ByteBrew SDK 2. Implement Purchase Validation (or Purchase Tracking) in your game. 3. Implement Ad Events to stream in impression level revenue from your game. |
| App only monetizes with In-App Ads | 1. Integrate ByteBrew SDK 2. Implement Ad Events to stream in impression level revenue from your game. |
| App only monetizes with In-App Purchases | 1. Integrate ByteBrew SDK 2. Implement Purchase Validation (or Purchase Tracking) in your game. |
How to integrate In-App Purchases
In-App Purchase integration takes place in the implementation process of the ByteBrew SDK. Go to your platform's SDK documenation page to learn how to track and validate purchases using ByteBrew. When In-app purchase tracking has been integrated, then purchases will auto-populate on the Monetization dashboards.
How to integrate In-App Ad Tracking
In-App Ads integration takes place in the implementation process of the ByteBrew SDK. Go to your platform's SDK documenation page to learn how to track ad events using ByteBrew. When in-app ad tracking has been integrated, ad events will auto-populate on the Monetization dashboards.
Monetization Overview Charts
Monetization overview charts show a high-level visualization of your game's key monetization metrics. Select different chart tabs to see each metric displayed by day.
See the table below for a breakdown of all the Monetization analytics charts:
| Total Revenue | Total Revenue chart shows the daily total revenue earned from your app or game. This chart uses all sources of available revenue (both Purchase and Ad Event revenue) to calculate total daily revenue. |
|---|---|
| IAP Revenue | IAP Revenue Chart shows the daily revenue earned from your app or game. |
| Ad Revenue | Ad Revenue Chart shows the daily revenue earned from your app or game. |
| ARPDAU | Average Revenue Per Daily Active User (ARPDAU) chart shows the daily fluctuation of ARPDAU in your game. This chart combines all sources of available revenue (both Purchase and Ad Event revenue) to calculate your app's daily ARPDAU. To see ARPDAU split between Ads and Purchases, explore the Revenue Reports dashboard. |
| APRU | Average Revenue Per User shows the daily fluctuation of ARPU in your game. This chart combines all sources of available revenue (both Purchase and Ad Event revenue) to calculate your app's daily ARPU. |
Exporting Charts
Every chart on the ByteBrew dashboard is able to be exported via .csv by clicking on the three dots icon in the corner of the chart.
FAQs
All analytics on ByteBrew show up in real-time. There aren't any wait periods like other platforms. Seconds after your user's play your game, you will see data start showing up on the dashboard.
This depends on how you monetize your games. If you have IAPs in your game, then you must initialize the ByteBrew SDK and implement Purchase Tracking (or Purchase Validation). If you only use in-app ads to monetize, then you must initialize the ByteBrew SDK and implement Ad Event Tracking. If you use both IAPs and in-app ads, then you must implement the ByteBrew SDK, and integrate both purchase and ad events.
The dashboard operates in UTC time.
Yes, ad revenue in ad events should be sent in USD.
Average Revenue Per Daily Active User (ARPDAU) combines all sources of available revenue (Ex. ad revenue + purchase revenue) to give a true statistic for your game's daily ARPDAU.
If revenue is not displayed as expected, check (1) that you've properly implemented both purchase and ad events, and (2) test the output of each event type to ensure the revenue values are being sent to ByteBrew as expected.
No, ByteBrew is not able to track purchase refunding from the app stores.