Backend architecture

Videoplaza Monetizer is a typical ASP product. The app relies on a plugin, which is integrated via our plugin API into your video player and then loaded at runtime from our servers.

Through the plugin and it’s API, Monetizer is able to control how the ads will show up and when to show them. More on this on the implementation page.

The plugin communicates with our backend distributor to decide which ads to show when. The backend distributor is responsible for every decision of when to show an ad, and when not to.

In order to do this the distributor collects information from the campaign database as well as data from our backend tracker, which holds information on how every campaign is performing.

The plugin communicates directly with the tracker to log events as they happen when the user is interacting with the video player.

Trough this structure the distributor is capable of halting campaigns running ahead of schedule and speeding up campaigns running slow in real time.

To ease the pressure on our own servers we use an external CDN partner (currently Akamai) for delivery of the creatives to the end users. The ad material is uploaded to the CDN when the campaign is created in the backend (most often via the Campaign Manager interface).

The distributor then tells the plugin which ad to show when and where to find the actual files. The plugin handles all the loading by itself and fetches the correct files from the CDN network via HTTP or appropriate streaming protocol.