> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-exchange/sdk-configuration/integrating-the-ios-sdk/dynamic-floor-pricing-developer-preview.md).

# Dynamic Floor Pricing

{% hint style="success" %}
This feature requires explicit enablement by DT.\
Please contact your DT Commercial Representative before using this feature. If the feature is used without proper enablement, it may not work as expected.
{% endhint %}

Setting a dynamic floor price allows you to establish a custom price for your ad requests. To configure a dynamic floor price, set the `floorPrice` property of `IAAdRequest` with a double value representing the custom floor price in USD, as described in the following example:

{% tabs %}
{% tab title="Objective-C" %}

```objective-c
IAAdRequest *adRequest =
[IAAdRequest build:^(id  _Nonnull builder) { 
    builder.spotID = @"YOUR_SPOT_ID";    
    builder.floorPrice = @(3.14); 
}];

```

{% endtab %}

{% tab title="Swift" %}

```swift
let request = IAAdRequest.build { adRequest in
    adRequest.spotID = "YOUR_SPOT_ID"
    adRequest.floorPrice = 3.14
}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Submit the `floorPrice` value in CPM (cost per 1000 impressions), not per single impression.
{% endhint %}


---

# 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://docs.digitalturbine.com/dt-exchange/sdk-configuration/integrating-the-ios-sdk/dynamic-floor-pricing-developer-preview.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.