Analytics

Aiola Analytics combines browser events, server-side AI-crawler hits, search-provider data, and attributed revenue. Configure it for each project in Settings → Analytics, then use the project dashboard for detailed analysis or Central → Analytics for a cross-project view. See Set Up Analytics for the exact installation snippets and settings workflow.

​

Traffic dashboard

The project dashboard has Traffic and AI views. Date presets, custom ranges, segment filters, and hour/day/week/month timeseries granularity control the active scope. The Traffic view includes:

• KPIs and trends: pageviews (shown as Views), visitors, sessions, bounce rate, and average session time, with previous-period comparisons. The header also shows revenue, conversion rate, revenue per visitor, online visitors, and refunds when refunds exist.
• Content: hostname, page, entry page, exit link, and title breakdowns.
• Acquisition: channels, referrers, campaigns, search keywords, and UTM source, medium, campaign, content, and term data.
• Audience: map, country, region, city, browser, operating system, device, screen, and language.
• Events and conversion: custom events, goals, funnels, user journeys, and individual session details with page and event timelines.
• Revenue: purchases and renewals grouped by their original currency and converted into the project’s selected display currency; session details also show refunds and customer activity when present.
• Behavior and search health: weekly activity heatmap plus Google Search Console and Bing indexing issues when those providers are mapped.
• Realtime: current visitors and a live event stream on the realtime globe.

​

AI and crawler analytics

AI crawlers do not execute JavaScript. Crawler panels require one server-side or edge crawler snippet; the browser tag alone can still record human visitors arriving from AI answers. Bot-crawl data is separate from human traffic. The AI view and its analysis data cover:

• an AI Visibility card with a deterministic score from 0–100 and its component scores
• crawl totals, distinct bots, crawled pages, and a timeseries
• top bots and top crawled pages
• crawl categories: Answers, Indexing, Training, and Other
• human visitors referred by AI answers, including assistant and destination-page breakdowns
• popular pages with no successful AI crawls
• broken pages that crawlers requested
• discovery-file activity and health for robots.txt, llms.txt, and sitemaps

The score is deterministic. Its components use popular-page crawl coverage, AI-crawler breadth, AI-answer referral visitors, assistant breadth, and discovery-file health.

​

Search keywords

Connect Google Search Console and Bing Webmaster Tools in Settings → Integrations, then map the correct property or site in Settings → Analytics → Search Keywords. The dashboard can then show search queries and search-driven pages with clicks, impressions, CTR, and average position, plus indexing problems from both providers. Search-provider data is not realtime; Search Console data is delayed by about 48 hours.

​

Revenue attribution

After Stripe is connected, include the aiola_visitor_id and aiola_session_id cookies as Checkout Session metadata. Aiola uses them to attribute payments to the visitor, session, referrer, campaign, and country. The tracker can also record manual revenue with the reserved __revenue event. The project setting Display Currency controls how totals are converted and displayed. Revenue remains available by original currency in the analytics data.

​

Project settings and data controls

Settings → Analytics also provides:

• IP exclusions for a single IPv4 or IPv6 address or an IPv4 CIDR range
• exact or prefix path exclusions, hostname exclusions including subdomains, and country exclusions
• Attack Mode, which enables stricter bot and headless-browser detection plus per-IP and per-site limits
• CSV export by month or month range, with exports capped at 100,000 rows
• AI-assisted CSV conversion and direct CSV/TSV import with automatic format detection
• permanent clearing of all pageviews, events, sessions, and historical analytics for that project
• disabling collection while preserving existing data, followed by re-enabling at any time

​

Timezones

All timestamps are stored in UTC. Charts, date ranges, hourly/daily/weekly/monthly buckets, exports, session details, realtime timestamps, and AI analysis scopes are displayed using the workspace timezone selected in Central settings.

​

Central Analytics

Central → Analytics shows a card for every configured site, a combined chart, cross-project totals, realtime activity, and a per-project breakdown table. You can hide or show projects in the combined chart and open a card to switch to that project’s dashboard. Visitors and sessions are unique within each site. Central totals are the per-site unique counts summed across visible sites; they are not deduplicated into one person across different sites. Central Analytics is an aggregate view only. It does not include the project dashboard’s Traffic or AI tabs, AI Visibility, bot or referral panels, goals, funnels, journeys, retention, or Analyze with AI action. Open a project card for those tools.

​

Ask the AI about your analytics

The workspace MCP exposes five analytics tools:

• get_analytics_overview returns the dashboard-style overview: exact current and previous summaries, timeseries, content, acquisition, audience, events, journeys, revenue, and AI-crawler data.
• get_analytics reads one focused analytics pipe for a drill-down such as realtime events, retention, heatmap, funnel results, revenue, or a session event log.
• get_analytics_definitions returns configured goals and saved funnels with their results for the requested period. Renderer-local goals may be unavailable because they live only on that device.
• get_search_keywords returns Google Search Console and Bing query or page performance.
• get_indexing_issues returns Google and Bing indexing and crawl problems.

Retention has no dashboard panel. To retrieve it, explicitly call get_analytics with the analytics_retention pipe and the workspace timezone. The dashboard’s Analyze with AI button opens a new analytics thread and tells the AI to fetch the selected scope through these tools. Presets are Yesterday, Last 7 days, Last 30 days, and Last 90 days, or you can choose a custom calendar range. It preserves active traffic and AI filters, uses the workspace timezone, skips previous-period comparison for a partial current day, and requests a number-backed report with prioritized recommendations. Analyze with AI is a reporting action on the project dashboard. It is separate from Settings → Analytics → Add to App, which opens an implementation thread to add analytics tracking to the application.

​

Usage and monthly limits

Analytics usage is the number of billable events in the current monthly plan cycle. A billable event is a pageview or custom event (event_type 1 or 2), excluding _leave, _identify, and _scroll events. The Usage page shows Analytics events for the cycle and a per-site breakdown. When the monthly analytics event limit is exceeded, the dashboard is locked until the plan is upgraded or the next reset. Events continue to be tracked in the background, so no data is lost.