Fix DV360 PMP Under-Pacing: Bid Shading & Floor Guide
You push a high-impact $15.00 CPM Private Marketplace deal in Display & Video 360 (DV360) for a tier-one CTV campaign. Forty-eight hours after launch, your line item has served barely 1,200 impressions against a daily budget target of 100,000. The publisher insists their supply-side platform (SSP) sends hundreds of thousands of valid bid requests per hour. Your bid history shows thousands of bids submitted, yet your win rate sits below 3%. What broke between the publisher's SSP and your demand-side platform?
When a Private Marketplace (PMP) deal under-paces in DV360, traders often default to raising the fixed CPM or asking the publisher for more volume. Most of the time, neither action fixes the underlying bottleneck. Under-pacing in non-guaranteed deals usually stems from automated bid shading algorithms undercutting publisher price floors, gross-versus-net fee mismatches, or conflicting pre-bid targeting parameters stacked on top of deal rules.
Where Is the Impression Dropping? Tracing the Bid Lifecycle in DV360
Before changing line item settings, you must isolate the point of failure in the bid request chain. An impression opportunity flows through four distinct stages: Bid Requests Sent by SSP, Bid Requests Received by DV360, Bids Submitted by Line Item, and Bids Won.
Navigate to Inventory > My Inventory in DV360, select your target deal, and open the Impression Health tab. This panel breaks down real-time performance across the delivery funnel:
- Bid Requests Received: If this number is near zero, the issue lies outside DV360. Either the deal configuration (Deal ID, Publisher ID, Exchange) is mismatched, or the publisher is routing traffic to a different DSP seat.
- Filtered Bid Requests: Requests that reached DV360 but were blocked before reaching your line item. High filtering rates indicate targeting rules set at the Partner or Advertiser level (such as global blocklists or geography exclusions) rejecting bid requests upfront.
- Bids Submitted: The count of opportunities where your line item evaluated the bid request and attempted to submit an offer. If requests are high but bids submitted are low, your line item targeting (audiences, frequency caps, brand safety, flight dates) is rejecting the inventory.
- Win Rate (Bids Won / Bids Submitted): If bids submitted are high but win rate is below 15-20% on a PMP, your submitted CPM bid is dropping below the publisher's effective floor price or failing auction cleared price requirements.
How Dynamic Bid Shading Suppresses PMP Win Rates
Bid shading balances clearing price optimization with delivery velocity. In Open Auction transactions, DV360's bid shading algorithm evaluates historic clearing prices for identical impression attributes (domain, ad size, app bundle, device) and shades your maximum CPM bid down to the lowest estimated price needed to win the auction.
Problems arise when bid shading algorithms process Private Marketplace inventory as if it were Open Auction inventory. In a Private Auction or Preferred Deal, publishers establish hard clearing floors or private pricing mechanics within their SSP (such as Magnite, PubMatic, or Xandr). If a publisher sets a strict floor of $8.00 CPM and your line item operates with a Max CPM of $10.00 under automated bidding, DV360’s bid algorithm might attempt to shade your response bid down to $6.50 based on open-market impression valuations. The SSP instantly rejects the $6.50 response bid for violating the $8.00 deal floor.
The result is a silent delivery failure: DV360 reports thousands of bids submitted, but your win rate drops to near zero because every shaded bid falls below the publisher's hard floor.
| Deal Type | Pricing Model | Bid Shading Risk | Recommended DV360 Bidding Strategy |
|---|---|---|---|
| Preferred Deal (PD) | Fixed CPM (1:1 Clearing) | Low (Fixed Price) | Fixed Bid set to match agreed Deal CPM exactly |
| Private Auction (PMP) | Dynamic Floor / First Price | High (Algorithm shading below floor) | Custom Bidding or Fixed Bid override set 10-15% above floor |
| Open Auction (OA) | Dynamic First Price | None (Designed for shading) | Automated Maximize Conversions / Target CPM |
When running Private Auctions where under-pacing occurs, switch off pure automated bidding strategies like Maximize CPM or Target CPM if you lack historical conversion volume. Instead, implement a Fixed Bid strategy set slightly above the clearing floor, or utilize custom scripts. To optimize advanced programmatic strategies, consult our guide on DV360 Bid Multipliers for CTV Audience Extension to adjust pricing dynamically without relying on default DSP shading routines.
Resolving Floor Price Mismatches and Fee Discrepancies
A frequent cause of failed bids on PMPs is the discrepancy between Gross CPM and Net CPM bids. When you input a $10.00 CPM bid in DV360, that figure is not necessarily what the publisher's SSP receives as the clearing offer.
DV360 deducts media fees, partner fees, and third-party data/measurement costs based on your Advertiser budget configuration. If your line item is set to bid a $10.00 Max CPM Gross, and your partner stack includes a 12% DV360 platform fee, a $0.15 IAS pre-bid fee, and a 10% agency fee, the net bid submitted to the exchange drops significantly below $10.00.
Consider this concrete pricing flow for a $12.00 PMP floor price:
- Target Line Item Bid (Gross): $12.00 CPM
- DV360 Platform Fee (10%): -$1.20
- Pre-Bid Brand Safety Fee: -$0.18
- Data Management Platform (DMP) Segment Fee: -$0.50
- Net CPM Submitted to Exchange: $10.12 CPM
Because $10.12 is less than the publisher's $12.00 hard floor, the SSP rejects 100% of your incoming bids. You can resolve this issue by ensuring your line item bid settings explicitly account for net delivery values. For a broader breakdown of deal execution failures, see our deep-dive on Fixing DV360 PMP Deals Not Spending.
Targeting Layer Overload: The Silent PMP Killer
Private Marketplaces inherently narrow your total addressable audience. The publisher has already pre-filtered supply based on specific domain groups, premium placements, or first-party audience segments. When programmatic traders apply their standard Open Auction targeting stack on top of a PMP deal, delivery often collapse entirely.
Each additional targeting layer acts as an AND operator against the incoming bid stream. If you target a PMP deal delivering 500,000 requests daily, and then layer on strict geographic constraints, third-party audience segments, custom intent keywords, strict frequency capping, and pre-bid brand safety verification, your available request pool collapses to zero.
Common Targeting Conflicts in PMP Setup
Audit your line item for these four high-probability targeting conflicts:
- Pre-Bid Brand Safety Over-Filtering: Enterprise verification wrappers like DoubleVerify or IAS apply strict pre-bid domain and content category filters. If a publisher's PMP includes news or user-generated content sections, aggressive brand safety settings will block bid responses before they reach the auction. Learn how to diagnose and configure tolerance thresholds in our guide to Troubleshooting High IAS & DV Block Rates in DV360.
- Redundant Device and App Bundle Targeting: If you negotiate a CTV-specific PMP deal with a publisher, do not apply device-type filters (e.g., Connected TV only) or explicit App Bundle list inclusions at the line item level. If the SSP formats device IDs or app IDs slightly differently than DV360's taxonomy, valid CTV requests will be dropped.
- Aggressive Frequency Capping: Setting a strict frequency cap of 1 impression per 24 hours at the line item level on a small PMP deal quickly exhausts your eligible audience pool. Expand your frequency caps to 3-5 impressions per period, or shift frequency capping up to the Insertion Order (IO) level across all deals.
- First-Party Audience Match Rates: Layering first-party customer lists onto a publisher PMP requires high identifier match rates (IDFA, GAID, or PPID). If match rates drop below 20%, your line item will lack the scale needed to pace evenly.
Step-by-Step Diagnostic Sequence: Isolating Under-Pacing Root Cause
Follow this exact diagnostic protocol when a PMP deal under-paces or fails to spend. Work systematically from the DSP settings down to the raw server logs.
Step 1: Check Deal Health and Bid Loss Metrics
Navigate to DV360 > Inventory > My Inventory. Locate the deal and open Deal Health. Review the primary bid loss metrics over a 7-day lookback period:
- Look for "Lost to Floor Price" percentage. If this figure exceeds 20%, your bid is too low, or bid shading is pulling your CPM below the clearing threshold.
- Look for "Lost to Line Item Targeting" percentage. If this figure exceeds 40%, your targeting stack is overly restrictive.
Step 2: Isolate Line Item Targeting Rules
Duplicate the under-pacing line item. In the duplicated test line item, strip away all layered targeting rules: remove third-party audience lists, clear category exclusions, remove pre-bid verification vendors, and set frequency capping to unlimited. Keep only the Deal ID assigned to the line item. Allow the line item to run for 6 hours. If spending immediately normalizes, re-introduce your targeting layers one by one to identify the specific constraint causing the block.
Step 3: Audit Line Item Pricing and Bid Overrides
Change your bidding strategy from automated/shaded bidding to a Fixed Bid strategy. Set the Fixed CPM value 15% higher than the nominal deal floor agreed upon with the publisher to absorb DSP fees and currency fluctuations. If using multiple line items across large campaigns, utilize Structured Data Files (SDF) to quickly review bid strategy types and floor parameters across all active entities. For full SDF workflow execution, refer to our operational manual on How to Bulk Edit DV360 Line Items.
Step 4: Verify Log-Level Bid Responses via Ads Data Hub
If UI metrics show high bid request volumes but zero win rate despite high fixed bids, query your log-level data using Google Ads Data Hub (ADH). Run a query analyzing impression loss reasons filtered by your specific Deal ID and Insertion Order ID. Examine the precise field outputs for `loss_reason_code` to confirm whether the loss occurred DSP-side (e.g., budget cap reached) or exchange-side (e.g., seat ID validation failure).
What to Do Next When a Deal Refuses to Spend
If you complete all diagnostic steps and the deal continues to stall, the breakdown exists within the publisher's SSP setup. Send the publisher's ad operations team your exact DV360 Partner ID, Advertiser ID, Deal ID, and a screenshot of your Impression Health dashboard showing incoming request volumes.
Request that the publisher execute a live bid trace within their exchange logs (e.g., SpringServe, FreeWheel, or Google Ad Manager). Ask them specifically to confirm whether your seat ID is correctly mapped to the deal contract, whether your creative format (VAST version, video length, SSL compliance) passes their ad server validation rules, and whether their exchange floor price is operating as net or gross.
Frequently Asked Questions
Why does DV360 show bid requests received, but zero impressions delivered?
This occurs when incoming requests reach DV360, but your line item fails to respond or loses the subsequent auction. The primary causes are line item targeting filters rejecting the request criteria, pre-bid brand safety blocks, or bid shading algorithms submitting an effective net bid that falls below the publisher's SSP floor price.
How does dynamic bid shading impact PMP Deals compared to Open Auction?
In Open Auctions, bid shading optimizes efficiency by reducing your bid to the minimum required to win based on market clearing history. On PMP deals with hard price floors, bid shading can incorrectly discount your submitted bid below the publisher's minimum floor requirement, causing high bid volume with near-zero win rates.
Should I use gross CPM or net CPM when setting up a PMP line item bid in DV360?
You should calculate your target bid based on Net CPM received by the exchange. If your partner account assesses DSP fees, agency fees, or third-party verification costs dynamically at the line item level, adjust your base bid upward to ensure the final net offer transmitted to the SSP meets or exceeds the agreed deal floor.
What is the fastest way to test if line item targeting is blocking a PMP deal?
Duplicate the under-pacing line item, remove all audience, brand safety, contextual, and device targeting layers, and set the bid strategy to a Fixed CPM 10-15% above the deal floor. Run this unconstrained line item for 4-6 hours to isolate whether targeting rules or pricing mechanics are causing the under-pacing.