|
| 1 | +--- |
| 2 | +title: Bento Destination |
| 3 | +id: 5ff25116284da6d5091e21b1 |
| 4 | +--- |
| 5 | + |
| 6 | +[Bento](https://www.trybento.co/) 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. |
| 7 | + |
| 8 | +This destination is maintained by Bento. For any issues with the destination, [contact the Bento Support team ](mailto:[email protected]). |
| 9 | + |
| 10 | + |
| 11 | +## Getting Started |
| 12 | + |
| 13 | +{% include content/connection-modes.md %} |
| 14 | + |
| 15 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 16 | +2. Search for "Bento" in the Destinations Catalog, and select the "Bento" destination. |
| 17 | +3. Choose which Source should send data to the "Bento" destination. |
| 18 | +4. Go to Org settings in [Bento](https://everboarding.trybento.co/settings/organization){:target="_blank"}, under Integrations copy the Segment **API Key**. |
| 19 | +5. Enter the Bento API Key in the Bento's destination settings. |
| 20 | +6. Make sure your account's unique ID always sends under Segment's context. Bento requires the [groupId](/docs/connections/spec/group/#group-id) as part of the payload. |
| 21 | + |
| 22 | + |
| 23 | +## Supported methods |
| 24 | + |
| 25 | +Bento supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). You can see what data has been passed into Bento in the Bento [Data dashboard](https://everboarding.trybento.co/data){:target="_blank"}. |
| 26 | + |
| 27 | +### Identify |
| 28 | + |
| 29 | +Send [Identify](/docs/connections/sources/catalog/libraries/website/javascript/#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: |
| 30 | + |
| 31 | +```js |
| 32 | +analytics.identify('userId123', { |
| 33 | + |
| 34 | +}); |
| 35 | +``` |
| 36 | + |
| 37 | +Segment sends Identify calls to Bento as an `identify` event. |
| 38 | + |
| 39 | + |
| 40 | +### Track |
| 41 | + |
| 42 | +Send [Track](/docs/connections/sources/catalog/libraries/website/javascript/#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: |
| 43 | + |
| 44 | +```js |
| 45 | +analytics.track('Login Button Clicked') |
| 46 | +``` |
| 47 | + |
| 48 | +Segment sends Track calls to Bento as a `track` event. |
| 49 | + |
| 50 | +### Group |
| 51 | + |
| 52 | +Send [Group](/docs/connections/sources/catalog/libraries/website/javascript/#group) calls for clusters of users. For example: |
| 53 | + |
| 54 | +```js |
| 55 | +analytics.group("0e8c78ea9d9dsasahjg", { |
| 56 | + name: "group_name", |
| 57 | + employees: 3, |
| 58 | + plan: "enterprise", |
| 59 | + industry: "Technology" |
| 60 | +}); |
| 61 | +``` |
| 62 | + |
| 63 | +Segment sends Group calls to Bento as a `group` event. |
| 64 | + |
| 65 | +--- |
0 commit comments