Nobid Reasons Reporting¶
Description¶
The NBR (No Bid Reason) u-Slicer is a reporting tool that provides detailed insights into bid rejection patterns and targeting validation performance across the DSP platform.
Report Categories¶
Source¶
Core: Validation performed by the core bidding engine
Node: Validation performed by distributed node services
Fail Level¶
Campaign: Rejection at campaign level (budget, flight dates, etc.)
Line Item: Rejection at line item level (targeting, frequency caps, etc.)
Creative: Rejection at creative level (format, assets, expiration, etc.)
Fail Reason¶
All nobid reasons listed in this document (e.g., inventory_type_targeting
, budget_check
, flight_dates
, etc.).
See No Bid Reason Description for details.
Additional Filters¶
Advertiser: Filter by specific advertiser account
Campaign: Filter by campaign ID or name
Line Item: Filter by line item ID or name
Creative: Filter by creative ID or name
Client ID: Filter by client account ID
Native Asset: Filter by native creative asset ID
Report Metrics¶
Attempted Targeting Checks: Total number of validation attempts for each targeting/budgeting check
No Bid Reason: Total number of failed validation checks (bid rejections)
Passed, %: Success ratio calculated as: (Passed / Attempted Targeting Checks) × 100
Shows the percentage of validations that passed
Allows easy identification of major failure points
Note
Due to the sampling methodology, the “Passed, %” metric may occasionally display as negative values (e.g., -2%). These should be interpreted as very low success rates.
How to Use NBR Slicer: Basic Analysis Workflow¶
Select Fail Reason uSlicer category
Apply Filters to select relevant filters thus narrowing down your analysis
Example: Filter by Line Item = 123 (“Sports_Video_Campaign_LI_123”)
Sort results by Attempted Checks (DESC) to see which checks are attempted most frequently
This shows the volume of validation attempts
Identify validation checks with the lowest Passed, % values
These represent the biggest optimization opportunities
Focus on improving targeting settings for these areas
Example Analysis Workflow¶
Filter: Line Item = 2345 (“Auto_Display_Retargeting_LI_2345”)
Order by: Attempted Targeting Checks (DESC)
Look for: Lowest Passed, % values
Result: Identify that
device_type_targeting
has 15,000 attempts but only 12% pass rateAction: Review and optimize device targeting settings
No Bid Reason Description¶
Inventory & Content Targeting¶
|
Bid rejected due to inventory type (ad type) mismatch (e.g., display vs video vs native ad format requirements not met) |
|
Bid rejected because the content type (web/app) and inventory type (ad type) doesn’t match campaign targeting criteria |
|
Bid rejected because the ad slot content type (web/app) doesn’t align with campaign targeting settings |
Device & Technical Targeting¶
|
Bid rejected due to device type mismatch (PC, Phone, Tablet, CTV) |
|
Bid rejected because the specific device model doesn’t match targeting criteria |
|
Bid rejected due to device brand or model targeting restrictions |
|
Bid rejected because the browser version doesn’t meet campaign requirements |
|
Bid rejected due to operating system version targeting mismatch |
Geographic Targeting¶
|
Bid rejected due to city-level geographic targeting mismatch |
|
Bid rejected because the user’s country or region doesn’t match campaign targeting criteria |
|
Bid rejected due to postal code (zip) geographic targeting mismatch |
|
Bid rejected because the Designated Market Area (DMA) doesn’t match targeting requirements |
Display & Creative Targeting¶
|
Bid rejected because the ad slot dimensions don’t match the campaign’s display size requirements |
|
Bid rejected due to banner type targeting mismatch (specific display banner format requirements) |
|
Bid rejected because the content or user language doesn’t match targeting criteria |
Audience & User Targeting¶
|
Bid rejected because the user doesn’t belong to required pixel-based audience segments |
|
Bid rejected due to LiveRamp audience segment targeting mismatch |
|
Bid rejected because the user doesn’t match LiveRamp first-party data segment criteria |
|
Bid rejected due to general audience segment targeting mismatch |
|
Bid rejected because the user doesn’t belong to required unified audience segments |
|
Bid rejected due to targeting group criteria mismatch |
Video Targeting¶
|
Bid rejected due to video MIME type mismatch (e.g., MP4, WebM format requirements) |
|
Bid rejected because video duration doesn’t match campaign targeting criteria |
|
Bid rejected due to VAST (Video Ad Serving Template) protocol version mismatch |
|
Bid rejected because video API framework doesn’t match requirements (VPAID, OMID, etc.) |
|
Bid rejected due to video orientation mismatch (portrait, landscape, square) |
|
Bid rejected because video placement type doesn’t match targeting (in-stream, out-stream, etc.) |
|
Bid rejected due to video start delay targeting mismatch (pre-roll, mid-roll, post-roll timing) |
|
Bid rejected because video skipping terms don’t align with campaign requirements |
Brand Safety & Content Filtering¶
|
Bid rejected due to blocked content categories (IAB content category filtering) |
|
Bid rejected because of blocked advertiser domains (competitive exclusion) |
|
Bid rejected due to domain allow/block list targeting rules |
|
Bid rejected because the URL doesn’t match allow/block list criteria |
|
Bid rejected due to app bundle ID allow/block list filtering (mobile app targeting) |
|
Bid rejected because IAB content categories don’t match targeting requirements |
Quality & Viewability¶
|
Bid rejected due to DoubleVerify viewability requirements not met |
|
Bid rejected because DoubleVerify contextual analysis doesn’t meet campaign standards |
|
Bid rejected due to DoubleVerify brand safety segment restrictions |
|
Bid rejected because of Integral Ad Science Invalid Traffic (IVT) detection |
|
Bid rejected because third-party tracking pixels/tags are not permitted |
Google-Specific Targeting¶
|
Bid rejected due to Google vendor type restrictions |
|
Bid rejected because of Google excluded attribute settings |
Programmatic & Marketplace¶
|
Bid rejected due to Supply-Side Platform (SSP) targeting restrictions |
|
Bid rejected because the buyer seat ID doesn’t match targeting criteria |
|
Bid rejected because private auction access is required but not available |
|
Bid rejected because no valid programmatic deals are present in the bid request |
|
Bid rejected due to Private Marketplace (PMP) deal seat validation failure |
|
Bid rejected because no targeted PMP deals are available for this request |
Frequency & Pacing¶
|
Bid rejected due to campaign-level frequency cap limits exceeded |
|
Bid rejected because line item frequency cap has been reached |
Native Creatives¶
|
Bid rejected because required native ad assets don’t match available inventory |
|
Bid rejected due to lack of relevant creative assets for the placement |
Budget & Campaign Status¶
|
Bid rejected due to insufficient campaign budget remaining |
|
Bid rejected because budget sampling validation failed |
|
Bid rejected because campaign budget is inactive during current time period |
|
Bid rejected due to emergency stop mechanism being activated |
|
Bid rejected because budget configuration data is not available |
|
Bid rejected because budget configuration is outdated and needs refresh |
|
Bid rejected due to missing budget object/configuration (line item, campaign, etc.) |
|
Bid rejected because the lambda value (bid control multiplier) is set to zero |
Flight & Timing¶
|
Bid rejected because current time is outside campaign flight date range |
|
Bid rejected due to time-based pixel firing restrictions or timing validation failure |
|
Bid rejected because the campaign, line item, or creative has expired |
Privacy & Compliance¶
|
Bid rejected due to GDPR compliance validation failure |
|
Bid rejected because user has opted out of targeted advertising |
System & Performance¶
|
Bid rejected due to Queries Per Second rate limit |
|
Indicates that this particular targeting check was successful (not a nobid reason) |
Note
Many entries show targeting_passed which indicates successful validation rather than rejection.
Some reasons appear multiple times, which is normal for different validation stages.
Budget v4 reasons suggest a specific budget management system version.
IAS, DV refer to major ad verification vendors (Integral Ad Science, DoubleVerify).