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:
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
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
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.