The "Click" event describes all user interactions with the page when that user clicks on elements - both those that are links and non-clickable elements. It is especially important to understand the difference between the “Click” and “Submit” events in analyzing form interactions (see: Submit (event) below).
Comparison when tracking page load traffic or external link traffic (referrer) allows you to specify how CUX should parse a given URL. In CUX we use 4 types of comparisons: Contains (regexp); Starts with; Ends with; Matches.
Data retention / Retention period
This is the period during which your data is stored. If you choose the “month” retention period, you can check customer experiences and journeys for data back to a month at any time. You don't have to wait for the tool to gather this data (as it works, for example, in Google Analytics).
Events describe users' interactions when visiting your website. CUX's Goals consist of one or more events. This allows you to track various interactions such as page load, referrer traffic, click, scroll, and interactions with forms.
Goals collect ALL traffic that meets your conversion. If you want to see the customer journeys for the 2-step conversion “Campaign Link → Conversion”, you will see both visits with these two steps and visits with more steps, e.g. “Campaign link → Go to product page → About tab → Convert”.
Goals allow you to understand the real patterns of behavior of users who convert.
At CUX, we conduct retroactive analysis. It means that we collect data all the time (according to your retention period), and you can go through it at your convince. For example, you can check the Customer Journey, Waterfall or Goal from historical data. We’re able to show you the data in different contexts from the very moment you’ve implemented our code into the page. Unlike, for example, Google Analytics, which displays the results only from the moment of setting the goal, without going back in the data.
A session is only a SECTION of the user's entire visit to the website. Thus, it shows only a part of the entire customer journey, e.g. interactions with one of many subpages/tabs. Most analytics tools like Google Analytics bases its observations on sessions, thus not providing a full picture of user behavior.
Steps describe users' interactions when visiting your website. CUX's Waterfalls consist of one or more steps. This allows you to track various interactions such as page load, referrer traffic, click, scroll, and interactions with forms. Unlike the events in Goals, the order of steps in Waterfalls matters.
In the Event Builder (for Goals and Waterfalls) you can select the “Submit” event for interacting with the form. Submit means that the user has submitted the form. When you select the “Submit” event, you should point to the xPath element (from the visual preview) for the ENTIRE form. Unlike the “Click” event for the form submit button, the “Submit” event will collect all interactions related to submitting the form (when the “Click” event will only collect clicks, and not e.g. submitting the form by pressing enter button).
A visit is the FULL PICTURE of a user's interaction with the site. A visit can consist of many sessions – opening tabs, comparing products, or even keeping the page visible in the background. Analyzing whole visits instead of sessions provides a complete analytical picture.
Visit recordings are actually website previews reproduced from the serialized user's HTML code, that aim to reproduce their visit as credibly as possible.
Waterfalls show ONLY the visits of those users who have gone through each of the steps you set in a certain order. Waterfalls allow you to understand the behavior patterns of users who drop out at individual steps leading to conversion.
xPaths are used to uniquely identify or address parts of a website like buttons or form fields that you want to track interactions with. In CUX Event Builder, you can extract xPath form visual preview of the website (by hovering and clicking on the element you need to track).
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article