Why Your Analytics Data Might not Match Dispatch Data

Introduction

This article explains some common reasons why the data you see in Dispatch might not perfectly match the data you see in Analytics. While we strive for consistency, subtle differences can arise due to a variety of factors. Understanding these factors can help you reconcile any discrepancies you encounter.

Common Reasons for Data Discrepancies

1. Rounding and Truncation:
   • In some cases, Dispatch data might undergo rounding or truncation during processing. This can lead to slight differences of +/- 1-2 in certain metrics.

2. Time Range Inconsistencies:
   • Dispatch and Analytics dashboards both use the selected start and end dates as context for backend calculations. It's critical to ensure you're using exactly the same time range in both platforms. Even small differences in the selected date range can result in data discrepancies.

3. Parameter Differences:
   • Failing to select the exact same parameters in Dispatch and Analytics is a common source of error.

4. Customization in Analytics:
   • Analytics provides a high degree of flexibility, allowing users to customize charts and analyses. Be aware that changes made in Analytics can significantly affect the data displayed.
   • Dispatch users might take certain default filters and columns for granted, while these might not be considered in Analytics.
   • Important columns to check in Analytics that are often assumed in Dispatch:
     • active
     • deleted
     • dispatch_type_critical
   • If someone is altering a chart, be aware that we have a lot of important columns exposed that dispatch users would take for granted. Columns like active deleted dispatch_type_critical are all common filters a user might not know about if they didn't look at the examples.

Troubleshooting Steps

If you're seeing data discrepancies, try the following:

1. Verify Time Ranges: Double-check that the start and end dates are identical in both Dispatch and Analytics.
2. Check Parameters: Carefully review all selected parameters in both platforms to ensure they match exactly.
3. Review Analytics Customizations: If you've modified any charts in Analytics, ensure that any added filters are consistent with Dispatch's default behavior. Pay close attention to the active, deleted, and dispatch_type_critical columns.
4. Consider Rounding/Truncation: Be aware of potential rounding errors, especially with certain metrics.

Need Further Assistance?

If you've tried these steps and are still experiencing issues, please contact support with the following information:

• Specific dashboards and metrics you're comparing.
• Screenshots of your Dispatch and Analytics configurations (time ranges, parameters, filters).
• Example of the data discrepancy you're observing.