E-Planning SSP can be implemented through Prebid Server and compete as any source within it.

Prebid Server allows to implement new sources with server-to-server connections, which are more efficient than those performed by Prebid.js. Furthermore, Prebid Server simplifies the implementation in AMP sites and mobile apps, both in iOS and Android.

Bear in mind that these instructions are meant to implement Prebid Server in traditional websites, both desktop and mobile.

To install Prebid Server in AMP sites, please refer to this document.

Content

Prebid.js and Prebid Server Download

Go to the Prebid official site and then to the Download section. You can also click here to be redirected automatically.
Select E-Planning and the sources you wish to implement.
Select the Prebid Server adapter.
Once you have selected, download your Prebid.js version and implement it in your site following the detailed instructions in the official docs.

Settings

Once you have installed your new Prebid.js version, you must configure the E-Planning adapter accordingly. The only parameter needed for implementation is ci, which has a unique value regardless of the site, space, or size where it is implemented.

How to Get the ci Parameter

To obtain the ci value for your account, access the platform with your ID and then follow these steps:

Click on Implementation
Click on the Implementation for display chart
Select Prebid
Copy the displayed value

Configuration in Prebid.js

Configure Prebid.js as stated in its official docs.

You must add the eplanning value within the bidders key defined in the s2sConfig object. Furthermore, you must plug the following code into each adUnit within the bids key. You must add your ci value. For example, if your ci value is 18f66:

var pbjs = pbjs || {};

pbjs.que = pbjs.que || [];

pbjs.que.push(function() {

    pbjs.setConfig({
        s2sConfig: {
            accountId: '1',
            enabled: true,
            bidders: ['eplanning'],
            timeout: 1000,
            adapter: 'prebidServer',
            endpoint: 'https://prebid.adnxs.com/pbs/v1/openrtb2/auction',
            syncEndpoint: 'https://prebid.adnxs.com/pbs/v1/cookie_sync'
        }
    });

    var adUnits = [{
        code: '/19968336/header-bid-tag-1',
        sizes: sizes,
        bids: [
			{
				bidder: 'eplanning',
				params: { ci: '18f66' }
			}
        ]
    }];
});

Video integration

You can send video traffic for both web and apps. To do so, declare for your ad unit the mediaType video. You can learn more about how to do this configuration in the official Prebid documentation: https://docs.prebid.org/prebid-video/video-overview.html

Note that the E-Planning bidder will return a VAST document in this case, so in Prebid.js you must set up a cache URL for video:

pbjs.setConfig({
    cache: {
        url: "https://prebid.adnxs.com/pbc/v1/cache"
    }
});

More information can be found in the following document: https://docs.prebid.org/prebid-server/features/pbs-caching.html

In-App integration

You can send mobile app traffic (both for iOS and Android) through a Prebid Server integration. No additional configuration is required beyond the ci value, however have in mind that the following values should be properly configured for your app in Prebid Server as those are required in the auction:

app.id
app.name
app.domain (developer domain for app-ads.txt validation)
app.bundle
device.ua
device.ip
device.ifa

Creation of the Inventory

The corresponding inventory is automatically generated in our platform. Once implementation has completed and E-Planning starts receiving traffic, you will find your sites and spaces within the platform. The platform automatically creates a space for each size received. Given this, if your site is example.com, you will get a taxonomy of this type:

example.com

300x250
728x90
160x600

For the site name, by default the top order domain will be taken. In other words, if your site is subdomain.example.com, it will be identified with example.com. If you want to use a sub-domain or a custom domain, set it up using the site.domain parameter in the request. You can set this value in your Prebid configuration or via a Stored Request.

Additional Docs

We recommend the following external links for further reference on Prebid Server:

Prebid Server Overview