> ## Documentation Index
> Fetch the complete documentation index at: https://docs.citino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Attribution

> Whether being named sent real visitors: AI-referred sessions from Google Analytics, matched back to your questions, with how much of the traffic could be matched.

Attribution answers: did any of this send a real visitor, and what is a question worth? It reads your AI-referred sessions from Google Analytics 4 and matches each landing page to the questions whose answers cited that page.

> [!WARNING]
>
> Attribution is a disclosed estimate, not proof. Google Analytics says a visit came from an AI assistant and landed on a page; it does not say which question the buyer asked. Citino matches the two by which answers cited that page. **Coverage**, always shown beside the numbers, says how much of the traffic that match could explain.

## Connecting Google Analytics

Until a property is connected, the screen explains what connecting gives: sessions from ChatGPT, Perplexity and Gemini split by referrer, the landing pages AI assistants actually send people to, and conversions tied back to the questions that produced them. Citino asks for read-only access to Analytics and nothing else.

* **Connect Google Analytics** opens [Integrations](https://docs.citino.ai/guides/account/integrations.md), where the connection is made and later removed. An owner, admin or editor can connect it.
* **Email a setup request** is for when someone else owns your analytics. It also starts from Integrations.

Each project connects its own GA4 property.

## What is on it, top to bottom

### The toolbar

The scope: the property and the window. The window is the last 30 days. **Export** is shown and not available yet.

Notices appear above the figures when they apply: Google has revoked the connection (**Reconnect**; what is shown is the last successful import), an import is running, or coverage dropped, in which case read the numbers as a floor.

### The totals

* **AI sessions**: visits to your website that came from an AI engine, as reported by Google Analytics, and how many of them came from engines Citino asks.
* **Conversions**: AI visits that went on to complete the goal you track in Google Analytics, and their share of AI sessions.
* **Revenue**: the value of those conversions, as Google Analytics reports it.
* **Coverage**: "The share of AI visits we could trace back to one of your questions. The rest still count; we just cannot say which question sent them." It is shown as a share with the sessions matched out of all AI sessions.

### AI sessions by source

Visits from each AI engine, by the referrer Google Analytics reported, with conversions, revenue and **CVR** (the share of visits that converted). Visits from Copilot, Claude and Grok are listed too and labelled **not sampled**, never dropped, even when the project collects answers from Claude or Grok.

### By landing page

The pages AI visitors landed on, and how many of those visits could be traced to a question. A page no question cites reads **not cited**: that is a finding about your questions, not an error. A page Google Analytics grouped into its own catch-all row says so.

### By prompt

What each question’s traffic was worth, as a range, with the traffic no question explains in the same table and at the same weight.

| Column | What it shows |
| - | - |
| Floor | Visits only this question can explain: the least it is responsible for. |
| Ceiling | Every visit this question could explain. Questions can share visits, so ceilings are never added up. |
| Est. revenue | The revenue from this question’s visits, estimated from what Google Analytics reports for the pages it sends people to. |
| Confidence | How sure we are that these visits came from this question. It is lower when the link rests on only a few citations. |

The ceiling column’s total reads **not totalled**. The unmatched rows say why each visit was not matched, and matched plus unmatched adds up to every AI session.

### Your own prompts

Questions you added yourself are reported in their own table, never mixed into the main one.

## What it cannot see

* **Google’s AI answers.** AI Overviews send visitors as google.com, the same as ordinary search, so their visits cannot be told apart from search and are not credited to a question.
* **A page no question cites.** Coverage is capped by your questions: traffic to a page none of them cites cannot be matched. The lever is more questions about the pages that get the traffic.
* **Return on spend.** There is no ROI figure, because dividing value by cost while coverage is below the whole would flatter the result.

## Empty and error states

* **No AI-referred sessions in this window**: nothing arrived to attribute. That is a finding about the window, not an error.
* **No question explains this traffic yet**: every AI session landed on a page no question has cited.
* **Not connected**: the connect card above.

## Related

> [card] [Integrations](https://docs.citino.ai/guides/account/integrations.md)
>
> Connect, reconnect or remove Google Analytics.

> [card] [Sources](https://docs.citino.ai/guides/screens/sources.md)
>
> Which of your pages the engines cite.

> [card] [Prompts](https://docs.citino.ai/guides/screens/prompts.md)
>
> Add questions about the pages that get traffic.

> [card] [What we do not measure](https://docs.citino.ai/guides/methodology/what-we-do-not-measure.md)
>
> The limits of every number here.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.