We recently wrote about the hell of debugging programmatic deals. 🔥😈

We thought it would be a good idea to take things a step further with a little tutorial for everyone getting their hands dirty trying to get those deals working. 😉

First, where exactly does the Deal ID stop working?

In a typical programmatic private marketplace (PMP) or curated deal, the chain looks like this:

A bid request (BR) is an auction opportunity sent towards a buyer; a bid response is the DSP's answer containing a bid. An impression is won only when that bid wins the relevant auction (a downstream ad-server decision can still affect actual ad serving).

SymptomFirst place to lookWho to involve
Deal ID not visible in the DSPBuyer seat, deal status, sync or manual registrationSSP / Curator + DSP
Very few sell-side BRsPlanner, eligible inventory, delivery rules, throttlingSSP / Curator
SSP BRs but none in DSP reportsRouting, buyer seat, bidstream filtering, report scopeSSP + DSP
DSP BRs but zero bid responsesActive line, budget, targeting, creative and internal auctionMedia trader / DSP
Bid responses but no winsBid versus floor, auction competition, creative auditDSP + SSP / publisher

These are troubleshooting starting points, not proof of root cause. Interface names and reporting definitions vary by platform; the same time period, seat, deal and format should be compared before escalating.

DEAL DISCOVERY

1. Why isn't the Deal ID appearing in the DSP?

My first instinct: a sell-side issue (the SSP or Curator seat), particularly the DSP_Seat_ID used when pushing the deal.

Check on the sell side (SS):

  • ✅ Has the Deal ID been pushed to the correct DSP_Seat_ID?
  • ✅ Is the deal active, within its flight dates and eligible for this buyer?
  • ✅ Has the buyer accepted or registered the deal in the DSP, where required?
  • ✅ If the seat and configuration look right, ask support to investigate SSP–DSP synchronisation.

A deal that does not automatically appear is not necessarily a sync failure: some DSP/SSP combinations require a manual Deal ID registration or buyer approval. Microsoft's deal troubleshooting guide details those possibilities.

SELL-SIDE VOLUME

2. What if the deal generates too few bid requests?

Start on the sell side. In the SSP or Curator planner, check whether your deal's configuration should be generating a large volume of bid requests (BRs).

  • ✅ Compare the planner's estimated eligible supply with the BRs actually sent.
  • ✅ Check format, inventory, site/app, geography, targeting and activation dates.
  • ✅ Look for QPS limits, supply filtering or throttling that may reduce the bidstream.
  • ✅ If the planner predicts substantial eligible traffic but requests remain scarce, investigate a possible delivery or synchronisation issue with support.

We have seen throttling affect the volume of requests reaching buyers, notably in our investigation into why DSPs avoid cookieless impressions.

A large planner estimate is not proof that every impression should generate an eligible bid request; the planner, routing rules and reporting may use different definitions or time windows.

SSP ↔ DSP ROUTING

3. The SSP reports lots of BRs, but the DSP reports none. Why?

This is the maddening one: the sell side says it is sending requests, while the DSP's Deal reporting shows... nothing. 😮‍💨

Start by comparing both sides:

  • ✅ Verify that the SSP or Curator is routing the deal to the correct buyer seat and DSP.
  • ✅ Check that the advertiser, insertion order (IO) and line items are active on the buying side (and any linked sell-side objects are active too).
  • ✅ Match the same Deal ID, time window, timezone, creative format and reporting definitions across platforms.
  • ✅ If all of those checks pass, request a synchronisation/routing investigation and, where available, a sample bid request.

My original shortcut was “SS problem”. It is a good first avenue of investigation, but it is not a definitive diagnosis: supply-side routing, bidder profiles, DSP filters and reporting differences can all produce this apparent gap.

BUY-SIDE BIDDING

4. The DSP receives BRs, but the SSP sees zero bid responses. What should the buyer check?

Now we are very likely dealing with a DSP-side bidding decision. The SSP knows that opportunities arrived, but the DSP chose not to respond (or the bid was rejected before reaching the SSP).

Ask the buyer for screenshots:

  • ✅ The Deal Troubleshooter view.
  • ✅ The Line Item Troubleshooter view.
  • ✅ The complete line-item set-up, including any relevant IO/Partner-level controls.

Then check:

  • ✅ Is the deal attached to an active line with a dedicated budget? (Otherwise the DSP may spend elsewhere.)
  • ✅ Are the creatives approved and eligible in the DSP?
  • ✅ Are targeting, frequency, pacing or brand-safety restrictions filtering all incoming requests?
  • ✅ Is the DSP losing its own internal auction before sending an external bid? (Look for bid or optimisation algorithms at Line / IO / Partner Centre level, depending on the DSP.)

On DV360, the Troubleshooter documentation explains filters for targeting, creatives, frequency, budget and internal auctions. (Screens and available diagnostics differ between DSPs.)

AUCTION & CREATIVE AUDIT

5. Bid responses are arriving, but no impressions are won. What next?

Now the DSP is bidding. But it still isn't winning anything. The cause can sit on either the buy side or the sell side.

  • ✅ Is the DSP's bid price too low? Check the bid strategy and any bidding algorithm at Line / IO / Partner Centre level.
  • ✅ Are the publisher's floor, the bid sent by the DSP and all layers of intermediary fees financially consistent?
  • ✅ Are any creatives blocked on the sell side? If the SSP supports it, retrieve the creative_IDs and review or approve them manually where authorised.
  • ✅ Is the SSP's creative audit domain being blocked by the ad safety / verification tool? Check the tool's integration and approved audit domains.
  • ✅ Is the bid losing to another bidder or to publisher-side ad-server prioritisation, even when technically valid?

Zero won impressions do not always indicate a technical failure. A valid bid may simply lose the auction; and for some integrations, a downstream ad-server auction can prevent a bid win from becoming a served impression. Microsoft/Xandr documents these distinctions.

Still no delivery? What information should you send to support?

And if, despite all these tips, it STILL doesn't work...

You'll have no choice but to... contact support! 😉

Just make sure you explain what you've already checked to save time. A useful support ticket includes:

  • ✅ Deal ID, seller SSP / Curator and DSP Seat ID.
  • ✅ DSP, advertiser, insertion order and line-item IDs as relevant.
  • ✅ Activation dates, timezone and precise reporting window.
  • ✅ Bid requests, bid responses, wins and any rejected-bid counters on both sides.
  • ✅ Screenshots of deal settings and troubleshooting views; sample bid requests if authorised.
  • ✅ The five checks already carried out and any error messages.

The goal is simple: fewer “can you send me one more screenshot?” emails... and faster activation. 😅

Why does this matter for programmatic curation and the French Open Web?

A Deal ID is supposed to simplify buying quality inventory. Yet the technical hand-off between sell side and buy side can still slow campaigns down. We've argued separately that giving SSP teams better access to DSP diagnostics could make troubleshooting much easier.

At GreyFox Ads, we're convinced that a high-quality French Open Web delivers real effectiveness for advertisers.

We offer:

Sources and further reading

Editorial note: the five troubleshooting scenarios come from our hands-on experience. Additional platform-specific checks and caveats are documented separately from that field observation; they are not claims that every DSP or SSP behaves identically.