The broadcast uses data from 4 different sources :
The dashboard only stores the data for 2 months. The M-1 month and the M-2 month.
The month corresponds to the snapshot date (snapshot is done at the end of the month).
You can choose the displayed snapshot through the "SnapshotMonth" filter :

In BO and BW, a report (or query/workbook/view/webtemplate in BW) can be sent to users via a broadcast. To send an automated email or "broadcast", an instance (in BO) or broadcast setting (In BW) must be created.
It's in this instance/setting that will be defined the broadcast information : to who, what report, when, which format...

User : Is considered a user an +email address, or BO Inbox. The email address can correspond to a person or to a mailbox (Ex : Eroom)
Broadcast : It's the object used to schedule. It's says which report, when, in which format and to who the report will be sent.
Report :
Some fields in the dashboard are not coming directly from BO or BW but are calculated :
Scheduled : Used to include or exclude broadcasts that are not scheduled.
Include IT : Used to include or exclude IT users from the statistics.
User Zone : This is used to classify the users by zone or type when not possible.
Topic : This is used to regroup the broadcasts by subject.
Groups are done from a list of key words found in the broadcast name (for BO) or setting technical name (For BW).
Ex : All broadcasts with "Order book" in the name will be classified in the order book topic.
This graphic counts the number of different reports broadcasted per topic. Only the top 10 topics with the most reports are displayed.
1 report = 1 report name
This is different from the number of broadcasts because the same report can be broadcasted multiple times.
A high number means that there are a lot of different reports used to broadcast on the same topic.
Note that for BO, if 2 reports have exactly the same name, it will be counted only once (For BO the dashboard uses the BO report name, not the internal ID).

This graphic counts the number of different broadcasts (settings/schedules) set per topic. It only displays the top 20 topics with the most broadcasts.
If a report is broadcasted several times it will appear only once in the Report graphic, but will be counted several times in this graphic.
It is different from the Users count because a broadcast schedule can be sent to many different users.

This graphic counts the number of different users receiving at least 1 report. The display is by topic and will only show the top 20 topics with the most users.
Notes :
if a user receives several reports/broadcasts for one topic, it will only be counted once.*
Ex : if a user receives several order books, it will be only counted once.

This graph allows to compare the BO and BW tools on 3 KPI :
Same rules as the graphics above apply.

Graph shows the number of existing broadcasts (settings/instances) per zone of the user.
Notes :
The zone is NOT the defined zone of the broadcast, but the zone of the users receiving it.
Ex : if a broadcast called "Novecare AP" is sent to a EU user it will be counted in the EU zone, not AP.
If a broadcast is sent to users in several zones it will counted several times. Total of broadcasts per zone <> Total number of broadcasts.
Ex : if a broadcast is sent to a EU user and a LA user, it will be counted once for LA and once for EU.

Graph shows the number of users receiving at least on report per zone of the user. See above for the zone definition.
Note:
Ex : if a broadcast called "Novecare AP" is sent to a EU user it will be counted in the EU zone, not AP

Counts the number of broadcasts sent to each users and displays the top 20 users with the most broadcasts.
Note that if a report has several broadcast schedules (ex : at D1 and another a D5) it will be counted as 2 broadcasts.

Count the number of broadcasts as well as the number of users receiving the broadcasts by owner of the broadcast.
Notes :

Counts the number of broadcasts (instances/settings) and persons receiving it for each report and shows the top 20 reports with the most broadcasts.
Note :

Counts the number of different reports broadcasted by topic and zone of the user.
Big differences between the zones mean that many zone specific reports/formats are used.

Counts per tool and kind ("Format") the number of broadcasts and persons receiving it.
The Kind corresponds to the format used for the report when it is sent. Values can be :
Best pratices : In BO the best pratice is to reduce the excel broadcasts and prefer PDF. In no best practice (but recommended to use query/view/webtemplate broadcast over workbooks)

The search tab is a detailed table with most of the fields available. In addition to the normal filters, you have 2 other search fields :
Email: you can type an email or user name and it will search all the broadcasts sent to that person.
Name/Subject : you can type a name and it will search into :


This page is similar to the Search tab but is customized for BO in order to display the reports by the folders tree found in BO :

This page contains information that explains the evolution (delta) between the 2 snapshot months : what is new and what has been removed.
Lists the Broadcast + User combinaisons that have been created during the month.
The broadcast or user may already exist before but it's the combinaison (this broadcast sent to this user) that is new.
Note that for BO if a broadcast is deleted and then re-created with the same name, it will still be counted as a different one (different internal ID).

Lists the Broadcast + User combinaisons that have been removed during the month (between both snapshots).

Counts the numbers of different broadcasts settings/instances for BW and BO and both month and then calculates how many have been completly removed or added between the 2 snapshots.
For BO if a broadcast is deleted and then re-created with the same name, it will still be counted as a different one (different internal ID).

Counts the number of users which receive at least 1 broadcast.
Deleted shows the number of users that are no longer receiving any broadcasts in the second snapshot but were receiving at previous snapshot.
Added shows the number of users that were not receiving any broadcasts in the first snapshot and are receving at least one in the current snapshot.
