🔎 Postback Delivery + Debugging Info
Everflow is designed to ensure reliable postback delivery. If your server encounters an issue and a postback fails to deliver on the first attempt, Everflow will automatically try to resend it.
A failed postback will be retried periodically for up to 25 attempts.
If the postback still does not deliver successfully after 25 retries, it will be automatically disabled to prevent further delivery attempts to a potentially problematic endpoint.
The Network Manager will be notified of the failure
This is a safeguard to prevent persistent delivery failures from causing further issues
🧰 How to Debug a Postback
Everflow provides tools to help you troubleshoot postback delivery issues:
Go to Reporting > Postback in your Partner Dashboard
Locate the postback you want to inspect
Click the vertical three-dot menu at the end of the row
Select View Debug Info
This section will display detailed information about the postback attempt, including the response received from your server. Analyzing the response can provide valuable clues about why a postback might be failing (e.g., server errors, incorrect parameters).
🔍 What Happens When a Conversion Fires?
When a conversion occurs and your postback is correctly configured, Everflow will send an HTTP request (typically a GET request) to your specified postback URL. This request will include the conversion details as parameters in the URL (as shown in the examples above). Your server needs to be set up to listen for and process these incoming requests.
If your postback is set up correctly, Everflow will send a request to your server that looks like this:
GET https://yourdomain.com/conversion?transaction_id=abc123xyz
This lets your system know a conversion occurred.
⚠️ Common Mistakes to Avoid
Missing or incorrect {token} token: Ensure that the unique identifier (i.e. CLID, click_id, transaction_id, etc) is present and correctly spelled in your postback URL. This is the fundamental link between the conversion in Everflow and your system.
Forgetting to save the postback: After entering or modifying your postback URL and settings, always click the Save button to ensure your configuration is applied.
Testing before adding server-side logic: Do not expect postbacks to work and display data in your system until you have configured your server or tracking platform to receive and process the incoming postback requests from Everflow.
Expecting postbacks to work retroactively: Postbacks will only be triggered for conversions that occur after you have successfully saved the postback configuration in Everflow. They do not apply to past conversions.
Common Tracking Issues and Their Solutions:
No Clicks Registering:
Double-check the tracking link for errors.
Ensure the offer is active.
Verify the partner is approved for the offer.
No Conversions Registering:
Verify the postback URL is correct.
Check for any errors in the postback debug information.
Ensure the {transaction_id} token is correctly implemented.
Confirm that any necessary parameters are being passed in the postback URL.
Check that the advertiser's tracking is firing correctly.
Data Discrepancies Between Everflow and 3rd Party Platforms:
Check for differences in attribution models.
Compare time zones.
Ensure all necessary parameters are being mapped correctly.
Pixel Not Firing:
Use pixel helper tools to verify placement and event triggers.
Ensure the correct pixel ID is implemented.
Check for any JavaScript errors on the page.
Postback Failures:
Check the Everflow postback logs for error messages.
Ensure the partner's server is receiving and processing postback requests correctly.
Check for server downtime or connectivity issues.