How it works
Findings
A finding is one problem with one subject: a client, an ad unit, a line item, a header bidding set, a site or the whole network. When the same problem reaches many ad units, it stays one finding, and the ad units are listed inside it. A finding opens when a check sees the problem and closes on its own when a later check sees it gone. Every finding says what happened in one sentence, with the numbers behind it, and what to do next in GAM.Losing and at risk
- Losing: revenue lost now, per day. For example, a demand channel that stopped for a client shows what it used to earn per day.
- At risk: revenue per day that will be lost from a date if nothing changes. For example, a sponsorship that ends on Friday with no renewal in GAM.
The four groups
Checks use complete days only. A day with no data is never read as zero. When a network’s traffic on a day is far from usual (more than double or less than half), the checks that depend on traffic wait for a normal day, and a banner says so.
Not checked and Not checkable
- Not checked: the check did not run today yet, or its data was not complete. It runs again on the next day.
- Not checkable: the check cannot run on this network. GAM refused the read, the check does not apply to this kind of network (ads.txt and site approval on an MCM parent, for example), or there is not enough history yet.
Open incidents
Incidents and Health answer different questions: an incident is a drop happening now, in hours, and Health is the setup behind it. When an open incident covers the same client and the same kind of cause, the Health finding is marked Open incident, does not alert and is left out of the money on the Panel card. The incident page then shows the finding as Likely cause (Health). Health shows open incidents as one line with a link to Incidents.Marks
Anyone in the organization can mark a finding. Changing a mark another member set needs an Owner or an Administrator.
Each mark can be undone right after it is saved.
Alerts
Health alerts only when something changes: a new finding, one that got worse, or one marked Fixed that is still there.
Marked findings and findings covered by an open incident never alert. Muting a network, a client or an ad unit in the Control Center also mutes its Health findings. Health never sends webhooks. See Email and in-app notifications.
What Stealth cannot see
GAM does not expose some problems through its API, so they never appear here: policy center issues, sellers.json, tag and page errors, bidder timeouts and viewability by placement.What you see
Open Health in the sidebar, under Incidents. Under the title there are four tabs with counts:- Needs action: open findings at Attention or Critical, most urgent first.
- Watching: Light findings, marked findings, and findings found on the first check that are worth little.
- Closed: findings closed in the last 30 days.
- By client: one row per client with the state of each group (OK, the number of findings, Not checked or Not checkable), clients with findings first.
Finding page
The page has the sentence of what happened, the impact with how it was estimated, the severity and since when it is open. Then:- What to Do: the next step in GAM, with its menu path. For ads.txt, the exact line to add, ready to copy, and Check again to read the file again.
- Mark: the marks above.
- Affected Ad Units: the ad units this finding reaches. Each one opens its ad unit page.
- How to check in Google Ad Manager: the report or the screen that shows the same numbers, with dates in the network’s time zone.
- The history of the same problem, every mark, and the linked incidents and Opportunities items.
Panel card
The Health & Prevention card on the Panel shows how many findings need action, the money losing per day and the deadlines this week, the three most urgent findings and one line for open incidents. See all in Health opens this screen.FAQ
Why did a finding close without anyone marking it?
Why did a finding close without anyone marking it?
The daily check ran normally and no longer saw the problem. A check that did not run, was refused or was on hold never closes a finding.
Why is a group Not checkable on my network?
Why is a group Not checkable on my network?
Google Ad Manager refused the read on that network, the check does not apply to it, or there is not enough history yet.
Why did a problem I already knew about not send an alert?
Why did a problem I already knew about not send an alert?
On the first check of a network, the problems found are listed but not sent, so the first day does not bring a pile of old problems. A finding covered by an open incident, a marked one, or a Light one does not alert either.

