Utilizing the bundle information from the open RTB bid response in the DT Exchange SDK, a personalized extension of your ad campaign is presented, featuring an extra/dual-end card.
This involves retrieving the app's name, icon, and creating a final touchpoint to provide users with a last opportunity to engage and install.
DSPs will be able to enable dual-end cards using a custom extension field under BidResponse.seatbid.bid.ext, this field will also be called dualendcard.
BidRequest.imp.video.ext
Note
This field will only be sent for eligible traffic
| Attribute | Description | Type | Example |
|---|---|---|---|
| dualendcard | Indicates whether the inventory is eligible for Dual End Card 1 - true; 0 - false |
Int; default 1 |
“imp”: { “ext”:{ } } |
BidReqsponse.seatbid.bid.ext
| Attribute | Description | Type | Example |
|---|---|---|---|
| dualendcard | Indicates whether DTX should render the Dual End Card 1 - true; 0 - false |
Int; |
“seatbid”: [{ “dualendcard”: 1 } }] }] |
Both receive a binary value of either 1 or 0, defining whether the DT Exchange SDK should enable the DT Exchange SDK to show the Dual End Card.
FAQ
To enable Dual End Card, DSPs would have to provide the store listing ID of the app under BidResponse.seatbid.bid.bundle.