S2S token mapping — build sheet for any new source
Before integrating a new traffic source, fill this mapping sheet. Pass it through tokens at click time so they round-trip on the postback.
Columns to map (source token to tracker variable):
— Click identifier to your tracker's pass-through field. This is the spine of S2S — without it nothing reconciles.
— Cost macro to your cost field. Pull real spend if the source supports it ({{cost}} on push networks, manual otherwise).
— Campaign ID to a custom variable. Lets you split-test source-side without losing tracker granularity.
— Creative/ad ID to a second custom variable. Required for creative-level optimization.
— Placement/zone ID to a third. This is where 80% of your fraud and waste hides.
— Site/publisher ID to a fourth, if the source exposes it.
Validation steps:
— Send one test click. Confirm every mapped token resolves in the tracker log, none left as literal {macro}.
— Unmapped literal macros mean the source uses different syntax. Check their docs, do not guess.
— Confirm the pass-through identifier survives the full redirect chain to the offer and back on the postback.
Keep one mapping sheet per source in a shared folder. New offer on a known source means zero new mapping work.
Save this SOP. Run this before every launch.
Tracker Playbook
@TrackerPlaybook
S2S token mapping — build sheet for any new source
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.