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.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add sergeyizmailov/knowledge-delta-skills --skill tracker-ops --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Tracker Ops?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sergeyizmailov-tracker-ops)More formats (shields.io, HTML) on the badges page.
---
name: tracker-ops
description: "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."
---
# Tracker Ops
Count money correctly and automate tracker work. Keitaro + Binom specifics
below; the metric rules and daily sync port to any tracker.
## 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 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!