Offer campaign troubleshooting
Use the campaign ID, current revision, and a development click or transaction ID when contacting support. Do not send postback tokens or user secrets.
| Symptom | Checks |
|---|---|
| Draft cannot be submitted | Open Readiness; check validated asset, creative, goal, positive budget, country, certified tracking choice, and credential |
| Campaign is approved but not visible | Confirm it is LIVE, within schedule, funded, under caps, and compatible with publisher placement, slot, country, platform, and policy |
| Destination receives no click ID | Confirm {click_id} appears in the HTTPS link template and no redirect removes its resolved value |
| Postback is rejected | For Custom S2S, check campaign key ID, signature, timestamp, click_id, transaction_id, exact goal_id, status, and the authentication response |
| Event is a duplicate | Reuse the same transaction ID for a retry; verify the original result instead of creating a second conversion |
| Reward remains pending | Check the goal's pending period and provider verification; do not issue a manual client-side reward |
| Budget falls faster than expected | Compare every milestone's gross revenue, caps, accepted conversions, reversals, and report freshness |
| Report differs from your system | Align UTC date boundaries, conversion status, late callbacks, and the report's freshness watermark |
Pause a live campaign when the destination or tracking is wrong, then investigate against development records. Changing the campaign creates a new draft revision that needs review. For a failed or refunded verified event, send a reversal tied to the original transaction rather than deleting history.
Endpoint details: offer postback reference and offer campaign API.