Preflight Checklist

Before officially launching RevU to your users, complete this checklist to ensure that tracking is accurate, your reward engine is secure, and the user experience is optimized for high conversion

1. Offerwall Entry Point & User ID Passing

• Action: Verify that your "Earn Rewards" button or placement is correctly appending the user's unique identifier to the URL.

• Verification: Click the button in your app and confirm the resulting URL matches the required format: https://wall.revenueuniverse.com/[Offerwall ID]/offers/[User ID]. Ensure the User ID (UID) is a unique, persistent identifier for the end user to ensure they can be credited correctly later.

2. External Browser Redirects

• Action: Ensure that the offerwall (and specifically offer clicks) always open in the user’s native external browser (e.g., Safari on iOS, Chrome on Android). Opening offers in a WebView or an in-app browser is a common cause of session loss and tracking failures.

• Verification: Test the flow on a mobile device. When you click an offer from the wall, it should launch the device's default browser via https://publishers.revenueuniverse.com/click.php.

3. Postback Crediting Test

• Action: Use the built-in testing tool in the RevU Publisher Portal to simulate a conversion.

• Steps:

  1. Navigate to the "Configure Postbacks" section of the portal.

  2. Select the specific Offerwall deployment you are testing.

  3. Enter a test User ID in the SID2/UID field.

  4. Enter a sample currency amount and hit Submit.

• Verification: Confirm that your server receives the postback and correctly credits the user's account in your database.

4. Postback Security (IP Allowlist)

• Action: Configure your server to only accept incoming postbacks from RevU’s authorized IP addresses to prevent reward impersonation.

• Verification: Ensure your firewall or application logic allows the RevU IPs (available from your account manager).

5. Server Response & Timeout Policy

• Action: Confirm your server is optimized to handle the RevU postback request efficiently.

• Verification: Your server must respond within 8 seconds (4 seconds to connect, 4 seconds to complete the post). Ensure your postback script does not return the single word "FAIL", "FAILED", or "FAILURE" in the response body, as this will trigger the RevU retry policy (up to 6 attempts every 10 minutes).

6. Final Conversion Verification

• Action: Perform a "live" test by completing a real, low-friction offer (such as a simple app install or survey).

• Verification: Confirm that both the click and the conversion are verified and appear in your Publisher Portal Reporting.