This section describes how to create a Cedato Demand item, which is type VAST.
The procedure for creating an RTB and a Prebid Demand item type is very similar and is also described below. The differences are indicated in each relevant section below.
CedatoX Demand items
This section is not relevant for CedatoX Demand items. You can see Configuring a CedatoX Demand Item for a description of how to configure a Demand item that was created by your CedatoX partner.
CedatoX Demand items are created by your CedatoX Supply partner as a Supply type item. They then automatically appear in your user interface as a Demand item of type CedatoX. CedatoX Demand items require you to turn them on and configure them before they become functional (for example, you must assign them to one of your Supply items).
To create a VAST type Demand item –
- In the left pane, select DEMAND ➔ MANAGE DEMAND to display a list of previously defined Demand items.
- Click the Create New button on the top right corner of the page. A page of settings is displayed –
To access all the settings simply scroll down the page or click on one of the options in the menu in the left pane, such as RESTRICTIONS.
Fill out the various sections of this page in order to define the Demand.
Mandatory fields appear with an asterisk (*).
Click Create to create the Demand.
Settings – Demand VAST
When you create a Demand by clicking the Create New button, by default it is a VAST Demand item type.
Note – If this Demand item was created by your CedatoX partner, its Demand item type is CedatoX. In this case, skip to see Configuring a CedatoX Demand Item.
Define the Settings (shown above), as follows –
- Demand Name* – Specify any free text unique name for this Demand.
- Demand type – Choose from the following- Vast/RTB/Prebid
- Demand Partner – Enter/select the name of your Demand item partner. If you already set a Demand item with this partner name, then it can be selected from the dropdown menu. For a CedatoX Demand item, the Demand partner is set automatically to the partner who created this connection and it cannot be changed.
- Active – By default, a Demand is active, meaning that it is available for use.
- Limited Assignment –The purpose of this feature is to have more control over sensitive demand items. By turning on the “Limited Assignment” toggle, the demand item will not be available for selection within the supply item’s edit page. Once the “Allow to assign Limited Assignment Demand” toggle is set to “On”:
The 'Limited Assignment Demand' items will become available for selection.
Once the demand item is set to Limited Assignment, it will be marked with an exclamation mark(!) on the top left side.
The toggle is always set to “off” by default.
Demand URL – Enter the URL of the VAST, and then replace the partner macros with Cedato platform macros. (Click View Available Macros to display a list of supported macros).
From this list, copy the relevant macros into the URL. Data will be passed through these macros.
- CPM – Specify the Cost Per Mille for impressions. This is the cost that the Demand pays for 1000 impressions.
- Environment* – In order to specify from which environments the Demand item can receive requests, select one or two of the relevant buttons – Desktop, Mobile App, Mobile Web or CTV.
Settings – Demand RTB
Deal id – The default value will be -1.
Only in case you have a deal id with your SSP, please enter the id instead of -1.
RTB partner –
1. Create an RTB Partner under MORE➔ MANAGE RTB PARTNERS here
2. Choose the relevant RTB partner you have created
You can easily navigate from an RTB demand item to its related RTB Partner (endpoint) by clicking on the icon, as shown below:
Floor CPM – Specify the minimum CPM that this Demand item must have to receive requests.
The rest of the settings are similar to Demand Vast item settings.
Settings – Prebid
Cedato supports client side prebid, which means that the auction code is placed on the publisher’s page and loads on the browser's header in real time.
Prebid partner – Choose the relevant Prebid partner from the drop down list. If your partner is not in the drop down list, please contact your customer success manager.
Configuration – You must enter the required parameters.
Prebid Configuration json – This field will update according to the configured parameters.
Floor CPM – Specify the minimum CPM that this Demand item must have in order to receive requests.
The rest of the settings are similar to Demand vast item settings.
In the Assigned Supply section, define the Supply items to which this Demand item is assigned by checking the relevant icon is in the Assigned column.
If no Supply items have been created yet, then go to Step 2, Creating Supply Items, and then come back to this step. Meanwhile, you can continue defining this Demand item according to the procedure below.
This list has the following tabs –
- VIEW ALL – This list shows all the active Supply items in Cedato.
- VIEW INELIGIBLE – This list only shows Supply items whose CPM cost is higher than the Demand CPM cost.
- VIEW ELIGIBLE – This list only shows Supply items whose Demand item CPM is higher than the Supply item’s CPM cost.
Ineligible (unprofitable) Supply items appear with red font as a kind of alert. This Supply item can still be selected, but you should know that it is not profitable. For example, as shown above – the Fixed Cost of 2.5 is displayed in red font. Fixed CPM Opportunity or Fixed CPM for impressions appear as the Fixed Cost.
This section enables you to specify the type of traffic from which to receive requests and to which to show ads, as follows –
Note ‒ If the targeting of a Demand item does not match any Opportunity, then this Demand item will never receive any requests.
- Country – The Demand item allowed/not allowed to receive requests from Opportunities arriving from the chosen countries (and these DMAs and/or states in case you choose US).
- Browser – The Demand item allowed/not allowed to receive requests from Opportunities arriving from these browsers (and these versions).
- Operating System – The Demand item allowed/not allowed to receive requests from Opportunities arriving from these operating systems (and these versions).
- Player Size – Enables you to target the size of the players. See Player Size Targeting.
- Day Parting- Enables you to target specific day/hours of the day when the demand item is eligible to receive requests.
VAST type Demand items have two additional Targeting options, as follows. Both these options require that you opt in to Cedato’s post-bid service.
In order to protect your Demand item from potential IVT and low Viewability, Cedato provides the option to send samples of your traffic to an external analysis tool in order to detect invalid traffic.
- Viewability Goal– Select this option to set the minimum Viewability rate of the traffic from which the Demand is allowed to receive requests. The Viewability Goal targeting decision is based on earlier collected and analyzed data.
- IVT Goal -This option enables you to set the maximum IVT rate of the traffic from which the Demand is allowed to receive requests. The IVT Goal targeting decision is based on earlier collected and analyzed data. To use our quality targeting options you must opt-in to our Post-Bid services with a minimum of 10% sampling rate. The following displays –
To opt in, click the Post-Bid button.
See Post-Bid for more information.
- VAST Requests Limit – Use the VAST Requests Limit By Scale (slider) to set the ad request rate – between 1 and 5. If you choose Min, then Cedato only sends a minimal amount of ad requests to this Demand item. If you choose Max, then Cedato sends as many ad requests as required to fill the Opportunity.
Use the VAST Requests Limit By Value in order to specify the maximum amount of Ad requests sent to a specific demand item.
The same setting exists on the Supply side. If the setting of the assigned Supply is different, then the actual VAST Requests Limit will be the lower of the two.
- In the Daily Impressions field, specify the maximum number of impressions per day. ASAP means that these impressions will occur as soon as possible each day.
- In the Daily Ad Requests field, specify the maximum number of requests that a Demand item will receive per day. This option does not exist for CedatoX Demand item types.
- In the IP Frequency field, specify the maximum number of impressions/ad requests coming from the same IP per hour/day. This option does not exist for CedatoX Demand item types.
This option enables you to pass/block requests from specific domains/app bundles/app names and/or to block requests from specific IPs.
Lists can be created to include or exclude domains, app names or app bundles. Other lists can be created to exclude IP addresses.
In the Select List Type dropdown menu, select a previously defined list or define a new list here. To do so, select the Whitelist or Blacklist option. Only one or the other can be selected – not both. You can start typing the name of the desired lists to see them in the dropdown menu. Alternatively, you can click the New List option to create a new list.
Note – Each Demand can be assigned up to 30 domain/app bundle/app name lists and up to 5 IP lists.
Callbacks can be defined for VAST,RTB,Prebid type Demand items.
A Callback URL enables you to configure the destination to which events associated with this Demand item are reported, such as your system or a 3rd-party system.
To define a Callback –
1. In the Callbacks section, click + Add Callback.
2. Enter the Callback URL.
3. This Callback URL is comprised of parameters and macros. These macros must be replaced with Cedato macros. Cedato macros pass correlating data during the associated event.
To display the list of available macros, click VIEW AVAILABLE MACROS. The following displays –
From this list, copy and replace the relevant macros into the URL.
From the dropdown menu, select the event that you would like to track and for which you want to receive a data for your 3rd-party platform –
Ad Start – Indicates an impression
Ad Complete - Indicates that the viewer has completed the ad.
Ad Click – Indicates that the viewer has click the ad.
You can define multiple Callbacks by clicking the +Add Callback option again, each to be triggered by a different event; and up to two Callbacks for each event type, as shown below