Detect Any Action or Event Taking Place on Your Website!
In this submodule, you will be able to create your very own tags for any event you would like to be tracked, add them to your website and see how the firing of an event develops over time. You can also use auto-tracking to scan your website for default elements without having to add any extra code & track them right away. This feature helps you immensely in tracking events you specifically want to know.
Important Note: Manual Event Tracking is not available for Wix websites (no custom tags can be created, as there is no control of the code for specific elements on the page). The Auto-Tracking will work.
This support article is structured into the following sections:
Right above the tiles, you can see a date picker. This enables you to select a certain time period, or specific day, for which you want the Dashboard's data to correspond.
It is crucial to limit the presentation of data to specific dates or timeframes during which you executed potential campaigns or implemented other strategies. This will allow you to assess the effectiveness of these actions and use the insights gained for future planning.
Important Note: The app now remembers previously set segments, filters, filter templates, and date intervals, even when you navigate away from the page, log out, or log back in. When your session expires or you close the tab, it automatically switches back to the default setting of "Last 30 Days."
The first tab of this submodule is the "Auto-Tracked Events". It is divided into two sections, "All Triggered Auto-Events Tracked" and the "Line Diagram".
Together, these sections offer a complete and insightful overview of the events that have been triggered and were auto-tracked.
This table gives an overview of all the auto-tracked events that have been fired throughout the selected period of time. Each line represents one firing of an event. So if the same event was fired 20 times in the selected period of time, then there would be 20 lines for this event.
The table contains the following columns:
The line diagram basically reflects the data presented to you in the table above. You will notice that only one line is visible – referring to the entire amount of events shown or filtered in the table above – by default.
Important Hints:
The Live Preview shows exactly what actions were triggered on which elements, viewing this directly within an image with your web page itself.
Within the main table of tracked events, there is a "Show event on website" button, for the auto-tracked elements.
Click that and a preview of the page itself will be open in a new tab with the possibility to see important details about your auto-tracked events, in a more human readable way, than only the table of the tracked events you've been previously looking at.
Above is a sample of the screen that you will see once you click on the "Show event on website" button. There are three important parts here:
Tapping the Live-Tracking Mode Settings Icon, will open the settings view that looks like this image below:
Every row of this Settings Menu shows your defined settings and some of the auto tracked elements related information:
Important Notes:
Hint: Our tracking may not currently capture data from invisible elements that appear only after a user interacts with the website. This includes elements like login text input fields, search fields revealed by clicking an icon, etc. These interactive elements may appear as "0" on the live preview because they aren't visible when the page first loads, but they are tracked correctly on the table. We're currently working on improvements to capture data from these dynamic elements in the future.
The table for both Auto-Tracked Events and Manual Tracked Events allow various filtering and grouping options. The main difference between filtering and grouping is relatively simple:
Play with it on the table, and you will easily understand the difference. Both approaches will give you simple yet powerful possibilities for displaying your data and retrieving interesting facts from it.
It is essential to understand the behavior of the line diagram. After grouping the data within the table, it becomes evident that to view the line diagram for a specific group, users must set the filter beforehand. Additionally, users have the option to select or deselect items within this group, streamlining the data to their needs. Deselecting an item will result in the removal of its corresponding line from the diagram.
Important Hints:
Moving on to the "Manual Tracked Events" tab (not available for Wix websites), you'll find a familiar layout with two sections: "All Triggered Manual Events Tracked" and the "Line Diagram", offering a comprehensive overview of manually triggered events and their visual timeline.
This table gives an overview of all the events that have been fired throughout the selected period of time. Each line represents one firing of an event. So if the same event was fired 20 times in the selected period of time, then there would be 20 lines for this event.
The table contains the following columns:
The line diagram basically reflects the data presented to you in the All Triggered Manual Events Tracked table. You will notice that only one line is visible – referring to the entire amount of events shown or filtered in the table above – by default.
Similar to the Auto-Tracked events, you'll find a radio button labeled 'Compare Previous Period' (with dates underneath) on the top right of this section which lets you compare your current data to the equivalent period before it. The light purple line illustrates the data from that previous time period.
To get more detailed information, hover your cursor over each data point on the line diagram. This will display a tooltip with relevant insights, including a comparison of each period when you enable the "Compare Previous Period" button.
The final tab in this submodule is the "Event Tag Generator" (not available for Wix websites). Instead of heading to your website, you can easily create new event tags right within the application whenever you need to track something new.
In general, an event tag can be made of the following fields:
Once you have defined all the fields above and have chosen the action you want the event to fire upon, click the "Generate Event Tag" button. After the event tag is created, you'll see the next window wherein you can copy the generated event tag. You can also create another tag by tapping the "Generate Another Event Tag" button.
Note that the created event tag needs to be integrated within your source code afterwards in order to track the event you created the tag for.
Here’s a list of the HTML events(actions) used and their description:
Once you generate your new event tag, integrate it into your website by adding it to each element you want to track (depending on your website builder platform). You can add the tag our app provides, either directly within the element's code or as a separate script, as shown in the tutorial below.
Here is an example for a button in HTML and how it should look like so that the click on that button is tracked as an event:
<button id="important-btn">Click me!</button>
Option A: JS snippet
<script> document.getElementById("important-btn") .addEventListener("click", function(){ va("send", "event", "example-category", "btn-click", "Important Button") }); </script>
Option B: directly on the element
<h2 onclick="va('send', 'event', 'example-category', 'btn-click', 'important', 123);">Important button</h2>
Both options are semantically correct and do the same thing in the ideal case.
However, Option A allows for more flexibility. The limitation with Option B is that it might be overridden by some other JS code that is loaded after the DOM is rendered ( element.onclick = function(){ ... } ), thus causing our code never to be called.
In comparison, Option A allows an unlimited number of event listeners to be added (as long as the memory on the user agent device can withstand it).
This section of the Module Settings allows you to select which type of event you want to be tracked by our platform: manually created event tags, default events being auto-tracked or both.
Once accessed, you will have two types of settings available:
Important Notes: