Introduction
Platform Overview
RevU is a performance-based monetization marketplace designed to bridge the gap between high-quality global advertisers and digital publishers. The platform’s strategic objective is to maintain a sustainable equilibrium between frictionless user experience and stringent advertiser quality standards. By offering a rewards-based model rather than intrusive display advertising, RevU incentivizes genuine engagement, ensuring long-term revenue growth for publishers across web and mobile environments.
A successful integration relies on understanding the "Journey of a Click," which follows a secure server-to-server (S2S) flow:
User visits RevU
A user clicks the offerwall or direct offer, and RevU ingests your unique User ID (UID) and any custom variables (SID 3, 5, or 6).
Click ID Generation
When the user clicks on an offer, RevU generates an internal Click ID to track the session with the advertiser.
The Conversion (Incoming Postback)
When the user fulfills the offer requirements (such as reaching a game level or completing a survey), the advertiser triggers an Incoming Postback to RevU. This notification references the original Click ID to signal a successful conversion.
Validation & Record Update
Before any reward is processed, RevU’s engine runs the incoming data through a series of matching and fraud-prevention rules. We verify that the transaction isn't a duplicate, that the transaction aligns with the offer's requirements, and that no suspicious patterns are detected. Once validated, the transaction is officially recorded in our ledger, updating the billing records for both the advertiser and the publisher.
The Reward (Outgoing Postback)
Finally, RevU notifies your server to issue the reward. 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.
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. You provide RevU with a Postback Template URL containing dynamic placeholders (variables) for the data you wish to receive. Our system automatically populates your placeholders with the actual values and calls your server via a GET request, delivering the completed URL.