> 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/campaign-management/how-floor-pricing-is-applied.md).

# How floor pricing is applied

## How floor prices (minimum bids) are applied

Floor prices (**minimum bids**) let retailers establish a **minimum cost per mille or click** for eligible inventory.

{% hint style="info" %}
Minimum bids that are set can vary by retailer.
{% endhint %}

Depending on your retailer, minimum bids can exist at multiple levels at once. The platform automatically shows the minimum bid that applies on the **Strategy** stage. In the example below, both campaign-level and keyword-level minimum bids are visible:

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FqdgnzubzrtLeSpiRrjKM%2FStrategy%20floor%20pricing.png?alt=media&amp;token=b8a7aac2-aef1-464d-9d1c-0b4f0ac7a1fa" alt=""><figcaption></figcaption></figure>

### Priority hierarchy

When several floor prices could apply, the system uses a priority hierarchy. It checks levels from most specific to broadest, selects the first matching minimum bid, and then stops.

It does **not** compare all matching values and choose the highest one.

For example:

* A keyword has a minimum bid of **$0.25**
* The retailer catalog minimum bid is **$0.75**

The **keyword** rule wins at **$0.25** because keyword rules sit above catalog rules in the hierarchy.

This approach respects the **most specific** control configured for the request, rather than mixing or averaging values across levels.

The platform evaluates minimum bids in this order when a level applies to the request:

1. **Keyword or keyword + placement**, including standard and cross‑sell placements
2. **Category or category + placement**, for standard category placement where configured
3. **Banner slot**, for differentiated floors by banner slot—for example **top versus bottom** of page, **video‑capable** banner slots, **shoppable** banners, or similar banner slot distinctions
4. **Placement**, including broad placements such as specials, checkout, home, and other high‑traffic surfaces
5. **Retailer catalog**

### Where you see minimum bids in campaign setup

#### Campaign wizard: Strategy stage

{% hint style="info" %}
Available minimum-bid scopes vary by retailer. It's likely that your retailer may use some, but not all minimum bid types.
{% endhint %}

**Banner slot, placement, and catalog minimum bids:**

The calculated minimum bid is displayed directly below where you set your campaign-level bid.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2Fip01zdYZKUXoxmX84l2q%2FCleanShot%202026-04-29%20at%2011.54.06.png?alt=media&amp;token=cad75fe4-3d70-4187-93f2-acdfc833e039" alt=""><figcaption></figcaption></figure>

**Keyword minimum bids:**

For campaigns with **search** targeting, you will see the **Minimum Bid** column when setting keyword-level bids.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FqdgnzubzrtLeSpiRrjKM%2FStrategy%20floor%20pricing.png?alt=media&amp;token=b8a7aac2-aef1-464d-9d1c-0b4f0ac7a1fa" alt=""><figcaption></figcaption></figure>

**Category minimum bids:**

On retailers configured for **category-level minimum bids**, applicable minimum bids can appear on the **Strategy** step. You can see the minimum bid for each category there.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FzK009JGLz8P6JOaxZhET%2FCategory%20Min%20Bids%20B.png?alt=media&amp;token=62787816-2458-4b1f-9a80-dd6f97720912" alt=""><figcaption></figcaption></figure>


---

# 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/campaign-management/how-floor-pricing-is-applied.md?ask=<question>&goal=<endgoal>
```

`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.
