The goal ID is now unique for the whole account. It used to be unique only on the site/app level. (Make sure your dashboards, segments, calculated metrics, dimension value grouping and meta sites/apps report goal data correctly after this change.)
Goal mapping in a meta site/app is now easier to set up. You can choose a site/app and goal name from the picker.
Fixed
The IPv6 address is now visible in the tracker debugger.
Tracker
New
We switched from the goal_id to goal_uuid. We encourage you to use the goal_uuid to track goals manually. The goal_id will still work, though.
Improved
We increased the limit of keywords tracked in your internal search from 65535 to 4294967295.
Fixed
We fixed an issue with tracking JavaScript errors. Events with too long error messages were treated as broken events.
Now you can find the number of unique product purchases in Ecommerce > Order list, so if someone bought 5 pieces of 1 product, the report presents 1.
The Quantity metric in ecommerce reports now shows the number of all purchased items.
Fixed
The Average Order Value metric is now calculated correctly.
Administration
New
You can now see the current and the new subscription comparison when you attempt to change the license key in Subscription > Enter a subscription key.
Improved
The Installation view now looks better, thanks to the improved design.
The 2FA authorization screen now has a better design.
Tracker
Improved
You can now use the full potential of the additional tracking dimensions: continent, country, city, lat, long. Any data provided within them will overwrite the Geolocation Database lookup result.
Now continent, country and city parameters can contain any string that will be copied to reports.
If the country parameter is a valid “ISO 3166 alpha 2” country code, you’ll see its name as the country name. Lat and long have to be decimal values.
Integrations
Improved
You can now use Google Data Studio connector filters the same way as custom reports and dashboards filters.
You can now use up to 200 slots for an event custom dimension and 200 slots for a session custom dimension. We increased the number of slots to give you more flexibility.
We set a limit for heartbeat pings counted as actions in our free and paid plans. If you use more heartbeat pings than page views, they won’t count towards your total action limit. You can see a breakdown of actions tracked in a month in Administration > Subscription > Plan.
You can now buy more actions in our free Core plan. Click on the upgrade buttons inside our product or go straight to https://piwik.pro/checkout/.
Integrations
Fixed
In Google Ads integration, data for dynamic ad groups is now imported correctly from Google Ads.
Quick filters in core reports and custom reports: You can now easily filter out data in tables using multiple conditions and regular expressions (regex).
Improved
You can now click on links to pages in Custom reports > User flow > Show all paths.
Deprecated
In August 2022, we’ll stop collecting data for the following dimension: Designated market area (DMA). The change is due to the new geolocation service that doesn’t provide such data. This dimension is no longer available in custom reports, but it is and will be in core reports (for access to historical data).
Tag Manager
Improved
We renamed these tags to align with the current brand names: Floodlight Counter (was DoubleClick Floodlight Counter), Floodlight Sales (was DoubleClick Floodlight Sales), Meta Pixel (was Facebook Pixel).
Removed
We removed outdated third-party tags: Clicktale Tracking Code and DoubleClick Conversion. Clicktale and DoubleClick no longer support them.
Tracker
Improved
We published a package for web log analytics on GitHub and Python Package Index (PyPI). You can now quickly analyze log files from your site in Piwik PRO.
Integrations
Improved
Our Angular tracking library now supports Piwik PRO versions lower than 16.0.0.
The total revenue in Analytics > Ecommerce > Ecommerce overview now shows correct data.
Administration
Improved
Clearer installation guides: You can find updated instructions on installing Piwik PRO on websites and mobile apps in Administration > Sites& apps > Installation.
In the site inspector for Chrome, you can now choose to see scroll data collected automatically or manually. We recommend switching to the automatic method.
Our React library now supports Content Security Policy (CSP). To use CSP, you need to add the nonce-string parameter when initializing the tracking library in React.
You can now add an additional dimension in core reports and custom repots (explorer type). This lets you see data for two dimensions in a single view.
Fixed
The values for the source, medium and source/medium dimensions are now lowercase. Example: google, bing, baidu.
Administration
Fixed
Visitors’ IP addresses are now fully masked when this option is used: Administration > Sites&apps > Privacy > Ask visitors for consent (on) > Collect data without using cookies (on).
Tracker
Fixed
Outlinks containing a child node are now tracked correctly.
Integrations
Improved
In our iOS SDK and Android SDK, you can now use a dedicated method to collect data from campaigns that use deep links (URI instead of URL).
In our React library, you can now use the DataLayer.push() method to push data to the Tag Manager’s data layer.
Ecommerce reports now show all data correctly on meta sites & apps. We fixed a bug that was hiding some collected data.
Tag Manager
Improved
Variable names can now contain a dot. Example: author.blog.
Tracker
Improved
Ecommerce events are now tracked correctly on pages with search results. Our mechanism used to incorrectly register such events as internal searches.
Integrations
Fixed
In Google Search Console integration, Google data is now displayed correctly in Analytics > Reports > Google Search Console.
In Google Data Studio integration, the drop-down selector now shows all available sites or apps from Piwik PRO. We fixed a bug that showed only ten sites or apps.
Single-page applications are now tracked automatically – page views are sent with each change of the browser history state. You can turn SPA tracking on or off in Administration > Sites& apps > Data collection > SPA > Track page views in a single-page application.
Tracker
Improved
Our JavaScript tracker now uses the [navigator.sendBeacon()](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon) method to send data from a client to a server. This method is more reliable than the previous one because it sends data asynchronously and doesn’t impact the loading of the next page.
Our JavaScript tracker now uses the [PerformanceNavigationTiming](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface instead of the legacy [Performance.timing](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing) property to measure page performance metrics.
Integrations
Fixed
We fixed a bug blocking some data downloads in the site inspector for Chrome. Now you’ll see all collected data for heatmaps, clickmaps and scrollmaps.
