Clicks & conversions
Conversion statuses and processing schemes
Define how pending, approved and repeat events affect conversions and revenue.
Define your event model
A lead can be created, approved, rejected or billed again. Decide which events should count as conversions and how revenue changes before configuring the processing scheme.
Configure the scheme
Open Settings → Postback processing and review the available rules. Match the values actually sent in cnv_status and cnv_status2. Connect the scheme to the relevant offer or configuration using the controls available in your panel.
| Question | Decision to document |
|---|---|
| Pending event | Count now or wait for approval? |
| Approved event | Replace payout or add revenue? |
| Rejected event | Which existing values should change? |
| Repeat bill | Same conversion context or a distinct event? |
| Outgoing postback | Which transitions should notify the source? |
Test the sequence
Use one controlled click. Send the planned status sequence in order and inspect the record after every request. Then repeat a notification to check duplicate behavior. Verify both aggregate revenue and the individual conversion history.
Resolve discrepancies
Check the offer's Upsell setting, any payout overrides and campaign postback settings. A correctly received status can still be ignored or transformed by a scheme. Preserve the input values and expected transition so troubleshooting is based on the actual policy.