t1k:marketing:monetization:max-network-watch
| Field | Value |
|---|---|
| Module | monetization |
| Version | 1.49.21 |
| Effort | low |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:marketing:monetization:max-network-watch[--end YYYY-MM-DD] [--baseline-days 7] [--exclude PKG] [--post]MAX Network-Partner Watch
Section titled “MAX Network-Partner Watch”Catches a mediated network inside AppLovin MAX (ADMOB_BIDDING, FACEBOOK_NETWORK, MINTEGRAL_BIDDING, UNITY_BIDDING, YANDEX_BIDDING, MOLOCO_BIDDING, …) that stopped serving or whose revenue fell hard, per app and portfolio-wide. Read-only: Report Key only, no Management API. It never pauses, re-enables or edits anything.
set -a; . ~/.config/t1k/ads.env; set +a # or any env holding APPLOVIN_REPORT_KEYpython3 -I .claude/skills/t1k-marketing-monetization-max-network-watch/scripts/network_watch.pyOne MAX call (day, package_name, platform, network, impressions, estimated_revenue), ~3s.
Default day = yesterday UTC (MAX days are UTC) vs the median of the 7 days before it.
| Flag | Use |
|---|---|
--end YYYY-MM-DD | check another day (e.g. re-check a day once revenue settled) |
--json | full alert list, machine-readable |
--post | send the text to DISCORD_WEBHOOK_URL, only when there is a partner alert |
--app-wide | also list app-wide drops (context, never posted on their own) |
--exclude PKG ... | skip extra packages on top of exclude.json (partner titles) |
--drop-pct --min-gap --min-cell-rev --min-stop-rev --net-drop-pct --net-min-gap --attrib-margin | tune thresholds (defaults in the script’s DEFAULTS) |
Exit 0 = no alert, 10 = alerts, 2 = error (key, API, no data for that day yet).
What it flags
Section titled “What it flags”| Kind | Rule (per app x platform x network) |
|---|---|
| STOPPED | had impressions on >= 70% of baseline days, usually earns >= $10/day, 0 impressions on the day |
| DROP | revenue <= 50% of the baseline median AND >= $20/day below it |
Only significant moves alert: the user reads day-to-day trends on the MAX dashboard and wants to hear only about a big drop or, worst, a network that stopped serving. Portfolio-wide (all apps summed per network): <= 70% of baseline and >= $50/day gap. Backtest over 2026-09-15..10-14: ~0.5 alert/day, and it caught every day of the Arrow Romance Meta outage (10/09 drop, 10/10-12 stopped, 10/13 drop) plus Yandex on the same app (-65% from 10/11).
Every alert is attributed:
- PARTNER PROBLEMS: the network fell much further than the app’s own total (network ratio more than 0.3 below the app ratio), or it stopped. This is what to act on.
- APP-WIDE: the whole app fell about as much. Traffic, a build or UA, not the partner.
Not printed or posted by default (
--app-widelists up to 5;--jsonhas all), and it does not set exit 10.
[2nd day] = the previous day also met the condition: persistent, not a one-day blip.
Reading it (write the answer in plain words)
Section titled “Reading it (write the answer in plain words)”- Lead with STOPPED. A network going to zero on an app that served it daily is almost always
config (adapter removed or broken in a new build, ad unit or network disabled in MAX, app-ads.txt
line missing, account or policy hold at the partner). Example: 2026-10-10, FACEBOOK_NETWORK on
com.arrow.beauty.revealwent from ~$108/day to 0 while the app itself was up. - One day is a signal, two days is a finding. Prefer
[2nd day]rows when ranking. - Same network down in many apps at once (or a portfolio row) = the partner’s side (demand, account, an SDK/adapter version), not one app. Check MAX network status and the partner’s own dashboard.
- eCPM vs fill. A DROP with impressions still normal is a price drop (demand); with impressions down it is fill/serving. Say which.
- Newest-day revenue can still move a little. Re-run with
--enda day later before escalating a borderline DROP. - Next steps, read-only: check the app’s network list and ad units in MAX
(
t1k-marketing-monetization-applovin-max), app-ads.txt (t1k-marketing-monetization-app-ads-txt), AdMob for ADMOB_BIDDING (t1k-marketing-monetization-admob). Any MAX or network write goes through those skills with explicit before -> after confirmation, never from here.
Hard rules
Section titled “Hard rules”- The API returns capitalised headers (
Day,Package_name, …); the script lowercases them. - ADMOB_BIDDING here is AdMob inside MAX. AdMob mediation groups (AOA) live in AdMob, not in this report; this watch does not cover them.
- Partner titles (Beatbox 3D, Punch Guy) are excluded by package in
exclude.json; MAX rows have no title, so never filter by name. - MAX API range limit is 45 days, so
--baseline-daysis capped at 40. - A brand-new app or network has no baseline and is never flagged until it has 7 days.
Executed by
Section titled “Executed by”The script is mechanical: run it inline or on a timer. Interpreting the alerts (rules above) stays with the main session.