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.
BidRequest.imp.video.ext
dspdualendcard
Indicates whether the inventory is eligible for DSP Dual End Card, based on the publisher's config and the SDK's supported version.
(true or false, lowercase; default: false)
Boolean
BidResponse.bid.ext.dspdualendcard
dspdualendcard
Allows the DSP to explicitly enable or disable DSP Dual End Card for this specific bid.
(true or false, lowercase; default: false)
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.
SKOverlay and Store Promo
DT Exchange does not display SKOverlay 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
Last updated

