> 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/dual-end-card.md).

# Dual End Card

A Dual End Card is a personalized extension of the ad campaign that gives users a final opportunity to engage with it. The DT Exchange generates it from the bundle information from the open RTB bid, which includes the app name and icon.

DSPs can implement this feature and set the `dualendcard` attribute in the `BidResponse.seatbid.bid.ext`, which sends it for eligible traffic.

### BidRequest.imp.video.ext

| ATTRIBUTE     | DESCRIPTION                                                                                                                                             | TYPE    |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `dualendcard` | <p>Indicates whether the inventory is eligible for a Dual End Card.<br>(<code>1</code> = true, <code>0</code> = false; default: <code>1</code>)<br></p> | Integer |

### BidResponse.seatbid.bid.ext

| ATTRIBUTE     | DESCRIPTION                                                                                                                                | TYPE    |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------- |
| `dualendcard` | <p>Indicates whether DTX renders the Dual End Card.</p><p>(<code>1</code> = true, <code>0</code> = false; default: <code>1</code>)<br></p> | Integer |

### FAQ

<details>

<summary>How will DT Exchange know which store product to show?</summary>

To enable a Dual End Card, DSPs must provide the store listing ID of the app under the `BidResponse.seatbid.bid.bundle`.

</details>

<details>

<summary>In which cases will the Dual End Card be displayed?</summary>

DT Exchange displays the Dual End Card when the user does not click on an ad video or completion.

</details>

<details>

<summary>How are click tracking and destination handled?</summary>

DT Exchange uses `CompanionClickThrough` and `CompanionClickTracking` from the displayed creative end card to track clicks and destinations.

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