Integration

of either a server-side ( SSAI ) or a client-side insertion ( CSAI ). SSAI implies integration and development at head-En where operator’s middleware has to be customized. In this case client devices work with existing, basic functionality without any changes of the firmware and the  operator’s head-end interacts with MostMedia platform on behalf of the client devices. CSAI focuses on devices’ firmware that should be made capable of communicating with MostMedia platform directly.

Ads Transcoding

Dynamically condition all creatives for HLS or MPD insertion accross all devices. The adverts are typically supplied as a single
Read More

Marking Advert Slots

we cooperate with TV channels to make commercial breaks be marked properly in feeds and assists operators and vendors in
Read More

Ads Exchanges

we arrange access to targeted content on different ad platforms like AsEx or AdFox etc.
Read More
Client Support

Contact our support team in the most comfortable way, i.e. a live chat, phone or email correspondence.

Individual Approach

For maximum efficiency of consultation, our professionals take an individual approach to each customer.

Project Management

Thorough planning of our daily activities allows us to achieve even the most challenging goals promptly.

Value Added

Using our services, you will learn how to earn without compromising the efficiency of outcomes.

Requirements

for integration

       Transcoders and packagers should be able to process SCTE 35 or DTMF triggers and generate ad insertion marks in m3u manifests (HLS) or MPD (MPEG DASH). If this feature is not is not supported, an API available can generate ad triggers

       Middleware or client device ( relevant either for CSAI or SSAI respectively ) should be capable of gathering required data as specified at ‘VAST-request format’ section

       Server’s or client device’s API as specified here could be capable of communicating with MostMedia VAST service

       Packager is capable of aligning HLS (or DASH) segments structure with ad break’s boundaries using ad triggers and break duration derived from VAST responses

  Establish either ad playout events available for tracking with ‘Tracking URLs’ or secondary events written by middleware substituting the tracking information confirming the playout of ads

      Media files delivery and transcoding modus