In-App Event Tracking and Postbacks
Why Install Attribution Is Not Enough
Attributing an app install to an affiliate is only the first step. You do not pay commissions on installs -- you pay on deposits, trades, purchases, or sustained activity. In-app event tracking captures the post-install actions that determine commission value. Without it, your affiliate platform knows which partner drove the install but has no idea whether that user became valuable.
A Forex broker running an IB program tracked 500 mobile app installs from a single introducing broker in one month. Only after implementing in-app event tracking did they discover that 340 of those installs never completed registration, and only 48 made a first deposit. The IB was driving installs, not traders -- a distinction invisible without event-level tracking.
Defining Your Event Taxonomy
Your event taxonomy is the set of in-app actions you track and send to your affiliate platform. It should include every action that is relevant to commission calculation, partner quality scoring, or fraud detection. Keep the taxonomy tight -- tracking 50 events creates noise. Most programs need 5-8 core events.
| Event | iGaming Example | Forex Example | Prop Trading Example | Commission Relevance |
|---|---|---|---|---|
| Registration | Account created | Live account opened | Challenge account created | CPA qualification gate |
| Verification | KYC documents submitted | Identity verified | Email confirmed | Quality gate |
| First deposit | First real-money deposit | First fund transfer | Challenge fee paid | Primary CPA trigger |
| First activity | First bet placed | First trade executed | First challenge attempt started | Activity verification |
| Revenue event | Wager placed (with amount) | Trade closed (with lot size) | Challenge purchased (with tier) | RevShare / lot-based calculation |
| Repeat purchase | Second deposit | Account top-up | Second challenge purchase | Lifetime value signal |
| Churn signal | 14 days inactive | No trades for 30 days | Challenge expired without attempt | Negative quality signal |
Never send personally identifiable information (PII) in postback parameters. Send anonymized user IDs, event types, and revenue values -- not names, emails, or phone numbers. PII in postbacks violates privacy regulations and creates liability if the postback URL is intercepted or logged.
Configuring Revenue Postbacks
Revenue postbacks send the monetary value of an in-app action to your affiliate platform. For RevShare models, this is essential -- your affiliate platform needs the deposit amount, wager value, or trade volume to calculate the partner's commission. For CPA models, revenue postbacks help you measure the quality of traffic each affiliate sends.
- Include the revenue value in the postback payload as a numeric field (e.g., revenue=49.99 or lots=2.5)
- Specify the currency code alongside the amount -- mixed currencies without conversion create accounting errors
- Fire revenue postbacks in real time, not in batch -- delayed postbacks mean affiliates see stale dashboards
- Include a transaction ID to prevent duplicate postbacks from inflating reported revenue
- Separate gross revenue from net revenue if your commission model is based on NGR or net lot volume
Postback Architecture: MMP to Affiliate Platform
The standard architecture routes in-app events from your app SDK to your MMP, and from your MMP to your affiliate management platform via S2S postbacks. Your app fires the event, the MMP enriches it with attribution data (which affiliate drove this user), and your affiliate platform receives the attributed event and calculates the commission.
Some operators bypass the MMP for post-install events and send them directly from their backend to the affiliate platform. This works when you have already attributed the install and only need to track subsequent revenue. Direct backend-to-affiliate-platform postbacks are faster, carry no MMP event costs, and keep sensitive revenue data out of third-party systems.
Set up a postback validation layer that checks every incoming event for required fields (click ID, event type, revenue value, timestamp) before processing. Reject malformed postbacks immediately and alert your ops team -- malformed events are often the first sign of integration drift or fraud attempts.
Testing and Monitoring
- Run end-to-end tests for every event type: click the affiliate link, install the app, trigger each event, and verify the postback arrives with correct data
- Monitor postback success rates daily -- a sudden drop in postback delivery indicates an integration failure
- Set up alerts for revenue postbacks with zero values, negative values, or values above a threshold (likely data errors)
- Compare MMP-reported events against your internal database weekly to catch attribution discrepancies early
Key Takeaways
- Install attribution alone does not drive commissions -- you need in-app event tracking for deposits, trades, and purchases
- Keep your event taxonomy to 5-8 core events that directly map to commission triggers and quality signals
- Revenue postbacks must include amount, currency, and transaction ID to support RevShare calculations and prevent duplicates
- Never send PII in postback parameters -- use anonymized user IDs and event codes only
- Monitor postback delivery rates daily -- a drop in delivery is an early sign of integration failure
Explore Further
Key terms and tools related to this lesson. Deepen your understanding and see how Track360 supports these concepts.
Postback
A postback is a server-to-server HTTP callback confirming a conversion event like a registration, FTD, or purchase. Unaffected by ad blockers or cookies.
Affiliate Tracking
The end-to-end measurement of affiliate-driven activity from initial click through registration, deposit, and ongoing user revenue, supporting attribution, commission calculation, and fraud detection.
Publisher
A publisher is an individual or company that promotes an advertiser's products or services through an affiliate program in exchange for commissions on conversions they drive.
Mobile Tracking
Mobile tracking is the process of attributing affiliate-driven conversions that occur on mobile devices or within native apps, using methods adapted for mobile environments.