<b>Campaign template — the duplicate-and-launch checklist</b>
New campaigns should be cloned from a verified template, never built from scratch. Building fresh re-introduces solved bugs. Here's what a launch-ready template locks in.
The template must pre-contain:
— Naming convention auto-applied (so the clone inherits a parseable name).
— Postback URL with verified tokens already wired to the network.
— Distribution rule stack: filters → compliance → offer split → LP split, in order.
— Bot/proxy filter and target-GEO gate as hard rules at the top.
— Cost token configured for the source so spend auto-imports.
— A frozen control arm to benchmark against.
What you change per clone (and ONLY this):
— Offer URL(s) and payout
— Landing page(s)
— GEO/source targeting in the name
The discipline: if you find yourself editing the postback or rule order in a clone, the TEMPLATE is wrong — fix the template, re-verify it once, then re-clone. Never patch individual campaigns.
Maintain one template per traffic source. Re-validate each template monthly against a live test conversion.
Run this before every launch.
Tracker Playbook
@TrackerPlaybook
<b>Campaign template — the duplicate-and-launch checklist</b>
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.