Tracker Playbook
21 subscribers
76 photos
12 videos
166 links
Repeatable systems for Voluum, Keitaro and friends: naming conventions, campaign templates, postback checklists and the exact setup steps to never lose a conversion to a config error.
Download Telegram
Redirect tracking vs direct (no-redirect) — when to use which

Both pass clicks. The tradeoff is speed vs control. Match the method to the constraint.

Use redirect (302) when:
— You need rotation, A/B path splitting, or geo/device rules at click time.
— You're cloaking or running multiple offers behind one link.
— You need server-side click logging you fully control.

Use direct tracking (tracking pixel + landing-side script) when:
— The traffic source penalizes redirects (some native/social do).
— Page speed is the conversion bottleneck — you save one hop.
— You only need attribution, not real-time routing.

Tradeoffs to log:
— Redirect adds 80-200ms but unlocks distribution logic.
— Direct keeps speed but you lose mid-click branching — all logic moves to the lander JS.
— Direct breaks if the lander's script is blocked; redirect breaks if your domain is flagged.

Default: redirect for paid arbitrage, direct for SEO/owned traffic where speed is king.

Save this SOP. Run this before every launch.
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
В публичный релиз вышел Fable 5.1

➡️ Читайте на сайте: https://aff.top/blog/v-publichnyi-reliz-vyshel-fable-5-1

🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
1xBet перестал спонсировать эмоции

История о том, как казахстанцы зарегистрировали рекламный слоган 1xBet, а сам бренд оказался в юридической ловушке: после сделки с TonyBet права на товарный знак так и не выкупили. На фоне ареста активов Романа Семиохина и уголовного дела по азартным играм вывод простой: с 1xBet сейчас лучше не строить рекламные связки на рынке Казахстана.

➡️ Читайте на сайте: https://aff.top/blog/1xbet-perestal-sponsirovat-emocii

🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
За продажу аккаунтов в мессенджере теперь грозит статья

С 1 сентября 2026 года продажа аккаунтов соцсетей и мессенджеров в России стала уголовно и административно рискованной: штраф до 700 тысяч рублей, принудительные работы или лишение свободы до 2–3 лет. Если через аккаунт украдут деньги, продавца могут записать в соучастники мошенничества по ст. 159 УК РФ с риском до 10 лет.

➡️ Читайте на сайте: https://aff.top/blog/za-prodazhu-akkauntov-v-messendzhere-teper-grozit-statia

🧠 Ещё больше инсайтов → в канале AFF.top
S2S postback vs pixel firing — choose by attribution risk

A conversion can report two ways. They are not interchangeable. Decide by where the conversion happens.

Use S2S (server-to-server) postback when:
— Conversion fires server-side (deposit, sale confirmed in network backend).
— You can't trust the user's browser (ad-blockers, app environments, cookie loss).
— You need iOS/Safari-proof attribution.

Use pixel (client-side) when:
— Conversion is a browser event you control (button click, thank-you page).
— The advertiser only offers a pixel, no postback URL.
— You need same-session retargeting data.

Failure modes to weigh:
— Pixels lose 5-20% to blockers and early-exit; S2S loses 0% but needs a click ID round-trip.
— S2S requires the network to store and return your click_id — if they drop it, you get null conversions.
— Pixels can double-fire on refresh; dedupe by transaction ID.

Rule: money events → S2S. Engagement events → pixel. Never trust a pixel for revenue.

Save this SOP. Run this before every launch.
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Google выпустил в релиз Gemini 3.8 flash

Google выпустил Gemini 3.8 Flash спустя две недели после 3.7: модель обещает сильный кодинг и быстрый отклик, а цена остаётся низкой — $0,75 за млн входящих токенов и $3,75 за млн исходящих. Вывод простой: пока Google демпингует, это выгодный вариант для тех, кому нужны дешёвые и быстрые нейросетевые запросы.

➡️ Читайте на сайте: https://aff.top/blog/google-vypustil-v-reliz-gemini-3-8-flash

🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Яндекс запустил сервис ПроБлогер

Яндекс запустил ПроБлогер — платформу для монетизации небольших каналов и групп во ВКонтакте, Дзене, Максе, Telegram, YouTube и Rutube. Для модерации нужны от 1000 подписчиков, свежие публикации, статус самозанятого, ИП или юрлица и соблюдение закона. Доход доступен через автопостинг с оплатой за просмотры и партнёрские ссылки; CPM можно задать самому или отдать аукциону.

➡️ Читайте на сайте: https://aff.top/blog/iandeks-zapustil-servis-probloger

🧠 Ещё больше инсайтов → в канале AFF.top
Forwarded from AFF.TOP - про арбитраж трафика и CPA рынок!
This media is not supported in your browser
VIEW IN TELEGRAM
Google ads упростил перенос креативов из Asset Studio

➡️ Читайте на сайте: https://aff.top/blog/google-ads-uprostil-perenos-kreativov-iz-asset-studio

🧠 Ещё больше инсайтов → в канале AFF.top
click_id vs sub-id tokens — which carries what

People jam everything into one token. Separate the jobs. Two different tokens, two different purposes.

click_id (single unique value):
— Job: round-trip identity for postback matching.
— One per click, opaque, never reused.
— Goes out in the offer URL, comes back in the postback. That's it.

sub-id / sub1-sub10 (structured passthrough):
— Job: carry campaign metadata you want in conversion reports.
— Holds creative ID, placement, geo, audience — readable values.
— Passed for slicing, not for matching.

When each breaks:
— Using sub-ids for matching → collisions when two clicks share metadata. You can't dedupe.
— Stuffing metadata into click_id → unreadable reports, you parse strings forever.
— Networks with limited token slots: protect click_id first, then prioritize sub-ids by reporting value.

Mapping rule: one click_id for truth, sub-ids for context. Reserve sub1 for your most-sliced dimension (usually placement or creative).

Save this SOP. Run this before every launch.
Weighted rotation vs auto-optimization — when to let the tracker decide

Your tracker can split traffic two ways. Manual weights or algorithmic. Pick by data volume, not preference.

Use weighted rotation (manual %) when:
— Daily conversions under ~50 — too thin for an algorithm to learn.
— You're testing a known hypothesis (60/40 split, controlled).
— You need predictable distribution for a brand or capped offer.

Use auto-optimization (AI/RON) when:
— Conversions per path exceed ~100/day — statistically feedable.
— You have 4+ paths and can't babysit weights hourly.
— The optimizer can act on revenue, not just CR.

Tradeoffs to record:
— Auto-opt exploits the current winner but stops exploring — it can lock onto a lucky early lead.
— Manual weights never overfit but they never improve on their own either.
— Hybrid: hold 10-15% on forced even rotation as a control arm even when auto-opt runs the rest.

Rule: thin data → manual. Thick data → auto with a control arm. Never auto-optimize on
First-click vs last-click attribution in your tracker — pick by payout model

Your tracker attributes a conversion to one touch. Which touch decides who gets paid and what you scale.

Use last-click when:
— You buy on a CPA/CPL deal — the network credits the last referrer, match it.
— Funnels are short (one lander, one click).
— You need numbers that reconcile with the advertiser's panel.

Use first-click when:
— You run multi-step content funnels and want to credit the discovery source.
— You're judging top-of-funnel channels that rarely close directly.

Tradeoffs to weigh:
— Last-click undervalues awareness sources — you'll cut a channel that actually starts conversions.
— First-click overvalues cheap broad traffic that never closes.
— Mismatch with the advertiser's model = reconciliation hell every payout cycle.

Default rule: match your tracker's attribution window and model to the advertiser's exactly. Run a second "analysis" view with first-click only for channel insight — never for payment reconciliation.

Save this SOP. Run this before every launch.