Feature owners, meet your dashboard.

Building and shipping features is hard, but getting customers to adopt and use them consistently is even harder. Bucket is the simplest way to track feature success and measure who’s using your key featuresand how often.

Hold to toggle matrix mode. Great for planning!
New home for your features!

This feature report is all you need.

The feature engagement report gives you all the information you need to determine, if your feature is succcessful or not. See which companies have tried your feature, how many that are actively using it, and how frequent they use it.

Informed decisions should be based on data, but there's no need to make it more complicated than has to be. Bucket keeps things simple by summarizing, if customers use your featuredaily, weekly, monthly, or yearly.

Trust the data. Are tracking events still coming in as they should?
Who's using this feature? Click through to see list of companies.
Are companies using this feature more or less over time?

Segment customers by feature usage.

Bucket comes with powerful customer segmentation built-in. Filter your customers by feature usage (daily, weekly, monthly, yearly) and by custom attributes, like monthly_spend or count of team_members.

Most features aren't meant for all of your users. One feature might be critical for onboarding new users, another for retaining larger customers. When looking at feature engagement, it's crucial to filter the feature audience to the relevant user segments.

To learn more about segmentation, read our Getting started guide.

Sort companies by feature usage: "Daily", "weekly", "monthly" or "yearly".
Filter customers by feature usage or custom attribute, like "monthly_spend".

The SaaS product lifecycle.

All SaaS products have leaks. For example, not all signups become active users. Not all active users become paying customers. Users adopt a feature, but abondon it quickly.

Bucket helps you identify the biggest feature leak in your product, so that you can resolve it. Sometimes a feature needs another iteration, or to be re-designed, or to be explained better, or sometimes it just needs to be removed.

When you've resolved the biggest leak, repeat the process.