Visitor analytics in city of Helsinki websites

Visitor analytics of the City of Helsinki website. The websites include the city’s main website [hel.fi](https://www.hel.fi/helsinki/fi), the [Nuorten Helsinki](https://nuorten.helsinki) website, the [Helsinki channel](https://nuorten.helsinki) offering webcasts and event recordings, and the geographic information service [map.hel.fi](https://kartta.hel.fi). Under Data and Resources, you can find a CSV-shaped list of all the sites in the city where visitor analytics is available. The data contains information such as the number of visitors to the website, the number of visits, the number of activities and the average time spent on the site. The data is obtained from the web analytics monitoring tool Matomo. The data is available monthly in three different files. The files are named on the principle of the year-month (YYYY-MM). The file is automatically updated daily at 02:00. The report contains the current month’s data until the previous day. ##Data characteristics by file **ID_list_Matomo (explanations for id numbers in other files)** — idsite = Website Identification Number. Match the fields of other files with key and idsite — name = Website name. Match the Sites file field label — main_url = Website address (url) — ts_created = Date when the site is connected to the Matomo tracking tool **Visits (general metrics)** — Key = Page ID in Matomo — nb_uniq_visitors = Number of individual visitors — nb_users = Number of individual active users (visitors with a known user ID/ID). If you do not use User ID, this meter is set to zero — nb_visits = Number of visits (30 minutes of inactivity is calculated as a new visit) — nb_actions = Number of actions (page views, links and downloads) — nb_visits_converted = Number of visits generated by target (goal) — bounce_count = Number of visits left immediately (viewed only one page) — sum_visit_length = Total time spent in seconds — max_actions = Maximum number of operations during the visit — bounce_rate = Relation of site visits after page entry (see bounce_count) — nb_actions_per_visit = Number of activities per visit — avg_time_on_site = Average time spent on a particular page, in seconds **Sites (pages in order to be the least visited)** — Label = Page name in Matomo — nb_visits = Number of visits (30 minutes of inactivity is calculated as a new visit) — nb_actions = Number of actions (page views, links and downloads) — nb_pageviews = Number of page views — Revenue = Total Goal Results — visits_evolution = % change from previous equal period — actions_evolution = % change from previous equal period — pageviews_evolution = % change from previous equal period — revenue_evolution = % change from previous equal period — idsite = Page Matomo ID — main_url = Address defined in Matomo **Devices (metrics sorted by device type)** —label = Type of device (e.g. desktop/smartphone/tablet/portable media player/phablet) — nb_visits = Number of visits (30 minutes of inactivity is calculated as a new visit) — nb_actions = Number of actions (page views, links and downloads) — max_actions = Maximum number of operations during the visit — sum_visit_length = Total time spent in seconds — bounce_count = Number of visits left immediately (viewed only one page) — nb_visits_converted = Number of visits generated by target (goal) — sum_daily_nb_uniq_visitors = The sum of daily individual visitors over the selected timeframe. Matomo does not handle individual visitors throughout the period — sum_daily_nb_users = Number of daily visits aggregated over the selected timeframe — segment:deviceType==desktop/smartphone/tablet/portable media player/phablet = specifies a custom segment to filter reports (sorts by devices) — logo:plugins\/Morpheus\/icons\/dist\/devices\/desktop/smartphone/tablet/portable media player/phablet.png = logo displayed in Matomo for the device in question