Player ID Stability: Why Postback Matching Decides Reward Reliability
Player ID Stability: The Foundation of Reliable Rewards
Every offerwall conversion must match a real user in your database. The link between them is the player ID – and instability there is the #1 cause of lost credits.
Why IDs Break
Random session IDs, device IDs that change, or email-based IDs that users change – all break the postback match. The result: completed offers that never credit.
The Stable ID Rule
Use your internal user ID from your backend user table. It never changes across sessions, devices, or reinstallations – postbacks always match.
Implementation
Pass the stable ID to PerkoxOfferwall.create(…) at launch. Configure postbacks with {player_id} placeholder. Your backend joins postbacks to users by ID.
Frequently Asked Questions
What breaks postback matching?
Unstable IDs – random, device-based, or changeable identifiers.
What is a stable ID?
Your internal user ID from your database.
How does Perkox use the ID?
It travels through the SDK and postbacks to match rewards to users.
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.