Changelog

This update did not edit any plugin files and only included adjustments and fixes to the readme.txt file used to create the page on the plugin repository.

You can now filter the User Journeys report by the landing page URL or any page’s URL.

For example, you can view journeys where visitors landed on a page containing “/resource/” in the URL, or you can view journeys where visitors looked at the “/blog/awesome-post/” page at any point during their session.

If you’re using the Complianz plugin and would prefer to track visitors with Independent Analytics only after they agree to your consent pop-up, that is now possible by checking a single box in Complianz.

While we don’t view this as necessary for most sites, it is a good option for those who want the strictest adherence to their local privacy regulations.

The Campaign Builder now shows inline error messages if you try to create a campaign link without the required fields or when using a full URL in the landing page path.

We tested with WP 7.0 and made some minor fixes to the interface to maintain the current design.

If you gave users the ability to view the analytics but not edit the settings, they were unable to save a default report. Choosing a favorite report is user-specific and won’t affect anyone else’s view of the analytics, so we added this option for them.

Clicking the “Refresh” link in the Overview report didn’t update the timestamp when the report reloaded. It now updates immediately after the data reloads.

Users who could view but not edit the analytics could not make changes to the Overview report, but the buttons to add modules and customize them were still visible. They have been removed for these users.

The Top 10 lists in the email report show the view count but were sorted by visitors, causing them to appear out of order. They are now sorted by the number of views.

Updates for Independent Analytics Pro would fail when bulk updating plugins via the Plugins menu. Freemius patched this in their latest SDK update, which is included in this version of Independent Analytics (Pro).

Changing the grouping of a table caused the columns to reset. For instance, if you hid the Visitors column and showed the Clicks column and then switched the grouping from Countries to Cities, it would add the Visitors column back and hide the Clicks column.

The chart was displayed at a very small size for any users with a right-to-left language website viewing their stats in the Safari browser.

The white-labeling now strictly adheres to admin accounts only, so if you create a custom user role for a client and give them the manage_options capability, the interface will remain white-labeled.

If you have user roles on your site that can view stats for authored-only content, the Pages report would crash when they viewed it.

Tracking clicks on form submission buttons could lead to form submission events getting overcounted because the click and form submission take place at the same instant.

If a non-admin is viewing the analytics and they’ve been white-labeled, they will no longer see the pop-up for the Getting Started tutorial video.

For “known referrers” like Google and Facebook, the links to these sites were broken in the Referrers report. They are now clickable and open the correct URLs.

Resolved an error that prevented Solo Reports from loading in the Pages report.

Resolved a PHP error that could occur when loading a report for a user with stats limited to their own content.

Visiting the Clicks report with any date range that contained zero clicks caused a fatal PHP error.

Translations were automatically updated for eight different languages in the free plugin via translate.wordpress.org. This update includes those same translations for Pro users.

Certain security features could prevent the asynchronous background task from loading the modules. The Overview now loads by triggering its cron event when viewed.

The vast majority of servers use UTC+0, but for those that don’t, the click tracking feature wasn’t recording clicks.

If a form’s submission button was being tracked with a link pattern, the total number of form submissions could get overcounted to include the click event.

If you have automatic data pruning turned on, the message text could break when email report delivery is paused.

For example, if your site is using Independent Analytics Pro and WooCommerce is installed, and your store has zero recorded sales, the eCommerce metrics in the Quick Stats would show “0” when filtered instead of “0/0” indicating a filter has been applied.

Selecting a User Journeys report for a module would cause a fatal error. Allowing them to be selected was an oversight, and that has now been removed as an option.

For sites without the Imagick PHP extension, favicons would not get generated for the Referrers and User Journey reports. Only the default top 100 sites would get favicons since those are packaged with the plugin.

v2.14.0 added a new daily cron job that gets current values for the site’s average views per session and session duration, which is used for the color gradients in the User Journeys report. This cron job was triggering a PHP error due to an “out of scope” function.

It was not clear that the Landing Page filter was for the title, and not the URL of the page. It is now called the Landing Page Title filter. Likewise, the Page filter was renamed to Page Title.

In Solo Reports, the values for the Visitors Growth and Views Growth columns were not calculated based on the single item being viewed.

Solo Reports were loading much more slowly in Firefox than in other browsers.

v2.14.0 added new favicons to the Referrers report and User Journeys report. The option in the Settings menu to delete all plugin data wasn’t removing the favicon images added to /wp-content/uploads/.

With the new User Journeys feature, you can explore every session recorded on your site. Each one includes a full timeline, letting you see exactly where each visitor came from, which pages they looked at, and any conversions they completed (clicks, form submissions, and eCommerce orders).

Form tracking has been added for Mailchimp for WordPress, Newsletter, Kadence Blocks, and Everest Forms.

When viewing a WooCommerce order, the Customer Journey box now includes a link to all their sessions in the User Journeys report.

Sites using WooCommerce and the YayCurrency plugin will see the eCommerce metrics in IA automatically adjusted to use the store’s base currency.

Line charts in the Overview were hard to read without hovering over the lines to see the legend. Now, the labels are visible by default, so you can easily distinguish between each line.

Before, you had to hover over a pie chart to see the percentage. This is now plainly displayed next to the labels, and the segments are sorted from largest to smallest, making it easier to read.

If you are sending the email report to a group of coworkers, you may want to pause the delivery over the holidays or at other times. You can now do this in one click.

Updated the translations in the Pro version to catch up with the free version.

The salt token can now be refreshed daily, weekly, or monthly.

The data table in the Referrers report now shows the favicon for each site. For some sites, a backup icon will be displayed instead, using a random color and the first letter of the site’s domain.

This should lead to a modest improvement in accuracy when deriving visitor geolocations from their IP addresses.

This allows Independent Analytics to recognize a larger number of device types, including some bots that can be blocked from tracking.

Users with either one of these plugins installed will be notified if an option that disables the REST API or impacts tracking has been enabled, so they can disable it.

Phone numbers in the Target column could display ugly encoding characters if they included a space. Those have been removed so that spaces display normally.

Applying certain filters could cause the number of form submissions to be overcounted in the Quick Stats and chart.

If a form had a title that was more than 64 characters long, the tracking would silently fail. This affected all form integrations. Longer form titles are now trimmed to 64 characters.