The Offerwall Integration Checklist: 20 Steps Before Launch
The Offerwall Integration Checklist: Go Live Without Gaps
Most offerwall launch problems are predictable. This 20-step checklist covers everything from publisher approval to postback testing – work through it before you go live.
The Checklist
1. Publisher account approved. 2. App live on Google Play/App Store. 3. App approved in Perkox dashboard. 4. App ID and SDK Key saved. 5. SDK added to project. 6. SDK initialized at launch. 7. Stable player ID passed. 8. Offerwall entry point built. 9. Reward events handled. 10. Postback URL configured. 11. Postback signature verified. 12. click_id dedup implemented. 13. All four statuses handled. 14. HTTP 200 responses. 15. Currency configured. 16. Design customized. 17. Sandbox test passed. 18. Device test passed. 19. Analytics verified. 20. Go live.
The Most-Skipped Steps
Status handling (especially reversed) and click_id dedup are the two most-skipped steps – and the two that cause the most revenue bugs.
Steps 1-5: Account and App Setup
The first five steps cover the foundation. Publisher account approval (step 1) involves a quick review of your developer profile and app portfolio – typically 1-2 business days. Your app must be live on Google Play or the App Store (step 2) because Perkox needs to verify the store listing before approving the app in the dashboard (step 3). Once approved, you receive an App ID and SDK Key (step 4) – save these immediately in a secure location, as you will need them for SDK initialization. Adding the SDK to your project (step 5) is platform-specific: Gradle dependency for Android, CocoaPods for iOS, Unity Package for Unity, pub.dev for Flutter, npm for React Native. Each platform’s integration guide lives in the Perkox docs.
A common mistake at this stage: starting SDK integration before app approval is complete. The SDK will initialize but offers will not populate until the app is approved in the dashboard. Save time by getting approval first, then integrating.
Steps 6-10: SDK Integration and Entry Points
SDK initialization (step 6) should happen at app launch, not on-demand, to ensure the offerwall is ready when the user accesses it. The stable player ID (step 7) is critical – use a persistent user identifier (not a device ID) so earned rewards follow the user across devices. A UUID generated server-side and stored in user preferences is ideal. Building the offerwall entry point (step 8) means creating a button or icon in your UI that opens the offerwall. Place it in the shop, settings, or home screen – never as an interruptive popup. Reward events (step 9) handle the callback when a user completes an offer; this is where you credit the virtual currency to the user’s account.
Step 10 – postback URL configuration – is where many publishers create problems. The postback is a server-to-server notification that a conversion occurred. Configure it with the correct URL and all required placeholders ({user_id}, {offer_id}, {amount}, {status}, {signature}). Test it in sandbox before going live.
Steps 11-15: Validation and Currency
Postback signature verification (step 11) prevents reward fraud – without it, anyone who knows your postback URL can fake conversion notifications. The click_id deduplication (step 12) prevents double-crediting when the same conversion sends multiple postbacks (which happens more often than publishers expect). Handling all four statuses (step 13) – pending, confirmed, reversed, and disqualified – ensures revenue accuracy. The reversed status is the most-skipped: if you do not handle reversals, users keep rewards that advertisers refunded, creating a revenue leak. HTTP 200 responses (step 14) tell Perkox your server received the postback; anything else triggers retries. Currency configuration (step 15) defines the exchange rate between real revenue and virtual rewards.
Steps 16-20: Polish and Launch
Design customization (step 16) – logo, colors, currency icon – makes the offerwall feel native to your app. Sandbox testing (step 17) lets you verify the full flow without real conversions. Device testing (step 18) confirms the offerwall renders correctly on real devices. Analytics verification (step 19) ensures revenue appears in the dashboard. Step 20: go live with confidence.
Why This Matters
Every step on this checklist exists because a publisher skipped it and lost revenue. The most expensive skips are status handling and click_id deduplication – together they account for the majority of post-launch revenue bugs. A publisher who does not handle the reversed status will see revenue drift: dashboard shows earnings, but actual payout does not match because reversed conversions were never deducted from user balances. A publisher who skips click_id dedup will double-credit users when duplicate postbacks arrive, paying out twice for single conversions. Both bugs are silent at first and compound over time.
The checklist takes under an hour to complete with the Perkox docs open. The cost of skipping a step is hours of debugging, revenue leaks, and user support tickets. The math is simple: do the checklist.
Key Takeaway
This 20-step checklist covers every critical point from publisher approval through go-live. The most-skipped steps – reversed status handling and click_id deduplication – cause the most revenue damage. Work through the list top to bottom before launch, test in sandbox, verify on device, and confirm analytics before going live. An hour of checklist work prevents weeks of post-launch debugging.
Frequently Asked Questions
What is the most-missed step?
Handling the reversed status – revenue leaks follow.
How long does the checklist take?
Under an hour with the Perkox docs open.
Where do I start?
Register, get approved, then work the list top to bottom.
Start Monetizing with Perkox
Register as a Perkox publisher and integrate the rewarded monetization SDK. Read the documentation
Perkox provides rewarded monetization infrastructure – SDKs, tracking, analytics, and reward validation – for mobile apps and games across Android, iOS, Unity, Flutter, and React Native.