Matomo - Package Updates

[Package Updates]

[1.52.2]

• Update matomo to 5.5.2
• Full Changelog
• 23775 Properly escape transitions export overlay title [by @sgiehl]
• 23761 Fix AI referrer detection cache [by @sgiehl]
• 23754 Fix superuser check in logme method [by @sgiehl]
• 23700 Ensure to only invalidate segment for desired site [by @sgiehl]

[Package Updates]

[1.53.0]

• Update matomo to 5.6.0
• Full Changelog
• Turn AI Agent traffic into first-class metrics
• From One Policy to Tailored Privacy for every site and app
• Polished details where you need them

[Package Updates]

[1.53.1]

• Update matomo to 5.6.1
• Full Changelog
• #23837 Fix possible archiving error “Column “referer_type” in WHERE is ambiguous – in plugin Referrers” [by @sgiehl]
• #23827, #23824 Fix external themes that are using CSS custom props [by @tzi]

[Package Updates]

[1.53.2]

• Update matomo to 5.6.2
• Full Changelog

[Package Updates]

[1.54.0]

• Update matomo to 5.7.0
• Full Changelog
• #23725 Track AI Bots through our HTTP Tracking API [by @sgiehl, @mneudert, @caddoo]
• #23870 Adds reporting around requests made by AI bots [by @sgiehl]
• #23818 Remove MadMimi from Newsletter privacy note [by @sgiehl]
• #23903 Fix issue for saving of preferences throwing errors and redirecting when logged in as anonymous user [by @chippison, @caddoo]
• #23743 Prevent logging tracking failure for obviously malformed idsite or token auth [by @sgiehl]
• #23768 Fix and Improve period selection via keyboard navigation [by @tzi]
• #23771 Allow to star and unstar stored segment [by @tzi]
• #23783 Redirect to login page when session ends [by @chippison]
• #23792 Segment selector: max out at 5-6, instead of throwing many errors in reporting interface [by @chippison]

[Package Updates]

[1.54.1]

• Update matomo to 5.7.1

[Package Updates]

[1.55.0]

• Update matomo to 5.8.0
• Full Changelog
• Dedicated AI Chatbots Overview and Over Time reports in the AI Assistants report menu.
• Telemetry ingestion via the HTTP Tracking API, with support for Cloudflare, Amazon CloudFront, and WordPress.
• On the All Websites dashboard, the Total AI Chatbots Requests shows the total number of AI chatbot requests for all tracked sites.
• The dashboard Total Hits metric now includes the total of human visits and AI chatbot requests across all tracked sites.

[Package Updates]

[1.56.0]

• Update matomo to 5.9.0
• Full Changelog
• UsersManager.logoutUser was added to sign a user out of all sessions.
• The jQuery UI liveWidget API ($.fn.liveWidget) is now deprecated and will be removed in Matomo 6. Use Live.AutoRefreshWidget vue component instead.

[Package Updates]

[1.57.0]

• Update matomo to 5.10.0
• Full Changelog
• Widgets can now be declared as client-rendered through WidgetConfig::setClientSideComponent() and WidgetConfig::setClientSideProps(). API.getWidgetMetadata and API.getReportPagesMetadata now expose a clientComponent field for these widgets, and Widgetize/dashboard rendering supports bootstrapping them without an extra widget controller request.
• The methods ArchiveTableCreator::getNumericTable() and ArchiveTableCreator::getBlobTable() now support a $createIfMissing parameter. Omitting this parameter is deprecated; pass true to create missing archive tables or false to return only existing tables. In Matomo 6 the default behavior for omitted calls will change to lookup-only.

[Package Updates]

[1.57.1]

• Set HTTP_AUTHORIZATION for the mcp plugin server

[Package Updates]

[1.57.2]

• Update matomo to 5.10.1
• Full Changelog

[Package Updates]

[1.58.0]

• Update matomo to 5.11.0
• Full Changelog
• SitesManager.addSite and SitesManager.updateSite now accept an optional description parameter (up to 255 characters). Site entities returned by the SitesManager APIs now include a description field.
• CustomDimensions.configureNewCustomDimension and CustomDimensions.configureExistingCustomDimension now accept an optional description parameter (up to 1000 characters) to provide additional context for a custom dimension.
• New ViewDataTable display properties were added: Config::$report_supports_flatten, Config::$show_flatten_table_export and Config::$export_parameters_to_modify / RequestConfig::$export_parameters_to_modify, allowing reports to control flattening availability and export link parameters independently of the UI.
• New Vue components are exported from CoreHome for use by plugins: MatomoModal, DraggableList and SearchInput.
• Themes can now customize the alternative border color using @theme-color-border-alternative.
• ScheduledReports.sendReport now accepts range as period parameter.
• CSV/TSV exports now replace carriage return characters in values with spaces (in addition to tabs).
• The theme variable @theme-color-border (ThemeStyles::$colorBorder) is deprecated; use @theme-color-border-alternative instead.

[Package Updates]

[1.58.1]

• Update matomo to 5.11.1
• Full Changelog

[Package Updates]

[1.58.2]

• Update matomo to 5.11.2
• Full Changelog

[Package Updates]

[1.59.0]

• Update matomo to 5.12.0
• Full Changelog
• The methods setIgnoreCampaignAttributionForSources and getIgnoreCampaignAttributionForSources have been added to the JavaScript tracker. They allow setting/getting sources whose campaign values in the current URL should be ignored for attribution. Matching campaign parameters are still kept in the tracked URL/request.
• Record::setAggregatedRecordTransform() lets a blob record register a callback that is applied to its aggregated table during non-day archiving, after the day blobs are aggregated together and before the table is truncated and stored. Use it together with Record::setBlobColumnAggregationOps() (marking a column 'skip') to recompute columns that cannot be summed across child periods for example a table-relative ratio, index or score so they can also be used as the sort column for truncation. It applies on both the standard blob path and the built-from-flat path (Record::setBuiltFromFlatRecord()), where the flat base record and the hierarchy rebuilt from it are each transformed on their own table. A matching optional $postAggregationTransform parameter was added to ArchiveProcessor::aggregateDataTableRecords().
• The reporting menu can now be split into several top-level sections (in addition to the default "Analytics" menu). A category declares which section(s) it belongs to via Category::setGroups() (and the protected $groups property); API.getReportPagesMetadata now exposes a groups field per category. Each non-default group automatically gets a top-menu entry that opens the regular reporting single-page-app filtered to that group (the active section is carried in the URL hash), so reports stay within the same SPA and quick search. The first such section, "AI Insights", surfaces the existing AI Assistants reports.
• datatable_archiving_maximum_rows_actions_flat caps the number of rows used when flat-archiving page/title Actions reports before the hierarchy is rebuilt (set to 0 to keep the legacy hierarchical-only Actions archiving). See Record::setAggregatedRecordTransform() above.
• datatable_archiving_maximum_rows_ai_chatbot_content caps the number of content URLs (pages/documents) listed in the AI Chatbots Content Requests reports.
• datatable_archiving_maximum_rows_ai_chatbot_favoured_pages caps the number of page URLs listed in the Human-Favoured / AI-Favoured Pages reports.
• live_ai_chatbots_maximum_rows caps the number of AI chatbots listed in the real-time AI Chatbots reports.
• live_ai_chatbots_top_page_urls_maximum_rows caps the number of page URLs listed in the real-time AI Chatbots top page URL reports.