Trends across every AI signal in one place.
Bot hits, referral conversions, citation share, top URLs by source. Time-series charts for the AI channel — same dashboard, same filters, comparable across every site you host.
free trial · 12 months of history kept by default
GPTBot up 22% week over week.
Every chart supports day, week, month and quarter rollups. Compare across sites, overlay annotations on top of deploys, export the underlying data when finance asks.
- day -0all bots2,847 hits · 187 humanslive
- day -1all bots2,684 hits · 161 humansok
- day -2all bots2,512 hits · 144 humansok
- day -3all bots2,398 hits · 138 humansok
- day -4all bots2,261 hits · 121 humansok
Raw event streams don't answer questions.
Logs are great if you want to know what happened at 12:04:22. They're useless if you want to know whether GPTBot reads more pricing pages this quarter than last. That question needs aggregation, time bucketing and rollups — not grep.
Most analytics platforms can do that for human traffic. None of them do it for AI. You end up writing SQL against your own logs, or pasting CSVs into a spreadsheet that goes stale by Tuesday.
Yovale aggregates the AI event stream into time-series and surfaces it as charts. Every metric you'd reach for: hit rate, citation share, conversion lift, page-level cumulative — already plotted, already filterable.
Charts an SEO lead will actually open.
Four chart families, each tuned for the kind of question an AI channel raises.
- 0101trend
Bot hit trend lines
Daily bot hits per source, stackable or overlaid. Annotate with deploys, content updates, robots.txt changes — see causation, not just correlation.
per-bot trend - 0202referral
Referral funnel
AI source → landing page → conversion. Same shape as a GA4 funnel, scoped to chat-driven traffic only. Day/week/quarter views.
funnel by source - 0303citation
Citation share over time
Of the pages quoted by ChatGPT, Perplexity, Claude and Gemini, which earned share this quarter? Which lost it?
share-of-voice - 0404compare
Cross-site comparison
Overlay metrics from two or more sites on the same chart. Pre-/post-redesign analysis, agency portfolio rollups, brand-vs-brand benchmarks.
n-site overlay
What AI-aware analytics should ship with.
analytics stack · how it works
From event stream to chart.
Yovale's analytics layer sits on top of the same edge event stream that powers bot tracking and referral capture. Roll-ups are pre-aggregated daily; ad-hoc filters resolve in seconds.
Every bot hit and referral event lands in a per-site time-series store. Same source of truth as the live dashboards — no duplicated capture path.
Daily, weekly, monthly and quarterly aggregates are computed each night. Common queries return in milliseconds, not seconds.
Charts render with the same design language as the rest of the dashboard. Filter by site, date range, source or URL — all chart-aware, all instant.
Charts in every plan, no analytics tier.
Datadog charges per host. Mixpanel charges per event. Yovale charges per WordPress site, and analytics is part of it.
Starter, 2 sites, full analytics on both. Annual only.
From raw stream to chart to action.
Things buyers ask before trusting the charts.
How far back does history go?+
12 months by default on every plan. Older data is available on Business plans up to 36 months.
Can I overlay deploy or content events?+
Yes. Drop an annotation at any date on any chart, manually or via webhook. We also auto-annotate when llms.txt or robots.txt changes.
Is there an API or just charts?+
REST endpoint per metric, CSV export per chart, webhook for thresholds you care about. Charts are the default UX, not the only one.
Can agencies overlay two clients' sites?+
Yes, if both sites are in the same Yovale account. Cross-account overlay is on the roadmap.
How are bots distinguished from real humans in referral charts?+
Bots and referrals are different event streams. Bot charts show UA-classified bots only; referral charts show visits without a bot UA whose Referer or client-hint matches an AI host.
Does this need any tracking script on the page?+
No. All capture is server-side at the edge. Page rendering is unchanged.
Stop building the chart you needed last quarter.
Move a site over in seven minutes. The first 30 days of charts populate as data arrives — the rest is yours to compare.