The Additional Reading Developer Hub

Welcome to the Additional Reading developer hub. You'll find comprehensive guides and documentation to help you start working with Additional Reading as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Reporting Overview

Introduction

Fyber handles over 15 billion events a day, producing some 3000 TB (approximately a trillion bytes) of data each month. Every event contains more than 80 attributes describing the advertisement request and response flow.

Fyber's Dynamic Reports are created from this data which is stored and correlated in an open-source database. It is used for business intelligence queries on time-series data - Online Analytical Processing (OLAP). The database provides close to real-time data ingestion, flexible data exploration and fast data aggregation.

Using the vast amount of information collected, 's Dynamic Reports provide publishers with the ability to create and view reports based on actual and accurate revenue data.

The Reports

Fyber's Dynamic Reports are divided into sections, each with its own groups of dimensions and metrics.

The information contained within the reports is sourced from different places, enabling you to use, monitor, analyze and filter the information.

What Can You Do?

Using Dynamic Reporting you can select the required dimensions and metrics and build unique and custom reports on various levels of granularity based on the dimensions and metrics you select.

You can filter the information, save share and export the reports.

For detailed explanations of what you can do with the Reports, click here.

Viewing the Reports

To view the reports:

  1. Login to the Fyber Console

The Different Reports

On the left-hand menu bar select Dynamic Reports and then select the report you want to view:

Click here, to continue reading about how to use the reports.

Reporting Overview


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.