Programmatic

Fix DV360 Programmatic Guaranteed Deal Under-Pacing

September 4, 2026

Diagnosing Programmatic Guaranteed Pacing Failures in DV360

Programmatic Guaranteed (PG) deals represent a contractual agreement in Google Display & Video 360 (DV360) where a publisher commits to reserving a fixed volume of inventory and a buyer commits to purchasing it at a fixed CPM. Unlike Private Marketplaces (PMPs) or Preferred Deals, PG line items rely on automatic execution: the buyer's Demand-Side Platform (DSP) is designed to bid automatically on 100% of the bid requests received for that specific Deal ID, provided the bid requests match basic technical criteria.

When a PG deal under-paces, the programmatic trader or ad-ops lead faces a high-priority operational blocker. Under-pacing indicates a structural breakdown in the bid-request-to-bid-response pipeline between the seller’s ad server (most commonly Google Ad Manager) and DV360. Troubleshooting requires systematic isolation of bid filtering, targeting mismatches, creative validation errors, and ad server prioritization settings.

1. Evaluate the Deal Health Diagnostic Funnel

The primary starting point for troubleshooting is the Deal Health module within DV360. Do not evaluate PG performance solely using high-level impression and spend reports. Open the deal in My Deals or navigate directly to the Line Item performance view to analyze the three core stages of the deal delivery pipeline:

  • Seller Bid Requests (Queries): The raw volume of inventory opportunities sent by the publisher's Supply-Side Platform (SSP) or ad server to DV360 for this specific Deal ID.
  • DSP Bids Sent: The number of times DV360 evaluated those requests and returned an eligible bid payload back to the SSP.
  • Winning Impressions (Bids Won): The number of submitted bids that cleared the publisher's ad server auction and rendered an active ad unit.

Comparing the ratios between these three metrics pinpoints the exact layer where delivery is failing:

  • Low Seller Queries: The breakdown is on the publisher's side. The publisher's ad server is not generating or routing bid requests to the Deal ID.
  • High Seller Queries, Zero or Low DSP Bids: The breakdown is on the buyer's side. DV360 is actively filtering out incoming bid requests due to campaign-level restrictions, creative errors, or targeting layering.
  • High DSP Bids, Low Winning Impressions: The breakdown occurs during auction execution or creative rendering. Common causes include line item latency, VAST wrapper timeouts, or ad server priority conflicts.

2. Strip Unintentional DSP-Level Targeting Layering

The foundational rule of Programmatic Guaranteed buying is straightforward: the seller manages audience and environment targeting; the buyer executes the media spend. Applying targeting criteria inside DV360 on top of a PG Line Item forces the DSP to evaluate and discard bid requests, directly violating the automated purchasing model and causing severe under-pacing.

Inspect the line item configuration and audit the following parameters:

Frequency Capping

Frequency caps must never be applied inside DV360 for a PG deal. If a publisher sends 100,000 bid requests for a targeted user, but a buyer sets a frequency cap of 3 impressions per user per day in DV360, the DSP will reject 99,997 bid requests. If frequency capping is required, it must be negotiated and executed within the publisher's ad server prior to contract push.

Audience Lists and Demographic Filters

Unless the deal was explicitly negotiated as a "PG with Audience Matching" setup—where a first-party or third-party audience list is linked inside the deal terms—ensure all audience targeting, remarketing lists, affinity segments, and demographic filters are cleared from the DV360 Line Item.

Geography, Language, and Device Targeting

If a publisher agrees to deliver impressions targeted to the United States, adding a secondary US geographic target inside DV360 creates location matching mismatches. Differences in IP geolocation databases between the publisher's ad server and DV360 will cause valid bid requests to be dropped. Set Geography, Language, Environment, and Device targeting to "No Restrictions" inside DV360 unless explicitly required by the contract terms.

Pre-Bid Brand Safety and Verification Filters

Pre-bid verification wrappers from Integral Ad Science (IAS), DoubleVerify (DV), or Oracle/Moat implemented directly within DV360 settings act as a hard bid filter. If an IAS pre-bid filter is set to block inventory with a viewability rating below 70% vCPM, or if strict contextual brand safety thresholds are enabled, DV360 will decline to bid on non-compliant requests sent by the seller. Disable pre-bid targeting filters on PG line items and rely on post-bid verification reporting for campaign auditing.

3. Audit Creative Status and SSP Verification Wrappers

A PG line item will not submit a bid if the assigned creative is unapproved, paused, or failing technical specs. Creative approval failure is the single most common cause of silent under-pacing.

Dual Audit Trait Status: Google vs. SSP Exchanges

In DV360, a creative asset must pass two independent approval workflows:

  1. Google In-House Policy Review: Verifies landing page function, SSL compliance, malware status, and basic ad content policies.
  2. Exchange / SSP Specific Audits: Third-party exchanges (e.g., Magnite, PubMatic, Xandr, Index Exchange) conduct separate programmatic audits. A creative approved by Google may still be rejected by an external exchange due to specific publisher constraints or missing macros.

Check the Creative Status tab in DV360 to confirm the creative is marked as "Approved" across both Google and the targeted SSP exchange associated with the PG deal.

CTV and Video VAST Technical Requirements

Video and Connected TV (CTV) PG deals carry strict VAST requirements. Technical discrepancies will lead to immediate bid rejections at the ad server level:

  • Exact Duration Alignment: If the deal is negotiated for a 30-second spot, the uploaded VAST video asset must measure exactly 30.00 seconds. An asset measuring 30.4 seconds will be rejected by ad servers strictly enforcing standard video slate durations.
  • Bitrate and File Transcoding: High-end CTV publishers frequently reject low-bitrate streams or non-mezzanine files. Ensure mezzanine files meet minimum bitrate benchmarks (typically 15 to 30 Mbps for HD/4K environments).
  • VAST Wrapper Redirection Limits: Ad servers enforce limits on nested VAST wrappers to prevent latency. If a DV360 video creative includes nested third-party tracking wrappers (e.g., Innovid wrapper surrounding an IAS wrapper surrounding a DV360 asset), the ad server may hit a 3-second timeout limit and drop the request.

4. Resolve Bid Loss via Offline Reports and SDF Audits

When the Deal Health UI does not provide sufficient detail, run an offline report to surface precise bid rejection codes.

Create an Offline Instant Report or Standard Bid Loss Report inside DV360 using the following dimensions and metrics:

  • Dimensions: Line Item ID, Deal ID, Bid Loss Reason, Creative ID.
  • Metrics: Seller Queries, Bids Sent, Impressed Count, Filtered Bids.

Analyze the Bid Loss Reason output. Common actionable codes include:

  • Creative Filtered - Pending Audit: The assigned creative has not completed manual or automated review by the exchange.
  • Creative Filtered - Size Mismatch: The creative dimensions assigned inside DV360 do not match the placement sizes requested by the publisher's ad server.
  • Targeting Mismatch - Pre-Bid verification: Third-party brand safety settings inside DV360 rejected the impression opportunity before bidding.
  • Advertiser Blocked by Publisher: The publisher's GAM instance has an active Category, Domain, or Advertiser exclusion blocking the specific DV360 Advertiser ID.

To audit settings at scale, download a Structured Data File (SDF v6) for the affected Line Items. Verify that values for Frequency Cap, Pre-bid Filtering, and Targeting Inclusion/Exclusion are correctly flagged as empty or false across all columns.

5. Verify Financial Parameters and Pricing Mechanics

Pricing discrepancies can prevent bid execution even when targeting and creative configurations are flawless.

Gross vs. Net Pricing and Fee Deductions

Verify whether the fixed CPM agreed upon in the RFP matches the floor price set inside DV360. If the deal was negotiated at a $12.00 CPM Net, but the DV360 line item applies active agency fees, tech fees, or third-party data fees that are configured to deduct from the gross bid price, the net bid returned to the publisher may fall below the fixed $12.00 threshold, causing the publisher's ad server to reject the bid.

Currency Conversion Skew

If the publisher's GAM instance trades in Euros (EUR) while the DV360 Partner level is set to US Dollars (USD), currency conversion rates applied during real-time bid processing can introduce minor fractional cent differences. If the exchange rate fluctuates slightly, a bid sent from DV360 may clearing-price fail by fraction-of-a-cent margins. Ensure currency alignment is explicitly locked during the initial negotiation within the DV360 Marketplace tool.

6. Seller-Side Ad Server Verification Requirements

If DV360 shows low query volume despite correct DSP configuration, the operational breakdown resides within the publisher's ad server. Programmatic traders should issue a formal diagnostic request to the publisher's ad-ops team specifying the parameters to check:

  • GAM Line Item Priority: Confirm that the deal is booked in Google Ad Manager as a Programmatic Guaranteed line item type (Priority 12). If the publisher accidentally booked the deal as a Private Marketplace (PMP / Price Priority - Priority 12/14) or Preferred Deal, it will not receive guaranteed allocation in the ad server.
  • Sponsorship Competition: Check if a high-priority direct-sold non-programmatic Sponsorship line item (Priority 4) is operating on the same ad units without inventory reservation safeguards, starving the PG deal of impression calls.
  • Key-Value Targeting Mismatches: Verify if custom targeting Key-Values attached to the GAM Line Item match the active tags deployed across the publisher's digital properties. Missing key-values on specific site sections will halt seller query generation.

4-Hour Protocol for Resolving PG Under-Pacing

  1. Hour 1 - Funnel Diagnosis: Check DV360 Deal Health. Compare Seller Queries vs. DSP Bids Sent. Determine whether the issue is query starvation (seller side) or bid filtering (buyer side).
  2. Hour 2 - Configuration Reset: Open the DV360 Line Item. Remove all DSP-level audience lists, frequency caps, geo-targeting layers, and pre-bid brand safety filters. Ensure creative duration and dimensions match the inventory spec precisely.
  3. Hour 3 - Bid Loss Reporting: Run an Instant Bid Loss Report filtering by Deal ID. Identify the exact top 3 bid loss reasons (e.g., audit status, size mismatch, pricing calculation error).
  4. Hour 4 - Escalation & Execution: If bids are dropping due to creative approvals, notify the exchange audit team or re-upload compliant assets. If seller queries are zero, send a diagnostic email to the publisher with the exact Deal ID, DV360 Advertiser ID, and a screenshot of the 0-query Deal Health dashboard requesting a GAM line item review.