Back to Bidders

Equativ

Features

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

Bid Parameter Usage

Different combinations of parameters are required depending upon which ones you choose to use.

There are three options for passing bidder parameters:

• Option 1. Specify networkId by itself (without siteId, pageId and formatId), or
• Option 2. Specify siteId and pageId and formatId (all together) without networkId, or
• Option 3. Specify none of the above parameters, and instead use either ortb2.site.publisher.id, ortb2.app.publisher.id or ortb2.dooh.publisher.id

See Sample Banner Setup for examples of these parameter options.

Supported Media Types

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 three general approaches to how you can specify parameters. Below are examples that illustrate them.

Option 1 – Using networkId as the only bid param

<script>
  var adUnits = [
    {
      code: 'div-123',
      mediaTypes: {
        banner: {
          sizes: [
            [600, 500],
            [300, 600],
          ],
        },
      },
      bids: [
        {
          bidder: 'equativ',
          // siteId, pageId and formatId are NOT
          // required if networkId is provided instead
          params: {
            networkId: 42,
          },
        },
      ],
    },
  ];

  pbjs.que.push(function () {
    pbjs.addAdUnits(adUnits);
  });
</script>

Option 2 - Using siteId, pageId and formatId as bid params

<script>
  var adUnits = [
    {
      code: 'div-123',
      mediaTypes: {
        banner: {
          sizes: [
            [600, 500],
            [300, 600],
          ],
        },
      },
      bids: [
        {
          bidder: 'equativ',
          // all 3 of the below params are required
          // when used together in place of networkId
          params: {
            siteId: 1,
            pageId: 2,
            formatId: 3,
          },
        },
      ],
    },
  ];

  pbjs.que.push(function () {
    pbjs.addAdUnits(adUnits);
  });
</script>

Option 3 - 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

Back to Bidders