Architecture Overview
High-level flow for how Trakqio, the Trakqio SDK, GrabMyRewards, ad networks, and offerwalls can work together in one tracking and rewards ecosystem.
Apps + Games
Mobile apps, Unity games, APK installs, and web properties that emit installs, sessions, events, and ad revenue signals.
Trakqio SDK
Captures device identifiers, user IDs, sessions, events, ad impressions, and callback parameters, then posts them to Trakqio endpoints.
Trakqio Platform
Normalizes traffic, stores request logs, runs dedup + fraud checks, attributes campaigns, exposes dashboards, and dispatches callbacks.
Offerwalls + Ad Networks
Provide click sources, campaign IDs, postback destinations, payout rules, and traffic supply for installs or rewarded events.
GrabMyRewards
Consumes validated conversions from Trakqio and turns them into centralized user rewards, wallets, partner rules, and merchant outcomes.
App / Game -> Trakqio SDK -> Trakqio API -> Trakqio validation + attribution + callbacks
| |
| +-> Offerwall / Ad Network postbacks
|
+-> Revenue / event / install signals
|
+-> Approved conversion feed -> GrabMyRewards
Recommended role split
- Trakqio owns attribution, validation, logs, fraud, and callback control.
- SDK focuses on lightweight event collection and transport.
- Offerwalls and ad networks remain external traffic and payout partners.
- GrabMyRewards remains the central rewards ledger and redemption layer.
Why this split works
- Tracking logic stays decoupled from rewards logic.
- Multiple acquisition partners can share one validation layer.
- Only approved conversions flow into the rewards engine.
- Each product can evolve independently without breaking the others.