Dear publishers, since our last platform update four weeks ago, our team has been hard at work on several new features. Today, we are ready to reveal a brand-new platform update that comes with some excellent improvements and bug fixes.
Here’s what the 6.2.0 update has in store for you!
Improved Prebidding Implementation
Great news for publishers — our dev team has streamlined our prebidding implementation!
Having analyzed our prebidding implementation, our team determined that an overhaul was in order. We wanted to simplify the process to make the feature more accessible to everyone.
The result is our new UI for adding Prebid.js bidders into the system. It will now be much easier to include your chosen bidders and maximize ad revenue with Brid.TV.
Another addition is our new JSON Editor suitable for any custom integrations you want to do.
Whether you’re a prebid beginner or veteran, you will find your way easily around this technology with this change.
Oracle MOAT Analytics Integration
The Brid.TV online video platform supports Oracle MOAT Analytics since update 6.1.5!
That means publishers can use this tool to supplement Brid.TV’s video and ad analytics and expand their advertising data set. On top of that, you can integrate the tool with the Brid.TV CMS!
For more on our Oracle MOAT Analytics integration, check out this article.
Full 6.2.0. Changelog
Here’s a complete list of changes that came with the 6.2.0. update:
New
- A huge overhaul of our prebidding implementation. We now sport a new UI for adding Prebid.js bidders into the system and a new JSON editor for all those custom integrations you want to do. We hope that we now have the optimal combination of features that both prebid beginners and advanced users need. Hop into the player edit screen and check out the new UI!
- Improved our YouTube fetch logic so that larger videos can now be ingested.
Added
- Added an option so you and your account (web player) can be fully GDPR compliant. We always liked to boast how our player does not use cookies in any way, and the only other hurdle to being fully GDPR compliant and not requiring consent was the fact that we would grab the GEO ISO code of a viewer and log this ISO code so you could show analytics by GEO. We now support any option, so you can DISABLE this on the site level so our player will not even track this. The main consequence of this is that you will not have access to any GEO analytics, so keep this in mind.
- Added multiple tag support to filters on your video lists. You can now use and combine multiple tags to get specific search results.
- Added support through our backend API so you can add custom GAM parameters to the edit video endpoint.
- Added an option to set max sizes for overlay display through Google IMA SDK.
Fixed
- Fixed a bug where carousel creation would fail if re-ordering was done with different slides.
- Prevented upscaling of video carousels for better video optimization and quality.
If you have any questions about these changes or need help with anything, let us know!
