Track your WordPress site easily and with lots of metadata: views per author & category, automatic tracking of outbound clicks and pageviews.
|Author:||MonsterInsights (profile at wordpress.org)|
|WordPress version required:||3.8.0|
|WordPress version tested:||4.9.5|
|Added to WordPress repository:||14-09-2007|
|Total downloads:||27 894 266|
|Active installs:||1 000 000+|
Click to start download
The overview report
Top countries and referrals
Top posts and pages
Authentication with MonsterInsights
For all frequently asked questions, and their answers, check the MonsterInsights Knowledge base.
- Install Google Analytics for WordPress by MonsterInsights either via the WordPress.org plugin repository or by uploading the files to your server. (See instructions on how to install a WordPress plugin)
- Activate Google Analytics for WordPress by MonsterInsights.
- Navigate to the Insights tab in your WordPress admin menu and configure the plugin.
- Want more features? Purchase MonsterInsights Pro!
7.0.5: April 9, 2018
- New: Introduced a system (behind-the-scenes) that automatically attempts to correct for improperly set timezones in the WordPress settings panel, server timezone settings and/or GA profile timezones. This should eliminate issues with timezones on Lite user accounts, as well as allow for more accurate date reporting.
- New: Introduced a system (behind-the-scenes) to allow for deauthentication of profiles set on websites whose profiles were migrated (for example from a staging site to a production site)
- Tweak: Made clientID retrieval more efficient.
- Fixed: Several translation/textdomain and typo fixes.
- Fixed: Undefined $num in the overview report.
7.0.4: March 7, 2018
- New: We’ve added links to the pages listed in the top pages part of the Overview report to make it easier to see which page each title belongs to.
- New: We’ve added the UA code to the account selector to make it easier to determine which property to use.
- New: Better compatibility with IE11.
- New: The links to view more reporting data now default to the currently selected daterange when you go to analytics.google.com
- Fixed: We’ve corrected some missing closing li tags on the overview report.
- Fixed: We fixed an issue where get_current_screen might be undefined on some pages.
- Fixed: We fixed an issue where some improperly configured servers might resolve symlinks that are not supposed to be resolved, leading to issues with loading asset files MonsterInsights uses.
7.0.3: February 28, 2018
- New: We added support for tracking download files that have a cache busting variable on the URL.
- New: We added support for the new UserID mode used in our AMP addon.
- Tweak: We fixed a bug with the notices class, and drastically cut back on the number of them.
- Fixed: We fixed a bug with our Facebook Instant Articles addon that prevented some users from being tracked for downloads.
- Fixed: We fixed a bug in the usage tracking for some types of installs.
- Fixed: We’ve allowed the disabling of tracking for admininistrator role users on single sites.
7.0.2: February 27, 2018
- Fixed: Fixed a bug with the analytics.js output where a UA code wasn’t entered, the $reason variable could be undefined.
- Fixed: Fixed an issue where a notice might not be dismissable and we’ve also removed several of them.
7.0.1: February 26, 2018
- New: Support for the updated version of MonsterInsights AMP plugin which switches from using a custom REST endpoint to using the now built in Google AMP ClientID synching feature. If you’re using the AMP addon, you’ll want to also update that addon as well.
- New: The __gaTracker and disable tracking functions will always be defined, even when we’re not tracking users (for example if viewing a preview, or if a logged-in administrator) to allow sites to not have to worry about breakage when variable exist checking isn’t done.
- New: We now output a notice in the console and output the GA code (though do not run it) when we’re not tracking someone. This makes it easier to verify the Google code is indeed outputting, and also makes it more clear as to why a particular user isn’t being tracked. Note, when testing Google Analytics code, always do it logged out, ideally in the private browsing/incognito mode of your web browser. We’re going to keep working on improving the frontend system to simplify it and add new features for both Lite and Pro users now that we’ve jettisoned ga.js support in MonsterInsights 7.0. You’ll see updates through the year that add new tracking features, particularly ones that we’re tweaking in order to expand and refine our built-in reporting.
- New: We added a “have a MonsterInsights license” link on the settings panel, to make it clearer the procedure for the quick and easy upgrade from MonsterInsights Lite to MonsterInsights Pro.
- Tweak: We removed the phrase referencing the dashboard (removed in MonsterInsights 7.0) from the permissions settings.
- Fixed: Due to us forgetting to include our jQuery shim for disable() in the Lite, some users were unable to use the 10/25/50 expand feature on the reports page.
- Fixed: An accidental use of the PHP function date instead of the one called time meant that some users were unable to see updated reporting data each day in the Lite version.
- Fixed: In sitei() in the api-auth class, we used mb_strimwidth to trim the final string to 30 characters. While this is a great PHP function, not all servers have the mbstring (Multibyte String) PHP extension installed, from which all mb_* functions are provided, despite it being a “required” PHP extension to use WordPress core. This caused some servers to be unable to authenticate and thus get our amazing new reports (sad face). This usage has been replaced with a standard substr use, thus allowing for compatibility with all servers.
7.0.0: February 20, 2018
- New: Completely revamped reports with a new UI.
- New: Ability to oAuth at the network level, and have that oAuth apply as the default to all subsites (can still override at a subsite level).
- New: Ability to enter a license key at the network level, and have that oAuth apply as the default to all subsites (can still override at a subsite level).
- New: Completely new oAuth flow, that handles more errors and allows for future growth. Importantly, your existing sites will continue to track (the UA code is manually moved in the upgrade process), but you will need to re-authenticate (a quicker, and even easier process in 7.0) to enable our all new reporting area. New permissions requested to allow for significantly expanded reporting (and some upcoming reports).
- New: Ability to see the site traffic graphs in both pageviews and sessions.
- New: You can now choose between Last 30 days, Last 7 days, or any date range of your choosing if you’re a paid MonsterInsights user!
- New: Compare site traffic to the previous period.
- New: Completely revamped overview report. You’ll find lots of new data has been added. Also, all of that data changes as you use change the date ranges (a Pro exclusive feature).
- New: A brand new eCommerce report for Pro users
- New: A brand new Search Console/Queries report for paid MonsterInsights users. This allows you to see which terms you are ranking for on Google and how Google searches are driving your site traffic, along with clickthrough rates.
- New: A brand new Publishers report for Plus level users allowing you to see breakdown of important site metrics.
- New: A lot of behind the scenes work enabling more reports to be added in the future. Stay on the lookout as we start significantly expanding the breadth and depth of reporting this year.
- New: A revised general settings panel which is significantly faster to load.
- New: Significant performance improvements. We completely top-to-bottom audited MonsterInsights. It’s now 286% faster in the admin and 161% faster in the frontend.
- New: Completely new internal notification handling has been implemented. This should make it clearer if you need to address anything, and if so make it less tedious to figure out exactly what.
- Tweak: We’ve changed the verbage for what users see if they are logged in as a site administrator on the frontend to make it more clear MonsterInsights doesn’t track site administrators to prevent them from skewing their own Google Analytics data (particularly demographics data) and to encourage them to use the Incognito Mode/Private browsing mode of their web browser (or log out) if they want to view the Google Analytics code.
- Tweak: The URL used for the measurement protocol calls has been updated per Google guidance.
- Tweak: We’ve discovered some strings that weren’t translatable, and fixed that.
- Tweak: Based on your feedback, we’ve clarified the titles and descriptions used in some of the settings to make it more clear as to what they do.
- Tweak: When first adding a license key, in rare cases sometimes the addons permissions didn’t sync. While extremely rare, and while MonsterInsights would automatically fix itself within 6 hours, we’ve added a system that eliminates this from happening, and made sure that there’s also a way to fix this manually if this need arises.
- Tweak: The countries map has been changed to a countries list (sorted). This means we can remove jVectorMap which had some issues in mapping, and also make it easier for you to see your top countries data.
- Removed: Support for the long deprecated PHP events tracking has been removed. We’ve had dismissable (and then later non-dismissable) persistent admin notices for over a year now offering a 1 click update. The PHP events tracking, a stayover from the Yoast years, caused a lot of issues and couldn’t track everything on a page. It could only track things in specific WordPress areas like the_content and widgets, but couldn’t track anything outside of that, or things that were added to the DOM after WordPress rendered the page. Our JS events tracking system can track all-the-things on all parts of a page, and is far more accurate and easier for us to maintain. Maintaining a gigantic PHP regex-based system took a lot of our development time up, and based on our opt-in tracking data, almost no one uses it anymore (which is good, because JS tracking is so much better). Users still using it will be automatically switched to JS events tracking on update (which requires no changes to switch to using it).
- Removed: Many deprecated filters from the Yoast era have been removed. After maintaining backwards compatibility for over a year now, and also issuing a notice every time those deprecated filters were used, it’s time to pull the plug on these to allow our tracking system to be able to be simplified in the future. We have a complete document in our documentation for the 6.0 release that details exactly how to update for each of these filters.
6.2.6: November 17, 2017
- Tweak: Compatibility with WordPress 4.9.
6.2.5: NOT ISSUED
- Skipped release version.
6.2.4: October 6, 2017
- Tweak: Adjusted how the optin tracking is sent to us.
6.2.3: September 9, 2017
- Tweak: Added a notice for new users of MonsterInsights about when the reports will begin populating.
6.2.2: August 16, 2017
- Tweak: Adjusted order of setup/config notices
- Fixed: Fixed an issue with the sanitation of number fields. Solves an issue with the Google Optimize extension.
6.2.1: August 9, 2017
- New: MonsterInsights now has the ability to automatically update itself and it’s addons. You can set MonsterInsights to automatically update minor versions only or all new versions inside the MonsterInsights settings panel in Tracking -> Permissions.
- Tweak: Introduce scrollbars on GA auth screen for users with many Google accounts
- Tweak: Added notice to users still on deprecated GA.js tracking and PHP-based events tracking.
- Fixed: Issue with notices having multiple icons has been resolved.
- Fixed: Facebook Instant Articles can now properly handle the Automattic Facebook plugin transformation changes (requires FB IA addon version 1.0.1 or newer)
- Fixed: Conflict with wp_head output for some themes.
- Fixed: Correct level for Forms and Google Optimize addons.
- Fixed: License key errors will no longer show to lite users.
6.2.0: June 6, 2017
- New: Form Tracking addon
- New: Google Optimize addon
- New: Facebook Instant Articles addon
- New: Telephone link tracking
- New: Functions for supporting enhanced eCommerce tracking in the eCommerce addon
- New: Measurement protocol functions
- New: Tweaks for the settings pages to get ready for a speed improvement release upcoming along with some coming soon addons.
- Tweaks: Spelling corrections.
- Fixed: Internet Explorer tracking fix.
- Fixed: Issue with initialization of settings on certain installs.
6.1.11: May 31, 2017
- Tweak: Renamed the tools tab for settings import/export
- Fixed: Issue with saving of manual UA codes
- Fixed: Fixed a couple display issues in the admin
- Fixed: Issue for undefined index when the settings array hasn’t been initialized.
6.1.10, May 18, 2017
- New: Performance improvement in tracking.
6.1.9, May 15, 2017
- New: Plugin has been tested for compatibility with WordPress 4.8-beta1. We’ll continue to test through the beta and release candidates, but MonsterInsights is 4.8 ready as-is.
- Tweak: Deleting lite plugin will no longer delete license key of installed pro version.
- Fixed: Import/export settings page has been fixed so that on sites with a ton of plugins installed that make lots of admin bar items, the admin bar will have relative positioning now to allow it to be scrollable.
- Fixed: Users with more than 1 property for the same domain name can now use any of the views for those properties.
- Fixed: For Pro users, sometimes all available addons for your license level didn’t show, requiring you to download them from our site. This has been corrected.
6.1.8, May 11, 2017
- New: Functions needed to support future features including enhanced eCommerce
- Fixed: Compatibility with Firefox for link tracking.
- Fixed: Issue saving certain fields.
6.1.7, April 10, 2017
- New: Changes needed to support new addons, including the Google AMP addon, available as of today.
- Tweak: Comments for frontend are minification-safe.
- Tweak: GA notice is now hidden when debug mode is on.
- Tweak: All settings now use the Settings API framework, including all addons.
6.1.6, March 29, 2017
- New: Select2 filter for the Google oAuth list of profiles, to make it easier to find your Google property by fully supporting search by URL.
- Tweak: Inbound-as-external now is prioritized before downloads in tracking preference order.
6.1.5, March 24, 2017
- New: Added some functions to prepare for upcoming new addon (Google AMP) and updates (eCommerce, Performance, Dimensions).
- Tweak: JS events tracking for click events.
6.1.4, March 23, 2017
- Tweak: JS events tracking for click events.
- Fixed: Edge case where JS events tracking won’t turn on if the main tracking setting was disabled (such as faulty import).
6.1.1 – 6.1.3 (depending on which version of MI you have), March 22, 2017
- Fixed: (pro users) Issue with JS events throwing an error for array on non-set settings.
6.1.0, March 22, 2017
- New: Campaign URL building tool with shortlink capability.
- New: Settings import/export tool.
- New: Experimental (beta) hash tracking for single-page style themes. Note, as the description for the setting says, this feature is a beta feature, and can be tweaked or removed in upcoming versions.
- New: Manual default subsite UA’s can now be set from the network settings panel for MonsterInsights.
- New: Optout of GA tracking is now enabled per Google standard. See https://github.com/awesomemotive/google-analytics-for-wordpress/issues/488 for more information.
- Tweak: Notices about JS conflicts now include the JS error when possible.
- Tweak: Some tweaking to when the “Connection error with Google” error is displayed during oAuth.
- Tweak: Notice now shown when too early to display statistics from Google.
- Tweak: Inbound as outbound links may now have a period in them.
- Tweak: Removed duplicate option checking on frontend.
- Tweak: oAuth dialog now only programically closes when the select profile view is shown or when a new one is opened.
- Tweak: Mailto links are now handled as an externally opening link, allowing to bypass issues with the Safari browser not following standards.
- Tweak: WP-Admin Login page tracking has been removed.
- Tweak: More countries now shown in the country map in the overview report.
- Tweak: License key field is no longer shown on lite installs.
- Tweak: Frontend JS file has been refactored to make it more unit testable.
- Fixed: Download events now correctly include data in all cases not just some.
- Fixed: A syntax error involving the manual UA code input has been resolved that could have affected some users under a rare circumstance.
6.0.16, March 7, 2017
- Fixed: Issues related to link tracking.
6.0.15, March 7, 2017
- Fixed: Issue with translation string numbering in the disabled user group frontend template.
- Fixed: Resolved issue that caused issue with lightbox-style redirects.
- Fixed: Issue where admin pages had JS issues from mis-ordered JS files.
6.0.14, March 1, 2017
- Tweak: Allow for invalid license to be removed if debug turned on.
- Fixed: Issues with internal links being tracked as internal-as-outbound
- Fixed: Issues with tracking of downloads
- Fixed: Issue where optin tracking would opt-out on settings panel save
6.0.13, February 28, 2017
- Tweak: Better detection of issues with authentication due to an outdate WP version.
- Fixed: Issue where JS tracking inadvertantly turned on debug mode due to a bad string to boolean conversion.
6.0.12, February 27, 2017
- New: The JS events tracking has been moved to a new JS file instead of inline. This will offer the same performance as inlining under HTTP/2, but with the benefit of better cache bursting.
- New: Expanded admin adblock detection.
- Tweak: Select2 is now bundled as Select300 in MonsterInsights. We’re pulling down the latest copy of Selct2 and then on-the-fly renaming it. This should end any conflicts between our select2 boxes and other plugins/themes.
- Tweak: We’ve implemented better error detection on the authentication flow. Some users may have previously seen “No profile errors”, due to issues with their server setup will now see more accurate errors.
- Tweak: For servers that use PHP Object caching, the cache will now be flushed during the uninstall routines. This should solve a very rare uninstall error.
- Fixed: A “Invalid UA code” error was displayed whenever someone used oAuth2 and then saved the settings panel, despite having a valid UA code.
- Fixed: An issue with the lazyloading of the Google Client for frontend use has been fixed.
6.0.11, February 24, 2017
- Notice: Version numbers 6.0.5 – 6.0.10 were not used, as we’re synching the version numbers of the Lite and Pro versions of our plugin. You didn’t miss any updates.
- Notice: As of this release, we no longer backport changes to the old
yst_gaoption. If you need to access MonsterInsights’s settings programically, please use our helper functions. Do not directly access a option.
- New: Redesigned authentication dropdown that shows the site urls to make it easier to find a profile when the users have many accounts.
- New: Tracking is now enabled for the WordPress admin login page (wp-login.php).
- Tweak: The Google class in the admin now only checks for blocking when the reauth is attempted. Expect to save a ton of external calls in the admin, and maybe a performance boost.
- Tweak: The GA client object is now lazyloaded on the frontend, so it’s loaded only when something (like another plugin) attempts to use it. In plain English, this will make a alot of sites load times significantly improve.
- Tweak: The analytics.js output has been tweaked to be slightly more asthetically pleasing (its aligned correctly). We realize no one probably cares but we look at this code for every user we support, so it help us.
- Tweak: The config expired notice has been updated to reflect that it can also be shown if the server is blocking MonsterInsights’s ability to connect to Google Analytics.
- Tweak: The cron jobs for opt-in tracking and statistics have been combined into a single cron.
- Tweak: Various performance improvements in the frontend output class.
- Tweak: A notice is now shown when MonsterInsights rejects a manual UA code from being saved for being an invalid format.
- Fixed: Issue where the plugin TweetShare would prevent users from being able to see their properties in the authentication dropdown.
- Fixed: Issue where the manual UA code might not be ported as we were backporting changes to the monsterinsights_settings option to the yst_ga option for backwards compatibility. This lead to a situation where the new settings would override the old ones before the routine to fix the manual UA code issue had run.
- Fixed: Issue where a fatal error from a reference to a class called “Yoast_Frontend_GA” which our plugin doesn’t have or use, would be shown caused by the previous Yoast usage of object caching via an autoloader. This is solved by doing a 1 time object cache flush on upgrade.
- Fixed: Issue where if you had more than 1000 profiles on your Google account, not all would be shown.
- Fixed: App analytics properties are now excluded from the dropdown of properties you can authenticate to.
- Fixed: The readme suggested a filter to use for filtering the UA to use, but the filter name was typo’d. This has been fixed.
- Fixed: Issue where the tracking cron would add a new unique cron each day.
- Fixed: We implemented a routine to cleanup those extra crons as well as the old yoast one we no longer use.
- Fixed: Issue where the .org theme Schema would prevent users from being able to see their properties in the authentication dropdown.
- Fixed: Issue where JS based events tracking might not correctly track a mailto: link.
6.0.4, February 20, 2017
- Tweak: monsterinsights_delete_options now checks to ensure an array is passed in
- Tweak: The reporting class now has many more object property checks.
- Fixed: In install if WP version not supported or if MI Pro was active, the plugin attempted to call a property of the plugin object which didn’t exist.
- Fixed: In the deactivate/uninstall routines, MI attempted to use a method of a class object which might not exist, as it might not be the active instance. Better instance handling has been added as well as many more exists checks have been added througought the plugin.
- Fixed: Conflicting loads when both MI Pro and Lite are installed. Note, you should only have Pro installed if you want to use it. That being said, we’ve done extensive testing to ensure we’ve handled all of the edge cases surrounding this. This could also lead to issues where it would be impossible to remove Lite and/or Pro from a site if both were installed.
- Fixed: Conflicts with the Pinnacle theme, which loads it’s CSS file (with overrides to literally all select2 inputs not just the ones it adds) across the entire admin. This lead to an issue where in the Google Auth, a user might not have been able to see (or could appear with wacky styling) the dropdown of profiles to select. If you cannot see this dropdown after authenticating, let us know as its most likely a simple plugin or theme conflict on CSS styling.
- Fixed: The notices to deactivate/uninstall MI Lite/Pro when the other one were installed had an errant extra quotation mark, and they’re now more specific about the action to take.
- Fixed: For some users, the setting for user role exclusion was not working. This has been corrected.
- Fixed: A redirect issue that was looping for some users. The code that does this, while working for most, doesn’t for some. We’ve removed it until a full investigation can be completed.
6.0.3, February 20, 2017
- Fixed: Path for fontawesome font files was incorrect
- Fixed: Notice in the install routine for the $version variable not being set.
6.0.2, February 19, 2017
- Fixed: Upgrade routine could drop manual UA codes in certain cases. If you upgraded to 6.0.0 or 6.0.1 and it lost the manual UA code, installing this update will automatically restore the UA code entered as long as you haven’t used the oAuth or re-entered the manual UA code.
6.0.1, February 19, 2017
- Fixed: Typo that caused an issue with PHP 7 installs.
6.0.0, February 18, 2017
- New: Completely overhauled design, from top to bottom. The plugin has been completely rewritten.
- New: no more advertisements in the settings pages. We hated them too.
- New: ga.js is now officially deprecated. New users cannot use it anymore, and existing users can only switch to analytics.js (but not back). Please note, all new features will be developed exclusively for analytics.js. Google has deprecated it, and now we’re deprecating our support for it.
- New: License key system now uses the MonsterInsights License management system
- New: Ability to pick which roles can access the dashboard/reports & settings/addons/tools page using our UI. There’s also a new custom capability for this (a meta capability)
- New: Support for Google Analytics Master accounts. When you oAuth into MonsterInsights now, the UA view is now locked to what you picked using the brand new oAuth procedure.
- New: Revamped dashboard
- New: Completely new settings system, with a completely new settings page, and a completely new settings API. Also some new hooks and tabs in preparation for the many addons we’ll be releasing over the next few months.
- New: No more conflicts between the base plugins
- New: Completely overhauled translation experience. The lite version translations are now fully managed through translations.wordpress.org.
- New: Opt-in to anonymous data so we can better improve MonsterInsights
- New: Significantly better addons page
- New: Single license key to manage all MonsterInsights extensions.
- New: Automatic detection of blocked asset files (from things like un-whitelisted uBlock Origin) with step by step directions on how to easily correct.
- Tweak: Completely overhauled the ga.js and analytics.js outputs to fix outstanding bugs.
- Tweak: Better debugging + disabled + preview tracking modes, that more clearly indicate what’s going on
- Tweak: Completely overhauled PHP regex tracking to solve nearly a dozen outstanding bugs including issues where non-link elements starting with the letter “a” such as tags would get parsed as links causing issues. Also solves issues related to single versus double quote usage for existing onclick handles, non-semicolon terminating onclick handles and various other parsing issues.
- Tweak: Many previously untranslatable strings are now translatable.
- Tweak: Minified in-plugin images.
- Tweak: Minified admin css and js
- Tweak: Uses latest version of Google PHP API now.
- Tweak: The system for creating reports and getting Google Analytics reports have changed. If you’ve hardcoded into Yoast functions previously not designed for frontend output this could cause problems. We’ll introduce an API intended for this type of use after we update to use the v4 reporting API.
- Fixed: Fixed an issue with HostEurope and other hosts modifying the default PHP arg seperator.
- Fixed: Prevents an issue where users with a plugin like Airplane Mode active will get a better error message than “code invalid” on the GA token auth screen (and also fixes how that detection is done in other parts of the plugin).
- Removed: unused track_full_url setting
5.5.3, October 3rd, 2016
- New: Announces MI 6.0 beta.
- Fixed: Compatibility with PHP compatibility scanner’s bug
5.5.2, July 7, 2016
- Tweak: Updates license manager to have more reliable update information including better compatibility with Yoast SEO products.
- Fixed: Compatibility with upcoming Shiny Updates v2 in WP core
5.5.0, May 1, 2016
- New: Added new System Info tab for faster support.
- Fixed: Issue with changelog missing some deployed versions.
5.4.9, April 15, 2016
- New: Font based dashboard icon
- Tweak: The “MonsterInsights” menu item name has been renamed to just “Insights”
- Fixed: Issue with eCommerce addon (also requires user to update eCommerce addon)
- Fixed: Issue with 2 dashboard links
- Fixed: A bug in pre-existing code caused the menu of the plugin to skyrocket unintentionally. This has been corrected.
5.4.8, April 14, 2016
- New: Google Analytics by Yoast is now MonsterInsights.
- Fixed: Compatibility issue with WordPress 4.5