> ## 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.

# Your first report

> Read your first attributed report and know what it is telling you.

Once events are arriving, open your property. The landing screen has two halves:
a box to ask a question in plain English, and below it the answer to the question
you did not have to ask — did marketing pay for itself.

## The overview

The bands on the landing screen state one period. The **blended** band is the
whole picture: all attributed revenue over all spend. Each platform band below it
is that platform's share of the same total.

There is no comparison arrow here on purpose. A single arrow cannot show you
whether a number is drifting or spiking, so movement belongs on a report that can
draw a trend.

The period you choose is shared across the product. Set it here and the reports
open on it; change it in a report and this screen follows.

## The attribution report

**Reports** opens on attribution, because it is the report that answers the
question the product exists for: which channels and campaigns caused your
revenue.

It reads the same data as the landing screen's bands, so the two cannot disagree.
If the blended figure on the overview looks wrong, the report is where you find
out why rather than a second opinion.

## Why this differs from your ad platform

Your ad platforms will report more revenue than Soran does. Added together, they
will often report more revenue than your store actually took.

That is expected. Each platform counts a conversion it had any hand in, judged by
its own attribution window and its own view of the click. Soran takes one
conversion and divides the credit across the touchpoints that actually led to it,
so the same sale is never counted twice.

This is why the blended band is the number to trust when deciding where money
goes, and why a platform's own ROAS is best read as that platform's argument for
itself.

> [!NOTE]
>
> Attribution is calculated against a goal — the conversion you have told Soran
> matters. A property with no goal has nothing to attribute revenue to.

## What to do next

If the numbers look thin, the usual cause is missing cost data rather than
missing events. Revenue arrives with your orders, but spend has to be connected,
and profit needs your costs.

> **[Attribution models](/docs/concepts/attribution-models)**
>
> Change how credit is divided across a customer's path.

> **[Goals](/docs/concepts/goals)**
>
> Define the conversion these reports are built around.


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