AI BEACON · ATTRIBUTION
Visibility on one side,
the visits it produced on the other.
Being named in an answer is where the argument starts. Finishing it means showing the visits and the goals that followed, and being straight about the share of AI traffic that arrives with nothing attached to say where it came from.
Finance asked what AI visibility is worth.
The question arrives eventually, and a screenshot is not an answer to it.
Somebody wants the business case for the work. Mentions and scores are interesting internally and do not survive that meeting on their own.
A visible share of the referrer report says direct, and everyone knows some of it is not, which makes every other figure easier to doubt.
The brand was credited in a major answer and there is no way to point at a single visit that came from it.
One script tag, then read the two together.
The visibility side is already in the project. This adds the traffic side and lines them up.
Add one script tag
The same tag enables Web Analytics and AutoFix. There is no GA4 connection.
See the setup →Visits from AI sources are recorded
From all AI sources, rather than only the engines you track.
See AI traffic →Set them against your prompts
Movement in presence beside movement in visits, in one project.
Put it in front of people
On a dashboard, exported, or scheduled by email.
See reports and dashboards →Two halves, joined in one project.
Four readings, one of which is an honest account of what cannot be measured.
Traffic that came from an AI tool.
Recorded in Web Analytics from the same script tag, covering AI sources generally rather than the tracked engines alone.
- All AI sourcesIncluding tools you are not tracking prompts on.
- Tagged where possibleOpenAI adds a source parameter to links in ChatGPT search, which makes those visits identifiable.
- Alongside everything elseIn the same analytics as your other traffic, on one timeline.
Presence on one axis, visits on the other.
Both halves read the same project, so a rise in presence and a rise in visits can be put on one chart without joining two exports by hand.
- Prompts and visits togetherMovement in each, over the same period.
- Down to the pageWhich of your pages the AI traffic landed on.
- With markersNote the day work went live and read the results against it.
The crawlers, counted separately.
Before a citation there is a crawl. Visits from AI crawlers and other bots are shown in their own right, apart from your human traffic.
- AI crawlersWhich bots are reaching your pages, and which pages they take.
- Other botsShown alongside, so the human figures stay clean.
- In both modulesBot visits appear in Web Analytics and in AI Beacon.
What this cannot show you.
A proportion of AI traffic cannot be attributed by anyone, and a report that pretends otherwise falls apart under a careful question.
- Visits with no referrerTraffic from the AI apps often arrives with nothing attached.
- Directional, not completeWhich is why presence and visits are reported side by side rather than as one conversion figure.
- Said out loud in the reportA stated limit is easier to defend than a confident number.
Mentions are the input. Visits are the outcome.
Reporting one without the other is what makes AI visibility work hard to fund, and the fix is to put both in the same project and the same report.
A typical stack
- –Visibility reported without any traffic beside it
- –AI visits sitting unexplained inside direct traffic
- –Crawler activity mixed in with human sessions
- –A business case made from screenshots
With citation attribution
- ✓Visits from AI sources recorded from one script tag
- ✓Presence and visits read together in one project
- ✓Bot visits counted separately from people
- ✓The unattributable share stated rather than hidden
SEORCE has no GA4 connection. Web Analytics collects traffic and goals from one script tag, and Google Search Console is connected.
The rest of AI Beacon, and where this one sits.
Attribution closes the loop that presence and citations open. These are the pages at the other end.
What is AI citation attribution?
AI citation attribution is the practice of reading AI visibility against the traffic and goals that followed it. In SEORCE, Web Analytics records visits from AI sources through the same script tag that enables AutoFix, and those visits are read against movement in the prompts AI Beacon tracks across 7 AI engines plus Google AI Overview, AI Mode and Search, inside one project. Visits from AI crawlers and other bots are counted separately from people. Some AI traffic arrives with no referrer, so the picture is directional rather than complete.
Key facts
- One script tag enables Web Analytics and AutoFix
- Web Analytics shows visits from all AI sources, not only the engines being tracked
- OpenAI adds a source parameter to links in ChatGPT search, which makes those visits identifiable
- Visits from the AI apps often arrive with no referrer and cannot be attributed
- Visits from AI crawlers and other bots are shown separately, in Web Analytics and in AI Beacon
- There is no GA4 connection; Google Search Console is connected
Last reviewed 15 October 2026 by the SEORCE team.
Proving it worked, and the limits.
No. Links in ChatGPT search carry a source parameter, and other engines usually send a referrer, but visits from the AI apps often arrive with nothing attached at all. Those land in direct traffic and no tool can separate them reliably. The honest version is to report presence and visits side by side and state the gap.
No. There is no GA4 connection and there is no plan described on this site. Web Analytics collects traffic and goals from one script tag, and Google Search Console is connected separately.
Sometimes, and not reliably. Plenty of answers name a brand without the reader ever clicking, which still counts as visibility. That is the reason presence is reported as its own measure rather than folded into a traffic figure.
They are counted, and separately. Visits from AI crawlers and other bots are shown in their own right in Web Analytics and in AI Beacon, so your human figures are not inflated by them. SEORCE does not claim to verify those bots by IP address.
Yes. Build a dashboard holding presence and AI visits together, export it as Excel, PDF or Google Sheets, or put it on a schedule. On Agency accounts and above, reports and emails carry your own branding.
Add a marker on the day the work went live and read the figures against it. That is correlation rather than proof, which is worth saying in the report, and it is a great deal more defensible than a screenshot.
Show what the visibility brought in.
Add the script tag, track the prompts that matter, and read presence and visits in one project.