Events
Events ranks the elements users click on a single view. Where a heatmap overlays interactions on a screenshot, Events reads them as a sortable grid: every element the RUM SDK captured on the view, with its clicks, dead clicks, rage clicks, and share of the view's total. Use it when you want the numbers behind a page rather than the picture of it, or when the view has no screenshot to overlay.
Events is built on the sessions, views, and actions your RUM SDK collects. See the data model for how these events work.
What you need
- The
PRODUCT-ANALYTICS:READpermission. - A web application instrumented with the Browser Real User Monitoring SDK (version 4.2.0 or later), generating action events on the views you want to analyze.
Open Events
- In Product Analytics, open Events. The application in view appears in the selector at the top left.
- Pick a view from the Views panel on the left. The panel header carries the number of views captured for the application, and each row names a view with its session count, busiest first. Events selects the busiest view for you until you choose another. Use Search views to find one by name.
- Set the period to analyze with the time range picker, which opens on the last 24 hours.
The grid, the chart, and the cards above them all describe the selected view.
The time range picker on Events offers up to the last 30 days. The 3, 6, and 12-month presets available elsewhere in Coralogix aren't offered here.
Read the summary cards
Four cards summarize the selected view over the time range:
- Elements clicked: how many distinct elements on the view received at least one click.
- Total clicks: every click counted across those elements.
- Dead clicks: clicks that produced no response, with their share of the view's total clicks beside the count.
- Rage clicks: rapid repeated clicks on the same element, also with its share.
Dead and rage clicks are signals of user frustration. A high count on either is worth chasing, because it usually means a control looks interactive but doesn't behave as users expect. See Spot user frustration.
The Top events chart below the cards plots the ten most-clicked elements on the view as bars. Select its header to collapse the chart and give the grid more room.
Read the events grid
The grid lists the elements clicked on the view, most-clicked first. It's titled Events on the selected view, with a badge carrying the row count.
| Column | What it shows |
|---|---|
| # | The element's rank on the view |
| Event | The action name the SDK reports for the element |
| Clicks | Total clicks on the element over the time range |
| Dead clicks | Clicks on the element that produced no response |
| Rage clicks | Rapid repeated clicks on the element |
| Share | The element's clicks as a percentage of the view's total, drawn as a bar |
Use the search box to find an event by name. Search runs against the full set of events on the view, so a match can appear with no metrics beside it when it falls outside the elements loaded for the grid. The summary cards don't narrow with the search, they keep describing the whole view.
An element Product Analytics can't identify appears as Unnamed element. Give it a readable name by adding an aria-label or a data-cx-action-name="your-element-name" attribute to it in your application, or analyze the unnamed elements to find them on the page and name them without reading the code.
A view can carry more clickable elements than the grid loads. When it does, a Top 500 badge appears: only the 500 most-clicked elements were read, so the totals and shares cover those elements rather than the whole view.
Analyze unnamed elements
When the grid holds unnamed elements, an Analyze unnamed elements button appears in its toolbar with a count of those rows. Select it to find each one on the page and give it a name.
The Unnamed elements on dialog, titled with the view, looks through up to six recent screenshots of the view for its 50 most-clicked unnamed elements. Its header reports how many it located, for example 12 of 50 elements found. Each element gets a card with its clicks and dead clicks, and reads One of N similar elements where the same element repeats on the page, such as a row in a table. An element no screenshot shows reads Not found in recent screenshots.
- Select a highlighted area on the screenshot to jump to its card, or step through cards with Previous element and Next element.
- Use Previous screenshot and Next screenshot to switch captures, Mark all elements to outline every element found, and Show click map to plot a sample of recent clicks inside the marked elements.
- Filter the cards with the All, To review, Named, and Ignored tabs. To review holds the elements you haven't named or ignored yet.
Once the analysis runs, each unnamed row in the grid also shows the text and kind of element it matched, so you can tell the rows apart.
Name or ignore an element
Naming and ignoring hand the change to the Coralogix Analytics Tool, version 1.1.0 or later. If the extension is missing or older, the dialog prompts you to install or update it.
- On an element card, select Name or ignore this element.
- Enter an Action name, for example
explore-add-filter, and select Apply. To stop reporting the element's clicks instead, select the option to ignore it. - Select Send N changes to Analytics Tool to add your pending changes to the extension. Select Discard to drop changes you haven't sent.
- Open the extension popup and save the report, then hand it to a developer. See Save and hand off the report.
The changes take effect once the developer adds the attributes to your application: data-cx-action-name to name an element, data-cx-action-ignore to ignore it.
If the dialog reads None of the unnamed elements were found, no screenshot from the selected time range shows them. Their structure may have changed since, or they may sit inside an overlay the screenshots didn't capture.
Narrow the data
Three controls narrow what the grid and cards cover:
- Instrumentation switches between Auto and Manual. Manual shows only the elements you tagged with
data-cx-action-name. Auto, the default, shows everything the SDK captured out of the box along with the manually tagged ones. - Page query param filter keeps only the sessions whose URL carried a given query parameter. Select a key, then a value. Each value lists how many sessions carry it, Any value matches the key whatever its value, and Not exists keeps only sessions whose URL lacks the key. Each active filter appears as a chip you can remove.
- Add filter under Filter by narrows by session attribute, the same set as a funnel step filter.
These filters scope the events on the selected view. The Views panel itself keeps listing every view for the application and time range.
Drag the trailing edge of the Views panel to resize it, or select Hide the views panel to collapse it to a rail and give the grid the full width. Your search term and scroll position survive the collapse.
Drill into an event
Select a row, or See users from its actions menu, to open a drawer for that one element. The drawer is headed Click on the event name, with a copy icon beside it.
- Total clicks counts every click on the element over the time range.
- Unique users reports the share of the view's unique users who clicked it, with the counts spelled out beneath, for example 12 of 340 unique users.
- The Users list names the people behind those clicks, up to 100, where each row shows the User, Account, Session date, Platform, and Country. A user your application didn't identify reads Unknown, and a session that set no account shows a dash. Select the play icon at the start of a row to open that user's Session Replay, or Download CSV to export the list.
Preview an action's screenshot
Select Preview from a row's actions menu to see the latest screenshot on which the RUM SDK recorded that action, without leaving the grid. The preview opens as a card pinned to the bottom right, scaled to fit, with the element scrolled into the frame and highlighted; the rest of the page stays usable. Select the card to expand it into a full dialog using the same capture, or select See heatmap to deep-link Heatmaps to that exact screenshot.
Start a funnel from an event
Select Start a funnel from a row's actions menu, or from the drilldown drawer, to build a funnel seeded from the element: a two-step funnel of the view followed by the click on that element. Refine the steps from there in the Funnels view. See Funnels.
Additional resources
Next steps
See the same interactions overlaid on the page itself: Heatmaps.