> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/retailer-team-and-user-management/understanding-team-health.md).
# Understanding team health
See how your advertisers are tracking at a glance. The Team Health report gives each advertiser a health score and a clear status — so your team knows who's healthy, who's trending down, and who needs attention before they stop spending.
### Overview
The Team Health indicators provide analysis of your advertisers based on their recent spend trends and activity and groups them into clear statuses so you can prioritise retention outreach and customer success engagement. It's designed to help account management move from reactive (*"they've already stopped"*) to proactive (*"they're trending down — let's reach out"*). \
\
The report is **read-only** and covers your advertisers only.
### Why use this feature?
* Spot advertisers who are declining before they churn.
* See *why* each advertiser has its status — a clear reason, not just a score.
### Prerequisites & availability
* **Where available:** Retailer teams (covers the advertisers in your account).
* **Limitations:** Read-only. Advertisers need enough spend history to be scored; very new or low-volume advertisers may not have a status yet.
* **Planned support:** This is an experimental, beta feature. Statuses, thresholds and guidance will continue to be refined based on customer feedback
#### How to access the Team Health report
Open **Teams**, then select the **Team Health** tab.
### Key Information
Each supplier team is scored **0–100** from its **auction ad spend across your network** (FTA spend excluded), as of today, then placed in a **health band**. Next to the band, a **Key Reason** names the single biggest factor behind it — so you see not just *that* a team needs attention, but *why*.
#### Health bands
| Band | Score | What it means | Typical action |
| ----------- | -------- | -------------------------------------------------------------- | -------------------------------- |
| **Healthy** | 70–100 | Growing or stable | No action needed |
| **Watch** | 40–69 | Declining but still active — or little/no recent spend history | Early check-in before it worsens |
| **At-Risk** | Below 40 | Stopped, or spend sharply down | Prioritise retention outreach |
{% hint style="info" %}
Teams with little or no auction spend history, or substantial gaps in spend, often show as **Watch**.
{% endhint %}
#### The five factors behind the Health band
The band combines five spend factors. Year-on-year spend carries the most weight; the others refine it. There's no prediction and no hidden model — it's a straightforward weighted combination of these factors, and the **Key Reason** simply names the one pulling the band down the most.
| Factor | What it measures |
| ---------------------- | --------------------------------------------------------------------------------------------------------- |
| **YoY spend** | Year-over-year change in ad spend vs the same period last year (weighted most) |
| **30-day spend trend** | Change in ad spend over the last 30 days vs the prior 30-day period |
| **Days since spend** | Days since the team's most recent ad spend |
| **Campaign diversity** | How many distinct campaigns are actively spending, compared to a 90-day benchmark |
| **LTV tier** | Spend quintile from 12-month auction spend vs other teams in your network — *not* consumer lifetime value |
#### Key Reason — the headline
The **Key Reason** column shows the biggest factor driving the band, as a short phrase you can act on:
| Key Reason | Shows as | Typical action |
| --------------------- | ------------------------ | ----------------------------- |
| **Stopped spending** | "45 days since spend" | Prioritise retention outreach |
| **Trending down YoY** | "−60% YoY" | Check in before it worsens |
| **Slowing (30 days)** | "−38% over 30 days" | Early check-in |
| **Growing** | "Growing" / "20% growth" | No action needed |
| **Stable** | "Stable" | No action needed |
{% hint style="info" %}
Campaign diversity and LTV tier feed the score too, but they tend to appear in the factor breakdown rather than as the headline Key Reason, as they are weighted lower.
{% endhint %}
#### How it appears in the report
* **In the table:** each team shows a **Health band** badge (Healthy / Watch / At-Risk), a **Key Reason** phrase, and columns for **Days since spend**, **Last spend**, and the four factors (YoY spend, 30-day spend trend, Campaign diversity, LTV tier). Filter by health band to focus your list.
* **In the detail view:** select any row to open the **Factor breakdown** — a table listing every factor with its **Trend** (Up, Down, or Flat) and a **Detail** value (e.g. "45 days", "−38%", "1 of 10 campaigns (90-day benchmark)", "Quintile 1"). If a band ever looks surprising, this is where you check exactly what drove it.
* **In export:** the CSV includes each team's **health band** and **Key Reason**, so the headline travels into your CRM, handover notes, or QBR prep (see *Exporting your list*).
#### Reviewing at-risk teams
1. Open the report and filter by **Health band**.
2. Focus on **At-Risk** teams first, then **Watch**.
3. Use the **Key Reason** to decide the next step, and open the row's **Factor breakdown** to see the full picture.
#### Exporting your list
Export to CSV to work your list outside the platform — the export includes each team's **health band** and **Key Reason**, so the headline travels into your CRM, handover notes, or QBR prep.
#### Tips for success
* Start with your highest-value **At-Risk** teams for the best return on outreach.
* Use **Watch** as an early-warning list — these are easier to save than teams that have already stopped.
* Not every at-risk team is saveable; use the band as a prompt, not a guarantee.
#### Troubleshooting & support
* **A band looks wrong:** Open the row's **Factor breakdown** to see the exact factors behind it. Bands are based on recent auction spend and can be affected by seasonality — the breakdown shows what drove the band.
* **A team has no band, or shows as Watch unexpectedly:** It may have little or no recent auction spend history (FTA spend isn't counted).
* Still need help? Contact your account manager or .
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.citrusad.com/retail-media-interface/retailer-team-and-user-management/understanding-team-health.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
