Track event

Definition

A track event in Bucket is sent by the client when an user interacts with a feature within your application. Bucket uses these events to track feature adoption or launch feedback surveys. In most cases, you don't need to create custom track events as you'll just use the feature key instead.

Attributes

An event entity is essentially a collection of attributes associated with an event name or feature key. Each attribute is a key — value pair supplied by your application. There is one mandatory attribute each event must have: userId. It is up to you to provide whichever attributes you deem necessary.

Event attributes are useful mainly when setting up event-based features which can be configured to match specific events based on these attributes. Another use case applies to automatic feedback surveys which can be set to trigger on a specific event based on a combination of attributes.

Bucket manages a set of computed attributes when you send data to Bucket:

• First seen, Last seen and Event count of the users and companies,

• First used, Last used and Event count of the companies relative to the feature that matched the event.

In Segment terminology, these events can be thought of as acting as a Track call. Event attributes can be thought of as Event traits.

Do not include PII data when sending in event attributes. It is recommended that any sensitive data should be hashed or otherwise not included.

Next steps

• Learn about feedback and setting up automatic feedback surveys within Bucket UI,

• Learn how to create an event-based feature using user attributes within Bucket UI.