Usage tracking for SeedProd 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. Below is the list of information that SeedProd collects 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.
• MySQL Version: so we know which versions of MySQL to support and test against for our custom tables.
• SeedProd Version: so we know which versions of SeedProd 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: combined with an SeedProd option called SAS are 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. SeedProd runs on over 1 million websites. While we can’t test with all 50,000+ plugins, we do our best to test against the top plugins from this list.
• License key and email and url: If you’re an SeedProd customer, then we use this to determine if there’s an issue with your specific license key, and to link the profile of your site with the configuration of authentication to allow us to determine if there’s issues with your SeedProd authentication.
• SeedProd settings: So we know which settings people are using, allowing us to determine potentially which new settings or areas of SeedProd people want us to expand on, and which settings people aren’t using.
• 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.
• Usage tracking config: The SeedProd 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.