Read Supply Paths by publisher

See which publishers' requests LtvAdx bids on, at what price and against what floor, with a plain hint on what to change for each one.

Supply Path Optimisation, shown on the page as Supply paths, is a by-publisher view of the requests your seat sends LtvAdx. It answers one question: for which publishers does LtvAdx bid, and is your floor in the way?

It is not a comparison of different routes to the same inventory. Your seat calls LtvAdx directly, so there is one path, and the page only splits it by publisher. It covers your own seat's requests only.

Steps

  1. Open Supply Path Optimisation.
  2. Choose the date range. The page opens on the last 30 days. Days are in UTC.
  3. Read each publisher's row, ending with What to do.
  4. Select Export CSV to download the table.

The columns

ColumnWhat it shows
PublisherThe publisher whose channels the requests were for
RequestsYour seat's requests for that publisher's channels that reached a bidding decision
LtvAdx bid rateThe share of those requests LtvAdx bid on
Avg bid CPMThe average price of LtvAdx's bids, per thousand impressions, in US dollars
Avg floorThe average floor in your requests that had one
What to doA hint, explained below

The hints

HintWhen it appearsWhat to do
LtvAdx has no demand here yetLtvAdx did not bid on any request for this publisherLtvAdx has no advertiser targeting these channels. Nothing in your integration is wrong. Check again later, or lower the floor if you set a high one.
Floors above LtvAdx pricesThe bid rate is under 20% and your average floor is higher than LtvAdx's average bidLower the floor on those channels. A floor above what advertisers pay turns bids into no-bids.
HealthyNeither rule appliesNothing needed

These hints come from two simple rules. They are a prompt to look, not a score. "Healthy" says nothing about fees, quality or revenue.

Refused inbound requests

Below the table, Refused inbound requests lists the requests from your seat that LtvAdx turned away before deciding whether to bid, over the last 7 days, whatever dates you chose above. Each reason has a count and what to fix, then the latest refusals with the time, the imp.tagid and the request ID.

ReasonWhat to do
Unknown channel (imp.tagid)Set imp.tagid to the LtvAdx channel ID of a live channel.
Channel not allowed for your seatYour seat may request only the publishers LtvAdx allowed it. Ask LtvAdx to add this one.
No impression in the requestEach request needs one imp with a video object.
Over your request limitYour seat sent more requests per second than it is allowed. Slow down, or ask LtvAdx to raise it.

A request with a missing or wrong key can't be matched to your seat, so it is not listed here. LtvAdx staff can see those.

What the page does not show

  • No wins and no money. Whether a bid won your auction is not reported back, and the page shows no payments.
  • No refused requests in the table. A request with an unknown channel ID, for a publisher your seat isn't allowed, or over your limit is listed under Refused inbound requests instead. A request with a wrong key appears nowhere on this page. See Connect with OpenRTB.
  • No other sellers. You don't see how other exchanges reach the same publishers.

If something goes wrong

What you seeWhat to do
"No requests from your seat in this date range"Widen the dates, or check that the seat is switched on.
A publisher shows a name of "Unknown publisher"LtvAdx saw the request but couldn't match it to a publisher record. Contact support.
"Could not load"Try again. If it keeps failing, contact support.

Last reviewed 2026-11-08

Related guides

Contact support