Visitors
A visitor, in the Trakkr sense, is a real person who asked an AI tool a question, got an answer that included you, clicked through, and landed on your site. They are the only AI traffic that pays your invoices. Everything else in the platform, visibility scores, citations, even crawler activity, is upstream of this moment.
That sounds simple, and in any other channel it would be. Email, paid search, organic, social, every one of those arrives with clean attribution: a URL parameter, a referrer header, a campaign ID. AI traffic doesn't. ChatGPT often strips UTM parameters, Perplexity routes some clicks through opaque redirects, and Claude's web client sometimes shows up as direct traffic. By the time the visitor lands on your page, the trail back to the AI tool is usually faint and sometimes gone entirely.
Visitors is the page that puts it back together.
What's actually different about AI referral traffic
A click from ChatGPT and a click from Google look almost identical in your access logs. Same browser, same device, same landing page. The differences are subtle but they change what you should do with the data.
| Behaviour | Search visitor | AI visitor |
|---|---|---|
| Intent at the moment of click | Browsing a list of options | Already partway through making a decision |
| Time spent before clicking | Seconds | Often minutes inside the AI tool first |
| What they know about you | The headline and meta description | Whatever the AI synthesized from your content |
| How they arrived | Clean referrer, UTMs preserved | Referrer often missing or generic, UTMs frequently stripped |
| Conversion rate (typical) | Baseline | 2-5x higher per session in most B2B categories |
The intent gap is the one that matters. By the time someone clicks through from an AI answer, they've already heard your pitch. They're not comparison-shopping any more, they're verifying. That's why AI traffic converts higher per session, and why even small volumes are worth treating seriously.
Why it's hard to measure
The honest answer: AI tools are not built with attribution in mind, and the picture is changing month to month. The four blockers you'll keep running into:
- UTMs get stripped. ChatGPT in particular often removes query parameters from outbound links. Anything you tagged on your site only survives if the AI tool decided to keep it.
- Referrers go missing. Some AI clients open links in a way that drops the
Refererheader entirely. In GA4, those visits land in "Direct / None." - Source names are inconsistent. Sometimes you see
chatgpt.com, sometimesopenai.com, sometimes a fresh subdomain after a product launch. A simple GA4 filter on one string misses the others. - Multi-step journeys are common. A visitor might land via ChatGPT, leave, come back via direct the next day, and convert. Last-click attribution undercounts AI in the first step and overcounts direct in the last.
The result is that almost every site is undercounting AI traffic in raw GA. Trakkr's job is to look at the whole pattern, not just one identifier, and surface what GA missed.
How Trakkr measures it
Visitors is a layer on top of your existing Google Analytics 4 property. You connect once via OAuth, and Trakkr reads visit data through the GA4 Data API. Nothing is intercepted in the browser, no extra script runs on your site.
What Trakkr does that GA4 alone won't:
- Matches referrers and source/medium strings against a maintained pattern set covering ChatGPT, Perplexity, Claude, Gemini, Copilot, Meta AI, You.com, Phind, Poe, and the long tail.
- Catches new AI hostnames as providers ship them, so a launch like a new ChatGPT domain doesn't quietly drop out of your numbers.
- Cross-references suspicious "direct" traffic against pages that are currently being crawled or cited, to recover visits that lost their referrer.
- Joins traffic data to your visibility data, so a spike in ChatGPT clicks lines up with the prompts and pages that earned them.
Connecting Google Analytics
You need a GA4 property (not Universal Analytics, which Google sunset in 2024) and editor or admin access to it. The connection is OAuth, one click after you've signed into your Google account.
- Open Visitors in the sidebar
- Click Connect Google Analytics
- Sign into the Google account that has access to the property
- Pick the property that matches your brand's domain
- Trakkr backfills the last 90 days automatically
Access is read-only at the GA4 level: Trakkr can see traffic data, nothing else. If you disconnect, the read access is revoked at Google's side.
If you manage multiple brands, each brand connects to its own GA4 property. Teammates who want to see Visitors for a brand they didn't connect just need to inherit access through team roles, they don't need to re-OAuth.
Reading the dashboard
Once data is flowing, the dashboard has two tabs that share the same date range, source filter, and AI taxonomy.
Traffic tab
The default view, organised around three questions.
- How much AI traffic am I getting? Hero stats at the top: total AI visits, change vs the previous period, share of overall traffic.
- Where is it coming from? Stacked chart and source filter for ChatGPT, Perplexity, Claude, Gemini, Copilot, and the rest. Click a source to isolate it.
- What are they landing on? Top pages ranked by AI sessions, with the source breakdown for each one.
Two side panels round it out: a Geo panel showing where visitors are coming from globally, and a Devices and sources breakdown when you need to slice further.
Conversions tab
Same visitors, viewed through the lens of what they did on your site. Pulls in the events you already track in GA4, plus optional revenue values you can set per event.
- Hero stats: total AI-driven conversions, conversion rate, AI-attributed revenue.
- Funnel: a multi-step funnel built from your own events (signup, trial start, paid, whatever you instrument), with conversion percentages at each step broken out by AI source.
- Sources by revenue: which AI tools are sending the visitors who actually convert, not just the visitors who arrive.
The Conversions tab is the answer to "is AI sending real customers, or just curious browsers?"
What to do with the data
Visitor data is most useful when you use it to feed decisions in the rest of the platform. A few moves that consistently produce something useful:
- Find your AI landing pages. Sort the Top Pages table by AI sessions. These are the URLs AI is sending people to. Treat them like landing pages: make sure they answer the implicit question and have a clear next action.
- Match clicks back to prompts. When ChatGPT traffic surges on a specific page, open the Citations page and look at which prompts cite that URL. That's the question pulling people in.
- Stop tagging links from inside your AI content for attribution. UTMs you add to your own site won't survive an AI tool rewriting the URL. Tag for your own analytics, but don't rely on UTMs to identify AI as the source.
- Treat "Direct / None" as suspect on AI-cited pages. If a page is cited by AI and getting direct traffic spikes, those are very likely AI visits with the referrer stripped. The Visitors dashboard accounts for this; raw GA4 reports usually don't.
- Use AI traffic to score content quality. Pages with strong crawler activity (see Crawlers) and weak visitor numbers are the ones to rework. Either AI isn't surfacing them or the snippet isn't compelling enough to earn the click.
Common questions
Why is my number lower in Trakkr than in GA4?
You're probably comparing different filters. Trakkr counts visits that match its AI source pattern set; raw GA4 reports often include "AI search" buckets that mix in real AI tools with regular search engines that have an AI feature. If the gap looks large, check whether your GA4 number is filtered to specific sources or includes a broader bucket.
Can I track AI visitors without GA4?
Not today. Visitors is a GA4 layer, and rebuilding the underlying pipeline (sessions, conversions, revenue, events) outside GA4 would mean asking you to install a separate tracker. If you don't have GA4 yet, the Live Visitors guide walks through the minimum install.
Does Trakkr modify my GA4 setup?
No. The connection is read-only. Trakkr never writes back, never creates events, never modifies properties. If you revoke access in Google's security panel, the connection drops cleanly.
How fresh is the data?
The dashboard reloads from GA4 every four hours. Click Refresh to pull on demand. GA4 itself usually lags reality by 1-4 hours, so a click that happened five minutes ago will not be in any view yet.
What if AI traffic just shows as "Direct"?
Some of it always will, particularly clicks from Claude and from in-app browsers that strip referrers. Trakkr cross-references direct visits against pages currently being crawled or cited to recover what it can. The rest you treat as a known undercount, the same way you treat "Direct / None" elsewhere in analytics.
Does this work in white-label client portals?
Yes. Visitors data is brand-scoped, so each connected brand has its own dashboard. Portal users see the dashboard exactly as you do, just under your branding.