This guide introduces you to the key concepts on Bucket, how to track feature interactions, collect qualitative feedback and guides you to tracking your first release.

Here's a 9-min guide tour, or you can continue reading:

Key concepts

Before doing so, let's take a second to go over the key concepts of Bucket:

Features
- STARS
- Live Satisfaction
Segments
Releases

Feature

A feature on Bucket maps to a product area or a specific product interaction. Features are tracked using either user events or company attributes. To learn more, check this blog post.

Most features are tracked with events. However, Bucket abstracts away the underlying feature data, so product teams can work with features and not event filters throughout the Bucket UI and when exporting the data.

To do so, each feature has a Tracking criteria and a STARS criteria. More on that later.

STARS

STARS is an open-source framework for measuring feature adoption and satisfaction. STARS is built into Bucket and is computed automatically for each feature. In short, STARS combines quantitative engagement data with qualitative feedback. The STARS funnel has the following steps:

Segment
Tried
Adopted
Retained
Satisfied

You can learn more about STARS at https://starsframework.org.

Live Satisfaction

Bucket can ask users at the right time to provide a C-SAT score for any feature. Bucket can do this automatically via the Live Satisfaction module.

Segments

Bucket is built for B2B so the primary account dimension is the company and not the individual users.

A segment is a collection of companies based on company attribute filters.

If you send data to Bucket via Segment, these attribute filters are "group traits" on Segment.

Each features is tied to a segment. For example, some features are only accessible to a paying segment of companies.

Releases

A release is the workflow-part of Bucket. Once a feature has been created on Bucket and the feature gets deployed, it's tracked on Bucket as a release.

Releases have an evaluation period during which they will report the progress toward any feature goals. A goal can be as simply as simply getting to 25 customers to use the feature, reaching a high feature satisfaction rate or getting 50% of all customers to adopt the feature.

Once the evaluation period is over, you can decide if the release was successful or needs another iteration.

Sending data and tracking your first feature

Sending data

First, you will need to connect your product to Bucket. There are three ways to accomplish this:

Adding Bucket integration through Segment.com (2 mins)

Bucket has both web and cloud destinations for Segment. We recommend always having the web destination active in order to guarantee that Live Satisfaction collection works in your app. See Tracking with Segment to learn more about our segment integrations.

Bucket's JavaScript SDK (~15 mins)

The Javascript SDK can be included directly as an external script or imported. To see full instructions on using the SDK, head to <https://github.com/bucketco/bucket-tracking-sdk>.

Our HTTP API (~1 hour)

The Bucket Tracking API is a simple JSON HTTP API which can be used both from browsers and from backends. To use this method, head to the Bucket HTTP Tracking API.

Make sure to associate users to a company

Bucket primarily tracks engagement at the company level. To properly track companies, make sure you associate users with companies, so that the users' actions are also counted towards their company's actions.

To associate individual users with a company, you will need to call the company method in the JavaScript SDK and HTTP API, or use the group call in Segment. The above guides detail how to call the function correctly for your chosen method.

To learn more about the advantages of sorting users into companies, see this blog: https://bucket.co/blog/introducing-attribute-based-feature-tracking

Note: Events from users who are not associated with a company will not show up in the Bucket UI. Once a user is associated with a company, the user's historic events are also attributed to the company.

With data in Bucket, you're now ready to track the your features in Bucket.

Tracking your first feature

To track your first feature, hit "Track feature" in the top left corner.

At a minimum, you'll need to specify a feature name and its tracking criteria.

The rest of the feature settings have defaults.

When you create the feature, Bucket will look for any data that matches the tracking criteria. If there's any data, you'll see the STARS funnel for the feature.

If there's no data, you'll see a tracking plan that you can pass on to engineering. Once the first data is received, Bucket will notify you on Slack and, if associated to a Release, start the evaluation period.