senior-buyer-ops git:20261014.8613433A

Immutable. This exact content never changes and is served at /api/v1/blob/e7c682fc38a2b57b.

---
name: senior-buyer-ops
description: "Senior buyer operations for Meta (FB/IG): portfolio-level decisions on what to kill, watch or scale across accounts. Day-1 operating contract, test/scale/reserve allocation, kill/watch/scale ladder with marginal scaling, Poisson-based automated rules, creative pipeline, funnel QA, spy intel, automation channels. Delegates buy/launch/count/measure mechanics to sibling skills; owns cross-account decisions, not single-ad-set diagnosis."
---

# Senior Buyer Ops

The layer above the sibling skills: they tell you HOW; this tells you WHAT to decide as the person
accountable for a portfolio and a team's numbers. Call them in order; this file owns the decisions
between them.

| Layer | Skill |
|---|---|
| Buy mechanics (structure, bidding, pixel/CAPI, policy, diagnosis) | [`meta-ads`](../meta-ads/SKILL.md) |
| Launch, infra, accounts, survival | [`meta-grey-ops`](../meta-grey-ops/SKILL.md) |
| Counting (tracker, payout event, postbacks, nowcast) | [`tracker-ops`](../tracker-ops/SKILL.md) |
| Is a result real | [`measurement-experimentation-ops`](../measurement-experimentation-ops/SKILL.md) |

Scope: Meta (FB/IG) only. In text, `skill/NN` means `../<skill>/references/NN-*.md`.

| Need | File |
|---|---|
| Lanes, canonical kill/scale figures, allocation, marginal scaling | `references/01-portfolio-and-cadence.md` |
| Creative production, spy tools | `references/02-creative-ops.md` |
| Funnel QA | `references/03-funnel-ops.md` |
| Automated kill/scale rules that survive small samples | `references/04-automated-rules.md` |
| Automation pipe (API/MCP/CSV/Sheets) for agent vs human | `references/05-automation-channels.md` |
| Spy intel via Tyver API (CLI `scripts/tyver.py`), join with team stats | `references/07-tyver-spy-api.md` |

Before you scale or kill on a difference, confirm it is real, not noise
(`measurement-experimentation-ops`): the kill/scale ladder and marginal-scaling math assume a
MATURED, non-contaminated result.

## Operating contract (pin on day 1, in writing, before any spend)

The most expensive mistake is optimising against the wrong definition. Get these from the TL
explicitly; don't infer:

1. Payout event: WHICH tracker status/measure pays (lead? reg? FTD? qualified FTD? confirmed COD?
   no tracker: network goal + status, tracker-ops/05). Everything downstream is priced on it. CPA
   pays per qualified FTD; redeposits are unpaid on CPA (quality KPI only), paid only on
   RevShare/Hybrid (field 2026-09-27).
2. Downstream stages + conversion lag: how long until the payout event matures (call-center
   confirm / deposit / KYC). Sets your judging window.
3. Caps: daily/total offer caps; traffic past a cap is unpaid.
4. KPI + targets: target CPA/CPL, and the QUALITY metric the advertiser judges later (reg→FTD,
   confirm %, scrub rate).
5. Timezone **and currency** of every ad account: the tz of every daily number and the sheet. A
   Meta change **closes** the account and opens a new act ID (`meta-grey-ops/08`); a mismatch is
   overhead for the life of the seat.
6. Naming + mapping: the campaign-name convention and the Meta-macro→tracker-param mapping that
   makes it split (tracker-ops mapping contract); no tracker → the click id that joins the PWA log
   and the network report (tracker-ops/05).
7. Reporting source of truth: which sheet/dashboard is authoritative, and by when each day.
8. Responsibility zones + escalation: who owns accounts/creatives/tracker/payments; who to ping on
   a ban wave, a tracking break, a billing hold.

Missing any of 1-8 = flying blind; resolve before launch. Pin the lane with them: in-place vs
set-and-forget (01), Keitaro vs no-tracker (tracker-ops).

## Cadence

- Daily: yesterday's spend per campaign (account tz) into the lane's counting system (Keitaro: cost
  push + end-of-day re-push; no tracker: own sheet + network deps per GEO; tracker-ops/03 § Daily
  routine) → cost per payout event vs target per account/GEO, full same-kind days (01) →
  kill/watch/scale (01) → update watchlist → report before the deadline.
- Weekly: portfolio review: winner migration, replacement queue, creative backlog health,
  buyer/stock comparison (01).