Background

For more advanced integrations, we highly recommend tracking game studio ARPU (Average Revenue Per User). Tracking this metric will allow you to understand when users are overperforming or underperforming an offer's goal. When overperforming, your overall earnings will increase. When underperforming, you can use the postback IAP data to weed out low-quality users. This endpoint provides a list of ARPU targets for each offer upon request. For further details, please contact your account manager.

Example

In this example, you will learn how to use In-App Purchase data to calculate your current ARPU and compare it against your target.

• Consider the game XYZ, which has a target game studio ARPU of $1 by day 7.
  Your goal is for your users to achieve an ARPU of $1 through purchases and/or ad viewing by day 7.
• Use the In-App Purchase callbacks to track game studio revenue per offer. Each In-App Purchase contributes to the game studio’s revenue.
• For example, if you have 10 users and one user makes a purchase worth $20 by day 7, your game studio's ARPU is calculated as: Total Game Studio Revenue ($20) / Number of Users (10) = $2 GS ARPU — above the target game studio ARPU.
• When an IAP event gets reconciled, then remove it from the ARPU calculation.

It is important to note that Installs, payouts/revenue, unique users, and ARPU are based on the install date. Please take a look at the following example:

Based on the example above, your reporting should look like this:

ARPU Goals

Once ARPU calculation is set up via IAP callbacks, you can compare your performance against the ARPU goals defined for each offer. Please note that ARPU goals are not available for all offers.

Example JSON:

"arpu_goals": [
  {"day": 1, "arpu": 2.40},
  {"day": 7, "arpu": 8.49}
  ...
]