Sovrn supports integrations with four ad servers: Publica (CTV), Springserve (CTV), Nimbus (App), and Prebid Server (Web, App, and CTV). The setup process differs depending on which ad server you're using.
These integrations require hands-on configuration support. Before getting started, make sure you're in contact with a Sovrn Solutions Engineer — they'll guide you through the setup end-to-end. The steps below outline what's needed from your side, including mandatory fields and where to create the necessary assets in the Sovrn Platform.
If you are utilizing a different server, please let your Sovrn rep know.
Publica, Springserve, and Nimbus
To integrate Sovrn with Publica, Springserve, or Nimbus, you'll need to provide your Sovrn Seller ID to your ad server's rep or add it directly in your ad server's UI. Your Seller ID is the numerical value found in your ads.txt entry — specifically the number in the lijit.com line of your ads.txt file:
lijit.com, 123456, DIRECT, fafdf38b16bf6b2b #SOVRN
In the example above, 123456 is the Seller ID. You can find your own Seller ID in the Sovrn Platform under Advertising > Ads.txt at platform.sovrn.com/advertising/ads-txt.
Mandatory fields for Publica, Springserve, and Nimbus:
-
Seller ID — your numerical Sovrn Lijit ID from your ads.txt entry
Prebid Server (Web, App, and CTV)
Prebid Server integrations follow the standard Prebid configuration using the Sovrn bid adapter. Full adapter documentation is available on the Sovrn Prebid adapter page on GitHub.
Before going live, you must provide Sovrn with your Prebid Server URL to ensure it has been whitelisted in Sovrn's system. Without this step, bid requests from your server will not be accepted. Reach out to your Sovrn Solutions Engineer or support to get your URL whitelisted.
Mandatory fields for Prebid Server:
-
tagid(required) — the unique numerical identifier for a Sovrn ad tag. You can create ad tags in the Sovrn Platform under Advertising > Ad Tags or by clicking here. Whiletagidis a required field, Sovrn does not currently report on tag ID in the platform, so there's no need to do a full tag mapping for reporting purposes. Sovrn recommends sending a singletagidfor now. Tag-level reporting will be available in a future update.
Optional fields:
-
bidfloor— the minimum acceptable bid in CPM (USD). Sovrn recommends leaving this unset, as Sovrn's flooring model uses buying behavior and publisher signals to drive CPMs. If you have your own flooring model, Sovrn can support it. -
adunitcode— a string identifier for the ad unit.
A basic Prebid Server configuration with Sovrn looks like this:
var adUnit = {\n code: 'div-ad-unit',\n mediaTypes: { banner: { sizes: [[300, 250]] } },\n bids: [{\n bidder: 'sovrn',\n params: {\n tagid: '315045'\n }\n }]\n}
Note: all bid params (tagid, bidfloor) are lowercase. Do not reuse the same tagid more than once within a single request.
To help improve fill rate and CPM for the Prebid Server auction: add the Sovrn beacon call to the <head> of your web page:
<script src="//ap.lijit.com/www/sovrn_beacon_standalone/sovrn_standalone_beacon.js?iid=12345678" id="sBeacon"></script>
Your Sovrn Solutions Engineer will provide your iid — it's unique to your Sovrn account. Replace 12345678 in the example above with your own iid.
Questions? Concerns? Our team would be more than happy to help. Reach out to our Support Team here.