Bento is your customers’ traveling companion throughout their buying journey, so any time a customer takes an action – Bento is there with them, watching and recording everything they do without them knowing.

So let’s say that a customer views certain web pages – Bento records an event for this. A customer cancels an order – Bento records an event for this. A customer completes a booking – you’ve guessed it – Bento records an event. There are different events for different actions, and the more events we capture on your customers, the more you learn about them.

By default Bento will capture the following events on your customers:

  • View - Triggers when a customer views any of our web pages where the Bento code is active. This event will specify which url the customer visited.

  • Click - Triggers when a customer clicks any URL or hyperlink on the page.

  • Submit - Triggers when a form submission is detected on the site. This is also used to auto-identify visitors.

Every event has its own details that include information relevant for that event. Let’s say a customer triggers a cancelled event – the details would be things like the amount of the booking, the exact time and date when the customer made the cancellation, and the site or platform they used to submit the cancellation.

Once you click on the Events category, you’ll be given three sub-categories to choose from:

  • Event Browser

  • Goals

  • Pages

Let’s go over each.

Event Browser

This is where you search for recent events or specify the type of activity you want to know more about. You’ll see the “add rule” button which you can use to apply criteria to your search.

For example, you can use this function to see which of your visitors read the content of your location pages. Just use the “data.type” to specify the event and the “view” event since your search is about what your customers are looking at. You can also add a second rule like “” which will catch any URLs starting with /locations.

After you do this, Bento will generate a list of visitors that match the criteria you included, in this case anyone that’s visited a location page. And in the page column, you can see the exact page they’ve visited.


Goals are ways to track when users complete certain tasks or jobs in Bento. All goals have a start and stop event based on event matchers (which you can setup on the same page just below).

Let’s start with the event matchers.

You can find an already existing event matcher by clicking on the “find events” button, or add a new one by clicking on the “quick add” button.

To create a new event matcher, after you click on the “quick add” button you’ll need to include the name of the event matcher and the event itself, and click on the “create event matcher” button.

To add a new goal, click on the “setup new goal” button. This will take you to the “add a new goal” screen, where you’ll need to include:

  • The name of your goal

  • The event matchers the visitor should match in order to start tracking the goal

  • The event matchers the visitor should match in order to complete the goal

Then just click on the “create goal” button and you’re done!


Here you can browse the data at the page level for your site. The data here will give you answers to questions such as "how many visitors browsed this page" or "how engaging is this article".

We also have heatmaps that you can use, but this feature is still in beta.