Programmatic

Fix DV360 Programmatic Guaranteed Underpacing: Ad Ops Checklist

November 10, 2026

A $50,000 Programmatic Guaranteed (PG) campaign launches with a tier-one publisher on Monday morning. By Thursday, Display & Video 360 (DV360) shows $4,200 spent and an overall impression pace of 28%. The client’s key product launch is 48 hours away, and the publisher’s yield team insists their ad server is pushing 100% of the promised bid requests. You are trapped in the classic ad-ops standoff: DSP reporting blames SSP bid volume, while SSP reporting blames DSP bid response rates.

In a Programmatic Guaranteed setup, the buyer promises to purchase 100% of the inventory pushed by the seller that matches the agreed-upon criteria, and the seller promises to reserve that inventory exclusively. When a PG deal underpaces, the breakdown stems from system-level targeting friction, creative misconfigurations, pre-bid verification blocks, or SSP-to-DSP sync delays. This troubleshooting guide walks through the exact diagnostic steps required to isolate the failure point and restore delivery.

Why Do Programmatic Guaranteed Deals Underpace in DV360?

To fix an underpacing PG deal, you must first understand how DV360 processes incoming bid requests for guaranteed inventory. Unlike Private Marketplaces (PMP) or Open Auction lines where DV360 evaluates bids based on performance algorithms and bid valuation models, PG line items operate under a strict execution rule: if a bid request matches the Deal ID, DV360 must submit a bid at the agreed CPM, provided the impression satisfies basic execution conditions.

Underpacing occurs for two primary reasons:

  • Upstream Shortfalls (Publisher/SSP side): The publisher is not sending enough bid requests matching the exact Deal ID, target parameters, or environment agreed upon during negotiation.
  • Downstream Filtering (Buyer/DSP side): DV360 is actively rejecting or dropping bid requests before a bid response can be generated due to line-item targeting over-constrain, creative rejection, or third-party verification blocks.

To systematically identify which side of the pipe is leaking, run through this five-step technical checklist.

Step 1: Check the DV360 Troubleshooter and Deal Health Status

Start your diagnosis directly inside the DV360 interface. Do not edit line-item settings until you review the built-in diagnostic metrics.

  1. Navigate to Inventory > Deals in your DV360 partner or advertiser account.
  2. Locate the underpacing PG Deal ID and open the Deal Health panel.
  3. Analyze the four key deal metrics:
    • Bid Requests: The raw volume of impression opportunities sent by the publisher's SSP to DV360.
    • Eligible Impressions: The volume of bid requests that passed basic DSP-level checks (e.g., active IO/LI status, valid flight dates, matching deal parameters).
    • Bids Placed: The number of actual bid responses sent back to the SSP.
    • Impressions Won: The total impressions successfully rendered and billed.

Evaluate the drop-off ratios between these stages. If Bid Requests are significantly lower than the publisher’s daily committed volume, the issue lies upstream in the publisher's ad server (e.g., Google Ad Manager, Magnite, FreeWheel). If Bid Requests are high, but Eligible Impressions or Bids Placed drop precipitously, DV360 is filtering the bids. For broader execution mechanics across non-guaranteed deals, read our guide on troubleshooting non-spending PMP deals.

Step 2: Audit Buyer-Side Targeting Layering (The #1 PG Sin)

The single most frequent operational mistake in PG execution is layering targeting restrictions on top of a PG line item in DV360. When negotiating a PG deal, targeting (such as geo, age/gender, key-values, or environment) should be handled entirely on the seller’s ad server prior to contract acceptance.

When you apply additional buyer-side targeting in DV360, the DSP evaluates incoming bid requests against these filters. If a request does not match, DV360 drops the bid. Because the publisher reserved inventory based on unfiltered availability, your line item will underpace rapidly.

Targeting Audit Steps:

  • Geography: Remove all geo-targeting from the DV360 line item unless explicitly agreed that the buyer would handle geo-filtering. Verify whether the publisher is passing the expected country/region signals in the OpenRTB bid stream.
  • Audience Lists: Remove all 1st-party and 3rd-party audience segments attached to the line item. Applying a 1st-party list to a PG deal turns it into a targeted audience extension, which drastically reduces reach.
  • Frequency Capping: Confirm frequency capping is set to No Cap at the Line Item and Insertion Order level. PG contracts assume every impression sent will be bought. If a cap is applied, DV360 will reject bid requests once individual user thresholds are met.
  • Brand Safety & Categories: Check for restricted content categories, domain blocklists, or app blocklists applied at the advertiser level that might silently block publisher impressions.

If you suspect targeting restrictions are choking delivery, refer to our comprehensive step-by-step manual on how to fix DV360 Programmatic Guaranteed underpacing caused by settings misalignment.

Step 3: Verify Creative Approval Status and VAST Handshakes

A deal can have millions of incoming bid requests, but if no creative is eligible to serve, the bid response rate drops to zero. Creative mismatches are especially common in CTV and video PG deals.

1. Check Approval Status Across All Exchange Entities

Navigate to Creatives in DV360 and inspect the Audit Status column. A creative must be approved by both Google and the specific SSP handling the transaction (e.g., Google Ad Manager, Xandr, PubMatic). If the status shows Pending or Rejected for the deal's exchange, DV360 cannot place a bid.

2. Audit Technical Creative Specifications

Ensure the creative asset matches the exact requirements of the publisher’s ad unit:

  • Secure URLs: All asset calls, tracking pixels, and third-party wrappers must use valid HTTPS protocols.
  • Video Bitrate & Duration: CTV publishers strictly enforce maximum video bitrates (often 15–30 Mbps for high definition) and rigid duration limits (exactly 15s or 30s, non-skippable). A 15.2-second video asset will cause the publisher's ad server to reject the bid.
  • VPAID vs. Native VAST: Most CTV environments flatly reject VPAID wrappers. Ensure your video line items utilize pure VAST 3.0 or 4.0 tags with HTML5 or native MP4 fallback assets.

If you notice VAST response timeouts or tracking errors in your video reporting, review how to fix VAST Error 303 in DV360 to resolve empty XML responses and failed creative renders.

Step 4: Analyze Pre-Bid Verification & Third-Party Block Rates

Integrating pre-bid brand safety, fraud, and viewability targeting via Integral Ad Science (IAS), DoubleVerify (DV), or Oracle/Moat creates invisible underpacing bottlenecks in PG deals.

When third-party pre-bid verification is active, the vendor’s SDK or wrapper evaluates the incoming bid request signals before DV360 submits a response. If the vendor flags the impression as high risk, low viewability, or non-brand-safe, DV360 refrains from bidding. Since the publisher has reserved this impression specifically for your deal, every vendor block results in an unfulfilled impression that cannot be recovered easily.

To diagnose vendor-level filtering, pull a Verification Custom Report in DV360 with the following metrics and dimensions:

  • Dimensions: Line Item, Deal ID, Pre-Bid Vendor, Rejection Reason.
  • Metrics: Pre-Bid Blocked Impressions, Total Eligible Impressions.

If the report reveals high block rates (e.g., over 3–5%), temporarily set the vendor verification settings to Monitoring Only or adjust brand safety thresholds in consultation with the publisher. For a deep dive into vendor wrappers and settings optimization, see our guide on troubleshooting IAS and DoubleVerify block rates.

Diagnostic Signals: Pinpointing Root Causes

Use this diagnostic reference table to match observed DV360 Troubleshooter metrics with the appropriate root cause and corrective action:

Diagnostic Signal / Metric Ratio System Indication Primary Root Cause Immediate Action Item
Bid Requests = Very Low / Zero
Contracted Volume = High		 Publisher ad server is not sending traffic to DV360. Deal ID incorrectly mapped, flight dates mismatched, or seller priority settings misconfigured in GAM/SSP. Contact publisher yield team. Demand SSP bid logs showing requests generated for the exact Deal ID.
Bid Requests = High
Eligible Impressions = Low		 DV360 is filtering incoming bid requests. Buyer-side targeting applied (Geo, Audience, Device, Frequency Capping) on the DV360 line item. Strip all line-item targeting. Ensure frequency caps are disabled across IO and LI hierarchy.
Eligible Impressions = High
Bids Placed = Low / Zero		 DV360 cannot assemble a valid bid response. Creative audit rejection, unapproved exchange status, or missing secure HTTPS wrapper protocol. Check Creative Audit tab in DV360. Re-upload or re-assign approved, compliant creative assets.
Bids Placed = High
Impressions Won = Low		 Bids are submitted but rejected upstream by SSP or ad server. Creative duration/bitrate mismatch, VAST timeout (Error 303), or pre-bid verification wrapping failures. Validate VAST tags in Google Video Suite Inspector. Remove VPAID wrappers on CTV environments.

Step 5: Execute the Publisher Alignment & Escalation Protocol

When internal checks confirm that line-item targeting is clean, creatives are approved, and verification filters are off, the issue resides on the publisher's side. Follow this structured escalation protocol to align with the seller’s ad ops team:

  1. Export the DV360 Deal Health Snapshot: Take a clear screenshot or export a CSV showing total Bid Requests, Eligible Impressions, Bids Placed, and Impressions Won over the last 72 hours.
  2. Request SSP-Side Bid Logs: Ask the publisher’s programmatic yield manager for an extract from their SSP (e.g., Google Ad Manager yield report) showing:
    • Total Matched Ad Requests for the Deal ID.
    • Total Bids Received from DV360 (Buyer ID / Partner ID).
    • SSP-Level Error Codes or Rejection Reasons (e.g., floor price breach, creative size mismatch, latency timeouts).
  3. Verify Rate Type and Pricing Floors: Confirm whether the deal was set up as Fixed CPM or Auction Automatic. Ensure that the price floor configured in the publisher’s SSP matches the exact CPM committed in the DV360 deal negotiation window.
  4. Check SSP Seat & Buyer ID Mapping: Confirm that the publisher routed the deal to your specific DV360 Partner ID or Advertiser ID. If the deal was pushed to an incorrect seat, DV360 will receive zero bid requests despite the publisher seeing active delivery attempts in their system.

Immediate Action Steps to Recover Underpaced Delivery

To rescue a campaign that is behind schedule, perform these four immediate steps right now:

  • Remove all Line Item Constraints: Open the underpacing PG line item in DV360 and set all targeting parameters (Geo, Technology, Audience, Dayparting, Demographics) to broad/unrestricted.
  • Turn Off Pre-Bid Verification: Transition IAS, DoubleVerify, or Oracle pre-bid rules from Block to Monitor within the line-item properties.
  • Assign Backup Creatives: Assign at least two alternative, fully approved creative assets (standard display or static MP4) to prevent downtime if primary video tags encounter render errors.
  • Request a Publisher Push / Make-Good Alignment: Notify the publisher immediately of the unspent balance and request an agreement in writing to burst delivery over the remaining flight days or extend the deal end date.

Frequently Asked Questions

Why is my PG deal showing high bid requests but zero impressions won?

This gap typically indicates that DV360 is receiving requests but failing to bid due to creative rejection, or that bids are being placed but rejected by the publisher's SSP because of technical specifications like duration, bitrate, or SSL compliance errors.

Should I apply frequency capping to a Programmatic Guaranteed line item in DV360?

No. Applying frequency capping to a PG line item in DV360 will cause severe underpacing. The publisher has reserved contractually agreed impression volume based on unfiltered reach; dropping bids due to frequency caps violates the deal conditions and prevents full budget utilization.

How quickly do performance changes take effect after fixing creative or targeting issues in DV360?

Targeting changes in DV360 reflect in the bid stream within 15 to 30 minutes. Creative re-audits or SSP approval syncs can take anywhere from 2 to 24 hours depending on the exchange involved.

What happens if a Programmatic Guaranteed deal finishes underpaced in DV360?

Unlike fixed direct insertion orders where advertisers are invoiced based on delivered impressions, PG deals in DV360 bill only on actual rendered impressions won. However, underpacing damages publisher relationships and fails to execute the client's planned media commitments, requiring manual flight extensions or make-good negotiations.