Track approved, pending, and rejected leads separately in every postback flow

Track approved, pending, and rejected leads separately in every postback flow

Treat status and payout as separate fields. A lead can be pending without being revenue, then move to approved or rejected. Your tracker should preserve that transition instead of counting every callback as a sale.

Use the network’s exact status values and map them to three internal buckets:
• approved — store the payout and count it as revenue;
• pending — store the lead, but exclude it from revenue;
• rejected — mark it invalid and do not credit payout.
If payout is unavailable, leave it blank unless your platform requires zero.

Pass a stable click ID, conversion ID, status, payout, and currency when available. Keep parameter names consistent, encode values correctly, and take payout from the network callback or report—not from a value supplied by the landing page.

Expect duplicate callbacks and status changes. Deduplicate by conversion ID, then update the existing record for pending → approved or rejected. If updates are not supported, reconcile pending records against the network report.

Keep revenue logic tied to approved status, not to the first conversion signal. That single rule prevents most inflated totals and mismatched reports.