What's new?

You can now sort companies by when they first or last used a feature. When shipping a new feature, this view enables you to easily track its new adopters.

We’ve spent the past weeks making significant improvements to load times in Bucket. The application was getting pretty slow for accounts with a large number of end-users (~20K+) that also tracked a large number of features.

When creating a feature in Bucket it is now possible to specify that only events with attributes which fulfill certain criteria be included in the feature report. This makes it even easier to start tracking advanced features in Bucket!

This week we extended the functionality we shipped last week - feature onboarding funnels - to work for features that track feature-usage using attributes.

The Bucket feature report has four feature adoption states. All of your companies are placed in one of these states based on their usage of the respective feature.

When you track an event-based feature on Bucket, you want to know how often your users interact with the feature. The Bucket frequency score tells you exactly that.

We’ve given our UI a facelift and improved the layout. Most changes are subtle, but they add up and give a much more polished look and feel, and a more scalable interface.

It’s common to track company-level features using attributes. For example, at Bucket, we’re tracking if customers use our weekly reporting feature. We do this by passing an attribute called "weekly_reporting" via Segment’s "group" call.

We’ve added typeahead search to the various dropdowns in the Bucket UI. It’s now much faster to find the event you’re looking for when tracking a new feature.

This week, we’re adding to last week’s release, which focused on making the feature adoption criteria configurable. Today, we’ve added another configuration, which allows you to toggle the “Stopped”-metrics on or off in your report.