Changelog

Previously, you could edit the footer background color, but not the text that shows in it. You can now edit both.

If you’ve already configured the email report to send to yourself and your clients, you can now choose to send the test email to the first email address only, so it doesn’t go to all your clients.

The file extension link pattern can now recognize the following nine extensions: aac, ai, dmg, eps, gz, msi, rar, sketch, and tar.

When you create a new campaign with the Campaign Builder, it now creates a much smaller, auto-dismissing success message.

The Recent Views module now includes a clickable link for every page listed, making it easier to check out the pages your visitors were viewing.

When you click on a report, the page now loads immediately instead of waiting for the Quick Stats and chart to load. Those are loaded in a second request after the initial page loading, leading to a smoother loading experience that feels faster.

There were a few plugins that showed their admin notices in the Analytics menu, so we hid them to remove the unnecessary clutter on our page.

If you’re using the My Private Site plugin and have enabled the setting that disables the REST API, you will now see a warning in the Analytics menu notifying you that visitors are not being tracked.

The Integrations menu lists every plugin that Independent Analytics Pro has a custom-built integration with. Each integration now links to its own page on our website.

When updating via the Dashboard > Updates menu, the Independent Analytics Pro icon would often fail to load. It’s now bundled in the plugin so that it will always display.

A long UTM Source value without any spaces could overlap into the Pages Viewed column. It now wraps into a second line if it’s too long to fit in one line.

If your site has WordPress installed in a custom location, this was causing the Campaign Builder to create links that use that URL as the base instead of the site’s true homepage URL.

The Pages report was displaying URLs based on the WP install location, rather than the homepage URL.

The event category archive pages improperly report as both custom taxonomies and custom post type archive pages. Independent Analytics now detects if pages qualify as both and counts them as custom taxonomies. This fixes the results in the Pages report that show “-” for the title and “http://0” for the URL.

The option to add a cookie to your own browser to ignore your activity on the site was working well, but it wouldn’t remove the cookie automatically if the option was disabled. It now does.

Hovering over a country in the world map shows a tooltip with stats from that country. In some browsers, it did not disappear when you stopped hovering over that country.

This PHP notice was appearing on every page load due to a translation being loaded too soon in the WP startup process.

This update added a new form tracking integration for Request a Quote for WooCommerce. This lets you view the number of quote requests you’ve gotten from each traffic source, UTM campaign, and more.

The Gross Sales filter could be used to find journeys that include a certain sales volume, or any sales at all. Now, you can also filter by zero sales in order to find journeys where customers didn’t buy anything. Combined with tracking clicks on Add to Cart buttons, this gives you a way to find shoppers who abandoned their carts.

Updating this library allows Independent Analytics to recognize more bots to exclude them from tracking.

If your site has pages with missing titles, these could cause errors in the User Journeys report. Now they display as “(Untitled)” and allow the report to load fully.

Fixed a PHP notice that could show up on page views.

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/.