Revenue Reports

Located under the Monetization tab on the dashboard, Revenue Reports breaksdown your revenue key performance indicators using your app's in-app purchases and in-app ad revenue.

reviewsPopular Use Case Revenue Reports gives developers the ability to pick and choose all their app's vital revenue KPI's in one dashboard. Using Revenue Reports you can query a customized table of revenue metrics from specific revenue sources to constantly track your app's monetizing performance.

Required to Start using Revenue Reports

tag

Revenue Reports tracks your game's revenue from all your in-game monetized sources. Requisites for using Revenue Reports 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.

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.

notification_importantImportant If you are intergrating in-app purchase tracking in ByteBrew, make sure you have inputted your game's Apple App Shares Secret or Google License Key in your Game Settings page.

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.

notification_importantImportant When integrating Ad Events in the ByteBrew SDK, make sure to send revenue in USD and test the output of revenue you send to avoid reporting issues in your monetization dashboards.

Building Revenue Reports

tag Watch Video play_circle

To start designing your customized revenue report in your app, see the sections below to learn how to build queries on the ByteBrew Revenue Report dashboard.

In the Revenue Reports dashboard there were several steps to building your query. See the following overview steps and their individual sections for a detailed step by step to building a report for your app:

Select "Step Report" to open the Report Settings

Select the revenue events to analyze in your report.

Optional: Choose how you want to Breakdown your query. You can select up to 2 breakdowns.

Choose the metrics you want queried in your report. See list below for available revenue metrics:

fiber_manual_record

ARPDAU: Average revenue per daily active user from all revenue sources.

fiber_manual_record

Ad ARPDAU: Average revenue per daily active user from only ad events.

fiber_manual_record

IAP ARPDAU: Average revenue per daily active user from only in-app purchase events.

fiber_manual_record

Revenue: Total revenue analyzed from all revenue sources.

fiber_manual_record

Ad Revenue: Total revenue analyzed from only ad events.

fiber_manual_record

Revenue: Total revenue analyzed from in-app purchase events.

fiber_manual_record

ARPU: Average Revenue Per User from all revenue sources.

fiber_manual_record

ARPPU: Average Revenue Per Purchasing User. Available when only selecting Purchases.

fiber_manual_record

Purchases: Number of purchases that occured.

fiber_manual_record

Purchase Conversion Rate: Number of purchases that occured by the total number of users.

fiber_manual_record

Ad Impressions Per User: Average number of impressions tracked per user.

fiber_manual_record

Ad ECPM: Average eCPM rate tracked from ad events.

infoNote The metrics will be listed based on the revenue events selected in the revenue report. For example: If Ad Events are deselected then items such as Ad ECPM wont appear in the list.

Revenue Report Chart

The metrics you select when setting up your revenue report will be visualized in this chart. You can visualize each metric you selected by switching the selected metric is the dropdown on the chart.

infoNote When adding breakdowns to the revenue report, the chart visualize the top 3 values within each broken down variable. The datatable will always show all values.

Revenue Report Data Table

In addition to the chart, the Revenue Report will output a datatable with all the metrics you've selected

Saving Revenue Reports

After building your query, you have the option to save it; so you don't need to re-build the same query each time. Follow the steps below to save a Mechanic:

infoNote Saving any Revenue Report will save across all your studio user's dashboards as well.

After building your Revenue Report, open the Save Filters panel by clicking the "Save Filters" button.

Type the name of the filter you're saving to remember what the filter you built.

Loading Revenue Reports

Any Revenue Report you save can be reloaded later by clicking the "Load Filters" button to open the Load Filters panel. See the options list below the Load Filter panel:

fiber_manual_record

Load Saved Filter: To load a filter you've saved in the "Load Filter" panel, click "Load" button next to the saved filter you want to analyze.

fiber_manual_record

Delete Saved Filter: To delete a filter you've saved in the "Load Filter" panel, click "Delete" button next to the saved filter you want to remove.

infoNote Deleting any Custom Workspace item will delete across all your studio user's dashboards as well.

Exporting Charts

tag

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

When is data calculated on the dashboard?

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.

What is required to start using Monetization?

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.

What timezone is data calculated in?

The dashboard operates in UTC time.

Should Ad Revenue be sent in USD?

Yes, ad revenue in ad events should be sent in USD.

Why is revenue not showing up as expected?

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.

Does ByteBrew track purchase refunds?

No, ByteBrew is not able to track purchase refunding from the app stores.

help What is the best practice for building Revenue Reports? To get access to all the available revenue metrics, make sure to integrate all revenue sources with ByteBrew.