> 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-reporting/inventory-yield-report.md).

# Inventory yield report

The Inventory Yield Report shows how your ad placements are performing. It displays ad requests and fill rate, revenue, impressions and eCPM, and where targeting demand concentrates, so you can spot under-filled placements and yield opportunities without building a report.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FvuoRZM1Z2r7kEMvnjmyd%2FYield%20Report%201.png?alt=media&amp;token=c7d10fd6-cdca-4cd5-92c8-5c9b63405b07" alt=""><figcaption></figcaption></figure>

### Overview

The Inventory Yield Report brings placement-level performance together in one view: a performance table, a trend chart over time, the split between auction and Featured/Targeted Auction demand, your active and scheduled Featured/Targeted Auction campaigns, and targeting opportunities by display category. Use it to understand fill rate, revenue, and demand across your inventory, and to decide where to act.

### Why use this feature?

* **See placement yield at a glance:** Fill rate, ad requests and ads served, revenue, impressions, and eCPM per placement.
* **Track performance over time:** A trend chart shows how placement metrics move across your selected date range.
* **Understand your revenue mix:** See how revenue and share split between auction and Featured/Targeted Auction demand.
* **Find targeting demand:** See where targeting demand concentrates by display category.

#### How to access the Inventory Yield Report

As a retailer, you'll find this under the Insights tab. Select **Inventory Yield Report** from the sidebar.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2F2u4wRZEgzPE4V1Z2jbUN%2FYield%20Report%2042.png?alt=media&amp;token=82f8e872-09b9-4828-a73e-848e071d1a77" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Don't see the report?**

Check that you're in the retailer team, and that the report is rolled out to your account.
{% endhint %}

### Key Information

**How request figures are measured**

Pages often ask for more ads than they can display. A search page might request 20 product ads but only have an available capability to show 4. Counting all 20 would make fill look far lower than it really is, so request figures in this report are modelled: each request is counted against the number of ad positions the placement can realistically display, called its cap.

For each placement, catalog and ad type, we look at how many ads that placement has actually displayed per request in recent history, and set the cap just above that, excluding rare outliers.&#x20;

A placement that typically shows 4 ads gets a cap of 4, regardless of how many it requests. Where a placement has too little history, a standard default applies.  \
The cap applies to both sides of the calculation:

| Example request         | Requested | Served | Reported as Ads requested | Reported as Ads served |
| ----------------------- | --------- | ------ | ------------------------- | ---------------------- |
| Cap of 4, partly filled | 20        | 2      | 4                         | 2                      |
| Cap of 4, over-served   | 20        | 5      | 4                         | 4                      |

Ad requests, Impressions and revenue are not modelled. They count recorded requests and ad events.

{% hint style="warning" %}

## Modelled Data is available from 31 July 2026.

For earlier periods, requested and modelled figures were the same, so fill appears to step up at that point even where delivery didn't change. Compare periods from August 2026 onward.
{% endhint %}

**Requesting unmodelled metrics**&#x20;

If you need the raw figures, such as every ad slot your integration requested and every ad returned, select 'Request Access To Integration Metrics' in the banner at the top of the report. This registers and expression of interest with our development team, so that we can evaluate introducing these figures in the future.

These are most useful for integration teams checking how many ads each page requests. We reccomend using the modelled metrics in most instances, as care has been taken to model for the achievable ceiling. Unmodelled integration metrics are available via API, but not the UI.&#x20;

#### Page filters

| Filter         | Description                                                      |
| -------------- | ---------------------------------------------------------------- |
| **Catalog**    | Select the retailer catalog to scope performance to.             |
| **Date Range** | The date range used to filter every table and chart on the page. |

#### Placement performance chart (Trend over time)

At the top of the **Placement performance** section is the **Trend over time** chart. It plots each placement currently in scope as its own series across your selected date range, so you can see whether a placement is climbing, holding steady, or declining instead of relying on a single snapshot. The chart has two controls — a **Group by** dropdown and a metric toggle — and the chart type (lines or stacked bars) changes depending on the metric you choose.

**Metric options**

The metric toggle has three options. The first two draw a **line per placement**; the third draws a **stacked bar per placement**.

| Option                              | Chart type  | What it plots                                                                                                                                                                                                                                                                                                                                                                                          |
| ----------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Percentage ads served** (default) | Line        | The share of available ad positions that were filled, for each placement over time. Use it to spot under-filled placements and whether they are improving.                                                                                                                                                                                                                                             |
| **Ads requested**                   | Line        | The number of ad positions available for each placement over time. Use it to see inventory volume and seasonality per placement.                                                                                                                                                                                                                                                                       |
| **Revenue**                         | Stacked bar | Revenue for each placement over time, shown in your catalogue currency. Each placement's bar is stacked from two segments — **Auction revenue** and **FTA Revenue** — so you can see both total revenue and the auction-vs-FTA split in one bar. The **FTA Revenue** segment appears only when Featured/Targeted Auction is configured for your catalog; otherwise the bar shows auction revenue only. |

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FsdwZmlEWAuTxMpvrcFu7%2FYield%20report%202.png?alt=media&amp;token=8990fd2c-067b-40c7-923f-a99aa98d81b8" alt=""><figcaption></figcaption></figure>

#### Placement Breakdown table

The main table breaks down yield for each ad placement so you can compare fill rate, revenue, and efficiency side by side. Use it to find placements that are under-filled or earning a low eCPM, then dig into the trend chart to see whether they are improving or declining.

| Metric                    | Description                                                                                                                                                                                                                                                                        |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Placement**             | The ad placement the row reports on.                                                                                                                                                                                                                                               |
| **Ad requests**           | The number of times a page asked for ads from this placement in the selected date range. *(Also known as 'ad calls' / 'API calls')*                                                                                                                                                |
| **Ads requested**         | The number of ad positions available across those requests, based on modelled request data.                                                                                                                                                                                        |
| **Ads per request**       | The average number of ad positions available per request (Ads requested ÷ Ad requests).                                                                                                                                                                                            |
| **Ads served**            | The number of ads returned from the ad server to fill those positions.                                                                                                                                                                                                             |
| **Percentage ads served** | <p>The share of available ad positions that were filled (Ads served ÷ Ads requested). </p><p>A low value can indicate unsold inventory, eligibility or targeting limits, or a configuration issue worth investigating.</p>                                                         |
| **Empty-request rate**    | The share of ad requests that returned no ads.                                                                                                                                                                                                                                     |
| **Partial-fill rate**     | The share of ad requests that returned at least one ad but did not fill every available position.                                                                                                                                                                                  |
| **Impressions**           | The number of served ads that were displayed to shoppers.                                                                                                                                                                                                                          |
| **Auction revenue**       | Revenue from auction campaigns for the placement, in catalog currency. \|                                                                                                                                                                                                          |
| **FTA revenue**           | Revenue from Fixed Tenancy campaigns for the placement, in catalog currency.                                                                                                                                                                                                       |
| **eCPM**                  | <p>Revenue earned per thousand impressions. Use it to compare how efficiently each placement monetises. </p><p>Note that this is an <em>effective</em> measure — Many ads or placements are billed by clicks, rather than impressions, so this is an  — not a billing record. </p> |
| **FTA share**             | The share of the placement's impressions delivered by Fixed Tenancy campaigns.                                                                                                                                                                                                     |

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FcyoBiFRWLPR0fIGdv7Ml%2FYield%20Report%20Placement%20Breakdown.png?alt=media&amp;token=71698944-6af7-42b1-aed7-0d5e9f8b9211" alt=""><figcaption></figcaption></figure>

**Reading request outcomes**

Every ad request has one of three outcomes: it returns no ads, it partly fills the available positions, or it fills every position. Empty-request rate and Partial-fill rate cover the first two. The remainder are fully filled requests.

These two rates can help to understand why a placement may have a gap:

* **High empty-request rate** — most requests find no eligible ad. This usually points to limited advertiser or product coverage for the campaigns targeting the placement.
* **Low empty-request rate but high partial-fill rate** — ads are found, but not enough to fill the page. This usually points to thin demand per page, such as few advertisers bidding on the relevant categories or search terms.

To separate the two, set empty requests aside and look only at requests that returned ads. The share of those that filled every position is:`(100% − Empty-request rate − Partial-fill rate) ÷ (100% − Empty-request rate)`

* If most served requests fill completely, the advertisers you have are performing, and the gap is coverage: too few advertisers across the site.
* If most come back partly filled, demand is thin everywhere, and the gap is depth.

A placement can't fill more positions than its non-empty requests allow. For example, if 70% of requests are empty, Percentage ads served will be at most 30%.

#### Targeting Opportunities

This table shows where targeting demand concentrates by display category, comparing ad requests against ads served. Categories with high requests but low fill are opportunities to capture more demand.

| Metric                    | Description                                                                         |
| ------------------------- | ----------------------------------------------------------------------------------- |
| **Targeting Dimension**   | The targeting dimension value the row reports on (for example, a display category). |
| **Ad requests**           | Ad requests attributed to the dimension in the selected date range.                 |
| **Ads requested**         | Ad positions available across those requests.                                       |
| **Ads per request**       | Average ad positions available per request                                          |
| **Ads served**            | Ads returned to fill those positions.                                               |
| **Percentage ads served** | Share of available positions that were filled.                                      |
| **Empty-request rate**    | Share of requests that returned no ads.                                             |
| **Partial-fill rate**     | Share of requests that returned some ads but did not fill every position.           |

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FH8dy5HLcR9o97ZBC2DUp%2FYield%20report%20targeting%20opportunities.png?alt=media&amp;token=eda6df34-ec12-4459-af45-577060670dcc" alt=""><figcaption></figcaption></figure>

#### Active and Scheduled FTA campaigns

A table of your active and scheduled FTA (Fixed Tenancy Auction) campaigns, so you can see what is driving FTA demand during the selected period. This section is hidden when Featured/Targeted Auction is not configured for your catalogue.

| Column            | Description                                  |
| ----------------- | -------------------------------------------- |
| **Campaign name** | The name of the FTA campaign.                |
| **Advertiser**    | The name of the advertiser team.             |
| **Start date**    | When the campaign starts.                    |
| **End date**      | When the campaign ends.                      |
| **Status**        | Whether the campaign is active or scheduled. |

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FyZzw2n0uvbd8WEExzypj%2FInventory%20Report%20FTA%20Campaigns.png?alt=media&amp;token=7e93c850-8c68-4c10-8827-423eecbedff7" alt=""><figcaption></figcaption></figure>

### Tips for success

* Set the date first — they scope every table and chart on the page.
* Use the placement table to find low-fill or low-eCPM placements, then check the trend chart to see whether they are improving or declining.
* If Fixed Tenancy is configured, compare auction and Fixed Tennancy revenue to understand your demand mix.
* If a number looks different from another report, check the date range and catalogue filter match.
* Compare placements that serve the same shopper intent, such as two Search placements.&#x20;
  * If one fills far better than the other on similar traffic, the gap is more likely a configuration or targeting issue than a lack of demand. Raise it with your account manager before treating it as a demand problem.
* Compare Impressions with Ads served.&#x20;
  * Ads that are returned but never displayed can't earn impressions or clicks. Some gap is normal, for example ads below the fold, but a large or sudden gap can point to a rendering issue on your site.

### Troubleshooting & support

* **Numbers differ from another report:** Confirm the date range and catalogue filter match the other report.
* **Percentage ads served differs significantly from an older report:** Older reports may count every requested slot rather than modelled ad positions.&#x20;
  * Compare periods from July 2026 onward only.
* **Featured/Targeted Auction sections are missing:** They appear only when Featured/Targeted Auction is configured for your catalogue.
* **A placement shows zero served or low fill rate:** This reflects the underlying data for the selected period; investigate placement eligibility or demand.
* **Ads requested is lower than the number of slots our integration requests:** This is expected.
  * Request figures are modelled against each placement's cap.&#x20;
  * Use **Request Access To Integration Metrics**, and the BigQuery API if you need the unmodelled counts.
* Still need help? Contact your account manager or <support@citrusad.com>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.citrusad.com/retail-media-interface/retailer-reporting/inventory-yield-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
