Skip to content

t1k:marketing:monetization:app-ads-txt

FieldValue
Modulemonetization
Version1.49.21
Effortmedium
Tools—
/t1k:marketing:monetization:app-ads-txt

Every store’s /app-ads.txt is served live from that store’s own Google Sheet — column A, one entry per row, the sheet’s first tab — except theonegamestudio.com, which serves the AppAdsText R2 build, not its sheet (write path: a PR to store-overrides/theonegamestudio.com.txt; see the Decisions table below and references/store-sheet-registry.md). For every other store: adding an entry means appending a row to the sheet of each store the user names. Nothing fans out to every store, and no line is copied from one store to another.

store's /app-ads.txt ← live from → that store's Google Sheet (column A)
append a row to the named store's sheet only; verify the live file

A write is outward-facing. A row appended to a sheet changes what that store serves to ad networks at once. Read “Confirm before you write” before touching it.

RuleWhy
Each store has exactly one sheet; find it by Drive title app-ads.txt - <store url>The sheet is the source for that store only
Append to each store the user names; ask which stores when not statedA wrong store is a live change on that store
Never copy lines from one store’s sheet to anotherEach store’s authorisations are its own
No shared / “all stores” defaultThe old AppAdsText fan-out is gone for new entries
AppAdsText (the R2 build) is legacy and read-only, except theonegamestudio.com, which still serves it: write that store via a PR to store-overrides/theonegamestudio.com.txtSee references/entry-decisions.md § “Repo-backed stores”

Entry-level decisions and the new-store path: references/entry-decisions.md. The store → sheet table and the title-search discovery: references/store-sheet-registry.md.

StepAgent
Run the offline suite bun test append-app-ads-row.test.cjs and report pass/fail verbatimt1k-tester
Diff-review the sheet row(s) for format, duplicates and the right storet1k-code-reviewer

The store choice, the exact lines, the preview read-out and the write confirmation are the operator’s calls, taken by the session that has the conversation. They are never delegated.

  • “add app-ads entries”, “add <network> to app-ads”, “app-ads.txt for <store>”
  • “is X live in app-ads”, “is <network> authorised for <store>”
  • A network asked for an app-ads line on a store’s site (for example, Liftoff’s live-app gate)
  • Onboarding a new store’s app-ads sheet
  1. Name the store(s) and the exact line(s). Copy each line verbatim from the network’s message. Never write one from memory.
  2. Resolve each store’s sheet by Drive title (references/store-sheet-registry.md).
  3. Preview each store. scripts/append-app-ads-row.cjs without --confirm prints the planned row and any duplicate. An entry already present is skipped, not re-added.
  4. Get explicit confirmation. One AskUserQuestion naming, per store: domain, sheet, row, and the exact line. A generic “ok” before that is not a go-ahead.

Reads are free: sheet exports, curl, the preview run, grep.

The write appends one row per store with append-app-ads-row.cjs --confirm, after step 4 above. The write is one store at a time (references/sheet-append-recipe.md). Each write is headless Chrome on a copy of an account that can edit the sheet, never the user’s live Chrome.

The script re-reads the sheet and asserts the planned row landed (exit 4 if not). Then check the live store, which must show the exact line:

Terminal window
curl -sL -A 'Mozilla/5.0' https://<store>/app-ads.txt | grep -F "<network publisher id>"

Grep for the exact publisher line, not the network name alone. A new row is not live at once: on partyus.fun (2026-11-11) it took about 90 seconds, and the response carried no-store / MISS, so the delay is on the sheet-source side. Poll for about 3 minutes before you call a miss real (references/sheet-append-recipe.md § “Verify it is live”). Only then re-read the sheet from fresh state before any retry.

Read the live file (above) and that store’s sheet (export or Drive read). Report “not live” only after checking both: a missing live line with the row present on the sheet points at caching or the site wiring, not at a missing entry.

  1. Find or create the store’s sheet titled app-ads.txt - <store url> in the shared folder.
  2. Add the store to references/store-sheet-registry.md.
  3. Point the store’s /app-ads.txt at its sheet (the site side, not this skill’s write path).
  4. Verify the live file (above) before any network is told the store is set up.

This skill writes ad-network authorisation records to store sheets. It does not configure a network’s SDK, mediation or bidding (that is t1k:marketing:monetization:mediation-strategy and the per-network skills), and it does not touch revenue reporting.

  • t1k:marketing:monetization:create-ad-unit-from-networks — Liftoff’s live-app gate points back here
  • t1k:marketing:monetization:mediation-strategy — which networks the studio works with
  • t1k:marketing:monetization:applovin-max — MAX setup and adapters
  • t1k:marketing:core:skill-domain-routing — the full marketing skill catalog