When usage tracking is on, Uncanny Automator sends us a report about how the plugin is used and the WordPress and server environment it runs in. The report helps us decide which features to build next and which setups our QA testing should cover. This article lists what the report contains and how to turn usage tracking on or off.
What the report contains
The report identifies your site by a code generated from its address. On sites with an Uncanny Automator license or a connected account, the report also includes the license key and the site’s domain. It never includes the values you enter in triggers and actions, or any data that passes through your recipes.
Uncanny Automator
- License details: the license key and license type, for sites with an Uncanny Automator license or a connected account.
- Integration, trigger, and action statistics: which integrations, triggers, actions, and recipe blocks your live recipes use, and totals such as the number of recipes and how many triggers and actions they have. Knowing what is most popular lets us focus development on the features that help the most people, so turning on usage tracking effectively adds a vote for every plugin your recipes use. The totals also show us whether the recipe builder suits the way people actually build. We count which items your recipes use; we don’t collect the options selected in them.
- Plugin settings: which Automator settings are switched on, such as the log retention settings, debug mode, and whether Uncanny Agent and Uncanny Page Builder are enabled, plus the names of any AI integrations connected for recipe actions (never their API keys). This shows us which settings are used and which are not.
- Plugin health and admin use: the Automator database version, whether all of its tables are present, and their sizes; how often some settings and status pages are opened; how in-plugin review prompts are answered; and how many users view recipes in Diagram view or List view, counted, never named.
WordPress
- Version: so features and updates are tested thoroughly on the versions our customers run.
- Active theme and plugins: so the most widely used themes and plugins get extra attention in testing and keep working with each Automator update.
- Locale: we want Uncanny Automator to be usable by everyone, and the site’s language tells us where to focus translation work.
- Timezone: our customers are spread across the globe, and knowing where helps us plan support coverage.
- Multisite: on a multisite network, the number of sub-sites, so we can make sure Automator scales to large networks.
- User count: the number of users on the site, so we build for the site sizes our customers actually have.
Web server
- PHP and MySQL versions and settings: so our testing covers the environments in use and avoids compatibility issues.
- Server software: whether the web server is Apache, Nginx, or similar, also for testing.
Turn usage tracking on or off
Whether usage tracking is on depends on how your site is licensed:
- Uncanny Automator Lite, not connected to an account: usage tracking is off until you enable it. It is voluntary and doesn’t change how the plugin works. To enable it, go to Automator > Settings > General > Improve Automator, switch Allow usage tracking to Enabled, and click Save.
- Uncanny Automator Lite, connected to a free Uncanny Automator account: usage tracking is switched on when you connect the site, and the Allow usage tracking switch is no longer shown.
- Uncanny Automator Pro active: usage tracking is on, and the switch is not shown.
To turn usage tracking off on a connected or Pro site, contact our support team, and they’ll send you a filter that turns it off.
For developers
The AUTOMATOR_REPORTING constant in wp-config.php overrides the setting on every plan: true sends the report and false stops it, whatever the switch or license says.
define( 'AUTOMATOR_REPORTING', false );
Related: Connecting your site with a free Uncanny Automator account, Using Automator logs, Privacy Policy
Comments (0)