Browse help topics
Postbacks and conversions
Your postback URL, its parameters, signatures, tests, statuses and reversals.
Set up
- How to set up a postback URL Create your postback secret, add one Conversion postback for every offer, then send a test before any traffic. Networks use Workspace settings.
- Verify a signed postback with HMAC-SHA256 Every publisher postback carries a verifier made with your
ps_secret. Strip it, hash the rest of the URL as received, compare, then credit the user. - Send a test postback Choose Send test postback on a saved row. It's signed like a real postback and carries
test=true. It proves your URL answers, not that traffic routes there. - One postback per step on multi-step offers Each step a user completes sends its own postback, with its own
action_id,goal_idand amounts. Install-paid games pay you once, at install. - Pull conversions instead (Reporting API) Call
GET /publisher/conversionswith yourpk_key to read your conversions under the sameaction_idyour postbacks carry. For reconciling and catching up.
Reference
- Postback parameters and macros, one by one Every parameter and macro a postback can carry, when each is sent, and which money field is yours on each lane. Network postbacks are listed apart.
- Global or offer-specific postbacks: which one fires For each conversion we pick one active postback row. A row for that offer beats a global one, and a row naming the exact event beats a general one.
- Conversion statuses: what each one means A conversion is completed, reversed or rejected. Only the first two post back to you. Here is what each means, where it shows and what your server does.
- How to answer a postback, timeouts and retries Answer with a 2xx, then credit the user. We retry publisher postbacks after a timeout, a 5xx or a 429, never after another 4xx, and never resend on our own.
When something's wrong
Nothing in this topic is written for that role yet. Search the Help Center or write to us.
Other topics
- Getting started 7 articles
- Account, team and security 8 articles
- Offers and the feed 13 articles
- Hosted Offerwall 10 articles
- Offer Links and click tracking 6 articles
- Fraud Defense and traffic quality 5 articles
- Reporting 5 articles
- Payouts, billing and funding 6 articles
- Advertiser campaigns 10 articles
- Running a network 3 articles
- Troubleshooting 8 articles
- Developer docs 3 articles
- Messages your users might see
- Glossary 41 terms
Support
Still stuck? Write to us.
One address for every question: hello@affiliateos.ai. Put the details from this list in your first message so we can find the click or conversion without asking you for them again.
Put these in your message
- 01The email you sign in with
- 02Your role: publisher, advertiser or network
- 03The offer ID
- 04The click ID or
action_id - 05The time it happened, with your time zone
- 06What you expected to happen
Looking for a reward in an app? Ask that app's support. It credits your reward, so only it can see your balance.