The Demand Report is used to give the user a view of impressions and revenue through a time chart on the top of the page, and to give information on the table below with metrics that are from a demand POV, such as: requests, bids, wins, success rate, impressions, revenue etc’.
The Supply Report is used to give the user a view of impressions and revenue through a time chart on the top of the page, and to give information on the table below with metrics that are from a supply POV, such as: Opportunities, Fill Rate, revenue, cost etc’.
The Custom Report entity is used by our users to create any type of report they wish to generate with full flexibility. You are able to choose the time frame, as many metrics and dimensions as you will and if selecting “today” the data extracted is in real-time. The report can then be viewed online on our UI, or downloaded to your computer as a CSV file.
Supply Partner is the top level entity in the supply side hierarchy. It is a folder that gathers different traffic channels and players that belongs to the same supply entity so that you can pull reports pivoting by this dimensions. You can also create a platform login to your supply partners and they will only be exposed to the activity of traffic channels and players that are set under the same entity.
Traffic Channel is a sub-Supply Partner entity that is used to differentiate different traffic sources of the same Publisher (e.g a direct publisher with a couple of different video placements on different pages). This entity is connected to the traffic coming from the website in the one or both of the following:
- On V2V activity or if you work with a publisher that has a player integrated already, you will use the VPAID exported by the platform and send it over to your supply partner where he will implement it on the player running on the page or on his adserver.
- On syndication activity you will need to create a sub-Traffic Channel entity called Player (see below) and use it to export a JS code that will be implemented on the page.
This entity encapsulates different configurations (Look and feel, Size, etc’) and behaviors (auto-play, looping, muting, etc’) for a player that will be placed on a website or through difference platforms (mainly SSPs)
Demand Partner is the top level entity in the demand side hierarchy. Similar to the Supply Partner entity it is used to store different Ad Sources coming from the demand source (e.g tags of different rates of the same demand partner). This entity makes it easy for you to pull reports for ad sources of the same parent Demand Partner entity.
This entity encapsulates info about the ad source such as its rate, its URL, it’s targeting conditions and some additional configurations such as request caps and/or impression caps.
The Waterfall entity lets you connect between the demand and the supply on the system. You’ll be able to choose between different tiers for every ad-source in every waterfall. Please read how to connect between demand and supply for more information.
In this entity you will be able to upload videos and then connect them to any player that you create. The content can be clickable and can contain data such as category, thumbnail, etc’
In this entity you will be able to upload lists of domains that can be then targeted by ad-sources as white-lists or black-lists. The lists should be uploaded either by a CSV or TXT file and do not have a limit of rows, domains or size. Please make sure to upload the domains as 1 domain per row and not with any symbols (, / ;)
In this entity you will be able to create 3 different types of users.
- Super User – A user that has all privileges within your account. This user can edit or create any type of entity.
- Network User – Can edit or create all entities besides Users.
- Supply Partner – A user that is meant to let your supply partner login and see his revenue (your cost) according to different tags (traffic channels)