Postback Pilot
Postback Pilot
@PostbackPilot

Track approved, pending, and rejected leads separately—and make payout data actionable

Track approved, pending, and rejected leads separately—and make payout data actionable

A lead status changes how you read ROI and what your tracker sends to an ad platform. Create separate postback events for pending, approved, and rejected outcomes. Send the same click ID on every update, with lead ID, status, payout, and currency when available.

Use a strict map:
• Pending: received, but not yet billable.
• Approved: eligible for payout; send the confirmed value.
• Rejected: not payable; send zero or exclude it according to tracker rules.
A missing payout is not proof of an approved zero-value conversion.

When status changes, send an update instead of creating a new lead. Deduplicate by lead ID and status, and preserve the original click ID. Test each path with a controlled click; inspect raw logs, URL encoding, currency, and final values. Reconcile by click ID before comparing counts and approved payout with the network report.

Use pending for forecasting, but optimize on approved data when possible. Clear status mapping prevents duplicate conversions and makes payout gaps easier to find.
Этот пост опубликован в Telegram-канале Postback Pilot. Подписаться можно по ссылке: @PostbackPilot.
verticals

Свежие посты в категории «Verticals & Offers»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.