Equativ
Features
Bidder Code | equativ | Prebid.org Member | no |
---|---|---|---|
Prebid.js Adapter | yes | Prebid Server Adapter | yes |
Media Types | display | Multi Format Support | will-bid-on-one |
TCF-EU Support | yes | IAB GVL ID | 45 |
GPP Support | tcfeu, usp | DSA Support | yes |
USP/CCPA Support | yes | COPPA Support | yes |
Supply Chain Support | yes | Demand Chain Support | check with bidder |
Safeframes OK | yes | Supports Deals | no |
Floors Module Support | yes | First Party Data Support | no |
User IDs | all | ORTB Blocking Support | yes |
Privacy Sandbox | check with bidder | Prebid Server App Support | check with bidder |
Registration
The Equativ bidder adapter requires setup and approval from the Equativ service team. Please reach out to your account manager for more information to start using it.
Bid params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
networkId |
required | The network identifier you have been provided with. Normally required, but there are certain conditions under which this may be omitted. See Bid Parameter Usage notes below for more information. | 1234 |
integer |
siteId |
optional | The placement site ID. See Bid Parameter Usage notes below for more information. | 1234 |
integer |
pageId |
optional | The placement page ID. See Bid Parameter Usage notes below for more information. | 1234 |
integer |
formatId |
optional | The placement format ID. See Bid Parameter Usage notes below for more information. | 1234 |
integer |
Bid Parameter Usage
Different combinations of parameters are required depending upon which ones you choose to use.
There are two options for passing parameters:
- Option 1. Specify
networkId
by itself (and optionally providingsiteId
,pageId
andformatId
), or - Option 2. Specify either
ortb2.site.publisher.id
,ortb2.app.publisher.id
orortb2.dooh.publisher.id
See Sample Banner Setup for examples of these parameter options.
Supported Media Types
Type | Support |
---|---|
banner |
Supported |
video |
Not currently supported |
native |
Not currently supported |
User Syncing
To enable cookie syncing, make sure their configuration setup is properly invoked.
This involves adding an entry for setConfig()
that allows user syncing for iframes with 'equativ'
included as a bidder:
pbjs.setConfig({
userSync: {
filterSettings: {
iframe: {
bidders: ['equativ'],
},
},
},
});
And also making sure that storage is enabled for equativ
:
pbjs.bidderSettings = {
equativ: {
storageAllowed: true,
},
};
Configuration Example
Sample Banner Setup
As mentioned in the Bid Parameter Usage section, when including 'equativ'
as one of your available bidders your adunit setup, there are two approaches to how you can specify parameters. Below are examples that illustrate them.
Option 1 – Using networkId as a parameter
<script>
var adUnits = [
{
code: 'div-123',
mediaTypes: {
banner: {
sizes: [
[600, 500],
[300, 600],
],
},
},
bids: [
{
bidder: 'equativ',
params: {
networkId: 42, // REQUIRED
siteId: 142, // optional
pageId: 242, // optional
formatId: 342, // optional
},
},
],
},
];
pbjs.que.push(function () {
pbjs.addAdUnits(adUnits);
});
</script>
Option 2 - Using ortb2 for parameter info
You can also, as an alternative to using bidder params, specify a value for publisher.id
that may be nested under an app
, site
or dooh
object. The Equativ adapter will, in turn, look for these property paths under the ortb2
property of the request:
ortb2.app.publisher.id
ortb2.site.publisher.id
ortb2.dooh.publisher.id
Additional Resources
Information about how Equativ supports the oRTB specification, along with additional examples, can be found on our OpenRTB API support site.
"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_equativ |
hb_bidder_equativ |
hb_adid_equativ |
hb_size_equativ |
hb_source_equativ |
hb_format_equativ |
hb_cache_host_equati |
hb_cache_id_equativ |
hb_uuid_equativ |
hb_cache_path_equati |
hb_deal_equativ |