> 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-ads-demand/dt-exchange-openrtb-2.5-specs/dsp-dual-end-card.md).

# DSP Dual End Card

DSP Dual End Card lets DSPs supply up to two of their own end card creatives in a single bid response and present them sequentially after the video ad, instead of DT Exchange generating the second end card from the app bundle information. For the standard, DT-generated approach, see [Dual End Card](/dt-ads-demand/dt-exchange-openrtb-2.5-specs/dual-end-card.md).

### BidRequest.imp.video.ext

| ATTRIBUTE        | DESCRIPTION                                                                                                                                                                                                                     | TYPE    |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `dspdualendcard` | <p>Indicates whether the inventory is eligible for DSP Dual End Card, based on the publisher's config and the SDK's supported version.<br>(<code>true</code> or <code>false</code>, lowercase; default: <code>false</code>)</p> | Boolean |

### BidResponse.bid.ext.dspdualendcard

| ATTRIBUTE        | DESCRIPTION                                                                                                                                                                         | TYPE    |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `dspdualendcard` | <p>Allows the DSP to explicitly enable or disable DSP Dual End Card for this specific bid.<br>(<code>true</code> or <code>false</code>, lowercase; default: <code>false</code>)</p> | Boolean |

### Supported Creative Types

Static, iframe, HTML, and Playable end cards are supported in either sequence position.

### Rendering and Fallback Behavior

* Ad completes or is skipped: the first available end card renders — DSP end card 1, or the FMP end card if no DSP end card loaded.
* User closes or skips the first end card: the next end card in sequence renders — DSP end card 2, or the FMP end card if it wasn't provided.
* If DSP end card 1 fails to load, DSP end card 2 renders in its place; if DSP end card 2 also fails or isn't provided, DT Exchange renders the FMP end card as the fallback.
* If both DSP end cards fail to load, DT Exchange renders the FMP end card alone.

{% hint style="info" %}
The FMP end card only renders when DT Exchange has the app bundle details needed to generate it, the same requirement as the standard [Dual End Card](/dt-ads-demand/dt-exchange-openrtb-2.5-specs/dual-end-card.md) feature.
{% endhint %}

### SKOverlay and Store Promo

DT Exchange does not display [SKOverlay](/dt-ads-demand/dt-exchange-openrtb-2.5-specs/skoverlay.md) or Store Promo on customized DSP end cards by default. Request either through your Programmatic Demand Manager, at the integration level or per bid response. If a bid response's SKOverlay on end card attribute suppresses SKOverlay, that restriction also applies to customized end cards. FMP end cards continue to display SKOverlay and the StoreKit controller as they do today.

### Preserved Behavior

The close (X) button timing and delay logic don't change. DT Exchange continues to use the existing global configuration based on creative type and position in the flow.

### FAQ

<details>

<summary>How is DSP Dual End Card different from Dual End Card?</summary>

Dual End Card lets DT Exchange generate a second, DT-branded end card from the app bundle details in the bid. DSP Dual End Card lets a DSP supply both end cards using its own creatives.

</details>

<details>

<summary>What happens if I set <code>dspdualendcard</code> to <code>false</code> on a bid?</summary>

DT Exchange doesn't render DSP Dual End Card for that bid.

</details>

<details>

<summary>Can I use different creative types for the two end cards?</summary>

Yes. Each end card in the sequence can use a different supported creative type (Static, Iframe, HTML, or Playable).

</details>


---

# 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://docs.digitalturbine.com/dt-ads-demand/dt-exchange-openrtb-2.5-specs/dsp-dual-end-card.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.