igeo.ai DocumentationOpen app

Measure results

AI Traffic

On-site visits from AI-related sources: embed our lightweight tracker, see dashboards at /analytics-separate from prompt monitoring in Mentions.

View Markdown · AI index · Full documentation for AI

Overview

AI Traffic is your workspace view of on-site visits tied to AI-related discovery — not the same story as Dashboard or Prompts (those track model answers to monitored questions).

Here, “top sources” means referral and path patterns in your traffic data — not citation domains from AI answers; for those, use Sources and Mentions.

  • /analytics — visits, trends, and breakdowns (pages, referral-style sources, geography, device, browser) for sites you connect.
  • /analytics/crawlers — crawler-focused analytics (AI Crawlers doc).
  • Prompt monitoring — see Understanding chats and Understanding your performance.

Embedding the tracker

Prompt monitoring shows what models say. AI Traffic shows who actually lands on your site from AI-led discovery — only after your pages send events to igeo.ai.

Your production snippet — with real workspace id and API host — is always shown under AI Traffic → Settings.

Example below: replace YOUR_ACCOUNT_ID; collect URL may match your deployment (e.g. https://api.igeo.ai/analytics/collect).

  • data-account-id — binds hits to your workspace.
  • data-endpoint — posts to /analytics/collect on the API.
  • Hosted script — loads https://public.igeo.ai/tracker/v1/tracker.min.js in the document head.
<script>
  (function() {
    var script = document.createElement('script');
    script.setAttribute('data-account-id', 'YOUR_ACCOUNT_ID');
    script.setAttribute('data-endpoint', 'https://api.igeo.ai/analytics/collect');
    script.src = 'https://public.igeo.ai/tracker/v1/tracker.min.js';
    document.head.appendChild(script);
  })();
</script>

What each event includes

  • Page context: URL, path, time; optional session and landing hints.
  • Attribution: referrer when available — links visits to AI surfaces.
  • Environment: user agent; browser, OS, device, language where derivable.
  • Human vs bot: classification and crawler name when relevant.
  • Location: coarse geography (e.g. country or region) from IP when present.

Privacy

Read the Settings tab on AI Traffic for EU storage, minimizing identifiable data, and wording to review before you deploy on customer-facing sites.

Traffic view

On the default view at /analytics you get:

  • Providers — LLM-related breakdown plus an aggregate TOTAL.
  • Volume & trends — visit counts with period-over-period context and a chart for your date range.
  • Tables — top sources, pages, locations, devices, browsers (AI-attributed traffic — not share of voice from prompts).

Filters

  • /analytics — analytics toolbar: providers, countries, shared date picker.
  • /analytics/crawlers — adds crawler-focused filters when relevant.
  • Monitoring pages (Prompts, Mentions, etc.) — different controls: regions, topics, tags, branded toggles.

Why on-site traffic matters at igeo.ai

Much of igeo.ai explains what models say about your brand. AI Traffic answers whether real visitors arrived via AI-led discovery.

  • Close the loop — see if interest in assistants and AI search surfaces turns into actual site visits.
  • Measure pathways — referrers, landing paths, geography, devices, trends — how people move from AI contexts to your pages.
  • Prioritize work — pair “signal in chat” with traffic on owned properties for content, attribution, and ROI — not leaderboard metrics alone.

Video walkthroughs