PixFuture Prebid Server Integration

PixFuture supports server-side bidding through Prebid Server (PBS). Publishers can integrate PixFuture using Prebid.js or send OpenRTB requests directly to the PixFuture Prebid Server.

Prebid.js Integration

If you are already using Prebid.js, add pixfuture to your server-to-server configuration:

pbjs.setConfig({
  s2sConfig: {
    bidders: ['pixfuture'],
    endpoint: 'https://pbs-dev.pixfuture.com/openrtb2/auction',
    syncEndpoint: 'https://sync.pixfuture.com/cookiesync',
    timeout: 1000
  }
});

PixFuture uses pix_id as the placement identifier. Add your PixFuture pix_id to the bidder parameters of each ad unit:

pbjs.addAdUnits([
  {
    code: 'div-gpt-ad-1',

    mediaTypes: {
      banner: {
        sizes: [
          [300, 250],
          [728, 90]
        ]
      }
    },

    bids: [
      {
        bidder: 'pixfuture',
        params: {
          pix_id: '62623'
        }
      }
    ]
  }
]);

The pix_id must be provided as a string.

Because pixfuture is included in s2sConfig.bidders, Prebid.js will route PixFuture bid requests through the PixFuture Prebid Server instead of executing the PixFuture bidder client-side.

Request Flow

Publisher Website
       |
       v
   Prebid.js
       |
       | POST /openrtb2/auction
       v
PixFuture Prebid Server
       |
       v
PixFuture Bidder
       |
       v
PixFuture Prebid Server
       |
       v
   Prebid.js
       |
       v
   Ad Server

Direct OpenRTB Integration

Publishers that do not use Prebid.js can send OpenRTB requests directly to the PixFuture Prebid Server.

Endpoint: https://pbs-dev.pixfuture.com/openrtb2/auction

The PixFuture pix_id must be passed as a string under imp.ext.prebid.bidder.pixfuture.

{
  "id": "req-1",
  "test": 1,
  "imp": [
    {
      "id": "banner-300x250",
      "banner": {
        "w": 300,
        "h": 250
      },
      "ext": {
        "prebid": {
          "bidder": {
            "pixfuture": {
              "pix_id": "62623"
            }
          }
        }
      }
    }
  ],
}

The site.publisher.id is the publisher identifier in the OpenRTB request and is separate from the PixFuture pix_id.

User Synchronization

For Prebid.js server-side integrations, use the following PixFuture cookie synchronization endpoint:

https://sync.pixfuture.com/cookiesync

Configure it as the syncEndpoint in your s2sConfig:

syncEndpoint: 'https://sync.pixfuture.com/cookiesync'

Configuration Reference

Existing PixFuture Client-Side Integration

If PixFuture is already configured in your Prebid.js ad units, you do not need to create a separate PixFuture bid configuration for server-side bidding.

Keep your existing pixfuture bidder configuration and add pixfuture to s2sConfig.bidders. Prebid.js will route PixFuture through the configured PixFuture Prebid Server.

pbjs.setConfig({
  s2sConfig: {
    bidders: ['pixfuture'],
    endpoint: 'https://pbs-dev.pixfuture.com/openrtb2/auction',
    syncEndpoint: 'https://sync.pixfuture.com/cookiesync',
    timeout: 1000
  }
});