Transparency
ads.txt for TheGrowthy
The exact line to add, what each field means, and where the file goes. If you are already integrated, your seller ID is in your onboarding email.
The line
thegrowthy.com, YOUR_SELLER_ID, DIRECTReplace YOUR_SELLER_ID with the ID we issue during onboarding. One line per authorised seller; order does not matter, and # starts a comment.
What each field is
- 1
Exchange domainthegrowthy.com
The domain of the system that receives the bid request. It matches the asi on our schain node and the domain our sellers.json is served from — buyers check that all three agree.
- 2
Publisher account IDissued at onboarding
The seller ID that identifies you inside our exchange. It is the same seller_id that appears against your entry in our sellers.json, which is how a buyer confirms the two sides match.
- 3
Account typeDIRECT
You hold a direct contract with us and we are authorised to sell this inventory. We do not buy from other exchanges to sell on, so RESELLER never applies to a TheGrowthy line.
- 4
Certification authority IDomit
Optional, and TAG-issued. We have none to publish yet, so leave the field off entirely. A missing optional field is valid; a wrong one is not.
Where the file goes
Web inventory
Plain text at
https://yourdomain.com/ads.txt— the root of every domain you sell on, served astext/plain. A subdomain that serves its own ads needs its own file.App inventory
The same line in
app-ads.txt, served from the developer domain listed in your app store entry — not from the app itself.
Checking it
We validate the file as part of onboarding: the line has to parse and the seller ID has to match the one on your account before we route traffic to you. Once it does, your entry appears in our sellers.json — the two are meant to be read together, and a buyer that finds them disagreeing is right not to bid.
One hop, and both files to prove it.
Published sellers.json, a complete schain on every request, and no resold inventory.