Coming soon! A Pro version of the Flipper gem for entirely local installations.

Get Updates

Blog

Feature Flag Analytics

· John Nunemaker · 1 min read

You might not have noticed it, but Flipper 1.3.0 (released in April) enabled telemetry by default for everyone using Cloud.

This means for the past month or two (whenever you upgraded), we've been rolling up some useful metrics and shipping them to Cloud. Nothing personal is in the analytics, just flag names, time periods and true/false counts.

Last night (a Friday of course 😘), I enabled flag analytics for everyone on a paid plan. They'll look kind of like the image below when you are viewing a feature flag.

Screenshot of last 24 hours for a feature flag enabled 1% of the time.

Analytics are a big deal because they increase confidence – whether it's knowing that your flag is working as intended or safe to remove.

We've been using the functionality internally for a few months and it's made flag cleanup a breeze.

  1. Remove the flag from the code.
  2. See the number of checks for that flag go to zero.
  3. Delete the flag from Cloud.
  4. 🍻

For the curious, I've already written up part 1 of how we built these analytics and hope to finish this series over the coming months (via a few more articles).

That's all for now. Happy flipping!

Ready to try it out?

Get audit history, rollbacks, advanced permissions, analytics, and all of your projects in one place.


Prefer our Cloudless option?

You can choose from several tiers to sponsor Flipper on GitHub and get some great benefits!

The Friday Deploy

News and open source releases for all things Flipper. Unsubscribe anytime.

Have questions? Need help?

Email us any time or head on over to our documentation or status page for the latest on the app or API.

Ready to take Flipper for a swim?

No credit card required. 14-day free trial. And customer support directly from the developers.