tracker-opslisted

# Tracker Ops Count money correctly and automate tracker work. Keitaro + Binom specifics below; the metric rules and daily sync port to any tracker. Baseline 2026-09-03 (Sonnet 5 blind, CPL cohort task): [R] — click-date cohort and pinned attribution window already known; do not expand that section. ## Metric rule (NEVER violate) 1. "conversions" (Keitaro) can exceed your payout-lead count, but that is INTEGRATION-SPECIFIC, not an inherent 3.5-4x: the same subid+status OVERWRITES; extra records come only from distinct `tid`s or a genuine multi-step funnel. Never do CPL math on "conversions" — the payout metric is ONE event/status; get it from the TL in writing. (Any "3.5-4x" is one setup's ratio, not a law.) 2. Metric names aren't portable: Keitaro "leads" = status Lead (first event); Binom "leads" ≈ all conversions. Verify semantics per tracker per setup. 3. Cross-check: platform-reported lead count ≈ tracker lead count. A big divergence = wrong metric or broken tracking; stop and reconcile before reporting. The "±20%" tolerance is an account-specific baseline you set from a reconciled day, not a universal constant. 4. Compute daily CPL in the AD ACCOUNT timezone for both spend and leads. Google's account timezone is permanent (senior-buyer-ops contract #5) — reconcile in the tracker, never by eye. 5. Rows with unsubstituted `{{...}}` macros: exclude from performance analysis, then classify the cause — bots/crawlers, yes, but also a broken