Ad system
content.ad
content.ad is the domain an ad system uses in app-ads.txt and ads.txt files. 28 apps in our data declare it.
- Apps declaring it
- 28
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 48.0 / 100
28 DIRECT · 0 RESELLER
Unreachable
no line checked yet
10 lines in total
28 apps scored
Apps and lines are recounted every 10 minutes. The sellers.json breakdown and the directory ranking are as of , recomputed daily. sellers.json last read 10 October 2026. The supply path score sums up how short and clean the declared paths are, 0 to 100 (how it is computed).
How to add content.ad to app-ads.txt
One line per account, in the app-ads.txt at the root of the domain your App Store and Google Play listings name as the developer website.
content.ad, YOUR_ACCOUNT_ID, DIRECT
content.ad, YOUR_ACCOUNT_ID, RESELLER
- Field 1:
content.ad, the domain content.ad uses in app-ads.txt. - Field 2: your account ID with content.ad. It must equal the
seller_idin content.ad's sellers.json. - Field 3: DIRECT if you hold the account, RESELLER if a partner holds it and sells your inventory. DIRECT vs RESELLER
- Field 4 (optional): a certification authority ID. Most lines naming content.ad carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Unreachable
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 10, 2026
Cross-check of lines naming content.ad
- Verified 0
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 0
- Unchecked 10
Every line naming content.ad is looked up in its sellers.json. What each status means
Apps that declare content.ad
| App | Store | Relationship | Status |
|---|---|---|---|
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live |
Questions about content.ad
How do I add content.ad to app-ads.txt?
Add one line for each account content.ad gives you: "content.ad, YOUR_ACCOUNT_ID, DIRECT". Use DIRECT when you hold the account yourself and RESELLER when a partner holds it and sells your inventory through content.ad. The account ID must be the seller_id content.ad lists for you in its sellers.json; content.ad will give it to you. Put the file at the root of the domain named as your developer website in the App Store and Google Play listings.
Does content.ad publish a sellers.json?
We could not reach it (last attempt 10 October 2026). Lines naming content.ad stay unchecked until it answers again.
How many apps declare content.ad in app-ads.txt?
28 apps in Stoqlab's data (delisted apps included) declare content.ad: 28 with at least one DIRECT line and 0 with at least one RESELLER line, across 10 app-ads.txt files. Counts are recomputed daily.
What is the difference between DIRECT and RESELLER?
DIRECT means the publisher owns the account; RESELLER means an intermediary sells the inventory on the publisher's behalf. DIRECT lines should match a PUBLISHER entry in the network's sellers.json, RESELLER lines an INTERMEDIARY entry.
Sources: the public app-ads.txt files of tracked apps and the sellers.json of content.ad. Something wrong? Tell us.