Question

Why can Everbridge Advanced Reporting show fewer recipients or responses than Custom (Legacy) reports or incident/notification details, and how should administrators choose and schedule Advanced Reporting versus Custom reports to ensure complete data?

Answer

Advanced Reporting and Custom (Legacy) reports use different data sources and are designed for different reporting needs. Custom (Legacy) reports and incident/notification details query the main Everbridge database directly. Advanced Reporting pulls data from a separate data warehouse that is optimized for analytics and dashboards.

The data warehouse that Advanced Reporting uses is updated on a refresh cycle and is confirmed to update approximately every four hours. Because of this refresh cycle, if an Advanced Reporting report is run only minutes after a notification or incident ends, the data warehouse may not yet have received and processed all notification and response data. In that situation, Advanced Reporting can return incomplete data, such as missing recipients or missing response values.

To ensure complete data in Advanced Reporting, reports should be scheduled to run at least four hours after the notification or incident ends. Running Advanced Reporting sooner than this approximate four-hour refresh window can result in missing or partial data for recent activity.

When deciding whether to use Advanced Reporting or Custom (Legacy) reports, administrators should consider both timeliness and data shape:

• If same-day or near-real-time results are required, Custom (Legacy) reports should be used because they query the main database directly and do not depend on the data warehouse refresh cycle. These reports generally return results sooner but may require manual interaction to run.

• If fully automated, scheduled delivery is preferred and a delay from the time of the event to when it appears in reports is acceptable, Advanced Reporting can be used. In this case, Advanced Reporting jobs should be scheduled to run at least four hours after the relevant notification or incident ends.

Output format can also influence which reporting tool to use. Custom (Legacy) reports typically provide one column per value, which can be easier for ingestion into external tools that expect column-based data. Advanced Reporting can present key/value pairs in a single column, which may require additional transformation before ingestion into some analytics platforms.

Advanced Reporting is available when Everbridge 360 is enabled. It supports scheduling reports to be sent on a recurring basis so that report delivery can be automated instead of relying on manual exports. If Advanced Reporting is not visible in the user interface, an Everbridge administrator must enable Everbridge 360 for the organization before Advanced Reporting can be accessed. For additional configuration guidance related to Advanced Reporting dashboards and filters, see EB360: Preserving Dashboard Filters in Everbridge Advanced Reporting.

Everbridge provides distinct tools for reporting:

• The Everbridge-native reporting tool, which includes Custom (Legacy) reports and Quick Reports. For Quick Reports behavior and available report types, see EBS: Quick Report Descriptions.

• Advanced Reporting, which is an external, Looker-based analytics tool. Reports created in the Everbridge-native reporting tool are not automatically present inside Advanced Reporting. To use existing native reports, continue using the native reporting tool. To build or recreate reports in Advanced Reporting, the desired data fields must be configured there separately because the two reporting environments are distinct.

Reporting behavior also differs between Everbridge Reporting and Advanced Reporting in how data is selected and filtered. In Everbridge-native reporting, users can typically add data fields with minimal filtering, often relying primarily on date ranges. In Advanced Reporting, each data item must be explicitly selected and filtered, so each piece of information included in a report requires deliberate configuration.

If an Advanced Reporting export appears to be missing recipients or responses compared to Custom (legacy) reports or incident/notification details, administrators should first verify when the notification or incident ended and when the Advanced report was executed. If the report ran within approximately four hours of the event end time, the difference is expected and is due to the data warehouse refresh cycle. In this situation, the recommended action is to re-run the Advanced report at least four hours after the notification or incident ends so that the data warehouse has time to update with all relevant notification and response information.