Bento Destination

Bento allows you to create embedded onboarding solutions to support your users as they get started with your product, and beyond. Using your customer data you can tailor user experiences providing a personalized journey through your product.

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

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Bento” in the Destinations Catalog, and select the “Bento” destination.
3. Choose which Source should send data to the “Bento” destination.
4. Go to Org settings in Bento, under Integrations copy the Segment API Key.
5. Enter the Bento API Key in the Bento’s destination settings.
6. Make sure your account’s unique ID always sends under Segment’s context. Bento requires the groupId as part of the payload.

Supported methods

Bento supports the following methods, as specified in the Segment Spec. You can see what data has been passed into Bento in the Bento Data dashboard.

Identify

Send Identify calls to identify a user in your application, along with traits around that user. This is usually called after a user has signed in to your application, or when a user’s attributes have been updated.. For example:

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

Segment sends Identify calls to Bento as an identify event.

Track

Send Track calls to capture some user action being taking in your application. This is often called when a user performs some action, like Button Clicked or Onboarding Completed. For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to Bento as a track event.

Group

Send Group calls for clusters of users. For example:

analytics.group("0e8c78ea9d9dsasahjg", {
  name: "group_name",
  employees: 3,
  plan: "enterprise",
  industry: "Technology"
});

Segment sends Group calls to Bento as a group event.

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.