Key Takeaways

• ads.txt data reveals revenue leaks when cross-referenced against sellers.json and SSP performance. The file itself is just authorization. The insights come from comparing it against other data sources.
• The biggest leaks come from verification failures, not missing entries. A present but mismatched entry often costs more than a missing entry because it creates false trust signals.
• Revenue leaks compound across SSPs. A 10% CPM reduction on three SSPs that each carry 15% of your revenue adds up to a 4.5% total revenue loss.
• Most publishers have multiple leaks they don't know about. BeamFlow's data shows 24% of ads.txt entries have some sellers.json verification issue.
• Fixing leaks is free and immediate. Unlike content improvement or traffic acquisition, supply chain fixes have no cost and take effect within days.

---

How to Spot Revenue Leaks Using ads.txt Data

Revenue leaks in programmatic advertising aren't like a broken pipe where water pours out and you notice immediately. They're more like a slow pressure drop.

Everything works, the water flows, but the volume is less than it should be.

ads.txt data is the diagnostic tool. Cross-reference your ads.txt against sellers.json, SSP revenue data, and supply chain signals, and you can identify exactly where revenue is being lost and why.

Leak Type 1: Authorization Gaps

What It Is

An SSP sells your inventory but isn't listed in your ads.txt. DSPs that check ads.txt reject the bid or discount it heavily.

How to Spot It

Compare your list of active SSP integrations against your ads.txt entries. Any SSP that receives ad requests from your ad server but isn't in ads.txt is an authorization gap.

Quick check: Count your active SSP integrations. Count your ads.txt DIRECT entries. If the numbers don't match, you have a gap.

Revenue Impact

Authorization gaps eliminate 100% of verified demand through the unauthorized path. The SSP still runs auctions, but only DSPs that don't enforce ads.txt bid.

Fix

Add the missing SSP entry with the correct account ID and relationship type.

Leak Type 2: Identity Verification Failures

What It Is

Your ads.txt entry exists, but the corresponding sellers.json entry is missing, confidential, or has incorrect data. The DSP passes the authorization check but fails the identity check.

How to Spot It

For each SSP in your ads.txt, check their sellers.json for your account ID. Flag any entry that is:

• Missing: Account ID doesn't appear in sellers.json
• Confidential: Entry is marked is_confidential: true
• Mismatched: Domain, name, or seller_type doesn't match expected values

Use BeamFlow's scanner to automate this across all SSPs simultaneously.

Revenue Impact

Identity verification failures reduce effective CPMs by 10-50% depending on the specific issue and how many DSPs enforce sellers.json. Missing entries have the biggest impact. Confidential entries have a moderate impact. Minor mismatches have the smallest impact.

Fix

Contact each SSP with issues. Provide your correct account information, request non-confidential status, verify the fix after the SSP confirms the change.

Leak Type 3: Relationship Type Mismatches

What It Is

Your ads.txt says DIRECT but the SSP's sellers.json says INTERMEDIARY (or vice versa). This inconsistency flags the supply path as untrustworthy.

How to Spot It

Cross-reference the relationship type in each ads.txt entry:

• DIRECT in ads.txt should match seller_type: PUBLISHER in sellers.json
• RESELLER in ads.txt should match seller_type: INTERMEDIARY in sellers.json

Any mismatch is a leak.

Revenue Impact

Relationship type mismatches raise fraud flags in DSP verification systems. The impact is 10-25% CPM reduction, plus potential exclusion from premium campaigns that require clean verification.

Fix

Determine the correct relationship type. If you have a direct contract and payment relationship with the SSP, it should be DIRECT/PUBLISHER. If an intermediary is involved, it should be RESELLER/INTERMEDIARY. Update your ads.txt or ask the SSP to update their sellers.json to match the actual relationship.

Leak Type 4: Reseller Path Leaks

What It Is

Your SSP resells your inventory through exchanges or resellers that aren't in your ads.txt. The downstream supply paths are unauthorized.

How to Spot It

Ask each SSP if they resell your inventory. Check for RESELLER entries in your ads.txt. If your SSP confirms reselling but you have no corresponding RESELLER entries, the downstream paths are leaking demand.

Revenue Impact

Varies by how much demand flows through the unauthorized reseller paths. If a big DSP only accesses your inventory through the unauthorized path, the impact is high.

Fix

Add RESELLER entries for legitimate resellers. Ask SSPs to stop reselling through unauthorized channels.

Leak Type 5: SSP Performance Divergence

What It Is

Not all verification issues are visible in the data. Sometimes the only signal is that an SSP is underperforming relative to peers without an obvious explanation.

How to Spot It

Compare CPMs across your SSPs. If one SSP consistently delivers 20-30% lower CPMs than similar SSPs carrying comparable inventory, check its supply chain data:

• Is your sellers.json entry clean on that SSP?
• Does the SSP support schain?
• How many intermediaries are in the typical supply path through that SSP?

Performance divergence often correlates with a supply chain issue that the publisher hasn't identified.

Revenue Impact

Depends on the underlying cause. Could be 5-30% lower CPMs on the affected SSP.

Fix

Investigate the specific supply chain characteristics of the underperforming SSP. The cause might be a sellers.json issue, a long supply path, or an SSP-side configuration problem. Address the root cause.

Quantifying Your Total Leak

To estimate the total revenue impact of your supply chain leaks:

1. List every verification issue found across all SSPs
2. Estimate the CPM impact per issue using the ranges above
3. Weight by revenue share for each affected SSP
4. Sum the weighted impacts for total estimated leak

Example calculation:

| SSP | Revenue Share | Issue | Est. CPM Impact | Weighted Impact |

|-----|--------------|-------|-----------------|----------------|

| SSP-A | 25% | Missing sellers.json | -30% | -7.5% |

| SSP-B | 20% | Confidential entry | -15% | -3.0% |

| SSP-C | 15% | Type mismatch | -20% | -3.0% |

| Others | 40% | None | 0% | 0% |

| Total | | | | -13.5% |

In this example, the publisher is losing an estimated 13.5% of programmatic revenue to supply chain issues. For a publisher earning $50,000/month, that's $6,750/month in recoverable revenue.

Frequently Asked Questions

Can I fix these leaks without SSP cooperation?

Partially. You can fix your own ads.txt immediately (add missing entries, correct relationship types). But sellers.json issues require SSP action. The good news is that SSPs are generally responsive to specific, documented requests.

How long after fixing does revenue recover?

DSPs cache ads.txt and sellers.json data for 24-72 hours. Initial improvements appear within a week. Full recovery takes 2-4 weeks as DSP quality scores update.

Which leak type should I fix first?

Fix authorization gaps first (missing ads.txt entries), then identity verification failures (missing sellers.json entries), then mismatches. This order addresses the highest-impact issues first.