EXAMPLE REPORT · FICTIONAL DATA

exchange.example
Listings & findings

This is a worked example, not a live customer report. All domains, seller IDs and findings below are fictional.

See where a seller is listed, inspect a broken relationship, and identify the team to contact.

01 / DISCOVER

Where your ID appears

Seller ID 18420Example rows

Property	Source line	Check result
journal.example	exchange.example, 18420, RESELLER	Missing upstream listing
weekender.example	exchange.example, 18420, RESELLER	Checked records agree
radio.example	exchange.example, 77210, RESELLER	Confidential record

02 / CHECK

The break is above you.

journal.example lists seller 18420. The exchange’s seller record names upstream.example, but that company has no listing in the publisher’s ads.txt.

The listing on weekender.example is checked separately. A finding on one property does not mean the seller ID is broken everywhere.

1. Publisher’s ads.txt

exchange.example, 18420, RESELLER

2. Exchange’s sellers.json

seller_id: 18420 seller_type: INTERMEDIARY domain: upstream.example

3. Missing publisher declaration

No line for upstream.example in journal.example’s ads.txt in this example.

A different outcome: unverifiable

radio.example’s seller record is confidential. That is not counted as a demonstrated broken chain.

03 / ACT

Take the evidence to the right team.

Follow up with
the publisher or SSP

Ask them to confirm the relationship with upstream.example and correct the declaration or seller record as appropriate. Include the affected property, seller ID and both source records.

AFFECTED PROPERTYjournal.example

Real findings include the source evidence and crawl context. The platform identifies the issue; it does not automatically edit publisher files.

Now look up your company.

Return to the lookup with your seller domain,
or ask us to walk you through your report.

Find my listings Book a report walkthrough