Tickaroo provides detailed statistics to help you measure the performance of your liveblogs and understand how readers interact with your content. Where to Find Statistics You can access statistics from two locations: Organization Dashboard – View performance across all liveblogs in your organization. Liveblog Statistics – View detailed analytics for an individual liveblog. While the entry point differs, both areas provide similar insights into audience reach and engagement. Available Metrics Depending on your setup and permissions, statistics may include: Page Views Unique Visitors Liveblog Visits User Engagement Retention Time Traffic Development Over Time Performance Comparisons Across Liveblogs Statistics can also be segmented by factors such as device type, country, time period, tags, templates, and properties. Notes Statistics are updated automatically. Available metrics may vary depending on your setup and subscription. Data can be exported and integrated with external analytics tools where configured. These insights help you evaluate the reach, engagement, and overall success of your live coverage.

Question: Are page views only counted when clicking the "Refresh" button in the live ticker? Or does refreshing the browser (Safari, Chrome, etc.) also count? Answer: Currently, the following events are counted as page views: t_ini: The live blog has loaded. t_mor: The user clicked "Load more." t_upd: The user clicked "Refresh." t_tag: The user selected a tag filter. t_mil: The user clicked on a milestone. Note: Often, a few users generate many page views, while the majority of users generate only one.

How is retention measured, and what criteria are used for time spent? Is it sufficient for a tab to be open, or does the blog need to be actively read? Tracking starts as soon as our Liveblog script is loaded. The current time spent is reported to our backend at regular intervals. The statistics display the average, meaning we sum up all the data and divide it by the number of unique users. This feature only works correctly if unique user tracking is active for as many users as possible (via the useCookiesoption). From a technical perspective, we use the browser's visibilitychange and pagehide/pageshow events, as well as an internal watchdog timer, to determine whether the page was actually visible during that time.