All articles
Platform
Postback audit checklist
A practical auditing checklist for monitoring postback health, retries, status mapping, and reconciliation readiness.
KiwiWall
ยท
Jul 03, 2026
ยท
10 min read
Postback audit checklist in brief
A postback audit is the easiest way to prevent silent reporting drift. Focus on completeness, consistency, and timing before increasing spend.
Who this is for
- Technical operators handling KiwiWall integrations.
- Campaign teams reconciling conversion data.
- Support teams closing payout and status disputes.
Definition
Audit scope includes:
- incoming postback schema integrity
- status mapping consistency
- retry handling
- payout and approval output
Decision table
| Checkpoint | Pass criteria | Fail action |
|---|---|---|
| Required IDs present | 100% for sampled traffic | Quarantine source |
| Retry and queue health | No abnormal retries or backlog spikes | Investigate integration path |
| Status mapping | Shared dictionary enforced | Pause reconciliations |
| Latency | Within alert threshold | Increase monitoring and cap |
How it works
- Run baseline against known-good traffic.
- Compare postback status and reason codes day-over-day.
- Verify retry handling and dedupe outcomes.
- Document every variance with owner.
Checklist
- Validate schema completeness on live traffic.
- Verify conversion id mapping.
- Compare postback status with advertiser records.
- Record retry and timeout failure clusters.
Conversion link
Use this audit before the Postback QA checklist and Fraud review decision tree.
Next up
Week one launch timeline