We improved the unsubscribe option in scheduled reports and alerts. Now antivirus software won’t automatically unsubscribe you from them.
Integrations
New
iOS SDK and Android SDK are now available for React Native. You can now collect data from mobile apps created with React Native, just like you did for native mobile apps.
On dashboards, you can now stack or group bar charts.
Tag Manager
Fixed
You can now use the YouTube video tracking tag and HTML5 video tracking tag in single-page applications without any problems. We fixed an issue where a script would sometimes fail to recognize videos in single-page applications.
Audience Manager
Fixed
You can now use widgets from Consent Manager > Forms > Privacy policy in single-page applications without issues. We fixed a problem where widgets wouldn’t load correctly in single-page applications.
Administration
Improved
You can now quickly copy the site or app ID using a copy button.
Fixed
We removed an unnecessary UUID from API call payloads.
Tracker
Fixed
We fixed an issue in the following options: (1) Tag Manager > Piwik PRO (tracking code) > Recognize a visitor across domains and (2) Tag Manager > Piwik PRO (tracking code) > Recognize a visitor across subdomains. The mechanism adds the pk_vid parameter to the page URL to pass the visitor ID between domains, but the bug would sometimes add the ?& characters at the end.
Integrations
Improved
iOS SDK and Android SDK are now on the same version and work the same way. This alignment will make it easier for you to work with our SDKs.
iOS SDK received some updates, including: (1) It tracks sessions more precisely; (2) It works in dry-run mode; (3) It sends data about the tracking source to the tracker debugger, and more.
Android SDK received some updates, including: (1) It sends data faster to Analytics – in 30-second intervals; (2) It tracks content impressions correctly; (3) It sends data about the tracking source to the tracker debugger, and more.
The social media source is now correctly assigned to sessions. Example: Source/medium: Facebook/referral. You can see data for social media sources in Reports > Websites& social > Social.
Thanks to wider bars, bar charts on dashboards are now easier to read.
Administration
Improved
We added a new privacy option in Administration > Sites& apps > Privacy > Don’t collect visitor’s device data to help you comply with the German Data Protection Act (TTDSG) and similar privacy laws. When this option is turned on, you won’t read screen resolution and browser plugins from a visitor’s device without consent.
User interface improvements.
Tracker
Improved
We now validate the tracking source version sent in the ts_v parameter via the tracking HTTP API.
In single-page applications, the tracker now collects data more accurately. Page performance metrics are sent only with the first page view. Previously, they were sent with each virtual page view, which distorted reporting.
In single-page applications, the tracker now tracks downloads and outlinks more accurately. Previously, the tracker ignored links added after the enableLinkTracking command was executed.
Integrations
New
Microsoft Power BI integration (beta) that lets you connect data from Piwik PRO and create powerful data visualizations on dashboards and reports in Microsoft Power BI Desktop.
In the tracker debugger, you can now see a tracking source like a JavaScript tracking client, web-log analytics, iOS SDK and more.
In the attribution and user flow reports, you’ll see a message warning about unsaved changes.
A browser name, device brand, operating system, search engine and social media source are now recognized more accurately. We updated dictionaries that help recognize them.
You can now see custom dimension names instead of dimension IDs in the tracker debugger.
Fixed
The Expand all and Collapse all options in the session log report now work correctly for meta sites and apps.
Tag Manager
Improved
You can now see detailed container’s errors in your browser’s developer console. The detailed errors help you identify problems in your tracking setup. These errors can also be reported in Analytics > Reports > Custom events when this option is turned on: Tag Manager > Tags > Piwik PRO tag (tracking code) > UX issues > Detect JavaScript errors.
Administration
Improved
User interface improvements.
Tracker
Fixed
When a campaign keyword is not available in the page URL, you’ll see No data in reports. Previously the tracker assigned a referrer domain when a campaign keyword was missing.
The tracker now handles user IDs that have special values correctly.
Session time is now counted more precisely to reflect the real session time. After this change, your session times may look a bit longer.
You can now use web-log analytics with the new tracker. Web-log analytics lets you collect data from a log file stored on a web server. It’s an alternative to using a tracking code.
Now sessions aren’t split if campaign keywords are taken from the referrer.
Page URLs now don’t contain a question mark when any of these options is turned on: Administration > Data collection > Remove parameters from page URLs or Administration > Data collection > Remove keyword parameters from page URLs.
Integrations
New
Google Data Studio integration that lets you connect data from Piwik PRO, combine it with data from other sources, and create powerful reports and dashboards in Google Data Studio.
Dashboard tooltips in the Microsoft Edge browser are now displayed correctly.
You can now always add custom channel grouping to a line or bar chart. We fixed the bug that blocked adding it in some cases.
Tag Manager
New
HTML5 video tracking tag that lets you collect data about interactions with videos on your site or app.
YouTube video tracking tag that lets you collect data about interactions with videos on your site or app.
Administration
New
You can now install our product more easily thanks to new installation instructions for Google Tag Manager, iOS SDK and Android SDK. You can find them under Administration > Sites& apps > Installation.
The JavaScript tracker now tracks custom errors when you use _paq.push(['trackError', ErrorObject] or _paq.push(['trackError', errorMessage, errorSource]).
