Alogame SDK
Integrate authentication, payments, analytics, and push notifications into your Android, iOS, or H5 (web) game.
Choose your platform
H5 games are login + analytics
The Web (H5) SDK implements login and Adjust/GA4 event tracking. Top-up, account info, change password, and logout are handled by the SDK's floating button, which redirects to the Alogame portals — so there's no payment/IAP or push setup on web.
Integration checklist
Complete these steps in order for each platform:
| # | Step | Android | iOS |
|---|---|---|---|
| 1 | Add SDK dependency & config file | Install | Install |
| 2 | Implement login flow | Authentication | Authentication |
| 3 | Bind player role after login | Game Role | Game Role |
| 4 | Integrate in-app purchases | IAP | StoreKit |
| 5 | Configure event tracking | Tracking | Tracking |
| 6 | Set up push notifications | Push | Push |
| 7 | Add account dashboard | Dashboard | Dashboard |
Credentials
Contact your Alogame Operation Manager to obtain:
| Credential | Used in | Notes |
|---|---|---|
game_id | oeg_config.json (client) | Identifies your game |
client_key | oeg_config.json (client) | SDK authentication |
secret_key | Game server only | S2S webhook signature — never embed in client |
The client credentials go into oeg_config.json, which is bundled into your app. The secret_key is used exclusively by your game server to verify Alogame webhook callbacks.
What the SDK provides
| Feature | Android | iOS | Web (H5) |
|---|---|---|---|
| Guest login / Play Now | ✅ | ✅ | ✅ |
| Alogame Account | ✅ | ✅ | ✅ |
| Google login | ✅ | ✅ | ✅ |
| Facebook login | ✅ | ✅ | ✅ |
| Sign in with Apple | — | ✅ | — |
| TikTok login | ✅ | ✅ | — |
| Google Play Billing IAP | ✅ | — | — |
| Apple StoreKit IAP | — | ✅ | — |
| Top-up / recharge | via SDK | via SDK | floating button → portal |
| Adjust tracking | ✅ | ✅ | ✅ |
| Firebase push (FCM) | ✅ | ✅ | — |
| APNs push | — | ✅ | — |
| Account dashboard UI | ✅ | ✅ | floating button → portal |