All Collections
Worklabs Insights
Active people per hour of the day
Active people per hour of the day
Updated over a week ago

Widget Visual:


The "Active People per Hour of the Day" widget visually portrays the volume of users interacting with the platform throughout different hours of the day. By showing hourly user activity, this widget aids in identifying peak usage times, making it a valuable tool for strategising campaigns or other user engagement initiatives.

Metrics Explained:

  • Hour of the Day (X-Axis)

    • Definition: Each 2 hour block, typically ranging from 00:00 to 22:00, represents a 24-hour day.

    • Significance: It indicates the specific hour being analysed for user activity.

  • Count of People (Y-Axis)

    • Definition: The number of users actively engaged on the platform during a specific hour.

    • Significance: This number offers insights into user activity trends, revealing the hours with the highest and lowest user engagements.

Metric Interplay:

By plotting the Count of People against the Hour of the Day, the widget offers a clear visual representation of user engagement patterns over a day. For example, a spike at 2 PM might suggest that users are most active in the early afternoon, while a dip at 4 AM would indicate low nighttime usage.

Use Cases:

  • Campaign Timing: If launching a campaign or an announcement, this widget can help pinpoint the best hours to ensure maximum user visibility and engagement.

  • Resource Allocation: For support or community management teams, understanding peak hours can guide staffing decisions, ensuring adequate resources during high-activity periods.


  • Q: Can I view data for a specific date range?

    • A: Yes, with date range filtering, you can adjust the view to analyse specific periods for hourly activity patterns.


  • Issue: The widget displays a consistent zero count for all hours.

    • Solution: Ensure that the date range filter isn't set to a future date or a non-operational day. If data still doesn't display, there might be an issue with data sources or platform tracking. Consider reaching out to technical support for resolution.

Did this answer your question?