A dating SmartLink may contain several destinations and event models. The tracking implementation must therefore preserve the original traffic identifiers while also recording the selected route, conversion event, status and payout.
Where approval or paid events arrive later, the same commercial record must support status and revenue updates without creating duplicate conversions.
- Preserve source, campaign, placement and tracker click IDs across the full redirect chain.
- Return explicit event type, status, payout and currency in the postback.
- Record destination or route ID where the SmartLink provider exposes it.
- Support pending, approved, rejected and rebill events where the commercial model requires them.
- Reconcile source, tracker and network data at transaction level before scaling.