Documentation

get_element_click_analysis

Click statistics per HTML element (CSS selector) — total, rage and dead clicks — optionally aggregated across every page of a template.

When to use it

The workhorse for "what exactly is broken on this page". Run it with groupByTemplate: true first to catch theme-wide defects, then drill into a single pageUrl.

Ask for it like this

You do not name the tool. These are questions that make an assistant reach for it:

Which button on my product pages is broken?
Find elements people click that do nothing.

How to read the result

  • Template mode is the reason this tool matters. Per-URL statistics fragment a widget broken on every product page into dozens of small rows nobody ranks highly. Template mode reports the same selector once, with distinct_pages, so "the subscription toggle rage-clicks on all 40 PDPs" surfaces as one finding fixable once for every page.
  • Cross-reference the selector with get_page_dom_snapshot. That turns "P element with 9 dead clicks" into "paragraph copy mistaken for a link, sitting in main after heading 3".

What will make you wrong

Caveats

  • Rage on repeated-use controls is usually not rage. Quantity steppers, carousel arrows and gallery Next buttons are clicked rapidly by design. Check what the element is before reporting frustration.
  • pageUrl is ignored when groupByTemplate is true.

Parameters

pageUrl
string
Restrict to one page, matched as a substring.
groupByTemplate
booleandefault: false
Aggregate each selector across all pages of a template archetype instead of per URL.
rageOnly
booleandefault: false
Return only elements with rage clicks.
deadOnly
booleandefault: false
Return only elements with dead clicks.
limit
numberdefault: 50
Maximum elements to return.

Shared parameters it accepts

Documented in full on the tool reference index.

Date window — defaults to the last 30 days.

dateFrom
stringdefault: 30 days ago
Start of the window, YYYY-MM-DD. Inclusive.
dateTo
stringdefault: today
End of the window, YYYY-MM-DD. Inclusive.

Every tool also accepts merchantId, which resolves from your connection. You never pass it.

What comes back

JSON. These are the top-level keys; date-scoped tools additionally carry a _meta block with the server date and the data coverage envelope.

elements
Per selector: element_text, total_clicks, rage_clicks, dead_clicks, normal_clicks, unique_sessions, rage_click_rate, dead_click_rate, and distinct_pages in template mode.
groupedBy
"template" when template mode is on, so you cannot misread the rows.

Pairs with