Check Your Purchase Data Before Launching a Mobile Game Campaign

Before using purchases to guide a mobile game campaign, check that the data describes the transactions you care about. A “purchase” in a dashboard does not, on its own, prove that the payment was verified, the revenue was counted once or the media partner can use it for your campaign.
Use the two worksheets below with your UA, engineering and analytics teams. The first records what should count as a purchase. The second checks what happens to that purchase as it moves from the game to your mobile measurement partner (MMP) and media partner.
Decide which purchases should count
Are you trying to acquire first-time paying players, encourage repeat purchases, or evaluate purchase value? Decide which players and products qualify before choosing an event name in the dashboard.
Keep these four things separate:
- A recorded event: the system logged an action.
- A verified payment: the transaction passed the checks required by your payment-verification process.
- A paying player: a person or account counted under your agreed identity and eligibility rules.
- Revenue: the amount, currency and gross or net value you use in reports.
One player can make several purchases. A checkout attempt is not necessarily a completed payment.
For example, Google Play distinguishes pending purchases from completed ones. Its documentation says to verify the purchase and confirm the purchased state before granting the player their item. Ask engineering how those states feed your reporting. This example applies to Google Play; other payment systems need their own checks. Google Play purchase flow.
Write down what your purchase event means
Complete one record for each event you want the campaign to use. Keep purchase revenue separate from ad revenue, even if another report combines them.
Purchase definition
First or repeat purchase, eligible players/products, app, OS and markets
Event name and trigger
The name used at each step, when it is sent and which conditions must be met
Where it is sent from
Store/payment system, app SDK, server or connector; every route that could send the same transaction
Duplicate handling
Transaction identifier, who prevents or checks duplicate records and any known limits
Dates and times
When the purchase happened, when it was received, timezone and handling of delayed records
Value and currency
Amount source, units, transaction/reporting currency and any currency conversion
Revenue rules
Gross or net value, taxes, fees, refunds and who explains differences between reports
Exclusions
Pending/failed purchases, test records and any other activity that should not qualify
Partner setup
How the MMP event maps to the media partner's event, required fields and permitted data sharing
Test results
Expected and actual result, supporting record, setup/version, tester and unresolved questions
Suppose a fictional game team wants to count each account's first verified purchase. Someone must maintain that account's purchase history and decide what happens after a reinstall. A system's “first event” flag may not match the team's definition of a first-time payer.
Check the payment, the MMP and the media partner
Follow a test purchase through three checkpoints:
- Payment: confirm the store or payment status and save the verification result.
- MMP: check the event name, time, amount, currency and count in the measurement record.
- Media partner: confirm it received the expected event and can use it in the selected campaign setup.
A pass at one step does not prove the next. If you cannot see the partner's result, mark it unverified and name the person who will obtain confirmation.
The details depend on your implementation. For example, AppsFlyer's documented Android purchase-validation method records an af_purchase event after successful validation. Sending that event separately as well causes duplicate reporting. Check every route that can send a purchase before adding another. This is a specific AppsFlyer method, not a requirement to replace your current setup. AppsFlyer Android purchase validation.
AppsFlyer's documented duplicate-removal mechanism also has limits: it covers qualifying SDK events, not server-to-server events. Do not assume one duplicate check covers every route from your game to its reporting tools. AppsFlyer in-app event handling.
Test the cases that can distort your results
Ask engineering to write the expected result for your exact store, SDK, MMP and partner setup, using current documentation. Run checks in the approved test environment with clearly labeled test records. Record what actually happened alongside what you expected.
Completed eligible purchase
Verified payment, correct count/value and expected result at the media partner
Pending or cancelled purchase
A payment attempt is not wrongly counted as a completed purchase
Same transaction sent again
Handling follows the documented duplicate policy; retain the observed counts
Purchase sent by SDK and server/connector
Which route owns reporting, and how duplicate revenue is prevented or detected
Refund
How each relevant report and partner receives the adjustment; any unsupported behavior
Restore or reinstall
Whether an existing transaction is sent again and how first-purchase/payer counting behaves
Wrong currency or value
How the mismatch is detected, who resolves it and whether the data is usable
Test traffic
How test records are identified and kept out of production campaign decisions
Refunds and restores do not have one universal reporting rule. If a destination cannot handle an adjustment your business needs, document that limitation before deciding whether to use the event.
Media partners may also have specific requirements. Unity, for example, publishes AppsFlyer event-mapping and revenue-value requirements. Check the actual destination: Unity's rules are not Edge226 configuration instructions. Unity's AppsFlyer integration requirements.
Agree whether the data is ready to use
Have the UA owner confirm what the event means and how the campaign will use it. Engineering and analytics confirm payment checks, event reporting and duplicate handling. The measurement owner confirms the partner mapping, report differences and evidence of receipt. Record the setup reviewed and anything still unresolved.
Choose one outcome: ready for the agreed use, ready with stated limitations, or waiting for a specific fix. Give every open issue an owner and date. Repeat the affected checks when the SDK, connector, payment flow or event mapping changes.
Verified purchase data does not automatically determine the right bidding model, required event volume or commercial terms. Our CPI, CPA and ROAS article introduces those models; confirm campaign suitability and terms separately.
Discuss your game campaign
Explore Edge226's in-app acquisition and CTV offerings. Contact the team with your game, target markets, campaign goal and measurement setup to discuss fit and what needs confirming before launch.
