# Prebid Integration Overview

The Chartboost Prebid adapter is a
[Prebid Mobile](https://docs.prebid.org/prebid-mobile/prebid-mobile.html){:target="_blank"} **plugin adapter**. When
your Prebid Server auction returns a Chartboost-flagged winning bid, the adapter hands that bid to the Chartboost
Monetization SDK to render, instead of Prebid's default renderer. It is the same Monetization SDK that powers
Chartboost Mediation, plugged into a Prebid Mobile auction.

## Platform availability

| Platform | Status | Guide |
| -------- | ------ | ----- |
| Android  | Available | [Android Integration](/en/monetization/integrate/prebid/android/) |
| iOS      | Available | [iOS Integration](/en/monetization/integrate/prebid/ios/) |

## How rendering is routed

Prebid Mobile hands a winning bid to the Chartboost plugin adapter only when all of the following hold:

1. The bid carries `ext.prebid.targeting` with `hb_pb` and `hb_bidder`, so Prebid Mobile treats it as the auction winner.
2. `ext.prebid.meta.rendererName` matches the plugin name. On Android that is `Chartboost-Android-SDK`, and on iOS
   it is `Chartboost-iOS-SDK`.
3. `ext.prebid.meta.rendererVersion` matches the plugin's registered version, byte for byte.
4. The bid's format is one the plugin renders: banner, interstitial, or rewarded.

On a match, the plugin builds a Chartboost banner, interstitial, or rewarded ad, hands it the bid's markup, and
renders it. If any key does not match, Prebid Mobile silently falls back to its own default renderer.

<div class="alert alert-warning" role="alert">
  <b>Caution:</b> A mismatch on the renderer name or version does not raise an error. The bid simply renders through
  Prebid's default renderer instead of Chartboost. During integration, confirm the registered version matches your
  Prebid Server's stamp so you don't debug a silent fallback. The
  <a href="/en/monetization/integrate/prebid/android/#5-verify-the-integration">Android</a> and
  <a href="/en/monetization/integrate/prebid/ios/#5-verify-the-integration">iOS</a> guides show how.
</div>

## Prerequisites

- A Chartboost account and a registered app. See [Get Started](/en/monetization/get-started/).
- The Chartboost Monetization SDK in your app. See the Monetization SDK Get Started for
  [Android](/en/monetization/integrate/android/get-started/) or [iOS](/en/monetization/integrate/ios/get-started/).
- Prebid Mobile in your app, pointed at a Prebid Server endpoint.
- Your Prebid Server configured to return Chartboost as the renderer (name and version) for the bids you want
  Chartboost to render. Coordinate this server-side setup with your Chartboost account team.

## Supported ad formats

- Banner. Rendered at one of the Monetization SDK's own sizes: 320×50, 300×250, 728×90, or 300×600. The adapter fits a
  bid into the largest of those that fits inside it, so see Banner sizes for
  [Android](/en/monetization/integrate/prebid/android/#banner-sizes) or
  [iOS](/en/monetization/integrate/prebid/ios/#banner-sizes) before you configure ad units.
- Interstitial
- Rewarded

## Consent and privacy

The adapter forwards no consent signals of its own. GDPR, US Privacy (CCPA), COPPA, and GPP stay owned by the
Chartboost Monetization SDK, and its consent state applies to plugin-rendered ads. See Consent and privacy for
[Android](/en/monetization/integrate/prebid/android/#consent-and-privacy) or
[iOS](/en/monetization/integrate/prebid/ios/#consent-and-privacy).

## Next step

Continue to the [Android Integration guide](/en/monetization/integrate/prebid/android/) or the
[iOS Integration guide](/en/monetization/integrate/prebid/ios/).