E-Planning SSP can be implemented through Prebid.js and compete as any source within it.
In order to proceed towards its implementation, E-Planning must be included into its Prebid.js version and configured accordingly.
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.
To obtain the ci value for your account, access the platform with your ID and then follow these steps:
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:
pbjs.que.push(function() { var adUnits = [ { code: 'div-gpt-ad-1438287399331-0', sizes: [ [300, 250], [300, 600] ], bids: [ { bidder: 'eplanning', params: { ci: '18f66' } } ] } ]; }); |
You can use the example described in the official docs as a guide.
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
This configuration can be modified to use the real names of each space within the platform. However, we strongly advise against its use unless it is necessary as the granularity of the created inventory may make its configuration something ambitious. Nonetheless, if you insist in its activation, you can do it through the optional ml parameter that must be added in the Prebid.js configuration.
You can find additional information on Prebid.js and E-Planning in Prebid.js. We recommend the following external links for further reference: