An impression can reach a buyer through several commercial relationships. The website name describes where an ad opportunity comes from; the company sending the bid request may be somewhere else in the chain. Understanding that route helps buyers ask better purchasing questions and helps publishers explain how their inventory reaches demand.

Three industry standards make parts of this relationship visible: ads.txt, sellers.json and the OpenRTB SupplyChain object. Read them together, with an understanding of their limits. A useful review connects the declared authorization, the identity behind each account and the route reported for a particular opportunity.

Read the roles before the route

The publisher makes advertising space available around content. A supply-side platform, or SSP, helps publishers offer that space to buyers. An exchange provides a marketplace or transaction mechanism connecting supply and demand. A demand-side platform, or DSP, helps advertisers evaluate opportunities and buy against campaign requirements.

These describe functions, not a compulsory sequence of four separate companies. An SSP can also operate an exchange. A publisher can work with several selling partners, and a commercial intermediary can contribute access, representation or packaging. Begin by asking who controls the inventory, who controls each account and who is paid by whom.

The same property may consequently have multiple legitimate supply paths. Reviewing the property once does not explain every route through which a buyer can encounter it.

Ask three different questions

IAB Tech Lab describes sellers.json and SupplyChain as complementary to publisher authorization declarations. The connection is the advertising-system domain plus the seller account identifier. Its transparency overview explains how the pieces relate.

What each transparency standard contributes
Standard Main question Where the declaration lives
ads.txt Which seller accounts are authorized to sell this website's inventory? A public file associated with the publisher's domain.
sellers.json Which entity does an account represent within this advertising system? A public file maintained by that advertising system.
SupplyChain Which selling route is declared for this particular bid request? An ordered set of nodes carried with the request.

A list of authorized accounts describes possible relationships. It does not establish that every listed account participated in one impression. Likewise, a recognizable company name does not, on its own, establish authorization for a particular website.

Interpret DIRECT and RESELLER precisely

In ads.txt, DIRECT means the publisher directly controls the specified account on the named advertising system. RESELLER means the publisher authorizes another entity to control that account and resell its inventory through the system. These are account relationships, as defined in the ads.txt specification.

A DIRECT entry does not establish a direct commercial agreement between the advertiser and the publisher. Nor does it certify audience quality, placement suitability or campaign performance. A RESELLER entry can describe an authorized, useful commercial relationship.

Ask your partner to explain the specific account in question. “We work directly with that publisher” is too broad if the request actually arrives through a different seller account. Match the identifier, system and relationship rather than relying on a familiar logo.

Follow one fictional opportunity

Consider an invented website, fieldnotes.example. Its owner controls account P104 at Cedar SSP. Cedar also sells through account S208 at Bridge Exchange. All companies, domains and identifiers below are fictional and illustrate one simple web arrangement.

  1. Field NotesPublisher
  2. Cedar SSPSelling partner
  3. Bridge ExchangeResale route
  4. Buying DSPEvaluates the opportunity
One illustrative request route. Real integrations can combine roles or use different arrangements.

The publisher's ads.txt includes these two authorizations:

cedarssp.example, P104, DIRECT
bridgeexchange.example, S208, RESELLER

The seller directories then identify the account holders:

  • At cedarssp.example/sellers.json, P104 identifies Field Notes Media, with domain fieldnotes.example and type PUBLISHER.
  • At bridgeexchange.example/sellers.json, S208 identifies Cedar SSP, with domain cedarssp.example and type INTERMEDIARY.

This follows the sellers.json specification: an account identifies one selling entity; that entity can have more than one account. PUBLISHER describes owned inventory for which the system pays the entity directly. INTERMEDIARY describes inventory it does not own, or a relationship in which the system does not pay it directly. BOTH covers accounts carrying both types.

A simplified SupplyChain object for this route could look like this:

{
  "ver": "1.0",
  "complete": 1,
  "nodes": [
    {"asi": "cedarssp.example", "sid": "P104", "hp": 1},
    {"asi": "bridgeexchange.example", "sid": "S208", "hp": 1}
  ]
}

The buyer connects each asi and sid pair to the corresponding directory and authorization. In this example, Bridge pays Cedar, and Cedar pays Field Notes. The object describes that payment chain without revealing the amounts each participant retains.

Read completeness within its scope

The OpenRTB object definition identifies the system with asi, its seller account with sid, and payment participation with hp. Node order matters. For the version 1.0 example above, complete: 1 declares a chain back to the inventory owner; complete: 0 signals an incomplete chain. Read these fields according to the declared version and your partner's supported implementation.

A declaration of completeness remains something to validate. Compare the first known seller, subsequent accounts and final sending system with the expected arrangement. The SupplyChain implementation guidance explains how resellers append their nodes and preserve an incomplete status when the upstream path is unknown.

Do not assume this is a trace of every technical service involved in loading an ad. For example, Google's documented payment-chain implementation excludes intermediaries that do not handle payment. A wrapper or measurement service may therefore have a technical role without appearing in that chain.

Separate a discrepancy from a conclusion

Missing data deserves investigation. A file that cannot be fetched, an account omitted from an available directory, a confidential identity and an incomplete chain are different observations. Record which condition occurred before deciding what it means. sellers.json permits confidential records that withhold identity fields; that reduces public visibility but is not, by itself, proof of fraud.

Ask the partner to reconcile the exact account and request sample. Consider cached copies, publication changes and the applicable authorization rules. A seller absent from the relevant authorization declarations is a different issue from a temporary retrieval failure. Buyers can apply different eligibility policies, so clarify how your buying platform handles each case.

Even a consistent set of declarations cannot prove that a visitor is human, that an ad was viewable, that the content suits a brand or that a conversion is genuine. Those questions require their own controls and measurement. Supply-path checks also do not disclose a complete fee breakdown.

Evaluate the value of each route

Once you understand the participants, ask what each contributes. A shorter route can be easier to explain, but counting nodes alone does not establish the best purchase. A selling partner might provide access to inventory, a particular commercial arrangement or operational support. The useful question is whether that contribution is clear and worth its cost.

Compare routes under similar buying conditions. Examine inventory overlap, reporting detail, available placement controls, total buying cost and measured outcomes. Request a commercial explanation of fees rather than trying to infer them from a node count. If two routes appear equivalent, test that assumption with a controlled allocation and a defined evaluation period.

Index Exchange's explanation of cross-checking the three standards provides a practical starting point for reconciling seller identities. Use that reconciliation to support a commercial review, while keeping the quality and effectiveness questions open.

Turn the review into a repeatable workflow

For media buyers

  • Ask for usable evidence. Obtain representative request samples or equivalent platform reporting, including the property, selling system, account and declared chain where available.
  • Reconcile the identifiers. Check authorization and account identity together. Record an unresolved mismatch separately from a confirmed match.
  • Understand the platform's decisions. Ask how it treats absent files, confidential entries, incomplete paths and stale cached data.
  • Review commercial value. Compare access, cost and outcomes before consolidating spend. Keep separate checks for traffic quality, context and measurement.

For publishers

  • Maintain an account register. Record which partner supplied each authorization, who controls the account and why the route is used.
  • Confirm your public identity. Ask selling partners to verify the seller ID, legal entity and domain recorded for your account.
  • Review additions and removals. Check proposed entries against actual arrangements, and reconcile changes when a partnership ends or an account moves.
  • Assign ownership. Name the person who handles mismatches and keep a record of what changed. Check the resulting request, not only the edited file.

A well-understood supply path gives both sides a clearer conversation: which relationship is authorized, who participates and why that route is useful. Pair that understanding with a thoughtful publisher ad experience and independent performance measurement.

Sources & further reading

Explore advertising with Promoweb.
Meet our self-serve platform