Conversion & Postback Event Flow
This document compares the current and future architectures for how conversion and postback events flow through AdAction systems. Use these diagrams as a comparison tool and migration roadmap.
Current State
The current flow relies on Tune (3rd-party campaign management) for conversion approval routing and the AdGem API for crediting users and sending outgoing webhooks to publishers.
Future State
The future architecture eliminates Tune and the AdGem API. Keystone routes directly to the Player API, ML models handle fraud/quality scoring, and a dedicated Outgoing Webhook Service replaces AdGem API's webhook responsibilities.
What Changes
| Category | Systems | Notes |
|---|---|---|
| Retired | Tune, AdGem API | No longer in the conversion/postback path |
| Added | ML Models (fraud/quality scoring), Outgoing Webhook Service, AdSuite Review Module | New purpose-built services |
| Unchanged | MMPs (Adjust, Appsflyer), Keystone, Player API | Core tracking and reward systems remain |
Key differences:
- No Tune dependency — Keystone routes conversions directly instead of forwarding to a 3rd-party platform
- ML-driven decisions — Automated fraud/quality scoring replaces Tune's approval rules
- Dedicated webhook service — Outgoing postbacks are handled by a standalone service instead of being embedded in the AdGem API
- AdSuite for manual review — Replaces Tune's manual approval workflow with an internal tool
Migration Stages
All stages are planned/future. Each stage can be validated independently before proceeding to the next.