Tapjoy offers Return on Ad Spend (ROAS) reporting to customers via the Tapjoy Reporting API and the Tapjoy Dashboard. The calculated ROAS metrics take into account an Advertiser's Ad Spend and Revenue from In-App Purchase (IAP) data and Monetization Ad Revenue when available.
For ROAS purposes, we treat an in-app event with an associated purchase value and USD currency code as IAP, meaning it will be counted in calculating ROAS for that campaign. It is critical to ensure that Tapjoy receives your app’s IAP data properly through a Mobile Measurement Partner (MMP) to have accurate ROAS metrics for reporting and optimizing your campaign performance. Similarly, Ad Revenue data from your acquired users must also be passed to Tapjoy via a MMP in order to be included in ROAS metrics.
This page provides information on how Tapjoy receives IAP and Ad Revenue data, the benefits to you, and best practices on setting up data forwarding with your MMP.
The primary source of incoming IAP and Ad Revenue data to Tapjoy is from MMP partners. As part of onboarding your app and setting up campaigns with the MMP, you’ll configure the IAP events as well as Ad Revenue if desired. Best practices for doing so are below and your Tapjoy account manager is available to assist. Specific setup issues should be addressed with your MMP representative.
Tapjoy’s ROAS reporting is based on install-date cohorts and Day 0, 1, 3 … 7, 14, 30, 60, and 90 metrics are available. For each of these Day X metrics, Ad Spend, Revenue (from IAP), Revenue from Ads, and ROAS are available directly through the GraphQL Reporting API, with selected metrics available in the Tapjoy Dashboard reporting. For example, the Day 3 ROAS metric is calculated from the sum of the revenue up through 3 days from install date divided by the associated Ad Spend for that cohort.
Tapjoy ROAS reporting is officially supported for customers integrated with Adjust, Appsflyer, and Singular. Please consult the Appsflyer pages in this Knowledge Center for IAP and Ad Revenue setup instructions. Adjust and Singular instructions can be found below but will be incorporated into their respective guides at a later time.
Before you begin, you must set up Tapjoy as a partner: Set Up Tapjoy - Adjust Help Center
In-App Revenue - Adjust Help Center
Mapped Events - Adjust Help Center
Step 1: Add your purchase events
Step 2: Map your IAP events
Once you’ve added your purchase events, you’ll need to map the events you want to share to Tapjoy. Data for unmapped events will not be shared.
Step 1: Map your ad revenue events
Step 2: Enable Ad Revenue
Set Up Tapjoy - Singular Help Center
General Instructions on how to set-up a Partner
The SDK event list includes the events '__ IAP__' and '__ REVENUE__'. __ IAP__ is any in-app purchase event that wasn't given a custom name. __ REVENUE__ includes:
- All in-app purchase events (__ IAP__ + events with custom names, if any).
- Ad revenue events reported by the SDK (if you have set up ad revenue attribution using the method of sending SDK events).
Before Singular can track installs and events for an ad network, you need to set up Tapjoy in the Attribution > Partner Configuration page.
NOTE: If you are sending both IAP and Ad Revenue data to Tapjoy, you should not use the general event __ REVENUE__ to capture revenue data.
The __ REVENUE__ event includes both purchases and ad revenue events, so mapping both types of revenue to the same Tapjoy Engagement ID may cause issues.
Instead, you should map all IAP events with __ IAP__, and all ad revenue events with __ ADMON_USER_LEVEL_REVENUE__.
See Singular’s in-app events documentation for more details.
Onboarding Guide for Ad Revenue Attribution
Before Singular can track installs and events for an ad network, you need to set up Tapjoy in the Attribution > Partner Configuration page.