Programmatic

Fix DV360 PMP Deals Not Spending: Ad Ops Troubleshooting Guide

When a Private Marketplace (PMP) deal in Display & Video 360 (DV360) fails to spend, the culprit is almost always a structural misalignment between the SSP's incoming bid requests and the DSP's line-item targeting. Unlike open exchange buying, PMP deals rely on a strict match of Deal ID, floor price, currency, and creative specifications. Resolving these bottlenecks requires systematic diagnostic work across both the DV360 console and SSP-side reporting.

Key Takeaways

  • Use the Deal Troubleshooter first: This native DV360 tool isolates exactly where the bid funnel breaks—whether at the incoming request stage, targeting filtering, or auction loss.
  • Keep targeting broad: Layering third-party audiences, hyper-local geotargeting, or strict device constraints on top of a curated PMP often shrinks the available bid pool to zero.
  • Account for SSP tech fees: Always bid 15% to 20% higher than the agreed-upon gross floor price to clear DSP/SSP margins and avoid floor-rejection errors.
  • Verify exchange-level enablement: Ensure the specific SSP exchange is globally enabled at both the Partner and Advertiser levels within your DV360 settings.

Step 1: Isolate the Funnel Stage via the Deal Troubleshooter

Begin the technical audit by opening the Deal Troubleshooter in the DV360 Inventory module. This tool provides a real-time visualization of the programmatic auction funnel. It breaks down the interaction into four key phases: incoming queries, matched queries, bids sent, and auctions won. Identifying where the volume drops to zero determines your course of action.

Zero Incoming Queries

If the troubleshooter shows zero incoming queries, DV360 is not receiving any bid requests from the publisher's SSP under that specific Deal ID. This is a supply-side issue. The publisher has either not activated the deal on their ad server (e.g., Google Ad Manager, Magnite, PubMatic), targeted the wrong DV360 Partner ID, or entered an incorrect Seat ID. You must contact the publisher's ad-ops team to verify that the deal is actively pushing traffic to your specific seat.

High Matched Queries but Zero Bids Sent

This state indicates that the publisher is sending the inventory, but your line-item settings are actively filtering out those opportunities. This occurs when there is a mismatch in creative sizes, targeting restrictions, or brand safety configurations. The DSP sees the inventory but is forced to pass on the bid.

High Bids Sent but Zero Auctions Won

Your line item is bidding, but the publisher's SSP is rejecting the bids. The primary cause here is bidding below the floor price, bidding in the wrong currency, or submitting creatives that violate the publisher's domain blocklists or ad-category restrictions.

Step 2: Resolve Deal ID and Exchange Configuration Errors

A frequent administrative oversight is a simple mismatch in the Deal ID or Seat ID. Deal IDs are case-sensitive and must not contain accidental leading or trailing spaces. When copy-pasting IDs from an email or external sheet, hidden formatting characters can corrupt the string in the DV360 interface.

Furthermore, ensure the parent exchange is authorized to transact on your account. Navigate to Partner Settings > Exchanges and verify that the checkbox for the target SSP is checked. If an exchange is disabled at the partner level, DV360 will silently drop all incoming bid requests from that SSP, regardless of individual deal configurations at the advertiser level.

Step 3: Calculate the Real Bid Price (Gross vs. Net Floor Dynamics)

Floor price discrepancies are a primary driver of PMP under-spend. The price agreed upon with the publisher is often a "gross" floor price, whereas DV360 operates on a "net" bid basis. If the publisher sets a floor price of $10.00, and your line-item bid is exactly $10.00, your bid will likely fail to clear the SSP's auction.

SSPs and DSPs apply tech fees that shave off a percentage of the bid. To guarantee your bid clears the publisher's floor, apply a buffer. If the floor is $10.00, configure your DV360 bid to at least $12.00 or $12.50. This accounts for the supply-path take-rate and ensures the net value reaching the publisher's ad server remains above their hard floor. Additionally, verify the currency settings. If the publisher's SSP is transacting in Euros (EUR) and your DV360 advertiser currency is USD, exchange rate fluctuations can cause your bids to drop below the floor on certain days. Always bid with a healthy margin to absorb these fluctuations.

Step 4: Eliminate the Over-Targeting Trap (Double Filtering)

Traders often treat PMPs like open exchange inventory, layering complex targeting criteria on top of the deal. PMP deals are already highly filtered by the publisher. For example, a publisher-curated sports PMP already contains sports-contextual inventory. Layering your own sports-contextual targeting or narrow first-party audience segments on top of that deal creates a "double filtering" effect that destroys scale.

Remove all unnecessary targeting parameters from the line item targeting the PMP. This includes:

  • Geographic restrictions (unless strictly required by legal mandates)
  • Strict device or browser operating system lists
  • Third-party audience data segments
  • Dayparting schedules

For specialized channels like Connected TV (CTV), keep targeting wide open. If you are buying a curated CTV deal, do not restrict the line item to specific device types or app environments, as this can prevent the bid from registering. For complex CTV campaigns, using advanced bidder features such as DV360 Custom Bidding for CTV SPO can help optimize performance without artificially choking your inventory supply.

Step 5: Audit Pre-Bid Verification and Brand Safety Filters

Pre-bid verification wrappers from DoubleVerify, IAS, or Oracle/Peer39 are designed to block risky inventory. However, when applied to premium PMPs, they can cause severe under-spending. These wrappers evaluate the page URL and content context in real time. If a premium publisher's page is flagged—even falsely—the DSP's pre-bid filter blocks the bid before it is sent.

If your deal is under-performing, check your brand safety settings. Highly restrictive settings (e.g., blocking all "unclassified" content or applying low-tolerance thresholds for standard editorial content) will decimate PMP scale. To isolate this issue, temporarily assign a standard, non-wrapped line item to the deal. If the deal starts spending immediately, your brand safety settings are too restrictive for the publisher's content structure. For a deeper look at how to resolve these verification conflicts without exposing your brand to actual risk, consult our guide on Troubleshooting High IAS & DV Block Rates in DV360.

Step 6: PMP vs. Programmatic Guaranteed (PG) Troubleshooting

It is critical to distinguish between non-guaranteed PMP deals and Programmatic Guaranteed (PG) deals, as their programmatic mechanics differ fundamentally. Non-guaranteed PMPs compete in a private auction where the buyer has no contractual obligation to bid, and the publisher has no obligation to deliver a set volume. If a PMP is not spending, the platform simply registers low bid activity.

With PG deals, the buyer commits to purchasing a set number of impressions at a fixed price, and the publisher guarantees that volume. Under-delivery on PG deals often triggers severe pacing alerts and requires a different verification path involving seller-side pacing configurations and synchronization of frequency caps. If your troubleshooting efforts are actually directed at a guaranteed contract rather than a flexible PMP, you should follow the specific steps outlined in our walkthrough on how to Fix DV360 Programmatic Guaranteed Under-Delivery.

Step 7: Creative Approval and SSP Mapping

Even if targeting and bidding are perfectly aligned, a deal will not spend if the creative is rejected. Programmatic creatives must pass two levels of approval: Google's internal DV360 creative audit and the individual SSP/publisher audit.

Check the "Creative Status" tab within your DV360 advertiser console. If the creative is flagged as "Pending" or "Rejected" by Google, it will not serve. If it is approved by Google but still not spending, check the SSP-specific approval status. Major SSPs like Magnite or Google Ad Manager run independent creative audits. If a creative contains heavy Javascript payloads, slow load times, or redirects to unapproved domains, the SSP will reject the creative at the exchange level, leading to silent bid rejection. Ensure your creative sizes match the exact dimensions specified by the publisher in the deal negotiation (e.g., 300x250 vs. 300x600).

Frequently Asked Questions

Why is my PMP deal showing zero bid requests in DV360?

This occurs when the publisher's SSP has not yet activated the deal, or the Deal ID/Seat ID has been entered incorrectly in the DSP. To resolve this, confirm with the publisher's ad-ops team that the deal is actively targeted to your exact DV360 Partner or Advertiser ID and that the deal status is set to "Active" on their ad server.

How does a gross floor price differ from a net floor price in DV360?

A gross floor price includes the SSP's technology fee, whereas a net floor price is the actual amount the publisher must receive after fees are deducted. DV360 bids on a net basis. To clear a gross floor price, you must set your DV360 bid roughly 15% to 20% higher than the publisher's stated floor to cover the SSP tech margin.

Can I use custom bidding algorithms on PMP deals?

Yes, you can apply custom bidding algorithms to PMP deals, provided the deal receives enough volume for the algorithm to train. However, because custom bidding relies on historical data and machine learning to score impressions, applying it to low-volume PMPs can cause the algorithm to bid too conservatively, resulting in under-spend.

Why does my PMP deal spend fine on one SSP but not another?

Each SSP has distinct floor dynamics, technology fees, currency conversion policies, and creative approval standards. An identical bid may clear on one SSP but be rejected on another due to differing tech-fee deductions or more stringent pre-bid brand safety evaluations on the SSP's side.