Integration docs
Outgoing Postbacks Overview
Outgoing postbacks are the final and most critical step in the conversion lifecycle for a publisher. They are server-to-server (S2S) notifications sent from RevU directly to your server endpoint to confirm that a user has successfully completed an offer and should be rewarded.
This mechanism allows you to credit your users instantly and reliably without requiring any client-side logic or manual oversight.
How Outgoing Postbacks Work
The outgoing postback functions as a "reverse" of the initial click flow. While you pass variables to RevU at the start of a user’s journey, RevU "mails" that data back to you once a conversion is validated.
The Template System: You provide RevU with a Postback Template URL containing dynamic placeholders (variables) for the data you wish to receive.
Population: When a user completes an offer and passes the "RevU Check" (validation), our system automatically populates your placeholders with the actual values from that transaction.
The Request: RevU calls your server via a GET request, delivering the completed URL.