Demand Partner Level
The Demand partner is the “parent’ account of the Demand tags called Ad Sources within our platform. Each Demand Partner can have many Ad Sources for different environments, Geo’s, different rates, etc.
Configurations available at the Demand Partner level:
Account Manager– the Account Manager that manages the Demand partner. This field is useful for reporting.
Labels – you can classify your Demand partners by their activity, tier or strategy based on your preference (for more information about Labels go to Optimization tips under Business logic and Optimization).
Required Macros– you can set the IFA and the Player size method as mandatory fields for your Demand partners. Meaning, in case your Publisher won’t deliver those specific macros- the Ad Sources of this Demand partner won’t receive any Requests coming from it.
*Please note- IFA refers only to InApp and CTV activity.
Targeting condition– you can apply Black/White list on the Demand partner level. You can also target specific Demand partners to receive traffic from specific Supply partners based on your preference.
Ad Source Level
Demand Partner– each Ad Source must be associated with a demand partner.
Environment – this is a mandatory field and it determines on which environment the ad itself will run. The options for environment are: Desktop, Mobile Web, Mobile App or CTV.
Rate– the CPM your Demand partner will pay for 1000 Impressions for this specific Ad Source.
Tag Type– this state in which format the tag’s response will be like- VAST / VPAID / IMA/ Hosted.
Tag URL– The tag’s URL that includes all the macros that should be passed to the Demand Partner (for the full list of available macros go to StreamRail macros under Let’s get started).
Prioritized Ad Source– by turning the toggle ‘on’, you can determine that this specific Ad Source will receive a tier of its own (regardless of its performance). That way, this Ad Source will receive a “Win” every time it responds with a Bid.
Labels– similar to the Demand partner level, you can also classify your Ad Source by its activity, tier or strategy based on your preference (for more information about Labels go to Optimization tips under Business logic and Optimization).
End Card– this section determines whether the player should present an End card at the end of the video (i.e Companion Ad from the VAST response). Close End card after X milliseconds determines how long the player should present the End card.
Delivery Policy – this section refers to the Ad Source capping. The capping is relevant for the following events: Ad Request, Ad Impression and Ad Completion.
Please note: capping will be applied according to UTC time zone.
Time & Date – set the time zone and flight time for each Ad Source (the Ad Source time zone is relevant for both flight dates and week parting). The flight dates combined with the Ad Source status will determine when the Ad Source will be eligible to run. The Week parting allows users to specify any combination of days of the week and hours of the day, that the Ad Source should be eligible to run. To use this feature the “Week Parting” should be enabled, any set of combination for days and hours based on your preference.
Targeting – contains many available targeting conditions (all can be either equal/ does not equal conditions) such as: Country, device, Traffic Channel, Player Size, OS etc.
Please note: Domain / Domain List (available for Ad Sources with Desktop / Mobile Web as environment) while Bundle ID / Bundle ID List (available for Ad Sources with Mobile App set as environment). Device (Tablet/Mobile- available for Ad Sources with Mobile App/ Mobile web set as environment)