Creating Events
Last updated
Last updated
Events are meaningful moments in your business and is recorded in your data in some ways. Using events, complex questions around customer behaviors, retention patterns can be answered, and you can get deep insights into how your product is bringing value to your users.
Imagine you track your customer orders in a table called Orders. Every record in this table is an order recognized in your system when it is successfully placed by a customer.
We can consider that: when Jane Johnson placed this $100 order on 2024-01-01, an event Order Placed has happened. Simple as that, Presight helps you define your events just using your data tables as-they-are.
Typically event analytics tools will require your tech or data team to integrate some form of SDK in your product, where every time an action is performed, it is recorded and send to said tools. Such requirement is a hinder for your other types of data that are not track-able in app, or exists elsewhere, like in your CRM tools.
Presight events tie the two types of data together simply by letting you define your events from data across many sources in a few clicks, and immediately unlock the potential of all of it - without needing tech support or sending all kinds of details to your event tools to workaround.
Visit your Data Hub, where you will be able to see the tab Events. Click + New to create.
There are 2 ways for you to define events on Presight
Simply select a date from the menu when you are prompted with this modal.
Give it a name and a description (optional), then hit Save Event.
In the example, the defined event Order Placed is when customer created orders, so, the date used to define the event is Order date in Orders table
The second type of definition applies when many actions can be considered as one event. For example, an Browsing Product event happens when a user either Views a Product or Searches for a Product. For this type:
Simple switch to tab Event and select what you want from the list
Select all the constituent events, then click Save Event.
This can alternatively be done when you use metric funnel, cohort or event paths if you just want to toy around with different definitions first before committing to creating a permanent event definition.
