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

# Performance

> What the bookings came to: revenue, return on spend, and what is driving the funnel.

**Performance** is the measurement end of the group. Everything else here decides what is offered; this reports what came of it.

***

## What is on the screen

**A period selector** at the top — last 7, 30 or 90 days, or a **Custom range** you set — and views that regroup the same period **By channel**, **By campaign**, or **By strategy**. The view you are on can be taken out as a **CSV export** of that table.

Below that, sections, each answering one question:

| Section                     | The question                                                             |
| --------------------------- | ------------------------------------------------------------------------ |
| **Needs attention**         | What the screen thinks you should look at first                          |
| **Anomalies detected**      | Where the numbers moved unusually                                        |
| **Top performer**           | What is working best right now                                           |
| **Revenue trend**           | Which way revenue is going                                               |
| **ROAS comparison**         | What your campaigns returned against what you spent on them              |
| **Booking funnel**          | Where guests are dropping out between asking and booking                 |
| **Strategy performance**    | How each of your [strategies](/front-desk/guerrilla/strategies) is doing |
| **Day-of-week performance** | Which days sell                                                          |
| **Lead time distribution**  | How far ahead guests are booking                                         |

***

## What you do here

<Steps>
  <Step title="Start at Needs attention and Anomalies">
    They are the two sections that point rather than describe. Everything else is context for what they raise.
  </Step>

  <Step title="Read the funnel to see where guests stop">
    It separates guests who left before asking for a price from those who left after seeing one. Which of those is happening changes where you would go looking next.
  </Step>

  <Step title="Compare ROAS only where you recorded spend">
    A campaign with no spend entered can show bookings, but its return cannot be calculated. Spend is set on the campaign itself.
  </Step>

  <Step title="Switch views to change the question">
    The same period read **By channel**, **By campaign** and **By strategy** answers three different questions from one set of bookings. **Lead time distribution** tells you how far ahead your guests actually book.
  </Step>

  <Step title="Export when the reading belongs somewhere else">
    **CSV export** takes the table you are currently on — the channel, campaign or strategy view — out for a report or a conversation this screen is not the place for.
  </Step>
</Steps>

<Info>
  **A figure here describes what happened, not why.** A strategy at the top of the list was applied to bookings that converted; the screen cannot tell you whether it caused them or simply rode along with a busy week. Treat the sections as places to start looking.
</Info>

***

## What happens next

Nothing changes from this screen. What it tells you is acted on elsewhere: prices and availability on [Calendar](/front-desk/guerrilla/calendar), rules on [Strategies](/front-desk/guerrilla/strategies), offers and caps on [Campaigns](/front-desk/guerrilla/campaigns).