The postback test action exists in Everflow, but it's only available on the network side — not in the affiliate dashboard. So if you want to validate that your postback URL is correctly wired before a real conversion fires, email us and we'll run the test for you and report back what the destination received.
What to email us
Send a single email to reception@ourdream.ai with the subject line Postback test request and these four pieces of information:
- Your affiliate ID — visible in your Everflow profile / dashboard URL.
- Your Everflow login email — so we can match the request to your account.
- The full postback URL you want tested, with Everflow macros intact (e.g.
https://your-tracker.com/conversion?cid={sub5}&payout={payout}). - Any specific parameter values you need on our side — for example, "please send
{sub5}asabc123" if you want the test to mimic a click ID your tracker is expecting.
Copy-paste template
# To: reception@ourdream.ai
# Subject: Postback test request
Hi team, Could you please fire a test postback against the URL below? Affiliate ID: <your-affid> Login email: <your@email.com> Postback URL: https://your-tracker.com/conversion?cid={sub5}&payout={payout}&tx={transaction_id} Suggested test values: sub5 = test_click_abc123 payout = 36 transaction_id = test_tx_001 Thanks.
What we'll send back
Within one business day we reply with: the exact request we sent (URL after macro substitution), the HTTP response code your destination returned, and the response body if there was one. That's usually enough to identify any wiring or macro-spelling issue without further back-and-forth.
What this validates
- The destination URL is reachable.
- HTTPS / protocol is correct.
- Macro substitution is working (the test values come through correctly).
- Any required parameters are present and accepted.
What this does not validate
- Whether
sub5is actually being captured on real clicks (the test values are fabricated; they don't validate your landing page is appending the click ID). - Whether your tracker matches the test sub5 value to a real click — it won't, because there's no click record on your tracker to match against. The test confirms the postback is wired correctly; the next step is verifying live click capture.
Once the test postback comes back clean, the next thing to check is that real clicks are populating sub5. Open the click report in Everflow and inspect a recent click — if sub5 is populated, you're end-to-end ready. If it's empty, see why is my postback not firing.