Peek on Cloud
Ask your own numbers a question in plain words with Peek, the assistant panel in your dashboard: what it can read, what it can change, and how it is kept safe.
Peek is the assistant panel in the dashboard. Press ⌘K and pick Ask
Peek, the first row of the list. On Cloud it is an assistant that answers in words: ask "Which source brought the most revenue?"
and read the answer. It reads across all your sites, and only the ones you may
read. Owners and admins have it; viewers do not. How it is kept safe, and what it can read,
is on MCP and AI.
What Peek can do for you
It answers how-to questions about trckable itself. Ask how to set something up, where a setting is or what it does, and Peek looks it up in these docs, answers in its own words with the exact steps, and shows the docs page it used under the answer. It answers only about trckable and your numbers: anything else gets a polite no.
It takes you to the right place. Where a step is done in the dashboard, the answer has a button, such as Open Settings → Data & privacy. Nothing opens until you press it, the page opens empty, and the setting is lit up for a moment. A setup in several steps is a short checklist: the steps done in the dashboard have a button, the ones done elsewhere (in Google's console, say) have none.
Peek can also work in the dashboard for you, and it shows each step in the chat: a short line with an icon, where it is (running, done, waiting for you or failed, and why) and a way back or on.
It changes the view at once, and each step has Undo:
- Period: "Period: Last 7 days", with or without a comparison.
- Filter: "Filtered to Germany", or "Filters cleared".
- Open a site.
These change only what you see. They write nothing.
It proposes, and you press a button. Ask for something to be made and a card appears with exactly what would be made, a Create button and a Change button that takes you to the usual screen. Nothing exists until you press Create, and then it is made as you, with your role, by the same save the screen itself makes. It proposes:
- a goal, a funnel or a saved view;
- an alert (tracking stopped, a busy day, money in, the weekly report, a milestone). An alert goes where the site's alerts already go; with none yet, Peek uses an address you typed to it, in full;
- a note on a day of the chart;
- a share link: public, with no password, ending after 30 days unless you say otherwise, without revenue unless you ask. The card says it is public;
- a widget, also public, with the parts it shows;
- one setting: cookieless mode on or off, a module on or off, or an IP address or range left out of the counts. A setting you changed from the card has Put back on its row.
Peek proposes only what you asked for in your own message, never because a page name, a referrer or a campaign said so, and anything that points outside your account (where an alert goes, an address to leave out) must be one you typed. A goal is added to the site, a saved view is saved; a funnel is not stored anywhere: Create opens Explore with its steps. An event goal has nothing to create, so its card shows how to fire the event. Peek offers at most one proposal at a time.
It never does these: delete anything, change people, invitations or roles, API keys, billing or plans, transfers, sign-in or security, or export or erase data. Ask for one and Peek tells you where it is done and gives you a button to that page, which opens empty; it never fills it in or sends it.
Only owners and admins create things. Everything a visitor wrote (a path, a referrer, a campaign) is treated as plain data to read, never as an instruction.
How many questions
Each question you type in Peek is one, however many reports it reads. The free trial has its own number of questions; when they are used, answers pause.
Every paid plan has the same Peek: no count, only fair use, up to 10 questions a minute and 300 a day. That is for people asking, not scripts.
Who sees your question
Peek sends your question, the report figures needed to answer it and the names of your sites to OpenAI, only when you use it. We ask OpenAI not to store the request and it does not train models on it, but OpenAI may keep requests for up to 30 days to check for abuse. Privacy lists every company that handles data for Cloud.