Checking authorized digital sellers across a publisher network

Audit ads.txt seller declarations using advertising systems, account IDs and relationship types. Identify stale regional copies before escalating.

A woman reviews a list with colored status indicators on a laptop in a bookshop.

An ads.txt record identifies who a publisher declares is authorized to sell its advertising inventory. For an ad operations team, the practical question is whether the current declaration matches the approved relationship for each property.

Start with a known partner

Take the account identifier and advertising system from the signed partner records. Compare them with the publisher’s public declaration and distinguish DIRECT from RESELLER as defined by the standard. A similarly spelled company name is an inadequate match. Keep the date and an original copy of the record used for the review. IAB Tech Lab ads.txt standard.

Investigate a geographic discrepancy

An ads.txt file generally should not need a residential connection. If regional teams report different versions, compare a small number of authorized observations with XtremeProxy and use the publisher’s CDN diagnostics to locate the difference. An old cached copy and a change in account authorization call for different action. Escalate the discrepancy to the publisher for confirmation before making a claim about invalid traffic.

One effective record is a before-and-after comparison for a single account ID. If the advertising system and account match but the relationship value changes, confirm the commercial relationship with the publisher. The plain-text file discloses its assertion. It does not independently verify a contract.

A reseller row uses the wrong exchange account

An owned publisher property has two contracted sellers on the same exchange. A spreadsheet lists the correct exchange domain but maps the reseller to the direct account identifier. Compare the account and relationship type with the contracts or records provided by the publisher. A regional retrieval can reveal that one hostname serves an older public file. Resolve the account mapping first, then verify the public representation on the authorized hostnames after deployment.

Keep the publisher hostname in the evidence

A publisher group can operate several hosts with separate selling relationships. Capture the authorized host, exchange account, relationship and date. Check whether a redirect changes the represented property before treating a missing entry as an unauthorized seller. Escalate questions about the commercial relationship to the contract owner.

A public seller row can remain syntactically valid after the underlying agreement ends. Give each source-of-truth relationship an owner and effective dates. When checking a historical impression, compare against the disclosure and contract in force at the observation date. Today’s file is insufficient to reconstruct yesterday’s authorization.

Compare the complete authorized relationship

A direct relationship and a reseller relationship can refer to different business arrangements even on the same exchange. Have the publisher validate the account identifier and relationship against its commercial record. A file entry containing the right exchange but the wrong seller account remains a mismatch. A second retrieval only determines whether the public representation changed.

Reconcile the publisher's own record with the exchange's published seller entry when that information is available. Start with the publisher-authorized advertising system and seller account, then look up that exact account in the exchange's official seller disclosure. Record whether the entry is identifiable, confidential or missing at the time of review. An undisclosed name can leave a question unresolved without proving the relationship invalid. Send the paired records to the publisher's ad operations owner so they can check the account against their direct documentation.

Treat account identifiers as text in spreadsheets used for seller reconciliation. A source can contain an identifier made entirely of digits with leading zeros, while an import tool may convert it to a number and discard those zeros. Use a publisher-supplied test row with a distinctive identifier and compare the raw field after import and export. If the string changes, repair the reconciliation workflow before reporting a missing seller. Otherwise the publisher could change a correct public declaration to match a broken spreadsheet.

When the exchange account differs from the contract, ask the publisher to resolve the relationship before treating a file edit as a complete repair. Publisher seller declarations checks the published declaration. How to verify an ad’s regional appearance without clicking it covers the neighboring advertising question of verifying regional creative and landing behavior through a platform's approved preview. Review XtremeProxy plans and allowances.

Frequently asked questions

Does the presence of an ads.txt row establish that an impression was genuine?

It documents an advertised selling relationship at the time of retrieval. Individual auction and impression records require their own evidence. Preserve the account identifier and supply-chain context when reconciling a particular transaction.

Related articles