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

# Reports overview

> What each report answers, and which one to open first.

Soran has four reports. They read the same engine and the same period, so they
agree with each other and with your property's landing screen.

> **[Attribution](/docs/reports/attribution)**
>
> Which channels, campaigns, ad sets, and ads caused your revenue.

> **[Products](/docs/reports/products)**
>
> Revenue, units, orders, and profit per product, variant, or SKU.

> **[Landing pages](/docs/reports/landing-pages)**
>
> Which entry pages start the sessions that convert.

> **[Persons](/docs/reports/persons)**
>
> Look up one customer and read their path to purchase.

Opening **Reports** takes you to attribution, because it answers the question the
product exists for.

## What every report shares

**One period, shared everywhere.** Set the period in any report or on the landing
screen and the others follow. Change it in one place, not four.

**One attribution model.** The model you choose changes every revenue number in
every report. It is a reporting choice, not a setting you configure once — see
[Attribution models](/docs/concepts/attribution-models).

**The URL is the view.** The tab you are on, the rows you have ticked, the model,
the lookback, and the period all live in the address bar. Reload and you get the
same view back; paste the link to a colleague and they see what you see.

## How drilling down works

The bigger reports have tabs that form a hierarchy — channel, then campaign, then
ad set, then ad. Ticking rows on one tab narrows the tabs *below* it, and never
the tabs above.

That direction is deliberate. If a selection could filter upward, the hierarchy
would be circular and no level's totals could be trusted. It also means the whole
report arrives at once, so drilling down is instant rather than a new request per
click.

## Checking your data

Two screens exist for verifying rather than analysing: **Event logs** for what
arrived, and **Persons** for one customer's history.

> **[Event logs](/docs/reports/event-log)**
>
> Every event the property received, from every source.


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