Ebuzzing Native Format

Published on

This post was reposted from BuzzPlayer.

Mobile advertising formats bringing unrivalled levels of user engagement and innovation to mobile whilst allowing publishers to monetise their premium content.

Ebuzzing have today announced that their family of rich media video advertising formats, already distributed on its global network of 40,000 web sites, are now available on the mobile web.

Ebuzzing have developed iOS and Android versions of its successful Captiview and We Spread formats.


Captiview Mobile is the world’s first mobile video wall

Allowing users to choose from a multi-choice video ad selector in order to gain access to premium content. This format, already implemented on an exclusive global network of Premium Media sites, will allow editors to monetise their mobile web traffic in a much better way than existing formats, which are mainly banners and basic interstitials.



We Spread Mobile rich media formats, including Engagement footer, Engagement Tab, Battle Tab, and E-Selector, will help the 20.000 media sites members of We Spread network to generate significant revenues for their mobile web audience.

Ebuzzing’s mobile lineup also includes the HTML5 video Buzz-player, which is widely used to distribute video ads within media properties and social networks. The Ebuzzing video player offers unique personalisation features, including geolocalisation, inclusion of interactive elements, or inclusion of an ecommerce site, within the video player.

Captiview Mobile


M-Tab, a revolutionary new rich media mobile video format

Ebuzzing have also today launched M-Tab, the most advanced rich media, and interactive mobile video advertising format on the market. The M-Tab takes mobile advertising to the next level allowing advertising to stand out from the webpage, taking on the form of a dynamic in-browser creative. Rather than vanishing into the content of a page, the ad can be moved around the screen by the user leading to increased user engagement with the brand.



Comment on this post