Events App

What is an event?

Event is any user interaction or occurrence you want to track beyond simple page-views, things like clicks on buttons or links, form submissions, video plays, scrolling depth, AJAX calls, or custom dataLayer pushes. Each event usually has:

• Login
• Registration
• Add to Cart
• Remove from Cart
• Checkout view
• Place order

By instrumenting events you get fine-grained insight into how people engage with your site or app, so you can measure conversions, monitor key interactions, and build audiences based on specific behaviors.

Webeyez doesn’t just fire when things go right. It can detect both successful and failed events, so you get full visibility into:

• Success: Users who completed your goal (a form submit, purchase, signup).
• Failure: Failed events track users who did not receive a successful event transaction, for example:
  • Login failures (wrong password, unrecognized email)
  • Add-to-cart failures (validation errors on quantity or options)
  • Checkout failures (incorrect CVV, expired card, mismatched billing address)
  • Form submissions that hit client-side validation (missing required fields)

By tracking failures as first-class “events,” Webeyez surfaces friction points in your funnel. You’ll see not only how many people converted, but also where and why others dropped off—so you can fix issues before they hurt your metrics.

What the Webeyez Events App Is For?

The Webeyez events module is your in-browser interface for defining, managing, and validating those same kinds of custom events. Without writing extra code. With it you can:

• Visually select triggers on your live site (clicks, URL patterns, DOM changes, DataLayer pushes, AJAX responses).
• Define success/failure outcomes (so you’re only counting true conversions).
• Extract custom data (cart values, user IDs, product SKUs) whenever an event fires.
• Test conditions in real time via a built-in console event.
• Manage versions locally, then publish your events live in one click.
• Revert or delete unfinished changes if you need to iterate.

In short, it’s a codeless way to turn any user action on your site into a tracked “goal” or event—giving you the same power as hand-coded Google Analytics events, plus the flexibility to tweak, test, and enrich them on the fly.

1. Open the Events Manager

In your WebEyez interface, click the Events icon in the toolbar.

A modal titled Manage Events will open, showing the Events dropdown and action buttons.

2. Select or Create an Event

Select Existing

Use the Select Event… dropdown to choose one of your previously defined events.

Create New

Click the + Add New Event option in the dropdown, or click the blue + button at top-right.

The modal header will switch to Create Event and a fresh form appears.

3. Define Your Event

Depending on whether you’re in Simple or Advanced mode, you’ll see slightly different fields. You can toggle modes in the header once you’re managing an existing event (Advanced gives you full control over the event key, delay, lifetime and AND/OR logic).

Basic Fields

Event Name (required)
Enter a human-readable name for your goal (e.g. “Signup Completed”).

Event Key (advanced mode only)
A unique machine-friendly identifier. If left blank, it will auto-generate from the name.

Timing Settings (advanced)

Delay (ms)
How long after page load to start watching for triggers.

Event Lifetime (ms)
How long to wait for outcome conditions before timing out.

4. Add Trigger Conditions

Triggers are what “fires” your event. By default you get one trigger, but you can add more.

Click Add new trigger condition under the Triggers section.

In that new block:

Choose a Type (e.g. Click, URL match, AJAX request, DataLayer push, DOM element change).

Fill in any fields that appear:

Selector (for Click or DOM events) – click the little “target” icon, hover your mouse over the element on your site, then click it to grab its CSS selector.

URL pattern, AJAX URL, or other details, depending on the type.

Repeat for additional triggers if needed.

5. Add Outcome Conditions

Outcome conditions determine whether your event is reported as Success or Failure.

Click Add new outcome condition under Outcome Conditions.

Select a Type (same set as triggers).

Choose Success or Failure (radio buttons).

Configure any type-specific fields (selectors, URLs, patterns).

If you have more than one outcome condition, the module will chain them (AND/OR) according to your Condition Operator setting.

6. Collect Custom Data

You can extract extra data when the event fires (e.g. cart value, user ID).

Click Add new collect data condition under Collect Data.

Select Extract from type (URL, AJAX response, DataLayer, DOM element, etc.).

Give it a Definition Name (how this field will appear in reports).

Choose an Operator (equals, contains, regex, etc.) and enter the Value or pattern to match.

For complex extractions, switch to Advanced mode to get the additional radio-button extract-on-Success/Failure/Error.

7. Auto-Save & Local Changes

Every change you make is saved locally in your browser immediately.

Local edits are marked in the dropdown with an asterisk (*).

8. Preview & Test Conditions

The module listens for a custom DOM event (wz.testEventCondition).

You can dispatch this event (e.g. via console) to highlight which conditions would match in real time.

9. Revert, Publish, or Delete

Revert Changes (per-event) or Revert All Changes (global) will discard your local edits.

Publish (per-event) or Publish All will send your changes live to production. You’ll be asked to confirm.

Delete lets you permanently remove an unpublished event. Confirm to proceed.

10. Close the Module

Click the dashboard’s Close or × button to exit.

Your last selection is remembered; reopen and continue editing any time.