RevContent
Features
Bidder Code | revcontent | Prebid.org Member | no |
---|---|---|---|
Media Types | display, native | GDPR Support | no |
User IDs | none | COPPA Support | no |
"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_revcontent |
hb_bidder_revcontent |
hb_adid_revcontent |
hb_size_revcontent |
hb_source_revcontent |
hb_format_revcontent |
hb_cache_host_revcon |
hb_cache_id_revconte |
hb_uuid_revcontent |
"Deal ID" Ad Server Key
hb_deal_revcontent
Note
To use RevContent bidder, you need to have an existing RevContent account. To create a new account visit https://www.RevContent.com. If you are an existing user, contact the account rep for api access and information.
For prebid server, Revcontent only uses basic OpenRTB requests, so only the endpoint will need to be customized. Your request must contain either app.name
or site.domain
to be considered valid. Revcontent will provide you with a custom endpoint that will contain your account details that you will specify in your adapater configuration, and you must manually enable the adapter. For example, your pbs.yaml would contain the following:
adapters:
revcontent:
disabled: false
endpoint: https://trends.revcontent.com/rtb?apiKey=<api key here>&userId=<account user id here>
Prebid.js Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
apiKey |
required | API key. | '8a33sdfsdfdsfsdfssss544f8sdfsdfsdfd3b1c' |
string |
userId |
required | Account User ID | 69565 |
number |
widgetId |
recommended | Widget ID. | 599995 |
number |
domain |
recommended | Domain Name - Default referral hostname | 'test.com' |
string |
endpoint |
optional | Api Endpoint - Used for testing | 'trends.revcontent.com' |
string |
bidfloor |
optional | Bid Floor | 0.1 |
float |
template |
optional | Format of the display ad | '<a href="{clickUrl}">{title}</a>' |
string |