What Peekaboo does not do
What Peekaboo does not do
Every major limitation in one place, grouped by theme, with links to the full detail and the workaround.
3 minute read · Last reviewed: August 14, 2026
You already know what AI Peekaboo tracks. This article is the honest flip side: every major thing it does not do today, grouped by theme, so you can plan around the real edges instead of finding them by surprise.
Coverage
- Five models only. ChatGPT, Gemini, Perplexity, Google AI Overview, and Google AI Mode are tracked. Claude, Copilot, Grok, DeepSeek, and Meta AI are not. See AI models we do not track.
- No history before you started tracking. There is no way to see what an AI said about your brand last year. Measurement begins the day a prompt starts being checked, not before.
What a tracked answer represents
- One observation, not everyone's answer. A tracked response reflects a specific prompt run under known conditions. It is not what every individual user sees, since personalization, location, account context, and model randomness all shift the real answer people get. See Personalization and history limits.
- Not proof someone asked that exact question. A tracked prompt tells you how AI answers that question, not how often real people ask it. Peekaboo is not a search-volume tool.
- Not proof of a sale. Peekaboo can show your brand was mentioned or cited. It cannot prove that mention caused a purchase or a traffic increase. See Guarantees and attribution.
Automation and alerts
- No proactive alerts. There is no email that tells you your score dropped or a competitor overtook you. Monitoring means checking the dashboard, a share link, Looker Studio, or the API on your own schedule. See Alerts and notifications.
- No public CLI. Automation runs through the REST API or MCP, not a command-line tool.
- No bulk brand or prompt creation in the UI. Setting up many brands or prompts at once goes through the API or MCP, not a bulk-upload screen.
Integrations
- No Gemini-app-side connection. The MCP and API integration works with Claude, Claude Code, ChatGPT/Codex, and Cursor. Gemini's own app isn't wired in; CSV export is the workaround.
- No native Agency Analytics or Octoboard integration. The current path is API to Google Sheets to your reporting tool of choice. See Integrations we do not have.
Numbers to treat carefully
- Competitor traffic estimates are directional, not exact. The "Market Traffic" numbers for competitors come from a third-party estimate. Your own Google Search Console and GA4 numbers are the reliable source for your own site.
- The free report understates on purpose. It uses 2 models, skips sentiment, and is built to be a conservative estimate, so it will read lower than what the paid dashboard shows once real analysis runs. See Free report vs. dashboard.
What Content Briefs will not do
- It will not write your articles for you. Content Briefs hands you the real citation data, the gap, and what to write about. It deliberately stops short of generating the article itself, because AI-written filler content is the opposite of what earns citations.
Account limits
- One free trial per workspace, ever. And only 1 brand can be tracked during any trial, regardless of the plan's normal brand allotment.
If something here affects a decision you're about to make, the linked articles go deeper on the mechanics and the workaround. If you don't see your question answered anywhere in this set, reach out at team@aipeekaboo.com.
Frequently asked questions
Does Peekaboo track everything an AI could say about my brand?
No. It tracks five specific models on the prompts you choose, so it is a measured sample under known conditions, not a record of every possible answer.
Will Peekaboo tell me automatically if something changes?
Not yet. There are no proactive score-change or competitor alerts, so you need to check the dashboard, a share link, or the API on your own schedule.
Can Peekaboo prove an AI mention led to a sale?
No. It can show that your brand was mentioned or cited, but connecting that to a specific sale or traffic increase is not something the data can prove.
What is the single biggest limitation to know before signing up?
There is no historical backfill. Measurement only starts once a prompt begins being tracked, so if you need to prove a past change moved the needle, tracking has to be running before that change happens.
