Creating a Walled Garden for a Leading OTT Video Publisher

Client Name :-  Tox Tv

Industry        :-  OTT

Location       :-  India

Zenver worked with a large OTT video-streaming publisher to design and implement its own AdTech stack. The following is a summary of our collaboration and the numerous development projects on which we collaborated.

Key points:

  • Our customer wanted to construct a walled garden and monetize their first-party data by building their own AdTech stack.
  • A self-serve ad platform, an ad server, a data lake, and a customer data platform made up the AdTech stack (CDP).
  • The project’s purpose was to replace our client’s existing third-party solutions so that they could have complete control and ownership of their AdTech stack.
    AWS, Python, Go, React, Terraform, Docker, TypeScript, Django, Bitbucket, and many other technologies were used to build the AdTech stack.
 

About the Project

Client's Need

  • Zenver worked with a large OTT video-streaming publisher to design and implement its own AdTech stack.
  • Our customer wanted to construct a walled garden and monetize their first-party data by building their own AdTech stack.
  • A self-serve ad platform, an ad server, a data lake, and a customer data platform are among the essential components in the AdTech stack that we planned and constructed (CDP).

What We Did

Self-Serve Platform

  • Designed and built the self-serve ad platform’s UI.
    Built the functionalities needed to create and manage ad campaigns, such as uploading creatives, creating line items, and setting up ad targeting.
  • Integrated with an external AdTech platform to execute and update the campaigns created in the self-serve ad platform.
    Integrated with a payment system to provide payment and billing-management functionalities.

Ad Server

  • Our team was responsible for delivering the ad serving platform that would be providing ads to our client’s videos.
  • The team designed and built the web SDK that would act as a layer between the ad slots and ad server.
  • Once the SDK was integrated with our client’s video player, it was able to send user IDs from the player to our ad server via an API call. Based on these IDs, we were able to pass them on to our client’s CDP for targeting purposes.

CDP and Data Lake

The purpose was to link the CDP to the ad server and self-serve ad platform so that advertisers could conduct targeted campaigns on our client’s OTT video-streaming platform.

The data lake was designed to retrieve information from a variety of sources, including:

  • Our client’s OTT video-streaming platform: data from our client’s content management system on movies, actors, and so on (CMS).
  • Event data regarding video views, watch time, sessions, as well as location, device type, and other forms of data, are collected by our client’s analytics platform.
  • Sources of external data: Third-party data was used to build interest-based audience groupings.
  • Our client’s data science team provided the following information: Machine learning and data analysis produce data.
  • Device Specifications: Price information for specific gadgets. This information was then linked to the analytics platform’s device-level data.

The Main Technologies and
Frameworks We Used

Are you planning to construct something similar?

Build Your Brand With Us