Publishers with Sovrn can license //Signal against their full demand stack – maximizing the value of each reader. The following steps have been outlined to help explain exactly what needs to be done for a successful implementation.
Step 1) Welcome, Next Steps, Expectation Setting
You should have already been in contact with someone from the Sovrn Publisher Growth team, and they will help you get the necessary documents signed.
This is where you’ll want to provide Sovrn with…
- key details about your ads that you wish to reload
- for example: only reloading ads on article pages and NOT on your homepage
- what (if any) ads you DO NOT want to reload
- for example: guaranteed inventory and direct deals
- any further customizations on your reload triggers
- any essential information on how frequently you want ads to reload
Sovrn will want the order IDs and line item information for any inventory that you do not want to reload.
Once this information is provided, we will begin to create your //Signal Licensing container.
Step 2) Enable API Access
If you want the //Signal reload only to be applied to certain items, we can apply exclusions based on Line Item Type, Order ID, or placement.
In order to provide in depth reporting, honor exclusions, and accurately bill you for //Signal, we require read-only API access to your Ad Manager account
Please refer to this article for more information on enabling API access for Sovrn.
Step 3) Set-up & Schedule Key Value Report
It’s always our goal to help publishers. To ensure we don’t hit any snags in the implementation of //Signal Licensing, we ask that you set up daily automated reports in Google Ad Manager.
If you can give us temporary admin access to your GAM account, our team will be able to set this up. That said, we’ve created two very simple guides that you can follow.
First, you’ll want to create your Key Value for the Sovrn reload in your Google Ad Manager account. You can find those instructions here. Sovrn will append this Key Value with each reload so that you’re able to distinguish between your initial impressions and the impressions created by //Signal.
Once your Sovrn key-value is created, you can setup the report. Find those instructions in this article.
Step 4) Receive //Connect Code
While you’re setting you your key-value reports, and enabling Sovrn with API access, our team will work on the creation of your //Signal Licensing container. This will be setup in Sovrn’s single delivery mechanism, //Connect.
You’ll be able to find this code in your account, however, our team will send it to you complete with instructions on how to successfully implement.
Step 5) Put //Connect Code on page
Many of our publishers test //Signal Licensing on a staging domain or test environment before going fully live. Be sure to let your Sovrn teams know how you plan on testing.
Make sure that you place the //Connect code on the page in one of the following ways:
- Adding code to all relevant pages by inserting the tag after the section of the page, ideally in the header.
- Trafficked as a creative via a vacant ad server ad slot (e.g. 1×1 or Out Of Page (OOP) slot)
For other installation instructions, please review this article.
Please make sure that you let the Sovrn team know when this has been added to your site.
Step 6) Confirmation that it’s working correctly from Publisher Advancement
It is essential that you share the details of your implementation with the Sovrn Publisher Advancement team. For example:
- are you currently testing on a staging domain?
- are you currently testing on a limited portion of your traffic?
Once confirming that the Sovrn container is correctly implemented, we will advise on if we are seeing a reload.
If you’re stuck in these steps, feel free to reach out to Sovrn Publisher Support and we will do our best to help out.