Links
➕

How to create metrics?

Metric Creation on Locale- Steps and Required Fields
Here are the following steps you can follow to create metrics that you can visualize and analyze on heat maps.
  • In the Metric studio on the left, click on the Add New Metric.
  • When the window appears, select Metric Type to begin visualizing the specified metric.
​

🪐 What are the required fields?

Sample fields for event count metric

Metric Name

This is a name given to the metric by the user.
✨ Pro tip: Name the metrics in a way that is understood across the organization by all the team members.

Entity

These are components of your business that have both a location and time component.
The entities can be:
  • User
  • Trips
  • Stations
  • Bikes
  • Driver/Delivery Personnel
  • Orders and so on
✨Note: The entities differ based on the user’s data and industry.

Entity property

These are properties that are associated with entities. For example,
  • If you consider user - it has user id, user age, user gender, and so on.
  • If you consider a trip - it has, distance, starting point, ending point, and so on.

Entity Event:

These are events that occur for every entity. For example,
  • If you consider a user, they have the following events - installed, searched, booked, canceled, selected, and so on.
  • If you consider a trip, there are only two possible events because a trip can either start or end.
  • If you consider a delivery personnel/driver, they can be idle, on duty, or off duty.
✨ Note: In entity property metrics and computed metrics, this field is not available.

Aggregation

Aggregation types on Locale
This field appears as soon as we choose the event property. What do we mean by aggregation?
It is basically the calculation of all the data points in one hexagon or a polygon.
✨ Note: This aggregation is performed on the event property field. For properties like user id, trip id where no two values can be the same we can only perform count or unique count.
There are different ways in which this calculation can be done:
  • Count: It is basically the counts of all data points in that particular area.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see 3.
  • Unique count: It is similar to the count function as above, but all the duplicate values are excluded.
For example, there are three users in a hexagon with installs 45, 78, 56, and 56. When you hover over the hexagon, you will see 3. Here, 56 is only counted once.
  • Average: As the name suggests, it basically shows the average of all values associated with any entity.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see an average of the three numbers, 59.67
Avg idle time metric creation
  • Maximum: As the name suggests, it basically shows the largest of all values associated with any entity.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see 78.
  • Minimum: As the name suggests, it basically shows the smallest of all values associated with any entity.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see 45.
  • Median: As the name suggests, it basically shows the median of all values associated with any entity.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see 56.
  • Sum: As the name suggests, it basically shows the smallest of all values associated with any entity.
For example, there are three users in a hexagon with installs 45, 78, and 56. When you hover over the hexagon, you will see 179.