Skip to main content

What Happens if the Callback Fails

Written by GoKart Support

There are several reasons why a callback may fail to send, preventing your system from receiving the conversion notification that triggers user rewards.

When a callback fails, GoKart automatically logs the failure and provides both an automatic retry mechanism and a manual resend option to ensure delivery.


Identify if Your Callback Failed

There are two ways to know if a callback was not successfully delivered:

  • In your Conversion Reports, check the Callback Sent column. If the value is No, the callback did not send successfully

  • In the Conversion Callback tab of the Event Reports, check the Status column. If the status is Failed, the callback did not send successfully


Common Reasons for Callback Failures

A callback may fail for several reasons, including but not limited to:

  • Server downtime: Your endpoint or hosting service was temporarily unavailable when GoKart attempted delivery.

  • Firewall or permission restrictions: Your server blocked the incoming request due to security settings.

  • Unregistered or incorrect IP whitelisting: GoKart’s IPs are not allowed in your system’s network settings.

  • Invalid or expired authentication tokens: If your endpoint requires authentication, expired credentials may prevent callback delivery.

  • Malformed response: The endpoint returned an unexpected or invalid response format.


Automatic Retry Mechanism

If your servers were down and GoKart could not successfully deliver a callback request, the system will automatically retry using an exponential backoff strategy.

  • GoKart’s built-in retry mechanism is triggered for failures returning 500 or 503 responses.

  • The first retry occurs after 2 minutes, and each subsequent attempt doubles in delay (4 minutes, 8 minutes, etc.).

  • If all retry attempts fail, the request is marked as Failed in the system and visible in the Conversion Callback tab of the UI.

This mechanism helps recover from temporary network or server outages without requiring manual action.


Reviewing and Manually Resending Callbacks

Option 1:

  1. Identify the conversion that needs to be retried

  2. If an error message appears, review the issue and click Resend to reattempt delivery.

  3. Once successfully resent, your system will receive the conversion notification and the user can be rewarded as intended.

Option 2:

  1. Identify the Conversion ID that need to be retried

  2. Select I have Click ID and Conversion ID

  3. Input the Conversion ID and/or Event ID and hit Send

Did this answer your question?