DSP’s Double End Card

Overview

InMobi Exchange supports DSP Double End Card for video ads, allowing demand partners to supply their own second end card creative in the bid response. Two consecutive end cards are then displayed after the video ad completes or is skipped by the user.

This differs from InMobi's Double End Card (Default), where InMobi Exchange generates the second end card itself from the advertised app's store assets. With DSP Double End Card, the second card is fully controlled by the DSP — creative, messaging, and click destination, giving demand partners an additional branded surface to drive conversions.

How it works

The DSP Double End Card experience consists of the following sequence:

1. The video ad plays.
2. The first end card (DSP creative) is displayed.
3. The second end card (DSP creative) is displayed immediately after the first.

InMobi Exchange signals eligibility for a second end card by including a second companion slot in the bid request. If the DSP returns two <Companion> creatives within the <CompanionAds> node of its VAST response, both are rendered in sequence.

Fallback behaviour

If the DSP returns only one <Companion> creative on an eligible request, InMobi Exchange falls back to Double End Card (Default), provided the default experience is enabled for that request. For more information on the vxec signalling used by that flow, see InMobi's Double End Card (Default) page.

Bid Request

Eligibility for DSP Double End Card is signalled through the presence of a second companion object in imp[].video.companionad, each carrying a distinct id.

Parameters

Sample Bid Request

"companionad": [
  {
    "format": [ { "w": 360, "h": 640 }, { "w": 320, "h": 480 } ],
    "w": 360,
    "h": 640,
    "pos": 7,
    "api": [ 3, 5, 6, 7 ],
    "id": "1",
    "vcm": 1
  },
  {
    "format": [ { "w": 360, "h": 640 }, { "w": 320, "h": 480 } ],
    "w": 360,
    "h": 640,
    "pos": 7,
    "api": [ 3, 5, 6, 7 ],
    "id": "2",
    "vcm": 1
  }
]

Bid Response

To serve a DSP Double End Card, the DSP must return two <Companion> elements within the <CompanionAds> node of the VAST markup, each with its own id attribute.

Parameters

Sample Bid Response

<CompanionAds>
  <Companion id="endCard1" width="360" height="640">
    <HTMLResource>
      <![CDATA[ <!-- first end card markup --> ]]>
    </HTMLResource>
    <CompanionClickThrough>
      <![CDATA[ https://example.com/click/endcard1 ]]>
    </CompanionClickThrough>
    <CompanionClickTracking>
      <![CDATA[ https://example.com/track/endcard1 ]]>
    </CompanionClickTracking>
  </Companion>

  <Companion id="endCard2" width="360" height="640">
    <HTMLResource>
      <![CDATA[ <!-- second end card markup --> ]]>
    </HTMLResource>
    <CompanionClickThrough>
      <![CDATA[ https://example.com/click/endcard2 ]]>
    </CompanionClickThrough>
    <CompanionClickTracking>
      <![CDATA[ https://example.com/track/endcard2 ]]>
    </CompanionClickTracking>
  </Companion>
</CompanionAds>