With the use of auto event tracking, you can monitor nearly every user behavior since it automatically logs actions like form submissions and clicks.

It provides a list of all the events that make up the web statistics reports as well as the data collected by user behavior analytics tools, such as heatmaps, session recordings, and conversion funnels.

Automated tracking aims to gather every possible event that can occur on a website, leaving it up to a researcher or analyst to determine whether or not it is significant during analysis.

This feature makes it easy to quickly identify which site-wide events are being tracked by default and is a fantastic starting point for those without coding experience to customize event tracking.

If you want to activate automatic event tracking within TWIPLA, you can go to Module Settings and turn on all of the user actions that you want to be tracked.

With manual custom event tracking, you can track more website elements and delve much further into how users interact with your website.

Although manual custom event tracking does require some coding knowledge, it is a good option for getting more insights about how users behave with certain elements. 

Once you understand how to proceed with it, the coding will no longer be a problem for you.

You can see below how to set the custom event tag to get more in-depth insights.

Manual Custom Event Tag

Creating a custom event tag - otherwise known as a trigger - is a relatively straightforward task. You just need to help the tool understand what needs to be tracked in order to offer you accurate results. 

You can find below six fields - mandatory or not - to fill in when it comes to setting your manual custom event feature:

• Event category - this is a mandatory label and requests that you specify a category for the webpage element you wish to track, and it should describe the element that visitors interact with, such as an image or button.
• Event action - this is also a mandatory label and requires the precise user behavior you wish to track; it should define the actions that fire the event such as key presses, mouse hovers, clicks, and so on.
• Event label - this is an optional parameter that can be used to name or explain the features or qualities of the unique event, making it simple to distinguish it from other comparable events (such as a product video or support image).
• Event value - event values are straightforward numerical values you assign to a particular action or interaction. Although they are optional, they allow you to track the event's worth to your company statistically and observe how it changes over time.
• Fields object - this area is also optional and asks for any more details you might wish to provide on your own to help identify the event.
• Binding action - this field asks for the specific action that you want to monitor and wants technical information rather than the descriptive label that you input in the event action field.

Using TWIPLA, the binding action field will present you with a drop-down menu with four different options to choose from:

• Onclick - the user clicks on the element
• Onmousehover - the user positions their cursor over the element
• Onkeypress - the user presses a keyboard key when interacting with the element
• Onkeyup - the user releases a keyboard key when interacting with the element

Once you’ve filled the fields needed, TWIPLA will automatically generate your custom tag.