SSP

Magnite

rubiconproject.com

Magnite was formed in 2020 from Rubicon Project and Telaria. rubiconproject.com is the domain its display and in-app supply uses in ads.txt and app-ads.txt.

Most of the 226,124 apps that declare rubiconproject.com reach it through a reseller: 99% have a RESELLER line, 51% a DIRECT one (37,080 files, 29,876 of them through LoopMe's account). Of 2,199,334 lines checked against its sellers.json (3,226 sellers), 73% match, 19% name an unlisted account and 2.5% declare the wrong seller type. 51 sellers left its sellers.json in the last 30 days.

Apps declaring it
226,124

114,897 DIRECT · 224,827 RESELLER

Sellers in sellers.json
3,226

0% confidential

Lines verified
73%

1,619,598 of 2,207,035 checked lines

Lines with errors
468,531

2,207,035 lines in total

Avg. supply path score
52.7 / 100

222,266 apps scored

App counts, the sellers.json breakdown and the directory ranking are as of , recomputed daily (the same numbers as the directory). Line counts are recounted every 10 minutes. sellers.json last read 13 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 Magnite 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.

rubiconproject.com, YOUR_ACCOUNT_ID, DIRECT, 0bfd66d529a55807
rubiconproject.com, YOUR_ACCOUNT_ID, RESELLER, 0bfd66d529a55807
  • Field 1: rubiconproject.com, the domain Magnite uses in app-ads.txt.
  • Field 2: your account ID with Magnite. It must equal the seller_id in Magnite'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): 0bfd66d529a55807, the certification authority ID on 97% of the lines naming rubiconproject.com.

sellers.json at a glance

Status
Published
Sellers listed
3,226
Confidential
0 (0%)
Passthrough
0
Removed, last 30 days
51
Last read
Oct 13, 2026
  • PUBLISHER1,538
  • INTERMEDIARY1,573
  • BOTH115

Cross-check of lines naming rubiconproject.com

  • Verified 1,619,598
  • Seller ID not found 412,768
  • DIRECT but intermediary 41,078
  • RESELLER but publisher 14,685
  • Seller type BOTH 118,906
  • Confidential seller 0
  • No sellers.json 0
  • Unchecked 0

Every line naming rubiconproject.com is looked up in its sellers.json. What each status means

Common errors with rubiconproject.com lines

  • Seller ID not found 412,768 lines

    Ask Magnite for the account ID it lists for you in its sellers.json, correct the line, or remove it if you no longer work with them. Buyers that check sellers.json drop these paths.

  • Seller type BOTH 118,906 lines

    The account is listed as BOTH, so sellers.json alone cannot tell a buyer which relationship applies. Nothing to fix on your side; buyers usually look at the seller's domain.

  • DIRECT but intermediary 41,078 lines

    If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask Magnite to list it as PUBLISHER.

  • RESELLER but publisher 14,685 lines

    If the account is yours, declare it DIRECT. If a partner holds it, ask Magnite why the account is listed as PUBLISHER.

Common app-ads.txt errors and how to fix them

Intermediaries most declared as RESELLER

Accounts on rubiconproject.com that its sellers.json lists as INTERMEDIARY or BOTH, by the number of app-ads.txt files declaring them. Confidential sellers are left out.

Seller domainTypeFiles
loopme.com INTERMEDIARY 29,876
opera.com BOTH 26,621
algorix.co INTERMEDIARY 25,117
start.io INTERMEDIARY 24,753
unrulymedia.com INTERMEDIARY 24,600
yeahmobi.com INTERMEDIARY 22,959
bidmachine.io INTERMEDIARY 22,909
pubnative.net INTERMEDIARY 22,491

Apps that declare rubiconproject.com

AppStoreRelationshipStatus
Android DIRECT + RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android DIRECT + RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live

Questions about Magnite

Does Magnite publish a sellers.json?

Yes. Its file at https://rubiconproject.com/sellers.json listed 3,226 sellers when we last read it on 13 October 2026: 1,538 publishers, 1,573 intermediaries and 115 listed as both; 0% are confidential.

How many apps declare Magnite in app-ads.txt?

226,124 apps in Stoqlab's data (delisted apps included) declare rubiconproject.com: 114,897 with at least one DIRECT line and 224,827 with at least one RESELLER line, across 37,080 app-ads.txt files, as of 14 October 2026 (recounted daily).

What is the certification authority ID for Magnite?

97% of the app-ads.txt lines naming rubiconproject.com carry "0bfd66d529a55807" in the fourth field. The field is optional; the IAB Tech Lab ads.txt 1.1 specification says identifiers in sellers.json supersede it, so a missing or different value does not make a line invalid.

Why do rubiconproject.com lines fail verification?

Of 2,207,035 lines naming rubiconproject.com, 468,531 contradict its sellers.json. The most common case is "Seller ID not found", on 412,768 lines. Ask Magnite for the account ID it lists for you in its sellers.json, correct the line, or remove it if you no longer work with them. Buyers that check sellers.json drop these paths.

Not sure whether your line should say DIRECT or RESELLER? DIRECT vs RESELLER in app-ads.txt

Sources: the public app-ads.txt files of tracked apps and the sellers.json of rubiconproject.com. Something wrong? Tell us.