Partners

Double End Cards

Double end cards is an innovative ad experience on the Chartboost Exchange that increases user engagement and campaign performance, particularly with app installs. This format includes two end cards displayed after the main video ad.

Bid Request πŸ”—

Not all video impression opportunities on Chartboost will be eligible for double end cards.

In order to properly communicate these opportunities, Chartboost will send two arrays within BidRequest.imp.video.companionad to indicate that up to two endcards can be used. The BidRequest.imp.ext.cbec field with value 1 will also be sent in the bid requests to indicate whether the impression opportunity is eligible for a Chartboost end card.

The eligibility of an impression opportunity for double end cards is communicated by Chartboost through two key fields in the bid request:

Field Type Required Description
companionad Object array Yes Indicates whether or not the inventory is eligible for double end cards when two arrays are present.
companiontype Integer array No Supported VAST companion ad types.
Chartboost supports
  • 1: Static Resource
  • 2: HTML Resource
cbec Integer Yes Indicates whether or not the inventory is eligible for a Chartboost end card.
  • 1: Inventory is eligible for showing a Chartboost end card.
  • 0: Inventory is not eligible for showing a Chartboost end card.

When two companion ad arrays and cbec=1 are sent, the DSP has the option to serve double end cards with either:

  • Two companion ads received from the VAST file.
  • One companion ad received from the VAST file, and one Chartboost end card generated by Chartboost.

Bid Response πŸ”—

Field Type Required Description
bundle String Yes The unique market ID. This is a platform-specific application identifier intended to be unique to the app and independent of Chartboost Exchange.
  • On Android, this is a bundle or package name (for example, com.supercell.hayday).
  • On iOS, this is a numeric ID.
cbec Integer No Indicates whether or not to add a Chartboost end card after the video or after the playable end card.
  • 1: DSP allows Chartboost end card to be added.
  • 0: DSP does not allow Chartboost end card to be added.

To enable a Chartboost end card as the third or second ad, the BidResponse.seatbid.bid.bundle field is required. This field is used by Chartboost to render the proper assets (app icon and app name) within the static end card.

If the BidResponse.seatbid.bid.bundle field is not provided and cbec is set to 1, Chartboost will override cbec to 0, indicating that only two end cards will be used.

Chartboost End Card (cbec) πŸ”—

Control the Chartboost end card using the BidResponse.seatbid.bid.ext.cbec field and passing 0 (do not allow Chartboost end card to be added) or 1 (allow Chartboost end card to be added). This field is optional. However, if no value is passed, then it will default to 1, and the Chartboost end card will be rendered on eligible impression opportunities.