Back to Bidders
Rakuten
Features
| Bidder Code |
rakuten |
Prebid.org Member |
yes |
| Media Types |
display |
GDPR TCF Support |
no |
| User IDs |
none |
USP/CCPA Support |
no |
| Supply Chain Support |
no |
COPPA Support |
no |
| Demand Chain Support |
no |
GPP Support |
no |
| Supports Deals |
check with bidder |
Prebid.js Adapter |
yes |
| IAB GVL ID |
check with bidder |
Prebid Server Adapter |
no |
| Floors Module Support |
no |
First Party Data Support |
check with bidder |
| Multi Format Support |
check with bidder |
ORTB Blocking Support |
check with bidder |
| Safeframes OK |
check with bidder |
|
|
"Send All Bids" Ad Server Keys
These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_rakuten |
hb_bidder_rakuten |
hb_adid_rakuten |
hb_size_rakuten |
hb_source_rakuten |
hb_format_rakuten |
hb_cache_host_rakute |
hb_cache_id_rakuten |
hb_uuid_rakuten |
hb_cache_path_rakute |
hb_deal_rakuten |
|
Bid Params
| Name |
Scope |
Description |
Example |
Type |
adSpotId |
required |
The AdSpot ID |
1234 |
int |
Configuration
The Rakuten adapter allows the endpoint to be configured with the following configuration option.
pbjs.setConfig({
rdn: {
endpoint: "https://new-endpoint.rakuten.com"
}
});
If unspecified the adapter will fallback to the default endpoint.
Back to Bidders