Bucket Destination

Bucket is feature-focused analytics. Bucket empowers software teams with a repeatable approach to shipping features that customers crave.

This destination is maintained by Bucket. For any issues with the destination, contact the Bucket Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Bucket” in the Destinations Catalog, and select the Bucket destination.
3. Choose which Source should send data to the Bucket destination.
4. Go to Bucket’s Settings and find and copy the “Publishable Key” under Settings.
5. Enter the “Publishable Key” as “Publishable Key” in the “Bucket” destination settings in Segment.

Identify

If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

analytics.identify('userId123', {
  name: 'John Doe',
  email: 'john.doe@example.com',
});

Segment sends Identify calls to Bucket as an identify event which updates User profiles.

Group

If you aren’t familiar with the Segment Spec, take a look at the Group method documentation to learn about what it does. An example call would look like:

analytics.identify('groupId123', {
  name: 'Acme, Inc',
});

Segment sends Group calls to Bucket as a group event which updates Company profiles.

Track

If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

analytics.track('Login Button Clicked', {});

Segment sends Track calls to Bucket as a track event which updates the Features page.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.