Skip To Main Content

Faust.js Telemetry – Please Help Us Understand How You’re Using Faust.js

By Chris Wiegman on

When we relaunched Faust.js at the end of 2022 we included a feature for basic telemetry to help us better understand how users are using the WordPress plugin and JavaScript framework. That telemetry is tied to WP Engine’s corporate Google accounts using Google Analytics and is strictly opt-in only to ensure absolutely no data at all is sent without your consent.

Today I’d like to ask you all to help us plan for the future of Faust.js by opting in to our telemetry collection. It collects no identifying information about you or your site directly but it does help us better understand what you are using which we can then use to help build better features and integrations for Faust.js in the future.

What do we want to know? Well, we are hoping to understand things like if you’re using plugins like ACF or or what the most popular SEO plugin is among Faust.js users. Even simple things like if Faust is being used on more multi-site instances and how many builds are being handled with Faust.js just aren’t things we have much visibility into at the moment.

Over the next year we have a dual focus on the Faust.js team to improve the developer experience of headless WordPress and to make it easier to personalize your content delivery. While we understand that it is more difficult to develop headless WordPress sites than traditional WordPress sites, quantifying what exactly that means is a completely different story. With your help we now want to anonymously see where the pain points are so we can make Faust.js the best headless framework for all of our users.

Opting into telemetry is easy, beginning with version 1.2.0 of the Faust.js WordPress plugin it will ask you when you activate the plugin. For further information on opting in to or out of our telemetry, please see our telemetry documentation.

Faust.js Research