--- title: "Programmatic - Troubleshooting" canonical: "https://hub.freewheel.tv/space/CHUG/510623781/Programmatic%20-%20Troubleshooting" format: markdown --- Overview The Troubleshooting dashboard provides enhanced troubleshooting capabilities, enabling users to quickly identify programmatic deal issues. The dashboard offers insight into which stage has the most prominent issue, which error might have caused it, and what next steps to take to boost delivery.  Access the Troubleshooting Dashboard Navigate to Reports > Demand > Programmatic > Performance . Troubleshooting UI Troubleshooting Widgets Widget Description Global Filters Mode Filter Description Historical, Real Time Time Range A date picker allowing users to specify the date range for the data displayed. Please note that the date range is the past three months.  Historical, Real Time Granularity The granularity of the data displayed in the dashboard. Options include hourly (default) and daily. Historical, Real Time User Drop Off Slot Specifies whether the drop off slot is included (default) or removed. Historical, Real Time Primary/Fallback Ad Specifies whether the data in the chart reflects primary ad or fallback ad data.   Historical, Real Time DSP Allows users to include or exclude data from one or more specific DSPs. Historical, Real Time Deal Allows users to include or exclude data from one or more specific programmatic deals. Historical, Real Time Player Profile Allows users to include or exclude data from one or more specific player profiles.  Historical, Real Time Site Allows users to include or exclude data from one or more specific sites. Historical, Real Time Site Section Allows users to include or exclude data from one or more specific site sections. Historical, Real Time Demand Type Specifies the particular demand type (also referred to as deal type) for the data displayed in the dashboard. Options include: Programmatic Guaranteed (PG) Non-PG Historical, Real Time Primary Trafficker Allows users to include or exclude data from one or more specific campaign traffickers. This allows traffickers and managers to easily review performance of programmatic deals from an particular campaign trafficker, team, or group of individuals.  Historical Ad Unit Position The temporal or visual position of the ad unit class or instance. Historical App Bundle The platform-specific identifier of the app associated with a bid request. This value is only available for bid requests that come from an app (the value of  Programmatic Auction Type  is  App Request ). Historical, Real Time Bidding Buyer The unique, system-generated identifier and name of the programmatic buyer specified in the demand partner's bid response.  Historical Content Brand The standardized brand associated with the network item. A brand is a collection of channels. The Programmer, Brand, and Channel (if applicable) standard attributes are declared or detected together. Historical Country The country/countries that ad requests associated with the network item came from, with each country returned in its own row. Historical, Real Time Creative The unique, system-generated identifier and user-specified name of the creative.  Historical, Real Time Deal End Date The end date and time of the deal. Condition  filter values can be selected by:  is before (Excluding Selected Date) is from  is between is empty Value  filter values can be selected by specifying a date and time in  YYYY-MM-DD HH:mm format.  Dates and times are displayed in the time zone of the current network, a network-level setting. Historical, Real Time Deal Start Date The start date and time of the deal. Condition  filter values can be selected by:  is before (Excluding Selected Date) is from  is between is empty Value  filter values can be selected by specifying a date and time in  YYYY-MM-DD HH:mm format.  Dates and times are displayed in the time zone of the current network, a network-level setting. Historical, Real Time Deal Status Provides the ability to report on deal statuses in Analytics, such as active, booked, accepted, and inactive. This dimension returns the same value as that shown in the user interface. This dimension is only available to users of the Programmatic Module. Historical, Real Time Deal Type The type of the deal. This value can only be changed if the deal is inactive and is not a Programmatic Guaranteed deal. Historical Device Type The general category of the device(s) that ad requests associated with the site item came from, with each category returned in its own row. Historical Endpoint Name The name of the endpoint(s) where a viewer watched the content associated with the site item, with each endpoint returned in its own row. Historical Endpoint Owner The owner of the endpoint(s) where a viewer watched the content associated with the site item, with each endpoint owner returned in its own row. Endpoint owners are typically programmers or MSOs (Multiple System Owners). Historical, Real Time FFDR The forecasted final delivery rate (FFDR) of the Programmatic Guaranteed deal. The FFDR is the percentage of the budget that the Programmatic Guaranteed deal is expected to deliver by the end of the flight. Historical Global Advertiser The Freewheel-assigned identifier and name of the global advertiser.  Historical Global Brand The Freewheel-assigned identifier and name of the global brand.  The identifier is a seven-digit number that begins with the number 1.  Historical Global Industry The Freewheel-assigned identifier and name of the global industry.  Historical IFA Type IFA Type refers to the Identifier for Advertising Type used in FreeWheel's advertising technology. It is a classification of the type of identifier used for tracking and targeting advertisements across different devices and platforms. Historical, Real Time Open Exchange Rule The unique, system-generated identifier and name of the Open Exchange rule.  An Open Exchange rule is a programmatic transaction model that allows certain buyers to bid on certain inventory without targeting a specific deal ID in the bid request. Historical, Real Time OSI The previous day's on-schedule indicator (OSI) of the deal. This value is updated daily, at 12 AM. The OSI is the percentage of an ad's actual delivery compared to its pacing curve. Historical Programmatic Auction Type The type of inventory monetized programmatically in the bid request. Historical, Real Time Programmatic Device The type of the device associated with the programmatic transaction. This value is parsed from the OpenRTB specification, by default from the device.devicetype attribute. Historical Programmer The programmer (the network or producer) associated with the network item. The Programmer, Brand, and Channel (if applicable) standard attributes are declared or detected together. Historical Purchased Order The unique, Freewheel-assigned identifier and user-specified name of the purchased order.  Historical, Real Time Salesperson The name of the salesperson associated with the deal. This value identifies the salesperson who should be contacted for any questions or issues. Historical Site Domain The domain name of the website associated with a bid request. This value is only available for bid requests that come from a website (the value of  Programmatic Auction Type  is  Site Request ). Historical Sub Stream Type The specific stream type of the network item. Historical Supplier The unique, system-generated identifier and name of the supplier of the inventory. Supplier ID:  The unique, system-generated identifier of the supplier of the inventory. Supplier Name:  The name of the supplier of the inventory. Partner Name:  The name of the partner acting on behalf of the buyer specified in the demand partner's bid response. Historical Supply Source The supply origin of the inventory item. Historical Video Series A Video Series collects together all episodes through all seasons of a particular show. In the hierarchy of videos, Video Series are considered children of video groups and can act as parents to video assets. However, not every video asset needs to be a part of a Video Series. For instance, movies, specials, or other longer content can be included in a Video Group without being associated with a Video Series. See below for more information.  Relevant actions:  Default View Pre-Filtered Bid Requests Underneath the global filters are four trend charts. These charts show programmatic troubleshooting metrics and follow Ad Server handling and selection process. Users can utilize these four charts to observe which stage has a higher failure rate, and then switch to the related tabs below to see the specific errors that occurred at that stage. Metric Description Eligible Invitations The number of bid request invitations. This value is calculated using the following formula:  Eligible Invitations = Bid Requests + Pre-Filtered Bid Requests Bid Requests The number of requests sent to demand partners.  This value is calculated using the following formula: Bid Requests = Response Errors + Responses with Bids  Pre-Filtered Bid Requests The number of bid requests that are blocked and not sent to the DSP. It differs from Pre-Filtered Deals. Pre-Filtered Bid Requests Rate This value is calculated using the following formula: Pre-Filtered Bid Requests Rate = Pre-Filtered Bid Requests / Eligible Invitations To isolate a particular trend, select a metric in the chart legend. The chart will show only the trend line for the selected metric. Click the metric again to revert changes. Users can also multi-select or multi-unselect metrics in the trend graph by holding the  command  or  Windows  key and selecting a metric.  Hovering over the chart enables a crosshair function that displays metrics for the Net Counted Ads Distribution by Priority Tier chart at the same date and time.  Relevant actions:  Expand CSV Export Response Errors Metric Description Bid Requests The number of requests sent from Streaming Hub to demand partners. This value is calculated using the following formula: Bid Requests = Response Errors + Responses with Bids Responses with Bids The number of received responses with bids from demand partners. Response Errors The number of requests associated with an error response from demand partners. Response Errors Rate This value is calculated using the following formula: Response Errors / Bid To isolate a particular trend, select a metric in the chart legend. The chart will show only the trend line for the selected metric. Click the metric again to revert changes. Users can also multi-select or multi-unselect metrics in the trend graph by holding the  Command  or  Windows  key and selecting a metric.  Hovering over the chart enables a crosshair function that displays metrics for the Net Counted Ads Distribution by Priority Tier chart at the same date and time.  Relevant actions:  Expand CSV Export Failed Bids Metric Description Received Bids The total number of bids received for the corresponding deal or open exchange rule in the bid request. Valid Bids The number of valid bids received from the demand partners. Failed Bids The number of invalid bids and invalid creatives. This value is calculated using the following formula: Received Bids - Valid Bids Failed Bids Rate This value is calculated using the following formula: Failed Bids / Received To isolate a particular trend, select a metric in the chart legend. The chart will show only the trend line for the selected metric. Click the metric again to revert changes. Users can also multi-select or multi-unselect metrics in the trend graph by holding the  Command  or  Windows  key and selecting a metric. Hovering over the chart enables a crosshair function that displays metrics for the Net Counted Ads Distribution by Priority Tier chart at the same date and time.  Relevant actions:  Expand CSV Export Filtered Bids Metric Description Valid Bids The number of valid bids received from the demand partners. Selected Ads Total selected Programmatic ads. When User Drop Off Slot is included, the calculation ignores user drop off behavior; when removed, it considers user drop off behavior, and only played slots are counted. When Primary/Fallback Ad is Primary, only ads in the primary position of an ad response are counted; when Fallback, only ads in the fallback position are counted. Filtered Bids The number of valid bids not selected by the ad server. This value is calculated using the following formula: Valid Bids - Selected Ads Filtered Bids Rate This value is calculated using the following formula: Filtered Bids / Valid Bids To isolate a particular trend, select a metric in the chart legend. The chart will show only the trend line for the selected metric. Click the metric again to revert changes. Users can also multi-select or multi-unselect metrics in the trend graph by holding the  Command  or  Windows  key and selecting a metric. Hovering over the chart enables a crosshair function that displays metrics for the Net Counted Ads Distribution by Priority Tier chart at the same date and time.  Relevant actions:  Expand CSV Export Detailed Error Reasons Trend Users can analyze errors occurring at each stage. The trend chart shows how the error count changes over time, which can help identify whether certain delivery issues are related to a surge in specific errors. The chart legend provides the total number of errors and their percentages, offering insight into which errors are significant. The Detailed Error Reasons Trend option displays the following:  Error name. For example:  Invalid VAST Response Error description. For example:  The VAST response doesn't follow the schema defined by the VAST specification. Used by JS, Android and iOS/tvOS AdManager. Potential remedial action. For example:  The VAST validates as XML, but does not validate per the VAST schema (i.e. there are missing mandatory elements or attributes, or combinations of elements/attributes that are not permissible). Ensure VAST XML is properly formatted per IAB spec. Stage Failure Reasons Pre-Filtered Bid Requests Additional slot-level analysis is also provided for Competition Failure and Profile Check Failed .   Pre-Filtered Bid Requests Error Name Description Potential Remedial Action Demand Partner Disallowed by Profile The ad was filtered due to a demand partner (e.g. DSP and SSP) allowlist set by the endpoint owner on the profile level, and the current demand partner isn't in the allowlist. Communicate with endpoint owner on adding this demand partner to the allowlist of the profile. Deal Frequency Cap Reached The ad was filtered due to exceeding the frequency cap. Expected behavior per client configuration - if desired, update the Deal level frequency cap under "Programmatic → Deals" Profile Check Failed The ad was filtered due to profile check fail with the following reasons: The creative returned did not meet the player profile requirements for content type, creative API or ad unit. The creative returned was longer than max duration restriction set up in the network's ad unit restriction or CBP. Please drill down to slot level Filtered Reasons and then take actions accordingly. Network Item Industry Restriction The ad was filtered due to an industry restriction set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Industry Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Listing Industry Restriction The ad was filtered due to an industry restriction set on an upstream Marketplace Platform Private or Marketplace Exchange listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the industry restrictions and communicate the restrictions to the Buyer. CCPA/GPP us privacy Opt-Out The ad was filtered because the DSPs do not accept CCPA/GPP US privacy opt-out bid requests. Expected behavior per DSP's Privacy configurations. GPP SPI Opt-Out The ad was filtered because the DSPs do not accept SPI no consent bid requests. Expected behavior per DSP's Privacy configurations. Deal Industry Restriction The ad was filtered due to an industry restrictions set at the deal level. Expected behavior per client configuration - if desired, update the Deal level Industry Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Inventory Protection - Industry The ad was filtered due to failing to detect creative industry information and industry level inventory protection restriction was set on a network item. Add an Industry for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Streaming Hub Global Settings → Restrictions". Inventory Protection  - Advertiser The ad was filtered due to failing to detect creative advertiser information and advertiser level inventory protection restriction was set on a network item. Add an Advertiser for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Streaming Hub Global Settings → Restrictions" Inventory Protection - Brand The ad was filtered due to failing to detect creative brand information and brand level inventory protection restriction was set on a network item. Add a Brand for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin →Streaming Hub Global Settings → Restrictions". Industry Restriction The ad was filtered due to deal level industry restrictions or upstream industry restrictions. Expected behavior per client configuration - if desired, update the Deal level Industry Restriction under "Programmatic → Deals" or check with upstream partner on expected industry restrictions. Otherwise, check with upstream partner to understand the  industry restriction and communicate the restriction to the Buyer. Deal Advertiser Restriction The ad was filtered due to deal level advertiser restrictions. Expected behavior per client configuration - if desired, update the Deal level Advertiser Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Network Item Advertiser Restriction The ad was filtered due to advertiser restrictions set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Advertiser Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Listing Advertiser Restriction The ad was filtered due to an advertiser restrictions set on listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the advertiser restriction and communicate the restriction to the Buyer. Deal Brand Restriction The ad was filtered due to deal level brand restrictions. Expected behavior per client configuration - if desired, update the Deal level Brand Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Network Item Brand Restriction The ad was filtered due to brand restrictions set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Brand Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Brand Frequency Cap Reached The ad was filtered due to exceeding the frequency cap set on brand. Expected behavior per client configuration - if desired, update the Brand level Frequency Cap under "System Admin → Global Settings → Global Brand and Advertiser configuration". Advertiser Frequency Cap Reached The ad was filtered due to exceeding the frequency cap set at the global Advertiser level. Expected behavior per client configuration - if desired, update the Advertiser level Frequency Cap under "System Admin → Global Settings → Global Brand and Advertiser configuration." Listing Brand Restriction The ad was filtered due to brand restrictions set on an upstream Marketplace listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the brand restriction and communicate the restriction to the Buyer. Ad Targeting Restriction The ad was filtered due to the ad targeting restrictions on the inventory. Expected behavior per client configuration - if desired, update the Ad Targeting Restriction on the network items under "Network → Network Items". Exclusivity The ad was filtered due to an industry exclusivity set against a direct sold ad. This includes exclusivities of scope type "all ad units" or "targeted ad units", but not "adjacent ads" exclusivities. Expected behavior per client configuration - if desired, update the Exclusivity on similarly targeted Direct Sold placements under "Advertising → Campaign". Only Pod Ad Allowed The bid was filtered because only Pod ads are allowed. Expected behavior per client configuration - for further information please check with your FreeWheel Account Team. Creative Not Applicable The ad was filtered due to one of the following two reasons: Flash version incompatibility HTTP/HTTPS does not match secure field Pull an example Bid Response from Ad Server Diagnostics and check the HTTP Protocol. Check with Buyer/DSP on expectations. Ad Pending Approval The ad was filtered because its creative was pending approval and therefore cannot be served. Approve the Creative in the Creative Approval tool under "Partner → Creative Approval". Ad Rejected The ad was filtered because its creative was rejected and therefore cannot be served. Expected behavior per client configuration - if desired, check the Creative within the Creative Approval tool under "Partner → Creative Approval". Network Item Inventory Source Optimization The ad was filtered due to Inventory Source Optimization set on a site or video axis. Expected behavior per client configuration - if desired, update the Inventory Source Optimization setting for the particular network item under "Network → Network Items". Ad Duration Exceeded The ad was filtered due to exceeding the max ad duration of the deal. Expected behavior per client configuration - if desired, update the Max Ad Duration for this Deal under "Programmatic → Deals". Deal Floor Price Not Met The ad was filtered because its bid price is lower than the floor price set on the deal. Expected behavior per client configuration - communicate the Floor Price to the Buyer. Competition Failure The ad was filtered due to the following reasons: The ad was filtered because it was the same as an ad already selected for the break. This is only relevant to OpenRTB integrations, which prevent the same ad from delivering more than once within an ad break. The ad was filtered because the exclusivity on the ad was set to adjacent ads. The Programmatic ad was ranked below higher scoring ads and could not be fitted into the break as the available time remaining in the break was shorter than the Programmatic ad creative duration. Please drill down to slot level Filtered Reasons and then take actions accordingly. Data Rights Restricted The ad was filtered due to data rights control. Expected behavior per client configuration - if desired, communicate with Data Right Owner or update Data Rights under "Partner → Data Rights" Reseller Blocklist Restriction The ad was filtered due to a reseller blocklist restriction set by upstream networks. Communicate with the upstream partner on reseller expectations, e.g. remove the reseller from the blocklist. Reseller Allowlist Restriction The ad was filtered due to a reseller allowlist restriction set by upstream networks. Communicate with the upstream partner on reseller expectations, e.g. add the reseller to the allowlist. Creative Restriction Failure The ad was filtered due to all creative renditions failing creative restriction checks (e.g. Clearcast codes restrictions preventing it from serving in the slot). Expected behavior per client configuration - if it's caused by Clearcast codes restrictions, update the Clearcast Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Streaming Hub Global Settings → Restrictions." For further information please check with your FreeWheel Account Team. Standard Attribute Advertiser Restriction The ad was filtered due to advertiser restrictions set on a standard attribute. Expected behavior per client configuration - if desired, update the Standard Attribute Advertiser Restriction under "Network → Standard Attributes" or communicate the restriction to the Buyer. Standard Attribute Industry Restriction The ad was filtered due to industry restrictions set on a standard attribute. Expected behavior per client configuration - if desired, update the Standard Attribute Blocked Industry Group Restriction under "Network → Standard Attributes"  or communicate the restriction to the Buyer. No Client Rendition The ad was filtered because we could not locate a client rendition, and only client renditions are allowed to serve. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. No JiTT Rendition This will occur for two cases: The JiTT task is in progress. No JiTT creative rendition located and only JiTT creative renditions are allowed to serve. Please check the transcoding status for the associated Creative under "Creative → Programmatic Creative" and check with the Transcoding Vendor. Only Companion Ad Allowed The bid was filtered because only companion ad is allowed. Expected behavior per client configuration - for further information please check with your FreeWheel Account Team. CCPA Opt-Out The bid was filtered because the ad request did not have the consent required by DSP for monetization under CCPA. Expected behavior per DSP's Privacy configurations. No TCF Consent The bid was filtered because the ad request did not have the consent required by DSP for monetization under TCF. Expected behavior per DSP's Privacy configurations. LAT Unsupported The ad was filtered because the DSP does not support LAT . Expected behavior per DSP's Privacy configurations. COPPA Unsupported The ad was filtered because the DSP does not support COPPA . Expected behavior per DSP's Privacy configurations. Apple App Tracking Transparency Unsupported The ad was filtered because the DSP does not support Apple App Tracking Transparency. Expected behavior per DSP's Privacy configurations. KV Unsupported The ad was filtered because the ad request used _fw_opt_out reserved key-value to trigger all compliance related features. Expected behavior per DSP's Privacy configurations. GPP Not Supported The ad was filtered due to the DSP not supporting reading the GPP privacy signal. Expected behavior per DSP's Privacy configurations. Low Response Rate Limiter The ad was filtered because the DSP bid rate was below the bid threshold and bid requests have been limited. Expected behavior per client configuration - if desired, please check with your FreeWheel Account Team to update the PG deal low bid rate limiter setting. Otherwise, check with the Buyer or DSP. DSP Status Inactive The ad was filtered because the DSP's status for this deal is inactive; the DSP is not ready to bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Pause The ad was filtered because the DSP's status for the deal is paused and the DSP will not bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Complete The ad was filtered because the DSP's status for the deal is completed and the DSP will not bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Unknown The ad was filtered because Streaming Hub could not identify the DSP's status of the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. Upstream Order Floor Price Not Met The ad was filtered due to its bid price being lower than the upstream order floor price. Please check with your upstream partner on price expectations of the purchased order. Advertiser Domain Restricted The ad was filtered because its advertiser domain was either empty or blocked by the incoming ORTB request’s badv (blocked advertisers) parameter. Please ensure that the ads advertiser has a valid domain assigned and does not violate the badv value in the incoming ORTB request. Other The ad was filtered due to other reasons. Please check with your FreeWheel Account Team. Competition Failure Error Name Description Potential Remedial Action CRO Advertiser Frequency Cap Reaching This error indicates the ad was blocked by the upstream CRO's Global Advertiser Frequency Cap, applicable only in MBD scenarios where upstream CRO control is allowed. MBD network should follow upstream CRO's setting, but if it is impacting the delivery, MBD could connect with the CRO to discuss if CRO could change the settings for Global Advertiser Frequency Cap on their side. CRO Brand Frequency Cap Reaching This error indicates the ad was blocked by the upstream CRO's Global Brand Frequency Cap, applicable only in MBD scenarios where upstream CRO control is allowed. MBD network should follow upstream CRO's setting, but if it is impacting the delivery, MBD could connect with the CRO to discuss if CRO could change the settings for Global Brand Frequency Cap on their side. Advertiser Frequency Cap Reached The ad was filtered because it exceeded the global advertiser’s frequency cap. NOTE: This slot level filter tracks the second check, while the first check is recorded as "Advertiser Frequency Cap Reached" at the candidate level. Expected behavior per client configuration - if desired, update the Advertiser level Frequency Cap under “System Admin → Global Settings → Global Brand and Advertiser configuration”. DSP Bid Cap Reached The ad was filtered because only one bid can win one impression opportunity per DSP in a multi-bid scenario. Expected behavior - limitation imposed by OpenRTB specification. Excluded by Pod Ads The ad was filtered because only Pod ads are allowed. Expected behavior per client configuration - for further information please check with your FreeWheel Account Team. Sequence Variant Targeting Failed The ad could not fill a position because it didn't meet the sequence variant targeting requirements of its ad unit. Expected behavior per client configuration - if desired, update the CBP settings from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Clearcast Restriction The ad was filtered because Clearcast restrictions prevented it from serving in the slot. Expected behavior per client configuration - if desired, update the Clearcast Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Advertiser The ad was filtered because of advertiser exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Brand The ad was filtered because of the brand exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Industry The ad was filtered because of the industry exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Back to Back Exclusivity The ad was filtered because the same ad had been selected in the break already. Expected behavior. Adjacent Ads Exclusivity The ad was filtered because of exclusivities set on other ads selected in the break. Expected behavior per client configuration - if desired, update the Exclusivity settings for similarly targeted Direct Sold placements under "Advertising → Campaign". Slot Exclusivity The ad was filtered because of the exclusivity set on selected placements in the break. Expected behavior per client configuration - if desired, update the Exclusivity settings for similarly targeted Direct Sold placements under "Advertising → Campaign". Max Slot Duration Exceeded The ad was filtered because its duration exceeded the slot's remaining time, and all spots were filled by higher-scoring ads. Expected behavior per client configuration - if desired, raise the deal to higher in priority waterfall. Max Number of Ads Exceeded The ad was filtered because the slot reached its ad limit, meaning all opportunities were filled by higher-scoring ads. Expected behavior per client configuration - if desired, raise the deal to higher in priority waterfall. Profile Check Failed Error Name Description Potential Remedial Action Adstor Linear Creative Unavailable The ad was filtered because the creative was not available to serve in Linear inventory. Please check the transcoding status for the associated Creative and follow up with Adstor. Adstor Creative Unavailable The ad was filtered because the creative hosted in Adstor was not available to serve. Please check the transcoding status for the associated Creative and follow up with Adstor. Adstor Creative Bitrate Incompatible The ad was filtered because the creative hosted in Adstor failed the profile bitrate or ad request bitrate check. Update Bitrate on Ad Request or check with your FreeWheel Account Team to update Bitrate on Player Profile, communicate with Adstor. Brand Frequency Cap Reached The ad was filtered because it exceeded the global brand's frequency cap. NOTE: This slot level filter tracks the second check, while the first check is recorded as "Brand Frequency Cap Reached" at the candidate level.  Expected behavior per client configuration - if desired, update the Brand level Frequency Cap under "System Admin → Global Settings → Global Brand and Advertiser configuration".  Creative Profile Incompatible The ad was filtered because the creative was not compatible with the player profile used in the ad request (e.g., frame rate, bit rate, etc.). Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Creative VPAID Incompatible The ad was filtered because the creative was a VPAID, and VPAID Support was disabled for the deal. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile, or update VPAID configuration on Deal level under "Programmatic → Deals", or communicate expectations with Buyer/DSP. Creative Ad Unit Duration Incompatible The ad was filtered because the creative exceeded the ad unit's maximum allowed ad duration. Pull an example Bid Response from Ad Server Diagnostics - if desired, update the CBP settings from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions" or communicate expectations with Buyer/DSP. Creative File Size Incompatible The ad was filtered because the creative file size did not match the allowed file sizes configured on the player profile. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Creative Dimension Incompatible The ad was filtered because its creative height and width did not match the allowed sizes in the player profile. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Deal Frequency Cap Reached The ad was filtered because it exceeded the deal's frequency cap. NOTE: This slot level filter tracks the second check, while the first check is recorded as "Deal Frequency Cap Reached" at the candidate level. Expected behavior per client configuration - if desired, update the Deal level Frequency Cap under "Programmatic → Deals". Estimated Duration Disabled for Live Inventory The ad was filtered because the ad request was for live inventory, and either the deal was Programmatic Guaranteed or the DSP couldn't provide the creative's exact duration due to technical limitations. Should you wish PG/demand from such DSPs to be able to serve against live inventory, please contact your Freewheel account team. Response Errors The number of requests associated with an error response from demand partners. Error Name Description Potential Remedial Action No Bids The number of responses received from the demand partners does not include any bids. Please check with the Buyer or DSP if no bids are expected. Timeout The number of requests timed out before demand partners returned a response. Please check with the Buyer or DSP for a potential integration issue. Or reach out to your account team to adjust the default timeout value. HTTP Error The number of responses received from the demand partners has HTTP errors. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Empty Response The number of responses received from the demand partners is empty. Pull an example Bid Request from Ad Server Diagnostics and check with the Buyer or DSP why they return an empty bid response. Mismatched Response Index The number of responses received from the demand contains a mismatched response ID. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Failed Bids The total number of failed bids. This is calculated by adding the total invalid bids and invalid creatives, and ensuring this number equals the number of received bids minus valid bids. This error is the parent error of other failed bid errors.   Error Name Description Potential Remedial Action Empty Deal ID The received bid did not include a deal ID Pull an example Bid Response from Ad Server Diagnostics and check with the DSP. Empty Bid ID The received bid did not have a bid ID. This error only occurs for PG deals when the returned triplet ID does not match the pre-ingested programmatic ads. Pull an example Bid Response from Ad Server Diagnostics, check against the ingested PG Creative(s), then check with the Buyer. Empty VAST Ad Markup The received bid did not include a creative link. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Mismatched Seat ID The received bid did not include a known seat ID. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Mismatched Impression ID The received bid did not include a known impression ID. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Mismatched Ad ID The received bid did not include a valid ad ID Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Invalid Bid Price The received bid did not include a valid price Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Invalid Bid Currency The received bid did not include a valid currency Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Mismatched Deal ID The received bid did not include a known deal ID. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Empty VAST The received bid did not include a creative (e.g., ). Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Non Secure Ad The creative is invalid due to failing the Secure Sockets Layer (SSL) check. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. No Ad in VAST No valid creative was found when unwrapping the creative. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Unsupported VAST Version The creative VAST version is not supported. Pull an example Bid Response from Ad Server Diagnostics - if you believe there is an error, check with your Freewheel Account Team to update your Player Profile. Otherwise, check with the Buyer or DSP. VAST Wrapper HTTP Error The creative received could not be resolved due to an HTTP error. Please check with the Buyer or DSP for a potential integration issue. VAST Wrapper Timeout The creative received could not be resolved within time limit. Expected behavior per client configuration - if desired, please check with your Freewheel Account Team to increase your network's timeout setting. In addition, please check with the Buyer or DSP for a potential integration issue. Invalid VAST Wrapper URL The wrapper URL in the creative VAST is not valid. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. Malformed VAST XML The creative VAST XML is not correctly formed.  Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. No Client Rendition No client rendition located and only client renditions are allowed to serve. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. No JiTT Rendition This will occur for two cases: The JiTT task is in progress. No JiTT creative rendition located and only JiTT creative renditions are allowed to serve. Please check the transcoding status for the associated Creative and check with the Transcoding Vendor. Other Other errors encountered when validating the bid and creative. Please check with your Freewheel Account Team. Filtered Bids The total number of bids that were not selected due to filtering. Additional slot-level analysis is also provided for Competition Failure and Profile Check Failed .   Filtered Bids Error Name Description Potential Remedial Action Network Seat Restriction The ad was filtered because its seat has been blocked at the network level.  Expected behavior per client configuration - if desired, update the network level Seat(s) Restriction under "System Admin -> Programmatic Management". Standard Attribute Reseller Allowlist Restriction The ad was filtered due to reseller allowlist restrictions set on a standard attribute. Expected behavior per client configuration. If desired, update the Standard Attribute Blocked Reseller Restriction under "Network →  Standard Attributes" or communicate the restriction to the Buyer. Standard Attribute Reseller Blocklist Restriction The ad was filtered due to reseller blocklist restrictions set on a standard attribute. Expected behavior per client configuration. If desired, update the Standard Attribute Blocked Reseller Restriction under "Network →  Standard Attributes" or communicate the restriction to the Buyer. Standard Attribute Ad Unit Restriction The ad was filtered due to ad unit restrictions set on a standard attribute. Expected behavior per client configuration. If desired, update the Standard Attribute Blocked Ad Unit Restriction under "Network → Standard Attributes" or communicate the restriction to the Buyer. Advertiser Domain Restricted The ad was filtered because its Advertiser Domain was either empty or banned by the incoming ORTB request's badv parameter.  Please ensure that the ads advertiser has a valid domain assigned and does not violate the badv value in the incoming ORTB request.  Demand Partner Disallowed by Profile The ad was filtered due to a demand partner (e.g. DSP and SSP) allowlist set by the endpoint owner on the profile level, and the current demand partner isn't in the allowlist. Communicate with endpoint owner on adding this demand partner to the allowlist of the profile. Deal Frequency Cap Reached The ad was filtered due to exceeding the frequency cap. Expected behavior per client configuration - if desired, update the Deal level frequency cap under "Programmatic → Deals" Profile Check Failed The ad was filtered due to profile check fail with the following reasons: The creative returned did not meet the player profile requirements for content type, creative API or ad unit. The creative returned was longer than max duration restriction set up in the network's ad unit restriction or CBP. Please drill down to slot level Filtered Reasons and then take actions accordingly. Network Item Industry Restriction The ad was filtered due to an industry restriction set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Industry Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Listing Industry Restriction The ad was filtered due to an industry restriction set on an upstream Marketplace Platform Private or Marketplace Exchange listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the industry restrictions and communicate the restrictions to the Buyer. CCPA/GPP us privacy Opt-Out The ad was filtered because the DSPs do not accept CCPA/GPP US privacy opt-out bid requests. Expected behavior per DSP's Privacy configurations. GPP SPI Opt-Out The ad was filtered because the DSPs do not accept SPI no consent bid requests. Expected behavior per DSP's Privacy configurations. Deal Industry Restriction The ad was filtered due to an industry restrictions set at the deal level. Expected behavior per client configuration - if desired, update the Deal level Industry Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Inventory Protection - Industry The ad was filtered due to failing to detect creative industry information, and industry-level inventory protection restriction was set on a network item. Add an Industry for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network-level settings under "System Admin → Streaming Hub Global Settings → Restrictions". Inventory Protection  - Advertiser The ad was filtered due to failing to detect creative advertiser information, and advertiser-level inventory protection restriction was set on a network item. Add an Advertiser for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network-level settings under "System Admin → Streaming Hub Global Settings → Restrictions" Inventory Protection - Brand The ad was filtered due to failing to detect creative brand information, and brand-level inventory protection restriction was set on a network item. Add a Brand for the Programmatic Creatives under "Creative → Programmatic Creative" or "Partner → Creative Approval". If desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Streaming Hub Global Settings → Restrictions". Industry Restriction The ad was filtered due to deal-level industry restrictions or upstream industry restrictions. Expected behavior per client configuration - if desired, update the Deal level Industry Restriction under "Programmatic → Deals" or check with upstream partner on expected industry restrictions. Otherwise, check with upstream partner to understand the industry restriction and communicate the restriction to the Buyer. Deal Advertiser Restriction The ad was filtered due to deal-level advertiser restrictions. Expected behavior per client configuration - if desired, update the Deal level Advertiser Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Network Item Advertiser Restriction The ad was filtered due to advertiser restrictions set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Advertiser Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Listing Advertiser Restriction The ad was filtered due to an advertiser restrictions set on listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the advertiser restriction and communicate the restriction to the Buyer. Deal Brand Restriction The ad was filtered due to deal-level brand restrictions. Expected behavior per client configuration - if desired, update the Deal level Brand Restriction under "Programmatic → Deals" or communicate the restriction to the Buyer. Network Item Brand Restriction The ad was filtered due to brand restrictions set on a site, video, or audience axis. Expected behavior per client configuration - if desired, update the Network Item Brand Restriction under "Network → Network Items" or communicate the restriction to the Buyer. Brand Frequency Cap Reached The ad was filtered due to exceeding the frequency cap set on brand. Expected behavior per client configuration - if desired, update the Brand level Frequency Cap under "System Admin → Global Settings → Global Brand and Advertiser configuration". Advertiser Frequency Cap Reached The ad was filtered due to exceeding the frequency cap set at the global Advertiser level. Expected behavior per client configuration - if desired, update the Advertiser level Frequency Cap under "System Admin → Global Settings → Global Brand and Advertiser configuration." Listing Brand Restriction The ad was filtered due to brand restrictions set on an upstream Marketplace listing. Expected behavior per client configuration - if desired, check with upstream partner to understand the brand restriction and communicate the restriction to the Buyer. Ad Targeting Restriction The ad was filtered due to the ad targeting restrictions on the inventory. Expected behavior per client configuration - if desired, update the Ad Targeting Restriction on the network items under "Network → Network Items". Exclusivity The ad was filtered due to an industry exclusivity set against a direct sold ad. This includes exclusivities of scope type "all ad units" or "targeted ad units", but not "adjacent ads" exclusivities. Expected behavior per client configuration - if desired, update the Exclusivity on similarly targeted Direct Sold placements under "Advertising → Campaign". Only Pod Ad Allowed The bid was filtered because only Pod ads are allowed. Expected behavior per client configuration - for further information, please check with your FreeWheel Account Team. Creative Not Applicable The ad was filtered due to one of the following two reasons: Flash version incompatibility HTTP/HTTPS does not match secure field Pull an example Bid Response from Ad Server Diagnostics and check the HTTP Protocol. Check with Buyer/DSP on expectations. Ad Pending Approval The ad was filtered because its creative was pending approval and therefore cannot be served. Approve the Creative in the Creative Approval tool under "Partner → Creative Approval". Ad Rejected The ad was filtered because its creative was rejected and therefore cannot be served. Expected behavior per client configuration - if desired, check the Creative within the Creative Approval tool under "Partner → Creative Approval". Network Item Inventory Source Optimization The ad was filtered due to Inventory Source Optimization set on a site or video axis. Expected behavior per client configuration - if desired, update the Inventory Source Optimization setting for the particular network item under "Network → Network Items". Ad Duration Exceeded The ad was filtered due to exceeding the max ad duration of the deal. Expected behavior per client configuration - if desired, update the Max Ad Duration for this Deal under "Programmatic → Deals". Deal Floor Price Not Met The ad was filtered because its bid price is lower than the floor price set on the deal. Expected behavior per client configuration - communicate the Floor Price to the Buyer. Competition Failure The ad was filtered due to the following reasons: The ad was filtered because it was the same as an ad already selected for the break. This is only relevant to OpenRTB integrations, which prevent the same ad from delivering more than once within an ad break. The ad was filtered because the exclusivity on the ad was set to adjacent ads. The Programmatic ad was ranked below higher-scoring ads and could not be fitted into the break, as the available time remaining in the break was shorter than the Programmatic ad creative duration. Please drill down to slot level Filtered Reasons and then take actions accordingly. Data Rights Restricted The ad was filtered due to data rights control. Expected behavior per client configuration - if desired, communicate with Data Right Owner or update Data Rights under "Partner → Data Rights" Reseller Blocklist Restriction The ad was filtered due to a reseller blocklist restriction set by upstream networks. Communicate with the upstream partner on reseller expectations, e.g., remove the reseller from the blocklist. Reseller Allowlist Restriction The ad was filtered due to a reseller allowlist restriction set by upstream networks. Communicate with the upstream partner on reseller expectations, e.g., add the reseller to the allowlist. Creative Restriction Failure The ad was filtered due to all creative renditions failing creative restriction checks (e.g., Clearcast codes restrictions preventing it from serving in the slot). Expected behavior per client configuration - if it's caused by Clearcast codes restrictions, update the Clearcast Restriction from the particular piece of inventory under "Network → Network Items" or from network-level settings under "System Admin → Streaming Hub Global Settings → Restrictions." For further information, please check with your FreeWheel Account Team. Standard Attribute Advertiser Restriction The ad was filtered due to advertiser restrictions set on a standard attribute. Expected behavior per client configuration - if desired, update the Standard Attribute Advertiser Restriction   under "Network → Standard Attributes"   or communicate the restriction to the Buyer. Standard Attribute Industry Restriction The ad was filtered due to industry restrictions set on a standard attribute. Expected behavior per client configuration - if desired, update the Standard Attribute Blocked Industry Group Restriction under "Network → Standard Attributes"    or communicate the restriction to the Buyer. No Client Rendition The ad was filtered because we could not locate a client rendition, and only client renditions are allowed to serve. Pull an example Bid Response from Ad Server Diagnostics and check with the Buyer or DSP. No JiTT Rendition This will occur for two cases: The JiTT task is in progress. No JiTT creative rendition located and only JiTT creative renditions are allowed to serve. Please check the transcoding status for the associated Creative under "Creative → Programmatic Creative" and check with the Transcoding Vendor. Only Companion Ad Allowed The bid was filtered because only companion ad is allowed. Expected behavior per client configuration - for further information, please check with your FreeWheel Account Team. CCPA Opt-Out The bid was filtered because the ad request did not have the consent required by DSP for monetization under CCPA. Expected behavior per DSP's Privacy configurations. No TCF Consent The bid was filtered because the ad request did not have the consent required by DSP for monetization under TCF. Expected behavior per DSP's Privacy configurations. LAT Unsupported The ad was filtered because the DSP does not support LAT . Expected behavior per DSP's Privacy configurations. COPPA Unsupported The ad was filtered because the DSP does not support COPPA . Expected behavior per DSP's Privacy configurations. Apple App Tracking Transparency Unsupported The ad was filtered because the DSP does not support Apple App Tracking Transparency. Expected behavior per DSP's Privacy configurations. KV Unsupported The ad was filtered because the ad request used _fw_opt_out reserved key-value to trigger all compliance-related features. Expected behavior per DSP's Privacy configurations. GPP Not Supported The ad was filtered due to the DSP not supporting reading the GPP privacy signal. Expected behavior per DSP's Privacy configurations. Low Response Rate Limiter The ad was filtered because the DSP bid rate was below the bid threshold, and bid requests have been limited. Expected behavior per client configuration - if desired, please check with your FreeWheel Account Team to update the PG deal low bid rate limiter setting. Otherwise, check with the Buyer or DSP. DSP Status Inactive The ad was filtered because the DSP's status for this deal is inactive; the DSP is not ready to bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Pause The ad was filtered because the DSP's status for the deal is paused and the DSP will not bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Complete The ad was filtered because the DSP's status for the deal is completed and the DSP will not bid on the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. DSP Status Unknown The ad was filtered because the system could not identify the DSP's status of the deal. The DSP Status is currently in development. Metrics will not appear for these filters until integration with demand partners is complete. Upstream Order Floor Price Not Met The ad was filtered due to its bid price being lower than the upstream order floor price. Please check with your upstream partner on price expectations of the purchased order. Other The ad was filtered due to other reasons. Please check with your FreeWheel Account Team. Competition Failure Error Name Description Potential Remedial Action Error Name Description Potential Remedial Action CRO Advertiser Frequency Cap Reaching This error indicates the ad was blocked by the upstream CRO's Global Advertiser Frequency Cap, applicable only in MBD scenarios where upstream CRO control is allowed. MBD network should follow upstream CRO's setting, but if it is impacting the delivery, MBD could connect with the CRO to discuss if CRO could change the settings for Global Advertiser Frequency Cap on their side. CRO Brand Frequency Cap Reaching This error indicates the ad was blocked by the upstream CRO's Global Brand Frequency Cap, applicable only in MBD scenarios where upstream CRO control is allowed. MBD network should follow upstream CRO's setting, but if it is impacting the delivery, MBD could connect with the CRO to discuss if CRO could change the settings for Global Brand Frequency Cap on their side. Advertiser Frequency Cap Reached The ad was filtered because it exceeded the global advertiser’s frequency cap. NOTE: This slot level filter tracks the second check, while the first check is recorded as "Advertiser Frequency Cap Reached" at the candidate level. Expected behavior per client configuration - if desired, update the Advertiser level Frequency Cap under “System Admin → Global Settings → Global Brand and Advertiser configuration”. DSP Bid Cap Reached The ad was filtered because only one bid can win one impression opportunity per DSP in a multi-bid scenario. Expected behavior - limitation imposed by OpenRTB specification. Sequence Variant Targeting Failed The ad could not fill a position because it didn't meet the sequence variant targeting requirements of its ad unit. Expected behavior per client configuration - if desired, update the CBP settings from the particular piece of inventory under "Network → Network Items" or from network-level settings under "System Admin → Global Settings → Restrictions". Clearcast Restriction The ad was filtered because Clearcast restrictions prevented it from serving in the slot. Expected behavior per client configuration - if desired, update the Clearcast Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Advertiser The ad was filtered because of advertiser exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Brand The ad was filtered because of the brand exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Inventory Protection - Industry The ad was filtered because of the industry exclusivities set in Inventory Protection. Expected behavior per client configuration - if desired, update the Inventory Protection Restriction from the particular piece of inventory under "Network → Network Items" or from network level settings under "System Admin → Global Settings → Restrictions". Back to Back Exclusivity The ad was filtered because the same ad had been selected in the break already. Expected behavior. Adjacent Ads Exclusivity The ad was filtered because of exclusivities set on other ads selected in the break. Expected behavior per client configuration - if desired, update the Exclusivity settings for similarly targeted Direct Sold placements under "Advertising → Campaign". Slot Exclusivity The ad was filtered because of the exclusivity set on selected placements in the break. Expected behavior per client configuration - if desired, update the Exclusivity settings for similarly targeted Direct Sold placements under "Advertising → Campaign". Max Slot Duration Exceeded The ad was filtered because its duration exceeded the slot's remaining time, and all spots were filled by higher-scoring ads. Expected behavior per client configuration - if desired, raise the deal to higher in priority waterfall. Max Number of Ads Exceeded The ad was filtered because the slot reached its ad limit, meaning all opportunities were filled by higher-scoring ads. Expected behavior per client configuration - if desired, raise the deal to higher in priority waterfall. Deal Frequency Cap Reached The ad was filtered because it exceeded the deal's frequency cap. NOTE: This slot level filter tracks the second check, while the first check is recorded as "Deal Frequency Cap Reached" at the candidate level. Expected behavior per client configuration - if desired, update the Deal level Frequency Cap under "Programmatic → Deals". Estimated Duration Disabled for Live Inventory The ad was filtered because the ad request was for live inventory, and either the deal was Programmatic Guaranteed or the DSP couldn't provide the creative's exact duration due to technical limitations. Should you wish PG/demand from such DSPs to be able to serve against live inventory, please contact your Freewheel account team. Profile Check Failed Error Name Description Potential Remedial Action Adstor Linear Creative Unavailable The ad was filtered because the creative was not available to serve in Linear inventory. Please check the transcoding status for the associated Creative and follow up with Adstor. Adstor Creative Unavailable The ad was filtered because the creative hosted in Adstor was not available to serve. Please check the transcoding status for the associated Creative and follow up with Adstor. Adstor Creative Bitrate Incompatible The ad was filtered because the creative hosted in Adstor failed the profile bitrate or ad request bitrate check. Update Bitrate on Ad Request or check with your FreeWheel Account Team to update Bitrate on Player Profile, communicate with Adstor. Creative Profile Incompatible The ad was filtered because the creative was not compatible with the player profile used in the ad request (e.g., frame rate, bit rate, etc.). Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Creative Profile Incompatible The ad was filtered because the creative was not compatible with the player profile used in the ad request (e.g., frame rate, bit rate, etc.). Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Creative VPAID Incompatible The ad was filtered because the creative was a VPAID, and VPAID Support was disabled for the deal. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile, or update VPAID configuration on Deal level under "Programmatic → Deals", or communicate expectations with Buyer/DSP. Creative Ad Unit Duration Incompatible The ad was filtered because the creative exceeded the ad unit's maximum allowed ad duration. Pull an example Bid Response from Ad Server Diagnostics - if desired, update the CBP settings from the particular piece of inventory under "Network → Network Items" or from network-level settings under "System Admin → Global Settings → Restrictions" or communicate expectations with Buyer/DSP. Creative File Size Incompatible The ad was filtered because the creative file size did not match the allowed file sizes configured on the player profile. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Creative Dimension Incompatible The ad was filtered because its creative height and width did not match the allowed sizes in the player profile. Pull an example Bid Response from Ad Server Diagnostics - if desired, check with your FreeWheel Account Team to update Player Profile or communicate expectations with Buyer/DSP. Ad Playback The number of selected ads played or displayed to the viewer. Error Name  Description Potential Remedial Action Invalid VAST Response The VAST response doesn't follow the schema defined by the VAST specification. Used by JS, Android, and iOS/tvOS AdManager. The VAST validates as XML, but does not validate per the VAST schema (i.e., there are missing mandatory elements or attributes, or combinations of elements/attributes that are not permissible). Ensure VAST XML is properly formatted per IAB spec. Mezzanine Transcoding Mezzanine is in the process of being downloaded for the first time. Download may take several hours. Ad will not be served until mezzanine is downloaded and transcoded. This is an expected error while the video is being transcoded, thus this error will stop once transcoding is complete and available. MediaFile Timeout Timeout of MediaFile URI. Increase the timeout limit of your player.  MediaFile Not Supported Couldn’t find MediaFile that is supported by this video player, based on the attributes of the MediaFile element. Ad is inline, but no compatible media file found; thus, ensure that all MediaFiles are eligible for this video player. Video Ad Failure General Linear error. Video player is unable to display the Linear Ad. Used by JS AdManager. Check that the MediaFile is a valid video file of the specified format in the request. Make sure the URL returns a valid video asset. Check for browser restrictions such as autoplay blocking, auto-mute, etc.  MediaFile Mismatch Problem displaying MediaFile. Video player found a MediaFile with supported type but couldn’t display it. MediaFile may include: unsupported Codecs, different MIME type than MediaFile@type, unsupported delivery method, etc Ensure that Codecs, MIME type, and delivery method are matched with your MediaFiles. MediaFile Not Found File not found. Unable to find Linear/MediaFile from URI. Ensure that all MediaFiles in the response return a valid video asset.  Unknown AdManager Error Errors without specific reasons. Usually happens when a 3rd-party ad fails without clear error protocols. Need to look into debug log for more information, please check with your Freewheel Support Team. Video Duration Mismatch Video player expecting different duration. Ensure duration requested is being respected. Ad Timeout Ad returns but does not render after a threshold of time. Let the player increase the timeout time by setting the respective timeout parameter (for example, on iOS video it should be "renderer.video.timeout".) If this does not work, look into debug log for details.  Media Format Not Supported The runtime doesn't support playing the current media format. Mainly for HTML5 video playback. Also used by iOS in SIMID, HTML, and VPAID renderers. Check if creative can be played in the environment. Unknown VAST Error Undefined VAST Error. Please check with your Freewheel Support Team. Ad Download Failure Network input/output error, usually happens when the renderer fails to download ad files. Can also be triggered by VAST wrapper limit exceeded. Check whether the ad URL still works. Check how many VAST wrappers are returned before a VAST inline response. No Renderer No renderer is selected. This usually happens when the required renderer is not configured correctly or compiled into mobile apps. Check player profile and see if the required renderer is included No Ad 3rd-party ad server doesn't return valid ads. Note this error is only counted when it can be recognized as a "no ad" situation, such as empty VAST response, or VAST response without valid ads. In comparison, VPAID 1.0 protocol allows creatives to throw errors, but does not specify a clear way to specify the error reason as "no ad", so VPAID ad cannot generate this error, but will only generate _e_unknown error instead. Notify 3rd party ad server (for example, VAST provider) and ask the server-side to fix the problem Distributor Pending Approval The approval for the associated creative is currently pending. (Some distributor and SVOD/OTT integrations require that the SVOD/OTT provider approves programmatic creatives before they can serve on the distributor's network.) Distributor Not Approved The associated creative has been rejected by theSVOD/OTT provider. (Some distributor and SVOD/OTT integrations require that the SVOD/OTT provider approves programmatic creatives before they can serve on the distributor's network.) Auction Metadata The Overview chart displays Healthy Bid Requests  versus Unhealthy Bid Requests and issue details based on the list of predefined auditing flags.  Chart Metric Description Overview Bid Requests – Healthy The bid requests that have passed the metadata audit check and are not flagged for any issues.  Bid Requests – Healthy is formerly known as Healthy Bid Requests.  Bid Requests – Unhealthy The bid requests that have not passed the metadata audit check.  Bid Requests – Unhealthy is formerly known as Flagged Bid Requests.  Bid Requests – Bypass The bid requests that have bypassed the metadata audit check for privacy compliance.  Bid Requests – Bypass does not contain historical data prior to May 6, 2025.  Response Rate – Healthy The response rate for healthy bid requests.  Response Rate – Unhealthy The response rate for unhealthy bid requests.  Issue Details Missing IFA Type IFA type was not declared within the ad request.The IFA type helps DSPs understand which name-space (eg, iOS) a particular IFA belongs to so that it can be used appropriately (eg, for audience targeting). Invalid IFA IFA passed evaluation within the ad request, but found it did not conform to the UUID spec, which has a format of 8-4-4-4-12. Missing App Bundle App bundle was missing from the bid request. IFA Type and App Bundle Mismatch Structure of the app bundle detected in the ad request did not match the IFA type declared in the ad request. Missing App StoreURL App Store URL was missing from the ad request. Invalid App StoreURL App Store URL was detected within the bid request but the structure was not a URL. Missing Site Domain Site domain was missing from the bid request. Invalid Site Domain Site domain was present but did not match the format of a domain. To isolate a particular trend, select a metric in the chart legend. The chart will show only the trend line for the selected metric. Click the metric again to revert changes. Users can also multi-select or multi-unselect metrics in the trend graph by holding the  Command  or  Windows  key and selecting a metric. Users can also utilize the Sync with Table functionality, which is toggled on by default, to further enhance the connectivity between Detailed Error Reason Trends and Breakdown Tables. When the Sync with Table function is toggled on, the Breakdown Tables will dynamically filter and sort for the most relevant view based on the error reason selected in the above trend chart. When the user selects error reasons in the trend chart for an isolated view, the Breakdown Tables will de-select all other error reasons and automatically sort by descending to highlight the most problematic dimensions.  Frequently Asked Questions What is the difference between Playback Rate and Render Rate?  The  Playback Rate is the percentage of primary programmatic ads that were played. This is calculated with the following formula: Playback Rate = Net Counted Ads / Selected Ads The  Render Rate  is the percentage of filled ads that were converted to action impressions. This is calculated with the following formulas:  If Invalid Traffic (IVT) is removed,  Render Rate = Net Counted Ads / Filled Ads If IVT is included,  Render Rate = Gross Counted Ads / Filled Ads The calculations revolve around determining the rate of actual impression conversions (i.e., how many of the ad opportunities actually resulted in impressions) relative to the   number of maximum potential impressions that could have been converted. This is calculated differently based on whether they are viewed from the supply perspective or the demand perspective. From the supply perspective, the maximum potential impressions are calculated based on the filled ads. A filled ad is an ad opportunity where both a primary ad and a fallback ad could potentially be served. However, since only one ad (either the primary or fallback) gets served for a given opportunity, the fallback ad is not counted separately in the conversion rate calculation. From the demand side, the maximum potential impressions include all times an ad is returned in the response, whether it's the primary or fallback ad. Even if an ad is returned as a fallback, it is still considered as a potential impression opportunity. What is the difference between Programmatic Device and Device Type?  A Programmatic   Device  refers to the type of the device associated with the programmatic transaction. This value is parsed from the OpenRTB specification, by default from the device.devicetype attribute. For example:  MOBILE_OR_TABLET PC CONNECTED_TV PHONE TABLET CONNECTED_DEVICE SET_TOP_BOX A Device Type  refers to the general category of the device(s) that ad requests associated with the site item came from, with each category returned in its own row. For example:  Personal Computer/Desktop Connected TV/CTV Phone Tablet Set Top Box Unknown In the Troubleshooting > Failed Bids breakdown tables on the Creative tab, why is there an Unknown creative? What does it mean, and what actions are there to take?  An  Unknown creative indicates that there is no valid ad in the bid response returned by the Demand Side Platform (DSP). This is most likely the cause for an Empty Ad ID error.  To diagnose this issue, switch to the DSP (or Bidding Buyer) tab in the breakdown tables and find which DSP (or Bidding Buyer) returns bids with  Empty Ad ID errors. Then raise the issue to the DSP (or Bidding Buyer) to identify the source of the issue.  In the Troubleshooting tab >  Pre-filtered Bid Requests, why is there no Creative tab?  During the Pre-filtered Bid Requests stage, the creative has not yet been retrieved, so no details about the creatives are available at this point. What is the difference between Candidate Level Error and Slot Level Error?  A Candidate Level Error occurs when a bid fails to serve in an ad request. This means the bid is not eligible for selection in any slot. Only one error reason will be logged for the whole transaction. Examples of candidate-level errors include Competition Failure and Profile Check Failed, both of which occur when attempting to assign a bid to a slot. To provide additional clarity on why the bid could not be assigned, we include Slot Level errors for these Candidate Level errors. A Slot Level Error  occurs when a bid fails to serve in one specific slot but may still be selected for another slot. Only one error reason will be logged for this slot. Examples of slot-level errors include Max Slot Duration Exceeded and Creative Profile Incompatible, which are child error reasons under Competition Failure and Profile Check Failed.  Why is Slot Level Error displayed as a percentage?  If a bid fails to serve in an ad request across all slots, each slot logs its own error, inflating the error count at the slot level. To maintain clarity in the funnel logic, slot-level errors are displayed as percentages. For example, in an ad request with four fillable slots, a bid goes through the following process: Slot 1: Bid filtered out due to Max Slot Duration Exceeded. Slot 2: Bid filtered out due to Back-to-Back Exclusivity. Slot 3: Bid filtered out due to Max Number of Ads Exceeded. Slot 4: Bid filtered out again due to Max Slot Duration Exceeded. At the transaction level, the bid is filtered due to Competition Failure. However, at the slot level, four errors are logged. If Programmatic Insights displayed slot-level errors, it would mislead users into thinking the bid was filtered four times. To avoid this, Programmatic Insights > Troubleshooting > Detailed Error Reasons Trend shows slot-level error reasons as percentages within the Competition Failure category: Max Slot Duration Exceeded: 50% Back-to-Back Exclusivity: 25% Max Number of Ads Exceeded: 25% What is known behavior in programmatic reporting when delivering on inventory? Under the following conditions: The deal delivers inventory purchased through a Purchased Order. Multiple order paths exist between the upstream inventory supplier and the current programmatic network in the transaction.  The current programmatic network maps different purchased orders to different Network Items in advance. This may lead to pre-delivery metrics being recorded on one Network Item, while delivery metrics are recorded on another one.  For example, NW A sells inventory to NW B via two orders. NW B placed Deal X targets on the purchased inventory from NW A and maps Order 1 to Site Section 1 and Order 2 to Site Section 2. When a request comes in, both orders are considered in the ad selection process. Deal X’s targeting overlaps with these orders, so the auction request sent to the DSP includes all deals found through both orders. While multiple eligible orders are present during the auction process, only one order is selected for delivery. This could result in a discrepancy between the order recorded for the auction and the one used for delivery. For example, Order 2 may be logged for the auction, while the actual delivery occurs through Order 1. Since NW B has mapped the orders to different site sections, pre-delivery metrics are logged on Site Section 2, and delivery metrics are logged on Site Section 1. See the example below:   Why is the number of ‘Others’ under the sankey chart in the performance tab does not equal to the  Troubleshooting > Ad Playback  errors under the troubleshooting tab? After selecting  ‘User Drop Off Removed’  then,‘Others’, in the sankey chart represents an approximation of the number of endpoint errors. However, it’s important to note that this value doesn’t necessarily equal the number of endpoint error callbacks we receive. Currently, ‘Others’ is calculated as selected ads minus net counted ads. In real-world terms, ‘Others’ just represents the gap between FW returned ads and the actual impressions we received. This gap can be caused by several factors: endpoint errors where the player failed to play the ad and sent an error callback to us, and FW also recognise that error callbacks; endpoint errors where the player failed to play the ad but sent their own error callback that FW couldn’t parse; or the player simply didn’t send any callback at all, so we don’t know if the ad was played or encountered an error. So it will result the inconsistent number between Others and the Total error counts in Troubleshooting > Ad Playback. Because Others contain above 3 situations, Total error counts in Troubleshooting > Ad Playback just contain the 1st scenario. Does this feature behave differently for FreeWheel SSP users? Yes  - FreeWheel SSP ad request counts may differ from ad server ad request counts. This is expected behavior. FreeWheel SSP applies request qualification and filtering logic before an opportunity is considered for monetization. As a result, some ad requests recorded by the ad server are intentionally excluded from FreeWheel SSP metrics, for example, when the system determines that an opportunity will not be processed.  Relevant actions:  Expand CSV Export Sync with Table Breakdown Tables The Performance page provides a standard breakdown table at the bottom of the page, providing users further data analysis options. Some commonly used dimensions are displayed by default.   Component Description Side Deal The unique, Freewheel-assigned identifier and user-specified name of the deal.  The formal agreement between a publisher and a buyer, delineating the terms and conditions for inventory buying and selling.  Demand DSP The unique, Freewheel-assigned identifier and name of the DSP (demand-side platform).  A Demand Side Platform is a system that allows buyers of digital advertising inventory to manage multiple ad exchange and data exchange accounts through one interface. Demand Player Profile The unique, Freewheel-assigned identifier and user-specified name of the player profile.  A player profile defines the specifications of the ad opportunities in the request. Supply Programmatic Device The type of the device associated with the programmatic transaction. This value is parsed from the OpenRTB specification, by default from the device.devicetype attribute. Supply Site The middle level of the Site Item hierarchy (Site Group → Site → Site Section). A Site is a collection of one or more Site Sections. A Site represents "where" content plays—for example, in the on-demand section of a mobile app—and is used to organize, manage, and sell specific inventory packages. Supply Site Section The most specific level of the Site Item hierarchy (Site Group → Site → Site Section). A Site Section belongs to exactly one Site. A Site Item represents "where" content plays—for example, in the on-demand section of a mobile app—and is used to organize, manage, and sell specific inventory packages. Supply Ad Unit Position The temporal or visual position of the ad unit class or instance. Supply App Bundle The platform-specific identifier of the app associated with a bid request. This value is only available for bid requests that come from an app (the value of  Programmatic Auction Type  is  App Request ). Supply Content Brand The standardized brand associated with the network item. A brand is a collection of channels. The Programmer, Brand, and Channel (if applicable) standard attributes are declared or detected together. Supply Country The country/countries that ad requests associated with the network item came from, with each country returned in its own row. Supply Endpoint Name The name of the endpoint(s) where a viewer watched the content associated with the site item, with each endpoint returned in its own row. Supply Endpoint Owner The owner of the endpoint(s) where a viewer watched the content associated with the site item, with each endpoint owner returned in its own row. Endpoint owners are typically programmers or MSOs (Multiple System Owners). Supply IFA Type IFA Type refers to the Identifier for Advertising Type used in FreeWheel's advertising technology. It is a classification of the type of identifier used for tracking and targeting advertisements across different devices and platforms. Supply Programmer The programmer (the network or producer) associated with the network item. The Programmer, Brand, and Channel (if applicable) standard attributes are declared or detected together. Supply Purchased Order The unique, Freewheel-assigned identifier and name of the purchased order.  Supply Site Domain The domain name of the website associated with a bid request. This value is only available for bid requests that come from a website (the value of  Programmatic Auction Type  is  Site Request ). Supply Sub Device Type The specific type of device(s) that ad requests associated with the site item came from, with each type returned in its own row. For example, if the device type is  Tablet , the sub device type might be  Android Tablet  or  iPad . Supply Sub Stream Type The specific stream type of the network item. Supply Supplier The unique, system-generated identifier and name of the supplier of the inventory. Supplier ID:  The unique, system-generated identifier of the supplier of the inventory. Supplier Name:  The name of the supplier of the inventory. Partner Name:  The name of the partner acting on behalf of the buyer specified in the demand partner's bid response. Supply Supply Source The supply origin of the inventory item. Supply Video Series The series that video assets belong to. Optional as some content (e.g., movies, special events, clips) may not belong to a series. Content that is apart of a series belongs to only the singular video series.   Supply Demand Type Specifies the particular demand type (also referred to as deal type) for the data displayed in the dashboard. Options include: Programmatic Guaranteed (PG) Non-PG Demand Open Exchange Rule The unique, system-generated identifier and name of the Open Exchange rule.  An Open Exchange rule is a programmatic transaction model that allows certain buyers to bid on certain inventory without targeting a specific deal ID in the bid request. Demand Relevant actions:  Expand CSV Export Table View Trend View Config Columns Add to Global Filter Quick Link Troubleshooting Actions Action Description Where is it? Switch to Real Time Mode  Selecting  Switch to Real Time Mode  toggles the programmatic performance data between Historical Mode and Real Time Mode.  Header Default View  Selecting  Default View  opens a dropdown that enables users to save filters and additional settings for future performance monitoring. Users can also reopen previously saved views.  Global Filters Expand    Clicking  Expand  extends the table/graph to full screen.  Pre-filtered Bid Requests,  Response Errors,  Failed bids,  Filtered bids,  Detailed Error Reasons Trend,  Breakdown Tables CSV Export    Clicking  CSV Export exports the data of the chosen widget to a CSV file. Pre-filtered Bid Requests,  Response Errors,  Failed bids,  Filtered bids,  Detailed Error Reasons Trend,  Breakdown Tables Sync with Table  Default setting. Toggling  Sync with Table  syncs selected Detailed Errors Reasons Trend legend with the Breakdown Tables columns.  Detailed Error Reasons Trend Table View  Default setting. Selecting this view displays data as a breakdown table.  Breakdown Tables Trend View  Selecting this view displays data as a Top 20 Entities Trend graph based on the selected  Metric , over time.  Config Columns  Clicking  Config Columns allows the user to configure the breakdown tables by selecting which column of dimensions and metrics to add or remove.  Add to Global Filter  Clicking  Add to Global Filter  applies the selected row's value to the corresponding global filter.  Quick Link  Clicking  Quick Link allows the user to access other pages of detailed information.