get_page_performance
Per-page engagement — views, unique visitors, average duration, scroll depth, bounce rate, rage and dead-click rates, plus p75 LCP.
When to use it
To compare pages against each other on engagement. For speed questions use get_page_vitals instead.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
Which of my pages have the highest bounce rate?
Am I sending traffic to my best pages?
What will make you wrong
Caveats
- Rates are view-weighted across days.
- Rows with lowSample: true are below 50 views and are not a basis for a rate conclusion.
Parameters
url
Restrict to URLs containing this string.
limit
Maximum pages to return.
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
dateFrom
Start of the window, YYYY-MM-DD. Inclusive.
dateTo
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.
pages
Per URL: total_views, unique_visitors, avg_duration_ms, avg_scroll_depth, bounce_rate, rage_click_rate, dead_click_rate, p75_lcp_ms and vitals_sample.
note
How the rates were weighted and what lowSample means.