Rage Clicks Table

Rage Click Elements identifies page elements that received several rapid clicks in the same place.

Overview

Repeated rapid clicks can indicate that a visitor expected something to happen but did not receive the response they expected.

The table helps you find:

• the affected page;
• the element text or selector;
• the HTML tag;
• how many qualifying sessions contained the behaviour;
• how many distinct clicks were involved; and
• the average click position.

Select a row to see the qualifying sessions, their date, device, browser and click count.

A rage-click signal is evidence worth investigating. It is not proof that an element is broken or that a visitor was frustrated.

Access and scope

Rage Click Elements is workspace- and website-aware.

• The active workspace controls which websites are available.
• A specific accessible website must be selected.
• The table reports qualifying behaviour across that website.
• The dashboard’s selected page does not restrict this table.
• Each row identifies the page where the element appeared.
• The Referrer, Audience and Device selectors apply.
• The table has its own 1-, 3-, 7- or 14-day period selector.
• Markets and search groups are not used.

The website-wide scope helps you find repeated interaction problems without checking every tracked page separately.

Before you begin

You need:

1. The Wheremore pixel installed.
2. Tracking enabled for the website.
3. Relevant pages added in Manage Session Tracking.
4. Eligible human interaction data.
5. Background session processing completed.

The table only includes an element after rage-click behaviour has appeared in at least two qualifying sessions.

Quick start

1. Open the User Behaviour Dashboard.
2. Confirm the active workspace.
3. Select a website.
4. Leave Referrer set to All Referrers.
5. Select All traffic and All devices.
6. Set Period to Last 7 Days or Last 14 Days.
7. Review the elements with the highest Sessions and Clicks values.
8. Select a row to inspect its contributing sessions.
9. Open a relevant session in Session Replay.
10. Check the live page before deciding whether a change is required.

Apply the filters

Website

A specific website is required.

The table searches qualifying rage-click activity across tracked pages belonging to that website. It does not combine websites or fall back to another workspace.

Page

The shared page selector does not affect this table.

Rage Click Elements is intentionally website-wide. Use the Page column to see where each element appeared.

Use Page Engagement or Session Replay when you want to investigate a particular page in more detail.

Referrer

Choose:

• All Referrers to include every qualifying source;
• Direct to include sessions without a stored referrer; or
• a specific stored referrer.

Specific referrers use exact session-level matching. Protocol, path and query-string differences can produce separate referrer values.

Audience

Choose:

• All traffic for all qualifying visitors;
• Prospects for activity not classified as authenticated or identified; or
• Identified visitors for activity classified as authenticated or identified.

Audience classification depends on the tracking mode, authenticated-user rules, consent settings and exclusions configured in Manage Session Tracking.

Identified visitor filtering does not reveal a visitor’s private identity.

Device

Choose:

• All
• Desktop
• Mobile
• Tablet

Responsive layouts can change selectors, element positions and behaviour. Compare devices separately before assuming the same element behaves identically on every layout.

Period

Choose:

• Last 1 Day
• Last 3 Days
• Last 7 Days
• Last 14 Days

The range includes the current UTC calendar day.

A longer period helps reveal recurring patterns. A shorter period is useful after deploying a fix.

How a rage-click sequence is detected

The table looks for three consecutive recorded activation events that:

1. belong to the same session;
2. occur on the same page;
3. use the same stored element selector;
4. occur within 500 milliseconds; and
5. remain within 30 pixels of the first event.

Qualifying event types are click, touch-start and pointer-down records.

Overlapping sequences are deduplicated. For example, four distinct rapid clicks are counted as four clicks rather than as multiple SQL combinations.

The table also requires:

• a processed session already carrying the rage-click signal;
• human traffic;
• a session that has not been excluded; and
• at least two qualifying sessions for the element.

Understand the columns

Page

The page where Wheremore recorded the repeated interaction.

The URL is shortened for display. Move over it to see the stored value.

Element

The best available description of the affected element.

The table can show:

• visible element text;
• an element ID;
• the stored CSS selector; or
• Unknown when descriptive element data was unavailable.

Long text and selectors are shortened in the table.

Tag

The stored HTML tag, such as:

• a
• button
• input
• div

The tag provides context but does not establish whether the element was meant to be interactive.

Sessions

The number of distinct qualifying sessions in which the element produced a rage-click sequence.

This is not a unique-person count. One visitor can create more than one session.

Clicks

The number of distinct recorded activation events involved in the qualifying sequences.

The total is deduplicated when rapid sequences overlap.

Position

The average recorded click coordinates:

• X is the horizontal position as a percentage of the page or viewport reference;
• Y is the vertical position as a percentage.

Position helps distinguish repeated elements and place the signal over a page screenshot. It is an average, so responsive layouts and moving elements can make it approximate.

Expand an element

Select a table row to display its qualifying sessions.

The expanded table shows:

• Session ID
• Date
• Device
• Browser
• Clicks

The date is displayed in UTC.

Use the Session ID to locate the same visit in Session Replay where available.

The expanded view is limited to the 50 most recent qualifying sessions for that element and filter selection.

Interpret severity carefully

The Sessions value is highlighted when an element has more recurring evidence.

A stronger signal can indicate:

• a broken button or link;
• a control that responds slowly;
• an element that looks clickable but is not;
• a form that does not show validation feedback;
• an overlay intercepting input;
• a menu or accordion failing to open;
• repeated clicks during loading;
• an impatient but successful visitor;
• an intentional repeated control; or
• duplicate browser events from the same physical interaction.

Do not judge severity from colour or click count alone. Check the replay, element behaviour and outcome.

Recommended investigation workflow

1. Start with All Referrers, All traffic, All devices and Last 14 Days.
2. Sort by Sessions to prioritise recurring behaviour.
3. Expand the highest recurring element.
4. Compare its sessions, devices and browsers.
5. Open matching visits in Session Replay.
6. Check the element in Page Engagement.
7. Test the live page on the affected device and browser.
8. Confirm whether the expected action occurred.
9. Check conversion data before deciding the business impact.
10. After deploying a fix, use Last 1 Day or Last 3 Days to watch for recurrence.

Common causes and responses

A control does nothing

Confirm that its handler loads, the control is not disabled and another element is not covering it.

A response is slow

Add immediate loading or progress feedback and prevent unnecessary repeated submissions.

An element looks clickable

Change its styling or make the expected interaction available.

Form validation is unclear

Place the message near the affected field and move focus to the problem when appropriate.

The signal occurs on one device

Test the responsive layout, touch target, sticky elements and overlays on that device.

The action succeeds despite repeated clicks

The visitor may not receive prompt feedback. Confirm that the action becomes visibly complete and cannot be submitted repeatedly.

Analyse with AI

Use Analyse with AI after selecting the intended website, referrer, audience, device and period.

Ask Wheremore to:

• identify the elements with the strongest recurring evidence;
• compare devices or audiences;
• suggest likely causes;
• recommend what to inspect in Session Replay; or
• prioritise tests.

AI analysis should treat rage clicks as signals, not confirmed defects. Verify recommendations against recordings, the live page and conversion outcomes.

Data timing and limits

Rage Click Elements uses processed session and interaction data rather than live browser events.

• Recent sessions may take time to appear.
• The summary returns up to 100 element rows.
• Each expanded row returns up to 50 sessions.
• Elements need at least two qualifying sessions.
• Excluded sessions and non-human traffic are omitted.
• The report depends on a stored element selector for reliable grouping and expansion.
• Changes to page markup can create a new selector for what appears to be the same element.

What should I do next?

• Use Session Replay to understand the interaction sequence.
• Use Page Engagement to place the average position over the stored screenshot.
• Use Clicks vs Scroll Depth to compare the element with broader click activity.
• Use Manage Session Tracking to review audience and exclusion rules.
• Use the Conversions Dashboard to understand business impact.
• Use Page Optimisation when the page needs a structural or usability review.

Troubleshooting

The table asks me to select a website

Select a specific website in the User Behaviour Dashboard.

If no website is available:

• confirm the active workspace;
• confirm the website is assigned to it;
• confirm your account has access; and
• add the website and tracked pages in Manage Session Tracking.

No rage-click elements are found

• Increase the period to 14 days.
• Select All Referrers.
• Select All traffic.
• Select All devices.
• Confirm tracking is enabled.
• Confirm the website has recent human sessions.
• Allow session processing to complete.

An empty result can be valid. The selected website may not have an element with qualifying behaviour in at least two sessions.

The selected page has rage clicks but the table shows other pages

This is expected. The table is website-wide and does not use the shared page selector.

Use the Page column to locate the relevant row.

A specific referrer returns no rows

The selected referrer may have no qualifying rage-click sequences.

Return to All Referrers, increase the period and confirm the exact stored referrer value.

Identified visitors return no rows

The selected period may contain no qualifying sessions classified as identified.

Review authenticated-user detection in Manage Session Tracking, increase the period or select All traffic.

A device returns no rows

No qualifying sequence may exist for that device. Select All devices, increase the period and confirm tracking operates on the relevant layout.

A row will not expand

• Confirm the row has a stored selector.
• Refresh the page and try again.
• Confirm the AJAX handler is active.
• Check whether the session has expired.

Rows without a usable stored selector cannot be matched reliably to expanded session details.

The expanded row contains fewer sessions than expected

The expanded view returns at most 50 recent qualifying sessions. It also follows the current website, referrer, audience, device and period filters.

Clicks look lower than before

The corrected calculation counts distinct recorded events. It no longer counts duplicate self-join combinations as extra clicks.

Clicks still appear unexpectedly high

• Compare the expanded sessions.
• Check whether one physical interaction creates more than one recorded activation-event type.
• Inspect the visit in Session Replay.
• Confirm the element intentionally supports repeated input.

The reported position does not exactly match the screenshot

The value is an average across qualifying events. Responsive layouts, sticky elements, page changes and different viewport sizes can shift the element.

Filter by device and compare with the matching screenshot.

The table reports an access error

Confirm:

• the workspace is active;
• the website belongs to the workspace;
• your account can access the website; and
• the shared workspace website-access helper is active.

The table reports a loading error

• Refresh the dashboard.
• Confirm the signed-in session and nonce are current.
• Confirm the AJAX handlers are deployed.
• Confirm MySQL 8 is in use.
• Check the server error log for a rage-click database error.

Frequently asked questions

Does a rage click prove that something is broken?

No. It is a signal of rapid repeated interaction. Confirm the cause with Session Replay and live testing.

Is this table page-specific?

No. It reports across the selected website. Each row identifies its page.

Does the shared page selector affect it?

No.

Are markets used?

No. This is behavioural tracking data, not search-market data.

Are bots included?

Processed sessions classified as non-human are excluded.

Are excluded visitors included?

No. Sessions marked as excluded are omitted.

Does Sessions mean people?

No. It is a distinct-session count.

Can one visitor contribute more than once?

Yes. A visitor can create multiple sessions.

Is the Clicks value a raw SQL match count?

No. It counts distinct recorded events involved in qualifying sequences.

Does the table change my website?

No. It is read-only.