Event Tracking

Event Tracking allows you to “raise a flag” whenever a user does something important within the flow, generating an event and giving you the ability to add any other piece of information (parameter) that is saved within the event as well.

All events that are tagged in Flow Builder automatically generate data in our new Events Dashboard.


In addition, this information will also be made available in our new Segmentation tool inside of Studio.

When to use

Whenever an end user reaches any step that represents a conversion (think: jobs done), does any high value action, or behaves in any way that we might want to use for later segmentation.


The information as events list and events data may take 24 hours or less to appear in dashboards.

How to use

  1. Open your flow in Flow Builder
  2. Click on the tab Track near the Publish button.
  3. Define what step will trigger the Event (see examples below)
  4. Click on your step
  5. Click on Add Event
  6. Name your Event
  7. Click on Save

How to see and extract Events

Your events will be shown in the new dashboard “Events”. This dashboard shows you relevant insights about how steps are performing in your Flow and allow you to extract all these data.

Activating events dashboard (only available for a few users)

First of all, you have to activate the new dashboard for your client, so login in Studio with your Yalo credentials, select the Customer Account you want to activate, go to Metrics Manager in the left menu, search for Events, activate and save. If you have doubts, check this quick video bellow.


What are good Events?

Conversion Events / Jobs Done:

Start by thinking about all the different things a user can do inside a Flow and tag the steps that act as conversion confirmations. You can think of this as Jobs Done from Studio OG.

  • Examples:
    • A tendero confirms an order.
    • A user asks for an FAQ.
    • A user gets escalated to a human agent.
    • A user searches for a flight in Aeromexico or completes a loan request flow in Coppel.
  • Make sure to tag the right step - the one where we know the user has completed the flow.

High-Value Actions:

Any action, that might not be a conversion event but that we might still want to track.**

  • Examples:
    • Tendero authenticates itself.
    • User responds CSAT.

Anything else that we might want to Segment: These will be specific per flow and customers, but anything that we can then use to create better audience segments should be tagged.

In all cases, make sure to include all the relevant parameters that we might want to segment with. Most of the time, these are the information or data that was gathered during a flow.

Example: After a user searches for a flight in Aeromexico we will track a conversion event with the following params: Departure date, number of passengers, origin city, destination city, etc etc. For an order confirmation, we might want to track the final cost, SKUs and their prices, cart size, etc.

What are Parameters?

Parameters represent the data you want to save inside an Event. You can save the user response, a custom value, or a specific variable that has already been created. Check these examples of Events, Parameters and Values

Promotion receivedCustom value: DoritosDoritos
Searched for a near storeVariable: {{location}}User location
CSAT completedVariable: {{csat-rating}}Rate answered by the user
Search flightParam1: Variable: {{departure-city}}
Param2: Variable {{arrival-city}}
Departure and Arrival cities searched by the user.
Events can have 1 or more parameters if you want.


A simple onboarding (check User Profile first)

Let’s go back to the simple onboarding you saw in the User Profile training. In it, we asked the user a couple of simple questions and then saved their answers as profile variables. However, since this onboarding is an important part of our flow, we also want to know whenever a user completes the onboarding.

Hence, we will tag find a step that the user will only reach if they finalize the onboarding successfully (our conversion step) and will tag this as an event. Additionally, we will pass the information given to us by the user as event parameters so they’re sent alongside the event and can be used for Segmentation.


How does this fit into Segmentation?

Our new Segmentation Engine will allow Studio users to create audiences based on information we have about Stores. Today, this information mostly comes from data shared to us by the customer AND important events that happen inside of commerce.

However, the plan is to make sure, that any user attribute that is saved with Profile Variables, and any user event is that tagged via Event Tracking – both of them in Flow Builder – will also be available for Segmentation.

Take a look at the loom to understand this better.

Updates from Aug 2023

Add activity templates with events and track your user behavior automatically

Now you can create your activity templates with all of your events already tracked. When you import your activity with events, these new events will be automatically tracked after publish and will appear directly in your dashboard. 🙌🏻

What’s Next

Let's go deeper with Funnels