Event
To achieve accurate data analysis and successful A/B Testing, you need to systematically collect and manage user behavior data — that is, Events.
This guide provides best practices for designing and managing events optimized for Hackle.
Event
An Event refers to any action or occurrence triggered by a user within your service. With Hackle, you can collect a wide variety of events and use them as the basis for all data analysis and measuring experiment performance.
Key Event Examples
Behavior-based
Sign-up completed, search button clicked, product detail page entered, purchase completed, etc.
System-based
Server response time, etc.
Based on event data like the above, you can use Hackle in the following ways:
A/B Test
Calculate key metrics such as 'purchase conversion rate'
Data Analytics
Analyze user behavior patterns such as event occurrence frequency
Funnel Analysis
Identify drop-off points as users progress toward a specific goal (e.g., purchase)
Taxonomy
The process of classifying events according to specific rules is called Taxonomy. A well-designed Taxonomy allows anyone in the organization to clearly understand and use data, accelerating data-driven decision-making.
To make effective and efficient data-driven decisions, you need to be able to accurately measure and analyze the data you want.
The first step in this process is defining and classifying events — event taxonomy definition — which makes this work critically important.
Event Naming Convention
An event naming convention refers to agreed-upon rules within an organization for clearly identifying and classifying events. Establishing a naming convention for events is critically important for well-defined and well-organized events.
Build a solid event naming convention to streamline communication across your organization!
Event Naming Convention Examples
Through events, we want to record 'where' a specific user performed an action and 'what they did.'
name
The location where the action occurred ('where')
home, gnb, login_page
action
The action taken ('what they did')
click, scroll, view, submit
object
The element that was acted upon
search_button, login_form, product_banner
Using the categories above, you can construct events as follows:
action_name
viewed_home
User entered (viewed) the home screen
action_object_name
clicked_search_home
User clicked (clicked) the search button (search) on the home screen
action_object
clicked_search
User clicked (clicked) the search button (search) (regardless of location)
For user actions occurring in common areas such as the GNB, you can record them together as clicked_search_gnb.
If you want to separately record the individual page where the GNB is displayed, it is recommended to include the page as a property value in the common event.
Last updated