Changelog

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.

There was an incorrect class property name that could potentially trigger a fatal error upon activating Independent Analytics.

If you aren’t able to use a class to track a link, you can now use an element’s ID to track it instead.

There is a new function documented in the API article that lets you grab the most popular posts of any post type from any date range.

If you are setting up a new site and then want to reset the analytics, you can reset all the data, and it will no longer delete the created link patterns or campaigns.

All translations in Independent Analytics Pro were updated.

They were reported as “Referral” type referrers until now.

Going forward, you will be able to see Facebook Ads traffic separately from your organic Facebook traffic.

You can choose from dark, light, or system to let you computer’s settings dictate whether IA is in dark/light mode.

You can set the IAWP_DISABLE_GEO_TRACKING constant to true in wp-config.php to disable geotracking.

On some sites, the required MMDB file fails to download and unzip. The retry mechanism attempts to resolve this on its own without requiring manual intervention.

The Buddy Boss theme, in particular, was affecting the styles of spinning icons in the UI.

The date picker is only scrollable on very short screens, so the scrollbar does not need to always be present.

The option to minify JS files was preventing the tracking script from firing, so it is now programmatically excluded from this option in their plugin

A check was added in case none of the recognized options for WP Cerber were found when checking for REST API compatibility.

If you are using the view counter, you may not want visitors to see the count on your less popular pages. With this new option, you can limit the view counter to only display when a page has X views or more.

There is a new retry mechanism that can auto-fix database migrations when Independent Analytics is updated.

If the date range contained the beginning/end of DST and the site is in the Azores timezone, data after the beginning/end of DST wouldn’t show in the chart.

You can now see the number of views the shop page has had in the admin toolbar, like other pages.

Before now, authors/contributors/etc could see the View count for all published pages in the Posts menu.

It was possible for the option to delete all data to leave some tables on the site. That is now fixed.

It was possible for a cached DB value to cause the Overview report to repeatedly fetch the modules, leading to very high CPU usage.

The line charts could be displayed too short, but they now fill the available space.

There was a mistake that caused the buttons in each module to have an ugly white background show up behind them when hovering over the module header.

If resizing a pie chart from two columns to one column, it would display out of position.

Their layout was not working properly when made two columns wide, and a potential JS error was resolved.

The email report now always takes DST into consideration when scheduling and rescheduling.