The previous compatibility fix for versions of MariaDB 11.4 and higher resulted in a performance drop for sites using MySQL. This update resolves the performance drop while maintaining compatibility with MariaDB.
Sites using MariaDB 11.4 or higher for their databases were experiencing an error that prevented the data table from loading.
There was an issue that could prevent Forminator forms from getting tracked on some websites.
Solo Reports allow you to view a dedicated report for any page, referrer, location, device, campaign, link, or link pattern. Browse the Quick Stats and chart, and find segmented data tables from every other report type.
You can now add a cookie to your browser to ignore your own activity on your site, even when you’re not logged in. This is available via the Ignore via User Role setting. Learn more here.
We’ve included these three longer date ranges for all modules in the Overview report.
Some users found the progress bar very distracting, so it’s been removed.
Update all translations in the PRO version of Independent Analytics (free version already updated.
The tracking script was not previously firing for sites in maintenance mode created by the popular Maintenance plugin.
If you’re using the REST API Toolbox plugin and disable the REST API, you’ll now receive a helpful notice prompting you to re-enable the REST API to allow IA to track your visitors.
Visitors from the Pinterest iOS app recently started showing up with the referrer 429047995. They will not be recognized as coming from the app.
30+ Pinterest subdomains from different locales are now being recognized and flattened into the same Pinterest referrer to make traffic analysis easier.
Two new filter hooks have been added for developers who need to track views on pages that don’t use the WordPress ID system.
Resetting the stats to zero would still show the former stats in the Overview report until the Refresh link was clicked.
Pages could show up even if they had 0 entrances and 0 exits.
There has been an ongoing issue, particularly with webgo.de, that caused the Analytics menu to show uncompiled code or a fatal PHP error. That has now been resolved.
There was a minor bug that could cause light/dark mode to not activate properly due to a common conflict with other plugins
It was possible for a deadlock error to be triggered upon a post being viewed.
IA was validating the existence of the MMDB file used for geolocation on every admin page load. Now, it only checks once per day.
You can now programmatically add analytics data from IA into the MainWP Pro Reports email by using the provided tokens.
Some special characters could appear encoded when exporting reports to CSV and opening them with Excel.
The link text has been reworded, and they now open in new tabs when clicked.
Thrive Leads submissions were going untracked in the analytics.
Incorrectly formatted ID link patterns could be added without error. Now, these issues are caught and prevent badly formatted link patterns from being created.
Further improvement to the reliability of click tracking. Namely, this update gets tracking to work for sites that have limited permissions for temporary files.
You can now conveniently see which plugins Independent Analytics Pro integrates with in the Integrations menu, with your currently installed plugins highlighted.
Forms in Fluent Forms Pro are now tracked upon submission, whether or not they require double-optin.
If the site’s temporary directory is non-persistent, it will now be avoided, and a PHP file will be used instead to store the click data.
It was possible to trigger an E_ERROR due to an SQL deadlock when bulk updating a large number of posts.
The database request used to create the tracking script has been removed, so a large influx of bot visits can no longer trigger a max_connections error.
Implemented a backup solution for sites that are blocking the Ajax request used to load the Overview modules.
If you’re using the Independent Analytics for MainWP extension, you can now display stats in the Pro Reports sent to your clients.
The view counter could show up inside excerpts used in widgets outside of the main content.
Visitors coming from subdomains like go.bsky.app weren’t getting recognized as coming from Bluesky.
It now always gets the site’s active timezone.
The edit buttons were overlapping the module titles for right-to-left language websites.
In the Clicks report, the Target column was omitting any Hebrew characters in the URL. This likely was affecting other languages as well.
Ampersands now display properly when downloading a CSV table report.
There was a fatal error on the page if a non-admin with permission to view the analytics but not edit them viewed the analytics before the “Getting Started Guide” notice was dismissed.
If you use the Admin Site Enhancements Pro plugin to disable the REST API, the warning that IA shows now recognizes if you have whitelisted the iawp/search route.