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

# The first hours and days

> What happens after you connect Google Ad Manager: the first check, the 28 days of history and when alerts start.

Right after you connect Google Ad Manager, the dashboard is still empty. This page explains what Stealth does in the first hour and the first days, and when you can expect numbers and alerts.

## How it works

Stealth works in hourly checks. Each check reads new data from every connected network, updates the dashboard and looks for drops. There is one check every hour, around 20 minutes past the hour.

### The first hour

The next hourly check reads the networks for the first time. Until then, each network shows **Preparing** in the **Control Center** ("Waiting for the first check (up to 1 hour)").

### The first day: loading history

To know what is normal for each ad unit, Stealth needs history. After the first check, it loads the **last 28 days** of each network, newest day first. The network shows **Loading history** with the progress in days. Loading uses the time left in each hourly check, so it is spread over several checks.

The list of clients and the link between clients and ad units come from a daily report that Google Ad Manager closes in the morning. Clients appear after the first daily report of each network, from 07:00 in the network's time zone.

### When numbers and alerts start

| What | When it starts |
| - | - |
| Revenue, requests and impressions on the screens | After the first check, for the days already loaded |
| Comparison with normal on the **Panel** | As soon as the 3 previous weeks of the same weekday are loaded |
| Hourly alerts (ad unit stopped, no ads served, client lost traffic or fill rate) | When the same hour of the same weekday has data in at least 3 of the 4 previous weeks |
| Daily alerts (revenue per request dropped, revenue trending down) | When the 3 previous weeks are loaded |

With the 28 days loaded, all of these are available. Until then, cards show **No normal yet** and no alert is opened for the hours without enough history.

> [!NOTE]
>
> Google Ad Manager data for an hour is not final right away, so each check evaluates the hour that started 2 hours earlier. An ad unit also has to be silent for 2 hours in a row before it becomes an incident. An ad unit that stops at 10:00 is therefore detected by the check at about 13:20. Daily data for yesterday is read from 06:00 in the network's time zone.

### What is monitored by default

* Every imported network is monitored.
* Clients in the **Brazil** category are monitored. Clients of the **Global** team and **Apps** are not. You can change this in the [Control Center](https://docs.usestealth.dev/en/screens/control-center.md).

## What you see

In the **Control Center**, each network moves through these stages:

| Stage | Meaning |
| - | - |
| **Preparing** | Waiting for the first check (up to 1 hour). |
| **Loading history** | Loading the 28 days of history, with the progress in days. |
| **Monitoring** | Working normally. Shows how many ad units the network has and the time of the latest data. |
| **No recent data** | Stealth could not read the network's Google Ad Manager reports for more than 3 hours. Every member is notified once. A network with little traffic does not trigger it: an hour with no ads is not a failure. |
| **Check failed** | The last check failed. Stealth tries again in the next check. |
| **No access from this Google account** | API access is off in Google Ad Manager. |
| **Connection revoked** | The Google permission was removed. An Owner or Administrator needs to reconnect. |

**Settings > General** shows the same information for the whole organization: **Not monitoring**, **Preparing**, **Monitoring** or **Needs attention**.

## FAQ

> [accordion] Can I speed up the first check?
>
> An Owner or Administrator can choose **Check now** in the **Control Center**. The check starts within 5 minutes. It refreshes the data, but hourly alerts are only evaluated in the regular hourly check.

> [accordion] Why does the Panel say there is too little data today?
>
> On **Today**, the comparison with normal starts after 3 complete hours of the day. Choose **Yesterday** to see a full day.

> [accordion] Will I receive alerts about the 28 days of history?
>
> No. Detection looks at the most recent hours and days. The history is only used to learn what is normal.


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