What is a Custom End Card?

A Custom End Card enriches your advertising campaign with a dynamic, added end card. Utilizing the app's bundle information obtained from the open RTB bid response, the PubNative HyBid SDK incorporates the app's name and icon, crafting an engaging and visually appealing final interaction point. This thoughtfully positioned feature provides a crucial, last-chance opportunity to captivate users and encourage app installations.

With Custom End Card, DSPs gain control over whether to display an automatically generated end card based on the app store assets, providing a final, compelling interaction point for users.

What are the benefits of Custom End Card

  • Enhanced Conversions: Capture user attention at the critical moment, leading to increased app installs and improved conversion rates
  • Optimized CPI (Cost-Per-Install): Achieve lower CPI by effectively engaging users and driving higher conversion rates
  • Easy Integration: Leverage the power of PubNative HyBid SDK to effortlessly incorporate a Custom End Card into your existing campaigns

Demo

Technical Implementation

Bid Request

Eligible inventory will be signaled in the bid request under BidRequest.imp.video.ext.

AttributeValuesDescription
customendcard0: false (default)
1: true
Indicates whether the inventory is eligible for the custom end card:

Example of Bid Request

"imp": { 
  "video": {
    "ext":{
      "customendcard": 1
    }
  }
}

Bid Response

DSPs can enable the Custom End Card feature by incorporating a specific extension field labeled"customendcard"in the BidResponse.seatbid.bid.ext object. This field accepts a Boolean value, either 1 (true) or 0 (false), which directs the PubNative Exchange SDK to either display or not display the Custom End Card.

AttributeValuesDescription
customendcard0: false (default)
1: true
Indicates whether HyBid SDK should render the custom end card

Example of Bid Response

"seatbid": [{ 
  "bid": [{
    "ext": {
      "customendcard": 1
    }
  }]
}]

Additional Information

  • PubNative exchange uses the BidResponse.seatbid.bid.bundle value to fetch app information from the Apple App Store and Google Play Store and generate the Custom End Card.
  • If you are a DSP and want to leverage this feature by default for all eligible traffic without signaling it in the bid response, reach out to your Pubnative account manager.