> ## 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. # Connect Google Ad Manager > Give Stealth access to read the reports of your Google Ad Manager networks, and what that access allows. Stealth has no data until you connect a Google account that has access to your Google Ad Manager networks. This page explains what Stealth asks Google for, how to connect, how to choose the networks Stealth reads, what you see while the data loads, how to add another Google account and how to disconnect one. Only an **Owner** or an **Administrator** of the organization can connect, add or disconnect an account. ## How it works * Stealth asks Google for two permissions: **Google Ad Manager** (`https://www.googleapis.com/auth/admanager`) and **email** (the address of the Google account that connects). * Google describes the first permission as access to Google Ad Manager in general. Stealth uses it only to list your networks and to run performance reports. It never changes orders, line items, ad units, inventory or settings. * To read the numbers, Stealth creates its own saved reports in each network, named `stealth-monitor-hourly`, `stealth-monitor-daily`, `stealth-monitor-catalog` and `stealth-monitor-demand`. * Stealth lists every network the Google account can access, except test networks, and reads only the networks you choose. Nothing is read before you confirm the choice. * For a network with MCM (Multiple Customer Management) partners, only the parent network is listed. Its partners are read through it. * An organization can connect more than one Google account, for example when one account reaches some networks and another account reaches the others. See [Add another Google account](#add-another-google-account). * The access is stored encrypted and is used only when Stealth fetches reports. ## Steps **1. Check API access in Google Ad Manager** In each network you want to monitor, open **Admin > Global settings > Network settings** in Google Ad Manager and confirm that **API access** is on. Without it, the network shows **No access from this Google account** in Stealth. **2. Open Integrations** In the Stealth menu, open **Integrations**. Find **Google Ad Manager** and choose **Connect**. **3. Continue to Google** Read the summary of the access and choose **Continue to Google**. Sign in with the Google account that has access to your networks and accept the permissions. **4. Choose the networks** Stealth opens **Integrations > Google Ad Manager > Choose networks**. Check the networks you want to monitor and choose **Start monitoring N networks**. See [Choose the networks](#choose-the-networks). **5. Follow the loading** The first check starts within 5 minutes. While it runs, the **Panel** shows the loading progress. Each network then moves through the stages described in [The first hours and days](https://docs.usestealth.dev/en/getting-started/first-days.md). > [!NOTE] > > If you manage several companies that must not see each other's data, create one Stealth organization for each one and connect each organization with its own Google account. ## What you see On **Integrations**, the Google Ad Manager row shows **Connected**, one line per connected Google account and its actions: * **Add another Google account** connects one more account. See below. * **⋯ > View status** opens the **Control Center**, where each network shows its stage and the time of the latest data. * **⋯ > Choose networks** opens the list of every network, to add or remove networks at any time. * Each account line shows the account's email and how many networks it reads. Its **⋯** menu has **Choose networks** (only that account's networks), **Reconnect** and **Disconnect**. * An account Google stopped accepting shows **Access revoked** and a **Reconnect** button. > [!WARNING] > > Disconnecting an account stops monitoring its networks at once and removes their clients, ad units and incident history from the dashboard. A network another connected account also reaches is not removed: Stealth goes on reading it with that account. Connecting again starts the removed networks from the beginning. ### Choose the networks The list shows each network the Google account can access, with its name, code, currency and time zone. * When the account sees up to 10 networks, all of them come checked. Above 10, none comes checked, so you choose on purpose. * From 8 networks up, a search box finds a network by name or code, and **Select all** checks every network in the list. * Networks Stealth already monitors appear checked under **Already monitored**. Unchecking one stops reading it. Its history stays. * When the list shows one account's networks, networks of that account it can no longer see are listed under **This account cannot see** and cannot be checked. * **Start monitoring N networks** confirms the choice. A network you leave unchecked is not read and shows under **Not monitored** in the [Control Center](https://docs.usestealth.dev/en/screens/control-center.md). ### While the data loads Until the first data arrives, the **Panel**, **Clients**, **Networks**, **Formats** and **Incidents** show the card **Loading Your GAM Data** instead of the data: * How many networks are ready out of the total, and the time since you confirmed the choice. * How many of the 28 days of history are loaded. * The time left, once a network has loaded 2 days of history. It is an estimate from that network's own pace, so it reads "About 40 min left". * **Connect another Google account**, to add an account that reaches more networks, and **See details**, which opens the **Control Center**. When no network is chosen yet, these screens show **Choose the Networks to Monitor** instead, with the **Choose networks** button. The **Panel** opens with data after the first check of the first network: today's traffic and yesterday's revenue. A slim banner above it follows the history until the 28 days are loaded. You can close it for the session. Two notifications arrive on the bell for every member: **Your Panel is ready**, when the first network finishes its first check, and **History complete**, when nothing is left loading. Alerts reach full accuracy once the 28 days of history are loaded. If the first check of a network fails, Stealth tries again in 5 minutes, up to 3 times, and then in the next hourly check. A network the account cannot read shows **No access from this Google account**, and the other networks go on loading. Disconnecting an account also removes the permission on Google's side for that Google account. The permission stays in two cases: another Stealth organization is still connected with the same Google account, or Google could not be reached at that moment. To check, open [myaccount.google.com/permissions](https://myaccount.google.com/permissions) with that Google account and remove Stealth if it is still listed. If you remove it there first, the networks show **Connection revoked** in the **Control Center** and every member is notified. ## Add another Google account Use this when your networks are split between Google accounts, or when another account has access to networks the first one cannot see. Nothing is removed: the networks you already monitor stay as they are. 1. On **Integrations**, choose **Add another Google account** in the Google Ad Manager row. 2. In Google, pick the other account and accept the permissions. 3. If the account sees networks Stealth does not have yet, Stealth opens **Choose networks** with that account's networks. Check the new ones and confirm with **Start monitoring N networks**. They load their last 28 days of history, as on a first connection. 4. A network both accounts reach is listed once and read with one account. If that account loses access to it, or is disconnected, Stealth goes on reading the network with the other account, with no gap in the history. To replace an account, for example when the person who connected it is leaving, add the new account first and then disconnect the old one. Signing in again with an account that is already connected only renews its access. ## FAQ > [accordion] Which Google account should I use? > > One that has access to every network you want to monitor and that belongs to your company, not to one person who may leave. Stealth only reads with it. > [accordion] Can Stealth change my ad setup? > > No. Stealth only lists networks and runs reports. It has no feature that writes to Google Ad Manager. > [accordion] Can I choose which networks are monitored? > > Yes. Stealth reads only the networks you check in **Integrations > Google Ad Manager > Choose networks**, and you can change that list at any time. For the networks it reads, you turn alerts on or off per network and per client in the [Control Center](https://docs.usestealth.dev/en/screens/control-center.md). > [accordion] Why does a network show No access from this Google account? > > The connected Google account cannot read that network: either the account has no access to it, or API access is off in that network. Give the account access, or turn API access on in Google Ad Manager under **Admin > Global settings > API access**. Stealth tries again in the next hourly check. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.