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.