Glossary

Internal designation determining the nature of a Supply seat. Used for reporting purposes.

The count of 'SSP Requests' issued to Ad Pod Ad Units.

The preferred default Auction Type to be used when creating auction based ad sources (i.e. Auction Price & Open Auction). Note depending on the DSP this may be overridden by exchange logic. Selections include: - First Price Auction: Winning bidders will pay the price that they bid - Second Price Auction: Winning bidders will pay 1 cent higher than the next highest bid (or floor)

Users have the option to limit the maximum duration of any ad that wins auctions related to that Ad Source. These settings work in concert with the maximum-duration values configured in Ad Units rather than overriding them. Here at the Seat level, users may establish an optional default value to be used in Ad Sources.

Users have the option to limit the minimum duration of any ad that wins auctions related to that Ad Source. These settings work in concert with the minimum-duration values configured in Ad Units rather than overriding them. Here at the Seat level, users may establish an optional default value to be used in Ad Sources.

The auction type of the 'Ad Source' (e.g. IOA, UFR, AG).

Internal control to restrict the number of instances of each Ad Source Type the publisher is allowed to have active in a waterfall. Typically applied for Open Auctions and Marketplaces to limit duplication.

The Ad System as provided in the VAST Response

The Ad Title as provided in the VAST Repsonse

Additional ad-hoc Advertiser Domains that will be used in this rule, adding to any aDomains declared via Reusable Advertiser Domain Lists. Note: these will be Blocked or Allowed depending on the Advanced Brand Safety Rule type.

Permissions determine the users or groups that have access to a given entity, and the level of access they have.

Advertiser Domain

The domain responsible for an individual Fill (and subsequent metrics). Often referred to as "aDomain."

The aDomain Frequency Capping option lets you ensure that an advertiser who just served an ad will have to wait a specified period of time before it is eligible to win an impression again. This feature is particularly useful when requesting ads multiple times within an ad break.

This feature allows a publisher to ONLY run ads from Advertisers that they have created via Controls > Classifications > Advertisers. Any Advertiser Domains not curated into an Advertiser will be rejected automatically. Once enabled at Seat level, it can then be actioned per Brand level entity.

Internal opt-in for beta Alerts program.

Adds a custom extension to VAST responses, indicating the Ad Source Type that won the auction. Presented as , where: - 2 = Fixed Price - 3 = Auction Price - 4 = Open Auction - 6 = Programmatic Guaranteed

Adds a custom extension to VAST responses, indicating the winning Advertiser Domain. Presented as winningadomain.com

Advanced UD feature, used when a publisher wants to track programmatic injected ads back in the ad server. In the case of GAM, the publisher will need to ensure a fallback Magnite CTV tag is always returned in a fallback position for each ad. When an ad replacement occurs, we will grab the Impression tracker from the fallback position and use it in the primary position. This setting ensures we'll only inject a programmatic ad if there is a Fallback impression tracker availblable that we can use in the External Ad Server ad response.

Adds a custom extension to VAST responses, indicating the winning Advertiser code, as mapped in Controls > Classifications. Presented as 1234

Adds a custom extension to VAST responses, indicating the Creative ID of the winning ad as provided by the DSP. Presented as 1234

Creative Block Mode permits a Seat adminstrator to establish how the inventory hierarchy node will treat Creative IDs (CRIDs) that have been updated to include a review status (e.g. "Approved" or "Rejected"). A value of "Off" indicates that seller will permit any CRID to win auctions so long as other methods of blocking (e.g. aDomain) don't prevent a bid with that CRID from winning. A vlue of "Block" will prevent CRIDs with the "Rejected" status from winning Auctions. A value of "Allow" will permit only CRIDs with an "Approved" status to win auctions. A value of "Inherited" will indicate that given inventory hierarchy node is relying on the value established by its parent entity. This setting can be configured at the Seat, Publisher or Brand level.

Adds a custom extension to VAST responses, indicating the name of the winning DSP. Presented as thetradedesk

Internal opt-in for TheTradeDesk Forward Market deal trial.

Allows Deal CPMs greater than the default max of $1000. This is useful for scenarios such as DOOH, or other edge cases where very high CPM values are required. When enabled, will allow CPMs up to $25,000.

Adds a custom extension to VAST responses, indicating IAB Category associated with the winning ad. Presented as

Internal toggle to enable OR targeting mode on a Seat.

Control setting for allowing to share publisher seat take-rate with buyers (agencies/brands)

Internal toggle to enable VAST Unwrapping functionality in this seat. Once enabled, Ad Units will have the option to force unwrapping on all VAST responses.

Selecting Yes indicates that this supply will accept VAST Wrappers. A VAST wrapper is a VAST XML response that contains a URI to a VAST ad, hosted at a different location.

Defines which sensitive fields are allowed to be returned via fmt=json type Ad Requests for this Seat. The amount of data shared in these responses should be limited unless fully necessary.

The number of instances ads using specific API types (e.g. VPAID) were supplied in sampled winning ads.

The asset API framework (if applicable) as declared in the VAST response.

The App Bundle ID associated with the inbound ad request. Ladles will be captured for this App Bundle (e.g. "com.myapp.appletv")

The type of App Bundle filtering being applied on this Seat. Block mode will rejected listed app bundles, while Allow mode will only accepted listed bundles. Note: App Bundle filters only apply to "app/ctv" type supply.

The list(s) of App Bundles used by the App Bundle Filter mode on this Seat. These are defined via Platform Admin.

The name of the Application, as shown in the corresponding App Store. Note: This is fetched and validated automatically when using defined app stores (such as Apple App Store, Google Play, Roku etc). Simply select the App Store and enter a valid App Bundle for that store. When using the "Other" App Store option, this value will need to be manually entered.

The name of the App Store that offers this application. Note: when selecting the "Other" option, all details will need to be filled in manually. If selecting one of the supported App Stores, the platform will automatically populate the correct values by searching for the App Bundle provided on the nominated store.

By default, the ASAP pacing settings will continue to deliver fills & impressions until the desired impression goal has been reached, with no throttling applied. This can be problematic for volatile supply that has long wait times, where many fills may be released, and come in much later. The ASAP Feathering option adds some "shaping" to delivery, so as the item approaches it's impression goal, the system will throttle delivery to help account for volatility. Once enabled at the Seat level, any item using ASAP pacing will start applying ASAP Feathering logic.

The detected bitrate of the audio component of the supplied video asset.

The detected number of audio channels in the supplied video asset.

The list of Marketplaces that are allowed to run within this seat. Marketplaces are entities that have additional demand behind them (with their own set of PMP deals).

The average time taken to process requests that result in a winning ad, measured in milliseconds.

Internal billing code that identifies this publisher in reports. Generally associated with a Saleforce PD number. Note: a default billing code can be set at the Seat level, and will be automatically inherited at the Publisher level, but can be overridden per Publisher.

The detected bitrate of the supplied video asset or the asset bitrate as declared in the VAST response.

The Blocked aDomain Lists allows you to append lists of blocked Advertiser Domains against this inventory object. This is useful for static/bulk lists of Advertiser Domains that are frequently blocked.

A list of individual advertiser domains that are to be blocked from running against this particular object. Blocked aDomains are inherited from parent levels in the inventory hierarchy (e.g. Supply, Brand, Publisher or Seat).

Types of creative attributes that are blocked from running on this Ad Unit. The selected attributes will be communicated to DSPs in the bid request, informing them that they should not provide creative that contains any of these attributes. The ability to block these attributes is entirely dependent upon the self-identification of these attributes in the ad response, as delivered by the DSP.

The Blocked Buyer Seat List settings allows you to nominate which buyer seats will be blocked from participating in auctions across your seat.

IAB Categories to be blocked for all supply underneath this Brand. The IAB Categories selected here will be sent on bid requests to buyers to indicate that they should not bid with advertisers that belong to the selected categories. When buyers provide IAB Category information in their bid response, the platform will enforce these blocks.

Select Allowed to indicate that letter boxing of 4:3 content is allowed to play in a 16:9 player.

The Bundle ID is the specific application bundle (or package name) that includes this mobile application. This value acts a unique identifier for this application across multiple exchanges. Note: If you have selected Other, you will need to enter both the App Store Name and optionally enter a Store URL (if available) manually.

The domain that represents this Seat as a business. This value is used in industry transparency initiatives (e.g. Sellers.json), and should only be changed when neccessary.

This feature enables certain controls specific to the Australian Broadcaster market, including support for OzTAM identifiers and OzTAM demographics.

"Calculon Use Rate Override" permits the Seat administration to set their own (rather than system default) Use Rate threshold at which Calculon will begin throttling the ability for a given aDomain to win auctions. "Upper Calculon Use Rate Override" permits the Seat Administrator to se their own (rather than system default) Use Rate threshold at which a given aDomain will cease to be throttled (leveraging Calculon's rapid self-healing mechanism). These settings can be applied at any node in a Seat's inventory hierarchy.

The IAB Categories to be associated with this supply. This information is sent on bid requests to buyers to help them better understand the context of the supply.

Enables Channel type hierarchy objects. Channels are "flattened" hierarhcy objects that can sit at the Publisher or Brand level, and are capable of handling both App and Site type supply within the single entity. They are fully dynamic with regards to Supply Domain & App Bundle/Store information, requiring publishers to pass information correctly at request time.

Enables click tracking for the Seat. When click tracking is permitted, only clicks from the 'Personal Computer,' 'Phone' and 'Tablet' Platform Families are collected.

Identifies the type of entity this Seat is for. SSP Client is for Publisher clients, creating a standard Publisher style seat. Network Client is used to manage DSP Partners. Both creates a seat that is capable of both roles, typically only used for testing scenarios.

The internal code to represent this object - unique across the platform. These will be automatically generated when the entity is created, but can be edited by Admin users. Editing should be done carefully as codes are used throughout Ad Request processing.

Indicates if the Code should be automatically generated, or if a Custom code will be used during creation.

Competitive Separation allows you to set rules to prevent ads from one or more IAB Categories/Industries from running within the same Ad Pod. For example, you may wish to run no more than one Automotive ad, and one Travel ad within a single Ad Pod. Competitve Separation rules use Competitive Separation Groups to define which categories to separate.

Competitive Separation Mode allows you to define what type of groups you want to use to enforce Competitive Separation rules. There are two options available: IAB Categories: The standard IAB Catgories, which are powered by Magnite's internal mapping of Advertiser Domain > IAB Category. Industries: Industries are customized lists of Advertisers that are controlled by the user. These are defined within Controls > Classifications

In cases where it is not possible to define the Content Metadata "Channel" field via standard Content Metadata passing methods (e.g. ingestion or tag paramters), it can be defined statically on the Ad Unit instead.

Enables Content Metadata ingestion options for the seat, including tag/request based ingestion and MRSS based ingestion. Configure these settings in the Seat > Integrations section once enabled.

By default, Content Metadata requires a unique ID (videoId) per entry. Content Metadata Keys assists where a publisher cannot provide unique Video IDs, but can consistently provide other Content Metadata fields (e.g. Series, Genre, Rating). Simply select the fields that the publisher can consistently pass, and the platform will synthesize a videoId per unqiue combination of values for the selected fields.

In cases where it is not possible to define the Content Metadata "Network" field via standard Content Metadata passing methods (e.g. ingestion or tag paramters), it can be defined statically on the Ad Unit instead.

A Yes selection indicates that this site adheres to the COPPA regulations, as established by the USA FTC. Select Yes if this supply is directed to children under 13 years of age, and select No in all other instances.

The country of the originating ad request.

Used to target specific Ad Serving feature Creatives.

Used to target specific Ad Serving feature Creatives.

The rate at which creative is sampled for use in Creative Review.

The currency used to convert revenue fields in the tables in Inventory Health.

Custom Pixels provide the ability to attach one or more 3rd party pixels to this inventory object. Select from pre-defined Custom Pixels. Note: New Custom Pixels can be defined in the Controls panel, via the Custom Pixels tab.

The date & time when this object was created.

The date & time when this object was created.

A Deal ID associated with the Bid Request. If selected, Ladles will be captured where this Deal ID was involved.

Internal billing code that identifies this publisher in reports. Generally associated with a Saleforce PD number. Note: a default billing code can be set at the Seat level, and will be automatically inherited at the Publisher level, but can be overridden per Publisher.

The amount of time after the return of an ad (i.e. a Fill) that the system will wait for the Impression event to come in.

The asset delivery type as declared in the VAST response.

The supported delivery methods for video ad assets. The most commonly used delivery method for video ad assets is Progressive. Streaming delivery may be used in the case of a live stream (e.g. sports event, or live broadcast). Download is more commonly associated with offline viewing.

A DSP associated with the Bid Request. If selected, Ladles will be captured where this DSP was called.

Description is a free text field; useful for maintaining notes & additional information about this object. This field is only available within the UI.

Toggle to enable the ability for a Seat to create AAT (Advanced Audience Targeting) DMP instances. Once enabled, new DMP instances can be created via Integrations > DMPs

The Supply Domain should accurately indicate the site associated with the Supply. Note: Only enter the domain, omitting "http://" and any path information after the domain (e.g. "publishersite.com", not "http://publishersite.com/page1")

Enables the winning ad price to be declared in VAST responses. Uses the standard Pricing field for VAST versions 3.x or greater. For VAST 2.x, it will be placed in an extension.

The list of data management platforms (DMPs) that are approved to work with this seat.

The allowed External Code Namespaces for this Seat. External Code Namespaces determine which inbound integration types are supported for the Seat, and consequently which options can have routing rules associated with them in the Integrations > SSP Connect configuration page.

The VAST Error code reported by the Publisher.

The number of instances of the VAST Error was recorded in the past 24 hours.

Once report data has populated, this field can be used to look at what potetntial revenue may have been at different floor settings.

The amount of time after the return of an ad (i.e. a Fill) that the system will wait for the Impression event to come in.

Used to populate the Comment field in the public sellers.json file.

External Data Streams are customized logging streams made available for different purposes, though for a seat's data to be made available within an External Data Stream, it needs to be authorized here.

The External Name represents the Supply Name value that is sent in Bid Requests to buyers. This field will default to using the name of this Supply element, though it can be overridden. The value entered here should accurately describe the name of the inventory being offered.

This is a legacy setting for Publisher that had a Fill Guaranteed contract. Should be left unchecked, unless explicity directed.

This setting determines how the Ad Pod will be constructed on the server. Available options include: Fill Optimized: This mode will process each slot in the pod sequentially, informing DSPs of which advertisers have already won previous slots in the pod, allowing them to return more unique demand. This can be slightly slower than Speed Optimized mode. Speed Optimized: This mode will process each slot in the pod in parallel. Once winning ads are found for each slot, de-duplication and competitive separation rules will be applied - which may result in one or more ads being rejected. While faster, this can result in lower fill than the Fill Optimized mode.

How often an 'Ad Opportunity' results in a 'Fill.'

Count of responses to the publisher that contain an ad for display.

A Floor describes the lowest amount of money the Publisher is willing to accept to display an ad. It is expressed in CPM, which is Cost Per Thousand views.

The desired floor (CPM) to use for this supply.

The detected format of the supplied video asset.

The detected framerate of the supplied video asset.

Internal setting to activate fraud detection on this Seat. Unless otherwise directed, this should always be on.

Global Labels are internal only labels that can be applied to supply, and used for internal reporting and targeting purposes within Marketplaces. These are not visible to external users. NICK TO CONFIRM

This field relates to the Google CPS proprietary GDPR consent framework. Setting this field indicates that the publisher has contractually agreed for Magnite to pass valid user consent for Google as a vendor to the Google DV 360 bidder, in addition to all other vendors for which the user has consented and that information has been received by Magnite in the incoming ad request.

Total 'Revenue' collected by Magnite CTV that is relevant to the payout to the seller.

The User Group to apply permissions to. These are managed in Platform Admin > User Groups

The detected height in pixels of the supplied video asset or the asset height as declared in the VAST response.

Sets the default for whether Direct Sold lines should honor supply floors. The Honor Supply Floor setting determines if Line items should always honor the floor set for the supply. This setting only applies to Direct Sold lines via the Ad Serving component of the platform.

Seat level enablement for Liveramp RampID enablement. Enabling this begins a pixeling process with Liveramp on CTV inventory inorder to build a mapping file to support matching CTVIDs to RampID utilizing Liveramp's Sidecar.

The Mode used to decide the IFA Type associated with this Supply. There are two options available: Automatically Detect and Specify.

Count of the displays of the ads

Floors set on Inventory Hierarchy will, by default, be inherited by child elements underneath them in the hiearchy. If an element is inheriting a Floor from a parent element, the Inherited From and Source fields will identify where in the hierarhcy the floor is being inherited from.

Floors set on Inventory Hierarchy will, by default, be inherited by child elements underneath them in the hiearchy. If an element is inheriting a Floor from a parent element, the Inherited From and Source fields will identify where in the hierarhcy the floor is being inherited from.

Interstitial ads are interactive, full-screen ads that cover the interface of their host app or site. These ads appear between content, so they place at natural transition points or breaks, such as in between activities or game levels.

Inventory is the collection of Ad Units that are created by a Publisher and are intended for sale to Buyers. Each Ad Unit identifies a place where an ad can be displayed.

Inventory Hierarchy describes the relationship between the Publisher and the Ad Unit. There are five levels to the Inventory Hierarchy. These levels, in order from highest to lowest level, are Seat, Publisher, Brand, Supply and Ad Unit.

Inventory Partner Domain is a component of ads.txt/app-ads.txt. It is primarily used in scenarios where content owners have rights to monetize ad inventory within an vMVPD parter owned application.

Indicates if this Seat is configured to be a Demand (DSP) Seat. Derived from the Seat > Client Type field.

Indicates if this Seat is configured to be a Supply Seat. Derived from the Seat > Client Type field.

Labels are used to "tag" Supply using pre-defined key/value pairs. This allows for convenient grouping of similar elements of supply across the Inventory Hierarchy for the purpose of Targeting or Reporting. Labels are managed via Controls > Classifications > Labels

A list of keywords assicated with the Site or Application represented by this Supply. Any keywords supplied here will be presented in bid requests to DSPs.

A diagnostic tool that can be accessed in Magnite Streaming or MCTV. A Ladle will show both a bid and a bid response, allowing you to troubleshoot underperforming inventory or creatives.

A name for the Ladle for presentation in the platform.

The date & time (in UTC) when this object was last indexed. This indicates when the object was last propagated to the ad decisioning servers.

The date & time when this object was last updated.

Used to target specifc Ad Serving feature line items. For Internal Use: Also used to target specific DSP line items.

The traditional form of TV, which is programmed and watched as scheduled through satellite or cable, and is not streamed to a specific user on demand.

Defines the linearity of video Ad Unit. Defaults to Linear/In-stream.

A Yes indicates that the content is broadcasting using a live feed and a No indicates that this content was prerecorded. This information is passed on in the bid request.

Live Stream Accelaration (or LSA) is an advanced feature for handling supply that sends traffic in burst-like per ad break patterns, typically associated with live events.

The detected loudness of the video asset, represented in LUFS. Color coded to indicate Low, Moderate or Loud levels.

"Calculon Use Rate Override" permits the Seat administration to set their own (rather than system default) Use Rate threshold at which Calculon will begin throttling the ability for a given aDomain to win auctions.

Enables IFA/Device ID masking across alll bid requests being generated from this Seat. Note that this applies to all Inventory and Ad Sources, thus should only be used when "always-on" masking is required. Alternatively, if selective IFA masking is required, this can be enabled per DSP at the Inventory > Supply level, or more granularly on Ad Sources via Transparency controls. NICK TO CONFIRM

Enables IFA/Device ID masking for selected Demand Partners (DSPs) across this supply. This will be always-on for the nominated DSPs when enabled. Alternatively, if more selective IFA masking is required, this can be enabled Ad Sources via Transparency controls.

This feature limits how many requests will be accepted from a unique user within 1 minute. This only applies to supply that supports cookies.

Determines the maximum number of times a single Advertiser can appear across a Playlist request.

Defines the maximum number of ads within an Ad Pod. Either Max Pod Seconds or Max Ads Per Pod must be defined.

The maximum allowed bitrate for a video ad asset, in Kilobits per second (Kbps)

This field signals to the DSPs the maximum length in number of seconds that creative returned must be for this ad unit.

Maximum extended video ad duration. Primarly used to indicate whether interactive creative units are allowed to run beyond the Max Duration time, based on user interaction.

The maximum length of an Ad Pod in seconds. Either Max Pod Seconds or Max Ads Per Pod must be defined.

The distribution & count media file bitrates observed in sampled winning VAST documents.

The distribution & count of Content Types (MP4, WebM, JavaScript etc) observed in sampled winning VAST documents.

The distribution of the number of MediaFile assets provided per Creative, observed in sampled winning VAST documents.

The distribution & count of Durations observed in sampled winning VAST documents.

UD Mediation is a header bidding style. UD integration caches and generates targeting strings for winning ads.

The list of demand MIME types supported for this ad unit. At a minimum, video/mp4 should be selected, as the most widely available and compatible format.

The minimum allowed bitrate for a video ad asset, in Kilobits per second (Kbps)

This field signals to the DSPs the minimum length in number of seconds that creative returned must be for this ad unit. The default value is 0; this is the recommended setting for this field.

Internal toggle to enable Moka, our traffic shaping technology. On is the default setting, and should be left as is unless otherwise directed.

Select the Multiplicity mode associated with this Ad Unit. There are three modes available: Single, Pod Configure and Playlist.

The name of this object or the name of the Internal Contact. This value will used for UI display purposes and is typically available in reporting.

Total post-margin 'Cost' paid out to the seller.

The DSP associated with the VAST error.

Enter Yes if this supply should return cookie sync pixels when there isn't an ad returned. Publishers who make server-side calls could misinterpret those cookie sync pixels as ad wrappers.

Used to target specific Ad Serving feature Orders.

The Paid Type settings indicate if this application is offered at a price or for free.

Custom Pixels provide the ability to attach one or more 3rd party pixels to this inventory object. Select from pre-defined Custom Pixels.

The Placement represents how the video ad is being inserted into the page or app environment. Available options include: In-Stream, In-Banner, In-Article, In-Feed, or Interstital/Sliding/Floating.

The end user equipment that generated a request at coarse granularity. Example values include: "Connected TV," "Set Top Box" and "Games Console."

The Playlist Defintion Mode indictes how the rules to create a playlist are determined.

The count of 'SSP Requests' issued to Playlist Ad Units.

When using a time defined Ad Pod, the Pod Enforcement setting will determine if the pod can run over the allotted time.

The count of individual ad opportunities generated by 'SSP Requests' sent to Ad Pod or Playlist Ad Units. For non-Pod and non-Playlist supply, this count will be equal to 'Requests.' Also known as "Pod Slots."

The Pricing Model associated with this fee, either a Fixed CPM or a Revenue Share

Specifies whether this site or application has a privacy policy available for users to read. A Yes indicates that this supply does offer a privacy policy.

Enables Ad Server functionality for the Seat. Once enabled will appear as a new tab: Ad Serving.

The name of the Publisher within the Inventory Hiearchy. Available in reporting and targeting interfaces.

Use this field to set a limit on the number of queries-per-second that this SSP will process, for each data centre supported by the platform.

A raw sample of tag paramters that were passed to the platform as part of an Ad Request

The Magnite Streaming data center handling the request, or the regional market where this demand partner is active. Options include USA, UK, APAC, Brazil, and Germany.

The number of requests that were not processed by the platform due to reasons related to supply quality, excessive qps or performance. NICK TO CONFIRM

The total number of valid inbound requests made to a supply Seat.

The Reusable Advertiser Domains option allows you to apply a pre-defined list of Advertiser Domains to this rule, rather than entering them individually in the Additional Advertiser Domains field.

Labels are used to "tag" Supply using pre-defined key/value pairs. This allows for convenient grouping of similar elements of supply across the Inventory Hierarchy for the purpose of Targeting or Reporting. Labels are managed via Controls > Classifications > Labels

Pre-filter Labels are special types of labels that will restrict demand against this Supply. When applied, only Ad Sources that have been tagged with the corresponding Label key & value will be eligible to run against this Supply.

The VAST Ad Tag for this Ad Unit or Channel. Tag Paramters can be pre-configured in the Controls section to quickly populate desired paramters with pre-configured values.

Enables Ad Pod & Playlist functionality on this Seat. Once enabled, Multiplicity controls will be exposed at the Ad Unit and Channel Level. Additionally, live stats metrics and the Dashboard will have Pod & Playlist related statistics enabled.

Indicates whether this Ad Unit has an option to skip the ad. Options include Yes, No and Unknown. When selecting Yes, both the Skippable Minimum and Skippable After fields will need to be completed.

Floors set on Inventory Hierarchy will, by default, be inherited by child elements underneath them in the hiearchy. If an element is inheriting a Floor from a parent element, the Inherited From and Source fields will identify where in the hierarhcy the floor is being inherited from.

The Source (src) Relationship field should describe the relationship between the ad content and the video content. Select Indirect if the inventory is sourced from a third-party partner. Select Direct if the inventory is owned by the seat holder.

If Server Side Ad Insertion (SSAI) is being used to deliver ads, this field is used to flag to DSPs how it is being used: None: Default option. All Client Side: Ads are being fetched client side, and trackers are being fired client side. Assets Server Side, Tracking Client Side: Ads are being fetched server side, and trackers are being fired client side. All Server Side: Ads are being fetched server side, and trackers are being fired server side.

Enables the SSP Connect feature which allows configuration of "mapping rules" to handle requests from different inbound integrations (e.g. SpringServe, Publica, Google Open Bidding, Generic OpenRTB etc). Once enabled, the Enabled External Code Namespaces will appear, allowing for the selection of the Integrations supported on this Seat. Once fully configured, will enable Integrations > SSP Connect within this Seat, which is where mapping and routing rules are managed.

The Status toggle allows you to define if the deal is active or not. The available options are Active and Paused. There is also an additional "Expired" status that the Ad Source will automatically shift into once it is past it's End Date.

The App Store URL for this application. Note: This is fetched automatically when using on of the indexed App Stores (e.g. Apple App Store, Google Play, Roku Channel Store etc).It must be entered manually when using the Other option.

The Supply Domain associated with the inbound ad request. Ladles will be captured for this Supply Domain (e.g. "site.com")

The type of Supply Domain filtering being applied on this Seat. Block mode will rejected listed app bundles, while Allow mode will only accept listed bundles. Note: Supply Domain filters only apply to "site" type supply.

The list(s) of Supply Domains used by the Supply Domain Filter mode on this Seat. These are defined via Platform Admin.

Allows for filtering VAST errors to a specific level of Inventory within the Seat.

The External Name represents the Supply Name value that is sent in Bid Requests to buyers. This field will default to using the name of this Supply element, though it can be overridden. The value entered here should accurately describe the name of the inventory being offered.

Legacy internal field used to indicate the support level provided to this client.

A list of supported API frameworks for this ad unit. Commonly used to indicate VPAID support. Available options include: VPAID 2.0 and VPAID 1.0.

The version(s) of VAST supported by this Ad Unit. Multiple options can be selected. The selected protocols will be sent in the bid request to buyers.

The Targeting applied for this Brand Safety rule. Any Ad Requests that match this targeting will have this Brand Safety rule applied. NOTE: If Targeting is left blank, this means this Brand Saftey rule will apply to ALL Ad Requests.

If 'Upload Test Creative' is enabled, you have the ability to designate one creative to be used. After you upload multiple creatives, click on one to look at the end of the url to find the 'id' of that specific creative and then paste the id number in to this field.

Enables the internal Test Creative functionality to this Seat. Will display limited Ad Serving functionality in the Seat for Internal users, where creative assets can be uploaded. Upon upload, the Creative will have an ID assigned that will be used to populate the Test Creative ID field.

When applying QPS caps, the platform utilizes Smart Throttling. Smart Throttling looks at supply characteristics and groups supply into 3 Tiers based on performance (Tier 1 being the best performant, and Tier 3 being the least performant). When QPS limits are hit, the system will aim to throttle poorer performing tiers harder to ideally leave more room for the better performing supply. The Tier 2 and Tier 3 minimum QPS % fields provide the ability to reserve a certain % of overall QPS available for each Tier.

When applying QPS caps, the platform utilizes Smart Throttling. Smart Throttling looks at supply characteristics and groups supply into 3 Tiers based on performance (Tier 1 being the best performant, and Tier 3 being the least performant). When QPS limits are hit, the system will aim to throttle poorer performing tiers harder to ideally leave more room for the better performing supply. The Tier 2 and Tier 3 minimum QPS % fields provide the ability to reserve a certain % of overall QPS available for each Tier.

The default Timezone for the seat. Used to pre-populate fields when creating new Ad Sources.

Unified Decisioning (UD) is an advanced mediation solution designed to incorporate a publishers Direct Sold lines as another demand source within their SSP Seat. Rules can then be applied to determine how Direct Sold campaigns interact with Programmatic demand, and the platform will become the central point for managing all demand and generate final Ad Responses for rendering.

Determines how UD will attmept to extract key Line Item identifiers from the External Ad Server (e.g. GAM, Freewheel) ad response. The Line Item ID is then used to lookup metadata about the direct sold campaign (such as Price, Priority, Advertiser) that can then be used to execute competition and business rules.

Toggling UD Opt-out will enable a safety valve that short-circuits standard UD Processing. The platform will no longer process the request, and instead will take the supplied External Ad Server URL, perform any macro substitutions requested and redirect directly to the Ad Server.

Enable this to unwrap any VAST Wrapper respones that are encountered from buyers.

"Calculon Use Rate Override" permits the Seat administration to set their own (rather than system default) Use Rate threshold at which Calculon will begin throttling the ability for a given aDomain to win auctions. "Upper Calculon Use Rate Override" permits the Seat Administrator to set their own (rather than system default) Use Rate threshold at which a given aDomain will cease to be throttled (leveraging Calculon's rapid self-healing mechanism). These settings can be applied at any node in a Seat's inventory hierarchy.

The asset URL as declared in the VAST response.

How often a 'Fill' results in an 'Impression'.

Labels are used to "tag" Supply using pre-defined key/value pairs. This allows for convenient grouping of similar elements of supply across the Inventory Hierarchy for the purpose of Targeting or Reporting. Labels are managed via Controls > Classifications > Labels

The distribution & count of the size (in Kilobytes) of sampled winning VAST documents. For convenience, these are grouped into buckets.

The distribution & count of VAST Versions (e.g. 2.0, 3.x, 4.x etc) observed in sampled winning VAST documents.

The distribution & count of video playbacks observed in sampled winning VAST documents.

This selection should describe the main video content's quality, as per the IAB's classification.

The Viewability Vendors provides the ability to declare that the Supply supports viewability code provided by the selected Vendors. This information is sent to buyers in the Bid Request. Vendors should only selected if they are definitely supported.

The detected width in pixels of the supplied video asset, or the asset width as declared in the VAST response.