App SupplyIndex Check an app
B88 / 100

FitNow, Inc.

loseit.com/app-ads.txt · 1 app · Android + iOS · 127 seller lines · checked Nov 16, 2026

5 lines to fix. One step takes this file from B 88 to A 94.

127 seller lines in www.loseit.com/app-ads.txt; 95 could be checked against the ad systems' sellers.json. Main finding: DIRECT lines inconsistent with public data.

app-ads.txtLines from step 1
16openx.com, 537150862, DIRECT, 6a698e2ec38604c6Confirm with the partner: sellers.json lists the account as INTERMEDIARY. If the account isn't yours, use RESELLER.
26triplelift.com, 12381-EB,DIRECT,6c33edb13117fd86Confirm with the partner: sellers.json lists the account as INTERMEDIARY. If the account isn't yours, use RESELLER.
120themediagrid.com, A7OJMU, DIRECT, 9fac4a4a87c2a44fConfirm with the partner: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 64 different companies. If the account isn't yours, use RESELLER.
+ 2 more DIRECT lines to confirm

What to change

Easiest first. Points are estimates, assuming every line in a step is fixed.

  1. Confirm 5 DIRECT lines with the partners that supplied them (3 partner blocks: App-Ads.txt LoseIt.com, Seedtag, nimbus); use RESELLER where the account isn't yours.+6 → A 94
  2. Ask partners about 6 seller IDs missing from their sellers.json (3 partner blocks: Liftoff/Vungle, display, nimbus); remove lines for closed accounts.+5 → A 99
  3. Add OWNERDOMAIN, or confirm 1 DIRECT account registered to another domain.+1 → A 100
Re-check now

Findings

Each finding lists the exact lines involved. Findings are automated observations of public files as of Nov 16, 2026. They describe file contents, not the intent or conduct of any company.

warning

DIRECT lines inconsistent with public data

5 −6 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." For these lines, either the ad system's own sellers.json lists the account as INTERMEDIARY, or the same account is marked DIRECT in the files of 3 or more companies with different owner domains. Either way, the public data does not support the DIRECT label. Buyers that use DIRECT labels in supply-path decisions may treat these lines differently.

How to fixUse DIRECT only for accounts your company controls. Confirm with each partner whether the account is yours; if it isn't, the specification calls for RESELLER. Full guide →
Evidence (5)
line 16     openx.com, 537150862, DIRECT, 6a698e2ec38604c6
             → partner block: App-Ads.txt LoseIt.com  observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Everyday Health, Inc. (via EB)  domain in sellers.json: google.com
line 26     triplelift.com, 12381-EB,DIRECT,6c33edb13117fd86
             → partner block: App-Ads.txt LoseIt.com  observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: everydayhealth (via EB Network)  domain in sellers.json: google.com
line 120    themediagrid.com, A7OJMU, DIRECT, 9fac4a4a87c2a44f
             → partner block: nimbus  observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 64 different companies  name in sellers.json: Nimbus Advertising Solutions  domain in sellers.json: adsbynimbus.com
line 162    xandr.com, 4009, DIRECT, f5ab79cb980f11d1
             → partner block: Seedtag  observed: the same account is marked DIRECT by 41 different companies  name in sellers.json: Seedtag Advertising SL  domain in sellers.json: seedtag.com
line 164    smartadserver.com, 3050,  DIRECT
             → partner block: Seedtag  observed: the same account is marked DIRECT by 43 different companies  name in sellers.json: Seedtag  domain in sellers.json: seedtag.com
warning

Seller IDs not listed in the ad system's sellers.json

6 −5 pts

The ad system's current sellers.json doesn't list these accounts, so buyers that validate the chain can't match them. Common causes are closed accounts or former partners.

How to fixAsk each partner whether the account is still active and request their current lines; remove lines for closed accounts. Full guide →
Evidence (6)
line 22     rubiconproject.com, 17750, DIRECT, 0bfd66d529a55807 #display
             → partner block: display  sellers_json: https://rubiconproject.com/sellers.json
line 65     adview.com,32076181,RESELLER,1b2cc038a11ea319
             → partner block: Liftoff/Vungle  sellers_json: https://adview.com/sellers.json
line 68     growintech.co,2723d092b63885e0d7c260cc007e8b9d2393g,RESELLER,9d8dfe5c6b00fb37
             → partner block: Liftoff/Vungle  sellers_json: https://growintech.co/sellers.json
line 73     xandr.com,10128,RESELLER,f5ab79cb980f11d1
             → partner block: Liftoff/Vungle  sellers_json: https://xandr.com/sellers.json
line 78     e-planning.net,081dcb996d2ccc1e,RESELLER,c1ba615865ed87b2
             → partner block: Liftoff/Vungle  sellers_json: https://e-planning.net/sellers.json
line 124    rubiconproject.com, 17476, RESELLER, 0bfd66d529a55807
             → partner block: nimbus  sellers_json: https://rubiconproject.com/sellers.json
info

DIRECT accounts registered to another domain

1 −1 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." For these DIRECT lines, the ad system's own sellers.json lists the account under another company's domain. Allowed when that domain belongs to the same company; add OWNERDOMAIN to make that explicit.

How to fixIf the account is yours under another domain, declare it with OWNERDOMAIN=<that domain>; otherwise mark it RESELLER. Full guide →
Evidence (1)
line 101    adsbynimbus.com, 637b4903-b2ca-4e40-bacb-c8e5e5de4909, DIRECT, dd263a8a859bd0e0
             → partner block: nimbus  domain in sellers.json: babycenter.com  name in sellers.json: BabyCenter
info

Ad systems whose sellers.json we couldn't read

18

We couldn't read a sellers.json for these ad systems at crawl time (no file, invalid JSON, empty, or automated access refused), so these lines weren't verified. No points are deducted.

How to fixAsk the partner to publish sellers.json; until then buyers can't verify that path. Full guide →
Evidence (18)
line 6      appnexus.com,7886,DIRECT,f5ab79cb980f11d1
             → partner block: App-Ads.txt LoseIt.com  sellers_json: HTTP 403 to automated requests
line 9      indexexchange.com, 184746, DIRECT, 50b1c356f2c5c8fc
             → partner block: App-Ads.txt LoseIt.com  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 10     indexexchange.com,193516,DIRECT,50b1c356f2c5c8fc
             → partner block: App-Ads.txt LoseIt.com  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 11     indexexchange.com, 210221, DIRECT, 50b1c356f2c5c8fc
             → partner block: App-Ads.txt LoseIt.com  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 12     indexexchange.com, 183617, DIRECT, 50b1c356f2c5c8fc
             → partner block: App-Ads.txt LoseIt.com  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 24     sharethrough.com,b126f4af,DIRECT,d53b998a7bd4ecd2
             → partner block: App-Ads.txt LoseIt.com  sellers_json: robots.txt of sharethrough.com disallows crawlers
line 28     appnexus.com, 11470, RESELLER, f5ab79cb980f11d1 #ogury
             → partner block: ogury  sellers_json: HTTP 403 to automated requests
line 59     iqzone.com,IQ97,RESELLER
             → partner block: Liftoff/Vungle  sellers_json: bot-check or captcha page (HTTP 202)
line 75     lunamedia.io,95ed51edc1cb499baaf3476fcb6fa463,RESELLER,524ecb396915caaf
             → partner block: Liftoff/Vungle  sellers_json: bot-check or captcha page (HTTP 202)
line 79     contextweb.com,562546,RESELLER,89ff185a4c4e857c
             → partner block: Liftoff/Vungle  sellers_json: robots.txt of projects.contextweb.com disallows crawlers
line 105    lunamedia.io, 6bf03349-293b-4b25-939f-c553ba38021d, RESELLER, 524ecb396915caaf
             → partner block: nimbus  sellers_json: bot-check or captcha page (HTTP 202)
line 109    sharethrough.com, Vlox9WTu, RESELLER, d53b998a7bd4ecd2
             → partner block: nimbus  sellers_json: robots.txt of sharethrough.com disallows crawlers
line 113    yieldmo.com, 3746143199094055132, RESELLER
             → partner block: nimbus  sellers_json: bot-check or captcha page (HTTP 202)
line 122    appnexus.com,12616,RESELLER,f5ab79cb980f11d1
             → partner block: nimbus  sellers_json: HTTP 403 to automated requests
line 138    zetaglobal.net, 989, RESELLER
             → partner block: Nativo  sellers_json: HTTP 404
line 140    sharethrough.com, 4878, RESELLER, d53b998a7bd4ecd2
             → partner block: Nativo  sellers_json: robots.txt of sharethrough.com disallows crawlers
line 151    appnexus.com, 8173, RESELLER, f5ab79cb980f11d1
             → partner block: Kargo  sellers_json: HTTP 403 to automated requests
line 152    contextweb.com, 562001, RESELLER, 89ff185a4c4e857c
             → partner block: Kargo  sellers_json: robots.txt of projects.contextweb.com disallows crawlers

Apps

1 app in this index; they all list a developer website on loseit.com, so buyers read this app-ads.txt for all of them. 1 is in this week's US charts.

AppGenreStoreIn the charts
Lose It! – Calorie Counter Health & Fitness iOS + Android #22

About this file

app-ads.txt
https://www.loseit.com/app-ads.txt · 200
Score
B 88/100 · 127 lines · 95 checked against sellers.json
Grouping
One file: every app whose store listing points to loseit.com. Store names alone never group publishers.
Checked
Nov 16, 2026

Is this your file?

Changed it? Check any of these apps live; this page updates weekly. Think something here is wrong? Request a correction.

Check an app