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)
- "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
tids 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.)
- Metric names aren't portable: Keitaro "leads" = status Lead (first event);
Binom "leads" ≈ all conversions. Verify semantics per tracker per setup.
- 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.
- 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.
- Rows with unsubstituted
{{...}} macros: exclude from performance analysis,
then classify the cause — bots/crawlers, yes, but also a broken URL template,
an unsupported/misspelled macro, or manual/direct traffic. Fix the template
if it's yours before blaming traffic.
Route references
| Need |
Reference |
| Keitaro: key, report/build, measures, update_costs, postback/S2S, postback drill, gotchas |
references/01-keitaro.md |
| Binom: legacy URL-param + v2 REST, reports, cost, postback/S2S |
references/02-binom.md |
| CPL math, funnel + anti-fraud metrics, cohort nowcasting, backend optimization contract (status→CAPI event), TMA/bot CAPI without pixel, multi-tracker sync + conversion ledger, ATT asymmetry, mapping, daily routine |
references/03-metrics-and-math.md |
Google lane: gclid/gbraid/wbraid, ValueTrack chains, Keitaro/RedTrack Google config, OCI windows + dedup, the 2026-06-15 cutoff, Data Manager events:ingest for new tokens |
references/04-google-lane.md |
Platform lanes are not interchangeable — Meta counts through CAPI, Google through gclid → OCI, with different windows, a different dedup key, and a hard onboarding cutoff. Read 04 before wiring anything on Google traffic.
Non-negotiables
- Work only on YOUR campaign IDs; every call carries a campaign filter. Other
buyers' campaigns are read-never-touch.
- No cost push = no CPL/ROI (report cost is 0). Overwriting a period is safe
(idempotent).
- API keys are write-once; store verbatim in gitignored notes.
1---2name: tracker-ops3description: Tracker ops for affiliate/media buying: Keitaro + Binom APIs (keys, reports, cost push), postback/S2S, metric discipline (payout event vs all-conversions, timezones, CPL math), daily spend-sync, gclid/OCI chain for Google. Principles port to other trackers.4---56# Tracker Ops78Count money correctly and automate tracker work. Keitaro + Binom specifics9below; the metric rules and daily sync port to any tracker.10Baseline 2026-09-03 (Sonnet 5 blind, CPL cohort task): [R] — click-date cohort and pinned attribution window already known; do not expand that section.1112## Metric rule (NEVER violate)13141. "conversions" (Keitaro) can exceed your payout-lead count, but that is15 INTEGRATION-SPECIFIC, not an inherent 3.5-4x: the same subid+status16 OVERWRITES; extra records come only from distinct `tid`s or a genuine17 multi-step funnel. Never do CPL math on "conversions" — the payout metric is18 ONE event/status; get it from the TL in writing. (Any "3.5-4x" is one19 setup's ratio, not a law.)202. Metric names aren't portable: Keitaro "leads" = status Lead (first event);21 Binom "leads" ≈ all conversions. Verify semantics per tracker per setup.223. Cross-check: platform-reported lead count ≈ tracker lead count. A big divergence = wrong23 metric or broken tracking; stop and reconcile before reporting. The "±20%"24 tolerance is an account-specific baseline you set from a reconciled day, not25 a universal constant.264. Compute daily CPL in the AD ACCOUNT timezone for both spend and leads. Google's account27 timezone is permanent (senior-buyer-ops contract #5) — reconcile in the tracker, never by eye.285. Rows with unsubstituted `{{...}}` macros: exclude from performance analysis,29 then classify the cause — bots/crawlers, yes, but also a broken URL template,30 an unsupported/misspelled macro, or manual/direct traffic. Fix the template31 if it's yours before blaming traffic.3233## Route references3435| Need | Reference |36|---|---|37| Keitaro: key, report/build, measures, update_costs, postback/S2S, postback drill, gotchas | `references/01-keitaro.md` |38| Binom: legacy URL-param + v2 REST, reports, cost, postback/S2S | `references/02-binom.md` |39| CPL math, funnel + anti-fraud metrics, cohort nowcasting, backend optimization contract (status→CAPI event), TMA/bot CAPI without pixel, multi-tracker sync + conversion ledger, ATT asymmetry, mapping, daily routine | `references/03-metrics-and-math.md` |40| Google lane: gclid/gbraid/wbraid, ValueTrack chains, Keitaro/RedTrack Google config, OCI windows + dedup, the 2026-06-15 cutoff, Data Manager `events:ingest` for new tokens | `references/04-google-lane.md` |4142Platform lanes are not interchangeable — Meta counts through CAPI, Google through gclid → OCI, with different windows, a different dedup key, and a hard onboarding cutoff. Read `04` before wiring anything on Google traffic.4344## Non-negotiables4546- Work only on YOUR campaign IDs; every call carries a campaign filter. Other47 buyers' campaigns are read-never-touch.48- No cost push = no CPL/ROI (report cost is 0). Overwriting a period is safe49 (idempotent).50- API keys are write-once; store verbatim in gitignored notes.
sergeyizmailov