Usage Tracking

Usage tracking for ExactMetrics helps us better understand our users and their website needs by looking at a range of server and website environments.

This allows us to continuously improve our product as well as our Q&A / testing process.

Usage tracking is opt-in, and must be manually opted in by an administrator level user or a user you’ve granted access to the GADWP settings, and you can undo it at any time from the settings panel.

We highly recommend our users opt-in, as the better we can understand our users, and in particular how they use our product, the better ExactMetrics will be for everyone.

Below is the list of information that ExactMetrics collect as part of the usage tracking:

  • PHP Version: so we know which PHP versions we have to test against (no one likes whitescreens or log files full of errors)
  • WordPress Version: so we know which WordPress versions to support and test against
  • ExactMetrics Version: so we know which versions of ExactMetrics are potentially responsible for issues when we get bug reports, allowing us to identify issues and release solutions much faster
  • The SERVER_SOFTWARE variable in PHP: Used to parse out which web hosting companies our users are using. We use this to determine the top hosts users are using and make sure that we have testing accounts with those hosting companies, so we can properly test our new releases with various host environments. This also helps us identify conflicts with specific hosting providers so we know which hosts to work with to fix the issue if it’s a server configuration issue.
  • Theme/Plugin names and versions: So we know which themes and plugins to support and test against. ExactMetrics runs on over 1 million websites. While we can’t test with all 50,000+ plugins in the WordPress.org repository, we do our best to test against the top plugins from this list.
  • ExactMetrics settings: So we know which settings people are using, allowing us to determine potentially which new settings or areas of ExactMetrics people want us to expand on, and which settings people aren’t using. We also use this to determine which features to deprecate, and for how long we support backwards compatibility of those deprecated settings.
  • Timezone: We use this to test our software with servers setup on the most popular timezones, so we can make sure your reports are up to date.
  • Site and user count and is_multisite: This allows us to gauge how important it is to support specific types of multisites like multi-network and similar styles of configuration and gauge how much we need to scale our servers before launching features like author tracking dashboards that are correlated to the number of users on a site using it in terms of scale. It also allows us to see how users of multisite use our settings differently than single site installs
  • Usage tracking config: The ExactMetrics option that contains the information on when the usage tracking data-sync will happen (once a week), so we can gauge the server load for the usage tracking servers.
  • Locale: For the top languages of ExactMetrics, we want to make sure that our translations are up to date.