Ask
/dashboard/<siteId>/ask — a chat over your own numbers. There is also an ask
bar at the top of Overview that hands its question
straight to this screen.
What it is given
Section titled “What it is given”Before the model sees your question, the server runs the same queries the dashboard runs — for the same site, the same range and the same filters — and builds a grounding block from the results. That block contains:
| Section | Contents |
|---|---|
| Site | Domain, site key, range label, timezone, currency |
| Identity | A standing note that the product is cookieless and what that costs |
| Filters | The active filter set, or “no filters applied” |
| Headline | Visitors, pageviews, visits, bounce rate, average visit, views per visit, revenue — each with its previous-period delta |
| Top pages | 8 |
| Referrers | 8 |
| Campaigns | 6 |
| Countries | 8 |
| Devices / Browsers / OS | 4 / 5 / 5 |
| Custom events | 8 |
| Goals | Every goal, with conversions, rate and revenue |
| Revenue | Revenue, transactions, average order, customers and revenue per visitor, in the site currency |
| Trend | Visitors per bucket for the whole range |
That is the entire universe the answer is drawn from. The model has no database access, no tools and no ability to run another query.
What it can answer
Section titled “What it can answer”- “What changed most in this period?”
- “Which campaign earned the most revenue?”
- “Is mobile converting worse than desktop?”
- “Summarise traffic from google.com.”
- “Which pages have the worst bounce rate?” — within the top eight pages.
- “Why did visitors drop last week?” — as a read of the data, labelled as one.
It also answers about something you highlighted on the page: a selection is sent alongside the question as the thing you are pointing at.
What it cannot answer
Section titled “What it cannot answer”Anything outside the grounding block. In particular:
| Question | Why not |
|---|---|
| “What is the 47th most visited page?” | Only the top 8 are in context |
| “Show me visitor 3a91…” | No session-level data is sent |
| “Compare March with July” | One range per question |
| “What does my competitor get?” | No external data |
| “Run this query for me” | It cannot query |
| “Retention for users who signed up in June” | Cohort data is not in context |
The system prompt requires it to say so plainly and suggest which screen to look at instead, rather than inventing a number. If you ever see a figure that is not on a screen somewhere, treat it as a bug and check the screen.
Fair use
Section titled “Fair use”Every account gets a monthly allowance for Ask. It is shown as a single percentage in Settings → Plan & usage, under the events bar: Hobby gets a smaller allowance, any paid plan a larger one.
At 100% Ask answers with a notice instead of an answer, and the rest of the dashboard is untouched. The allowance resets on the 1st of the month (UTC), the same window events are counted in.
There is no charge either way — nothing about Ask appears on an invoice, and running out costs nothing. It is a fair-use ceiling, not a meter.
Ranges and filters
Section titled “Ranges and filters”The range comes from the URL. If the question itself names a period — “yesterday”, “last 7 days” — that wins for the turn.
Filters are taken from wherever you asked. Asking from an Overview that is
filtered to country=DE produces an answer about German traffic, and the
context block says so.
Suggestions
Section titled “Suggestions”The starter chips are named after your own site: your second-busiest page, your top non-direct referrer, your top campaign, your top country. They are examples of questions that will work, not the only ones.
Privacy
Section titled “Privacy”URL parameters
Section titled “URL parameters”| Parameter | Values | Default |
|---|---|---|
range |
the nine range keys | 30d |
q |
a question to ask immediately | none |
q is asked once and then removed from the URL, so a refresh does not re-run
it. The range picker and the export button are hidden on this screen.