When AV Insights data is calculated in real time, we cannot guarantee that all data is correctly allocated and that performance is optimal, so we make two changes overnight:
- The consecutive av.heartbeat and rm.refresh events are merged. The objective here is to limit the number of lines stored to provide optimised performance in our interfaces in order to enhance the user experience.
Real-time example: 10:00:00:00 av.heartbeat (0 seconds duration) -> 10:00:30 av.heartbeat (30 seconds duration) -> 10:01:00 av.heartbeat (30 seconds duration)
Example the next day after the treatment: 10:00:00 a.m. before heartbeat (duration 60 seconds)
- The durations are re-allocated to the right events in order to have a 100% correct analysis even when analysing a specific event.
Example in real time: 10:00:00 Play (duration 0 seconds) -> 10:00:30 Stop (duration 30 seconds)
Example the next day after treatment: 10:00:00 Play (duration 30 seconds) -> 10:00:30 Stop (duration 0 seconds)
These adjustments may have an impact on your analyses.