Programmatic

Fixing DV360 Programmatic Guaranteed Under-Delivery

September 11, 2026

Programmatic Guaranteed (PG) deals carry a contractual obligation for 100% pacing, yet line items routinely under-deliver. When a PG deal stalls in Display & Video 360 (DV360), the failure stems from an asymmetry between publisher-side ad server settings and buyer-side DSP configurations, creative wrappers, or filtering logic. Because PG inventory is reserved, every lost impression represents contracted value left on the table. This guide provides an operational manual for programmatic traders and ad-ops leads to systematically isolate and resolve PG delivery failures.

Phase 1: Diagnostic Triage via DV360 Deal Troubleshooter

Never troubleshoot a PG deal by guessing at settings. Begin directly in the platform metrics to pinpoint where inventory drops in the bid stream.

Navigate to Partner or Advertiser level > My Deals, select the under-delivering deal, and open the Deal Troubleshooter. Analyze the metric progression across the core conversion funnel:

  • Bid Requests Received: The total volume of opportunities sent from the seller’s ad server (e.g., Google Ad Manager, FreeWheel) to your DV360 Partner ID for this specific Deal ID.
  • Bids Placed: The volume of requests where DV360 submitted an eligible creative back to the supply source.
  • Impressions Won: The total number of rendered impressions accepted and billed by the supply partner.

Diagnosing Funnel Drop-offs

Pattern A: Low or Zero Bid Requests Received. DV360 is not receiving inventory signals from the publisher. The issue lies entirely upstream in the publisher’s ad server targeting, Deal ID mapping, or SSP configuration.

Pattern B: High Bid Requests, Low Bids Placed. The publisher is sending inventory, but DV360 is actively filtering out requests before a bid is sent. The root cause is buyer-side targeting over-constraining the deal or creative non-eligibility.

Pattern C: High Bids Placed, Low Impressions Won. DV360 is responding to requests, but the publisher’s ad server or SSP is rejecting the response. This indicates creative rejection, VAST rendering errors, macro mismatch, or extreme latency timeouts in Server-Side Ad Insertion (SSAI) environments.

Phase 2: Resolving Buyer-Side DSP Filtering Bottlenecks

By industry definition, a Programmatic Guaranteed deal transfers targeting execution to the seller’s ad server. Layering DSP-level targeting on top of a PG line item creates competing parameters that breach the buyer-seller agreement and trigger bid filtering.

1. Eliminate Redundant Line-Item Capping and Targeting

Audit the assigned Line Item in DV360 for these common configuration errors:

  • Frequency Capping: Ensure frequency caps are disabled at the Line Item level. If a 1/24 frequency cap is enabled in DV360, the DSP will reject valid bid requests after a user receives one impression, preventing the line item from fulfilling its daily impression commitment. Capping must be managed exclusively within the seller’s ad server during inventory reservation.
  • Audience Lists: Remove first-party or third-party audience targeting attached to the PG Line Item. If audience targeting is required for the campaign, it must be baked into the publisher’s key-value pairing within Google Ad Manager (GAM) or FreeWheel prior to deal acceptance.
  • Geography, Dayparting, and Environment: Verify that line item geo-targeting does not conflict with the publisher’s targeting. If the publisher sets the deal to target the United States, but the DV360 line item is set to target specific DMAs, DV360 will drop every request originating outside those DMAs.

2. Pre-Bid Verification and Brand Safety Overlays

Verification wrappers (IAS, DoubleVerify, MOAT) applied at the DV360 Partner or Advertiser default level frequently suppress PG bids without generating explicit campaign alerts.

If pre-bid brand safety, contextual filters, or custom fraud thresholds are active on the PG line item, DV360 evaluates incoming bid requests against these parameters. If an incoming impression fails the pre-bid safety score, DV360 refuses to bid. Navigate to Line Item Settings > Brand Safety / Digital Content Labels and disable pre-bid blocking for PG inventory, relying instead on post-bid monitoring and publisher-side blocklists.

Phase 3: Creative Audit and Technical Compatibility

Creative rejection or technical mismatches account for a massive percentage of "High Bids Placed, Low Impressions Won" metrics.

1. Multi-Exchange Creative Approval Status

In DV360, navigate to Creative > Audit Status. A creative approved by Google may still be rejected by the specific exchange or publisher SSP (such as Magnite, PubMatic, or Index Exchange). Ensure the asset shows a clear pass status for the supply source hosting the deal. If the status reads "Pending" or "Rejected," re-submit the creative or contact the SSP deal desk directly for manual approval.

2. Format and Specification Strictness

  • Dimensions and Asset Types: Verify that creative dimensions match the deal agreement precisely. If a publisher sends a bid request for a 300x600 slot and the DV360 line item only has a 300x250 assigned, DV360 will not place a bid.
  • SSL Compliance: All creative assets, tracking pixels, and sub-requests must use secure secure protocol (`https://`). A single non-secure asset in a third-party tag will cause silent drop-offs across modern ad server stacks.
  • HTML5 File Size and Polite Load Limits: Ensure standard display assets do not exceed initial file size limits (typically 150KB for standard display). Overweight assets trigger ad server timeouts during impression rendering.

3. CTV and Video VAST Specification Bottlenecks

CTV and video PG deals are uniquely sensitive to VAST wrapper formats and bitrates.

  • Exact Duration Alignment: If the seller reserved a 30-second slot, the creative duration must be exactly 30.0 seconds. A video asset measuring 30.04 seconds will be rejected by ad server transcoders or SSAI stitchers.
  • VPAID vs. VAST in CTV: Never assign VPAID or JavaScript-wrapped creatives to Connected TV PG inventory. CTV native environments lack web browser rendering engines and will fail to execute JS logic, resulting in VAST Error 303 (No Ad Response) or VAST Error 400 (General Linear Error). Use pure VAST 3.0 or 4.x XML tags with raw MP4 media files.
  • Bitrate Constraints: Ensure video media files match standard platform delivery windows. Media file bitrates should generally sit between 15 Mbps and 30 Mbps for 1008p/4K CTV inventory, and under 2.5 Mbps for desktop/mobile video.

Phase 4: Publisher-Side and Ad Server Configurations

When DV360 registers low or zero bid requests received, the breakdown sits inside the seller’s ad server infrastructure. Escalate the issue to the publisher's yield team with specific diagnostic parameters.

1. Google Ad Manager (GAM) Setup Checks

If the publisher uses GAM, request that their ad ops team verify the following settings:

  • Line Item Type and Priority: PG deals in GAM must be booked as Sponsorship (Priority 4) or Standard (Priority 10) line items linked to Programmatic Direct. If misconfigured as a "Preferred Deal" or "Private Auction" line item type, GAM will treat inventory as non-guaranteed and process it through price-priority lookups, suppressing request volume.
  • Key-Value Target Matching: Verify that key-values appended to the GAM line item match the live inventory calls. If the publisher targets `pos=above_the_fold`, confirm that the live ad tags pass this exact key-value string.
  • Expected Creative Sizes: GAM must mirror every creative size assigned in DV360. Missing a multi-size option in GAM forces requests to drop before hitting the DSP bid stream.

2. FreeWheel Setup Checks (Video & CTV)

For premium video environment deals running through FreeWheel:

  • Ad Unit and Layout Assignment: Confirm that the Deal ID is bound to the correct slot profiles and placement positions (e.g., pre-roll vs. mid-roll).
  • Macro Syntax and Dynamic Parameter Passing: Ensure required macros—such as `[CACHEBUSTER]`, `[DEVICE_ID]`, and app bundle identifiers—are explicitly passed through the SSAI pipeline without syntax corruptions.

Phase 5: Automated Bulk Audits with Structured Data Files (SDF)

For accounts managing dozens of active PG deals, manual UI navigation is inefficient. Use Structured Data Files (SDFs) to audit line item compliance across bulk setups.

  1. Export an SDF for all active Programmatic Guaranteed Line Items via DV360 Tools > Bulk Management.
  2. Open the downloaded CSV and verify the following column values:
    • Frequency Amount: Ensure this field is set to Unlimited or blank.
    • Geography Targeting - Include: Ensure values align exactly with the contracted region without extraneous negative geo-polygons.
    • User List Targeting - Include: Must be empty.
    • Creative Assignments: Confirm active status and valid Creative IDs across all associated deal rows.
  3. Modify invalid values directly in the CSV and re-upload the file to DV360 to immediately strip problematic targeting parameters at scale.

Diagnostic Checklist Summary

Run through this operational sequence every time a PG deal drops below expected delivery pacing:

  • [ ] Check DV360 Deal Troubleshooter for Bid Request volume vs. Bid Response volume.
  • [ ] Confirm 0 frequency caps are applied in DV360 at the Line Item or Insertion Order level.
  • [ ] Strip third-party audience lists, device restrictions, and custom geo-targeting from the Line Item.
  • [ ] Set pre-bid verification (IAS, DoubleVerify) to post-bid monitoring only.
  • [ ] Verify creative approval status across exchange partners in DV360 Creative Audit.
  • [ ] Confirm video creative specs: VAST XML (no VPAID JS), exact duration matching, static MP4 files for CTV.
  • [ ] Request publisher ad server confirmation: GAM priority set to Sponsorship/Standard (Programmatic Direct) and Deal ID mapped correctly.

Following this checklist isolates structural mechanics from inventory constraints, restoring contractual delivery pacing to DV360 Programmatic Guaranteed campaigns efficiently.