Last month SmartHub released 10 April updates starting from new auction logic, Protected Media pre-bid integration, and ending with integration possibilities through VAST tags. This round of updates delivers a continuation of the features as now we’ve also added Protected Media post-bid protection, extended trading opportunities through the VAST player, new blacklist options, and many other useful enhancements. These 9 updates will not only make your system more protected and efficient but they will also extent possibilities of media trading with new integration protocols that support new traffic types. Intrigued? Let’s go ahead and unveil them.
Waterfall VAST player
We figured out it would be cool to implement the functionality that makes it possible to trade via VAST video player on demand side. Now media trading is happening right in the player which increases the chance that impression will be filled regardless of API framework supported by supply. The trading takes place in the publisher’s source player (VPAID). VPAID player contains several VAST creatives inside. It sorts out the tags according to the prices (arranged by descending order). If the VAST connection supports VPAID, VPAID player bids and runs waterfall inside supporting the technology stack.
CRIDS and Publisher IDs for a global blacklist
For now, you already can use such global blocklist options as domains, bundles, and apps. As practice proved, option “apps” didn’t prove to be used often so we removed it and added other ones that you’ve asked for - Creative IDs¸ Publisher IDs. Using these options you can automatically filter out publishers by their Creative IDs¸ Publisher IDs in order to avoid traffic from undesirable sources.
Use Protected Media post-bid and pre-bid with SmartyAds account
Good news, now the full-scale protection is available for both pre-bid and post-bid with SmartHub account. After you make a request, you will be able to use scanners with credentials of SmartyAds, no need to negotiate direct integration, just choose "use SmartHub account" and set the limit of scans. With Protected Media integration you will be able to monitor and inspect the health of your traffic on impression-level, preventing and eradicating ad fraud.
Interface for scanners and stats
We’ve created a single page where you can find all scanners and set up from here endpoints at the stage when you make connections. On this page, in the Statistics section, you will be able to find scan stats for all of those partners of yours who have these scans connected. Such navigation makes it easy to configure the scanning at each endpoint. You can also access comprehensive stats and activity per each type of scanner, and then juxtapose this data with separate scanner boards.
Change log and change notification
Keep every platform improvement or change by your side and within reach. Now we made it possible as we rolled out the function that reflects how your system is getting upgraded. Can’t remember what features we’ve added in the last release? Click on the graduation cap icon (knowledge base) inside of the dashboard. The latest updates will appear at the top block (with links to documentation and a short description). Plus, you can always enter the keyword in the search and find information on the feature you need.
Improve digital adaptor
You can improve settings in one place and independently adapt the endpoints to the DSPs that have individual demands and requirements. The purpose of such customization is to meet the requirements of Improve Digital DSP. For this, you’ll have to configure values like Partner ID, Exchange Pub ID, Exchange Tag ID, so the things you configure on Improve Digital end.
Bcat filter for SSP
Bcat filter can be turned on when you configure a new SSP endpoint. Such a filter is aimed to control responses and prevent replying to IAB categories indicated in the request. Turning the option on will mean that responses with IAB categories that are defined in the request (in Bcat array) will not be sent to such endpoint.
DSP filter “Only with IFA”
Now you can turn the new filter called ”Only with IFA” on the demand-side endpoint. IFA is a unique identifier given to the device. Enabled ”Only with IFA” filter means that this DSP automatically won’t be receiving requests without this identifier.
We hope that upgrades of May are those game-changing improvements that will strengthen your SmartHub platform capacities, extend your revenue opportunities, and make your marketplace ultimately profitable. We’ll keep enriching SmartHub with new functionality, yet we’ll simply the workflow in the future so that you could prioritize really important tasks over routines. As always, don’t forget about the button “suggest a feature” in the dashboard to request functionality implementation. We’ll gather your feedback, analyze it, and put the most relevant ideas on the development roadmap.
Remove all barriers, see how your SmartHub becomes stronger!
Roman Vrublivskyi, Business Development Manager of SmartHub