Events Dashboard

Events Dashboard

The Events Dashboard in Webeyez gives you a clear view of how users interact with key actions on your site. This guide will walk you through how to read and interpret the data for any goal within the dashboard.

What is an Event?

An event is any specific action a user takes on your website that you want to track.

Think of it as a micro-conversion — a moment that signals user engagement or intent. Events can be anything from clicks to page views to scrolls — basically, anything a user does that you care about measuring.

Examples of Events:

• Clicking the Place Order button
• Clicking on Login
• Viewing a Product Page
• Adding an item to the Cart
• Submitting a Form

What You’re Looking At

To help you get the most out of this dashboard, we’ll break it down using one goal as an example — Place Order. The same principles apply to any goal you track, such as Login, Add to Cart, etc.

1. Sessions

The Sessions metric shows the number of sessions that interacted with the specific event.

For example, if you're looking at the “Place Order” goal, this number represents sessions where users actually clicked the Place Order button.

Only sessions with direct interaction are counted here. So, if no click = no count.

2. Successes

A Success is when the user completes the expected journey after triggering the event.

For “Place Order,” success means the user reached the Thank You page — a completed purchase.

Webeyez considers this as meeting the expected behavior of the event.

3. Failures

A Failure happens when the expected outcome doesn’t occur.

For the same “Place Order” example, a failure means the user clicked the button but did not reach the Thank You page.

⚠️ Important: Even if the user eventually succeeds after a failed attempt, the system still counts it as a failed session. Once a session is marked as failed, it stays that way.

Important Tips for Using the Dashboard

1. Leverage Filters for Efficiency
   • Use the failure rate and impacted revenue filters to focus on the goals with the greatest impact on your site and your customers.
      
2. Prioritize High Revenue Loss Goals
   • Start with goals associated with significant lost revenue to address the most critical issues first.
      
3. Address High Failure Rates, Even Without Revenue Impact
   • A high failure rate signals a potential usability issue, even if it doesn’t directly impact revenue.
   • Example: A 60% failure rate for login attempts due to "wrong email or password" errors may indicate a need for better login options (e.g., password recovery, social logins). While the site is functioning as expected, this indicates a poor user experience that prevents many customers from logging in successfully.
      
4. Analyze Error Messages for Clarity and Actionability
   • Review the error messages customers receive:
     • Identify odd or unexpected messages.
        

Look for messages that lack a clear call to action or fail to explain what the customer should do next.