DocsHelp
Testing and troubleshooting
How to test your integration before launch, and how to fix the problems we see most often.
Test the offerwall link
- In the Integration tab, type a user ID into Test a link. It shows the exact link your server should build.
- Build the link with your own code for the same user ID and compare the two. They must be identical.
- Open your link. You should see the offerwall, not the Link not valid page.
Test postbacks
- Save your postback URL, then click Send test postback in the Postback tab.
- The message under the button shows what your server answered. Every attempt is also listed under Logs, Postbacks.
- The test uses status 1, user
test_user, a transaction ID that starts withtest_, and a payout of $1.
Common problems
| What you see | Cause | Fix |
|---|---|---|
| Link not valid | The hash does not match the user ID. | Sign the exact user ID you put in the link, use the link hash salt, not the postback secret key, and output lowercase hex. |
| Missing user ID | The user ID is empty or has characters we do not accept. | Use 1 to 128 characters from A-Z a-z 0-9 . _ @ : + - and URL-encode it. |
| The offerwall does not load in your iframe | The page is not on the website you registered for the app. | Embed it on that domain or a subdomain, or ask us to change the website. |
| Postback log shows 403 or 404 | Your script rejected the call, or the URL is wrong. | Open the URL from the log in a browser and check your hash code. |
| Postback log shows a timeout | Your script takes longer than 6 seconds. | Answer with 200 first, or make the slow work run in the background. |
| Postback log shows 301 or 302 | Your URL redirects, for example from http to https. | Use the final URL. We do not follow redirects. |
| Postbacks never arrive | A firewall or bot protection blocks server requests. | Allow our requests to your postback path. Ask support for our IP addresses if you need them. |
You see {user_id} in your logs | A macro is misspelled. | Copy the macros from the Postback tab. |
| Hash mismatch on postbacks | The values were changed before hashing, or the wrong key is used. | Hash the values exactly as received, in the order transaction ID, user ID, reward, status, with the postback secret key. |
| A user got a reward twice | The same transaction was processed twice after a retry. | Store the last status per transaction ID and skip repeats. |
Questions
Can I use the same app for my website and my mobile app?
Yes, as long as the user ID is the same for the same person on both. If they need different currencies, add a second app.
Do I get a postback when a user only starts an offer?
No. Started and expired offers are shown to the user on the wall, but they are not sent to you.
Can the reward in a postback be negative?
No. The status tells you whether to add or take back.
Who do my users contact about a missing reward?
You. If you cannot solve it with your own records, send us the user ID, offer name, and date at [email protected].