Analytics — web, AI crawler, and agent-native insights
Measure traffic, journeys, acquisition, audiences, and multi-currency revenue; track 58+ AI/LLM crawlers and assistant referrals; and let agents review your real data through MCP.
Web analytics built for the AI traffic era
Understand visitors, journeys, acquisition, revenue, search indexing, AI crawlers, and assistant referrals—then let your agents analyze and act on the same data.


Measure the whole site, not just pageviews
Compare visitors, pageviews, bounce rate, visit duration, conversions, and revenue with the previous period on one timeseries. Revenue events are converted across currencies into the display currency you choose.


Follow goals, funnels, and individual journeys
Define goals and multi-step funnels, find drop-off points, and open a visitor's chronological journey across pageviews and custom events to understand what led to a conversion.


Find every acquisition path
Break traffic down by channel, referrer, campaign, keyword, and UTM source, medium, or campaign. Compare top pages, entry pages, exit pages, and titles to see where visits begin and end.


Segment any audience without losing context
Explore country, region, and city on a map, plus browser, OS, device, screen, and language. Add include or exclude filters on any dimension, then apply that segment across the dashboard.
See how AI crawls, cites, and sends traffic to your site
Separate machine discovery from human visits, then see which assistants send real people back to you.


Track 58+ AI and search crawlers page by page
Track GPTBot, ClaudeBot, PerplexityBot, Googlebot, Grok/xAI crawlers, and more. Compare per-bot crawl trends, drill into requested pages, classify activity as answers, indexing, training, or other, compare bot crawls with human traffic, and monitor fetches of robots.txt, llms.txt, and sitemaps. Bot-hit 404s reveal missing pages and content opportunities.


Connect assistant referrals to search visibility
See human visitors arriving from ChatGPT, Perplexity, Claude, Gemini, Copilot, and Grok in the AI Assistants card. A deterministic AI Visibility Score explains crawl coverage, crawler and assistant breadth, referral visitors, and discovery-file health. Google Search Console and Bing panels show affected URLs and the reasons pages are not indexed.


Watch activity happen in realtime
Open the realtime globe to see live visitors and events as they happen, then use the weekly traffic heatmap to find the days and hours when your audience is most active.
Let your coding agents analyze the same data you see
Analytics is part of the agent workflow, not a separate dashboard your agents cannot reach.


Run a full analytics review in an agent thread
Analyze with AI opens an agent thread that queries your real Aiola data through MCP: headline metrics, previous-period trends, pages, acquisition, audience, revenue, and AI-crawler activity. It returns an executive report with evidence-backed recommendations. Schedule the same workflow—such as a weekly AI-visibility report that checks crawler activity and AI-assistant referrals—as an automation on your existing CLI subscription. Agents can also query analytics, app logs, and feedback through MCP while coding.
Which agent CLIs and GUI Lifetime plan does Aiola support?
Aiola supports five agent CLIs: Claude Code, Codex, Cursor, Grok CLI (including grok-4.5), and OpenCode.
GUI Lifetime is available now at launch pricing: first 10 customers $49, next 30 $89, then $129. One-time payment.
Your code and repos stay on your machine. Agent prompts and file context are sent only to the AI provider you choose — Anthropic (Claude Code), OpenAI (Codex), Cursor, xAI (Grok CLI), or whichever provider you configure in OpenCode — under your own subscription. Aiola never proxies, stores, or resells your code or model traffic. Threads, tasks, notes, and automations are stored locally (SQLite + plain files in your repo). If you use the optional analytics/logs/feedback layer for your shipped products, that telemetry is ingested via Aiola's cloud (Supabase/Tinybird). Offline: agent orchestration UI works offline; running agents requires provider access; GUI Lifetime keeps the local app opening even if Aiola's servers are unreachable.
Frequently asked questions
What web analytics does Aiola show?
Visitors, pageviews, bounce rate, visit duration, and previous-period trends; top, entry, and exit pages; channels, referrers, campaigns, and UTM data; geography and device breakdowns; custom events; multi-currency revenue; goals, funnels, visitor journeys, a weekly heatmap, and a realtime globe. Include and exclude filters can segment the dashboard by any available dimension.
Which AI crawlers does Aiola track?
Server-side tracking recognizes 58+ AI/LLM, search, advertising, and link-preview crawlers, including GPTBot, ClaudeBot, PerplexityBot, Googlebot, and Grok/xAI crawlers. Aiola classifies activity as answers, indexing, training, or other; shows per-bot trends and page drill-downs; tracks robots.txt, llms.txt, and sitemap fetches; captures bot-hit 404s; and compares crawler activity with human traffic. The other bucket also retains unclassified bots detected by the browser-tracker endpoint.
Can an agent analyze my traffic?
Yes. Analyze with AI opens an agent thread that queries your real dashboard data through the Aiola MCP server, covering summary metrics, trends, pages, acquisition, audience, revenue, and AI-crawler activity. The agent returns an executive report with recommendations, and agents can query analytics, app logs, and feedback through MCP while they code.
Does Aiola replace Google Analytics or Plausible?
It can replace a general web analytics dashboard when its shipped coverage fits your needs, including traffic, acquisition, audience, events, revenue, goals, funnels, journeys, realtime, and segmentation. Its differentiators are AI crawler and assistant-referral tracking plus agent access through MCP. If you depend on a specialized GA or Plausible integration not listed here, verify that workflow before switching.
How does AI-visibility automation work?
Aiola computes a deterministic 0–100 AI Visibility Score from tracked popular-page crawl coverage, AI-crawler and assistant breadth, AI-answer referral visitors, and discovery-file health. Agents can explain the same component breakdown through MCP, and a scheduled analytics automation can report how the score and its underlying signals change over time.