Several problems here are likely costing you demand.
You declare these companies with INVENTORYPARTNERDOMAIN, so buyers check their app-ads.txt for impressions they sell on your behalf. Without it, that inventory can't be authorized.
Ask each partner to publish app-ads.txt listing their authorized sellers, or remove the declaration if the partnership has ended.
| Ad system | Account | Detail |
|---|---|---|
| - | - | Inventory partner partner-32.example has no readable app-ads.txt (status tls_error), so DSPs cannot authorize the inventory it sells for sample-streaming.tv |
| - | - | Inventory partner partner-24.example has no readable app-ads.txt (status not_found), so DSPs cannot authorize the inventory it sells for sample-streaming.tv |
| - | - | Inventory partner partner-22.example has no readable app-ads.txt (status not_found), so DSPs cannot authorize the inventory it sells for sample-streaming.tv |
| - | - | Inventory partner partner-28.example has no readable app-ads.txt (status empty), so DSPs cannot authorize the inventory it sells for sample-streaming.tv |
Buyers can't verify these accounts end to end, so paths through them fail validation. Stale lines can also keep authorizing accounts you no longer control.
Check each ID with the SSP. Remove lines for accounts you no longer use and update any that changed.
| Ad system | Account | Detail |
|---|---|---|
| altitude-arena.com | ••••CK | altitude-arena.com sellers.json has no seller_id ••••CK |
| altitude-arena.com | ••••1C | altitude-arena.com sellers.json has no seller_id ••••1C |
| google.com | ••••80 | google.com sellers.json has no seller_id ••••80 |
| contextweb.com | ••••69 | contextweb.com sellers.json has no seller_id ••••69 |
| freewheel.tv | ••••10 | freewheel.tv sellers.json has no seller_id ••••10 |
| freewheel.tv | ••••18 | freewheel.tv sellers.json has no seller_id ••••18 |
| siprocalads.com | ••••CK | siprocalads.com sellers.json has no seller_id ••••CK |
| siprocalads.com | ••••1C | siprocalads.com sellers.json has no seller_id ••••1C |
| appnexus.com | ••••16 | appnexus.com sellers.json has no seller_id ••••16 |
| yieldmo.com | ••••93 | yieldmo.com sellers.json has no seller_id ••••93 |
| admanmedia.com | ••••85 | partner-2.example sellers.json has no seller_id ••••85 |
| rubiconproject.com | ••••80 | rubiconproject.com sellers.json has no seller_id ••••80 |
| appnexus.com | ••••84 | appnexus.com sellers.json has no seller_id ••••84 |
| rubiconproject.com | ••••52 | rubiconproject.com sellers.json has no seller_id ••••52 |
| rubiconproject.com | ••••82 | rubiconproject.com sellers.json has no seller_id ••••82 |
Buyers check each DIRECT line against the SSP's sellers.json. When the SSP calls the account an INTERMEDIARY, supply-path tools treat the line as misdeclared and often route spend elsewhere.
Change these lines to RESELLER, or, if the account really is yours, ask the SSP to mark it PUBLISHER.
| Ad system | Account | Detail |
|---|---|---|
| aps.amazon.com | ••••4e | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| openx.com | ••••94 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| consumable.com | ••••98 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| indicue.com | ••••44 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| openx.com | ••••63 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| fasttvltd.com | ••••ee | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| onetag.com | ••••9c | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| omgstudios.com | ••••41 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| nobid.io | ••••69 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| mediafuse.com | ••••89 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| 33across.com | ••••AZ | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| themediagrid.com | ••••TI | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| lemmatechnologies.com | ••••29 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| onetag.com | ••••OB | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
| admanmedia.com | ••••25 | DIRECT line but sellers.json says INTERMEDIARY (should be RESELLER) |
These domains no longer resolve. The lines can't earn anything and make the file look unmaintained to buyers who audit it.
Remove every line for the exchanges listed below.
| Ad system | Account | Detail |
|---|---|---|
| spotxchange.com | ••••95 | spotxchange.com no longer resolves in DNS: its lines point at a retired exchange and can be removed |
| districtm.io | ••••56 | districtm.io no longer resolves in DNS: its lines point at a retired exchange and can be removed |
| engagebdr.com | 16 | engagebdr.com no longer resolves in DNS: its lines point at a retired exchange and can be removed |
The SSP lists these accounts as belonging to you. Declaring them RESELLER can make your direct supply look intermediated.
If you control these accounts, change the lines to DIRECT.
| Ad system | Account | Detail |
|---|---|---|
| dxkulture.com | ••••58 | RESELLER line, but sellers.json says this account is the publisher sample-streaming.tv itself (usually should be DIRECT) |
How the estimate works: revenue on the affected accounts × a 25%–67% discount. The high end assumes buyers value those impressions like unauthorized supply (a third of the RPM, per Index Exchange); the low end assumes only some buyers discount them. It's a rough range to help you prioritize fixes, not a measurement. Your SSP reports are the source of truth.
Get an alert the moment an SSP drops one of your seller IDs or a partner's app-ads.txt breaks.