<b>Token reference table — stop guessing macro names</b>
Every source and tracker names its macros differently. Guessing wastes test budget. Build one reference table and never guess again.
Maintain a sheet with one row per source, columns for each token:
— Click ID: Voluum <code>{cid}</code>, Keitaro <code>{subid}</code>, Binom <code>{clickid}</code>
— Source cost: most use <code>{cost}</code> but push networks vary (<code>{bid}</code>, <code>{payout}</code>)
— Creative ID: <code>{creative_id}</code> / <code>{banner_id}</code> / <code>{ad_id}</code>
— Zone/placement: <code>{zoneid}</code> / <code>{site_id}</code> / <code>{pub_id}</code>
— GEO and device: confirm whether the source passes these or you derive them in-tracker
Rules:
— Curly-brace style differs: some sources use <code>{token}</code>, others <code>[token]</code> or <code>##token##</code> — copy exactly
— Verify each token returns a real value in a test click, not the literal macro string
— When a source updates its macro list, update the table the same day
This table turns offer setup from trial-and-error into copy-paste.
Save this SOP. Run this before every launch.
Tracker Playbook
@TrackerPlaybook
<b>Token reference table — stop guessing macro names</b>
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.