Importing revenue
One way of collecting revenue data from monetization partners is by importing the revenue from their backend service. When we have the revenue data in justtrack, we update the dashboard to display the most up-to-date revenue for the partner.
One important caveat is that it can take monetization partners time, sometimes days, to process ad impressions and the revenue you earn from them. So, if an event occurs on day one, the partner may not report it until day two or three. To account for this delay, we always request the last three days' worth of revenue data and correct the dashboard accordingly.
We go through the process of importing revenue data three times per day to provide you with somewhat fresh revenue data. However, you shouldn't consider imported revenue for the last three days as complete.
Verifying revenue estimates
Depending on the monetization partners you use and how you configure their SDK in your application, we may receive real-time revenue estimates directly from the SDK.
In this case, when we import revenue data for your app, we compare the imported results against the real-time estimates from the SDK and verify those estimates. The result is that we align the original estimates with the imported revenue data.
After the three-day import window has passed, all revenue estimates that haven't been accounted for by imported data are deleted from our system.
Revenue data granularity
When we import revenue data from a monetization partner, that data can come in one of two ways:
- Aggregated revenue data
- User-level revenue data
The difference between these methods is the granularity of the data.
Aggregated data
In this case, the revenue data is imported as an aggregated sum of all revenue generated over a specified amount of time. This data isn't broken down further, so we don't know when portions of the revenue were generated or by whom.
However, because we have user events, such as when a user sees or engages with an ad, we have other data that can help us make educated assumptions about this data. In the dashboard, we distribute the aggregated sum over the user event data to estimate where the data comes from at a more granular level.
User-level data
In this case, we accurately know, for a given user, how much revenue they generated over how many ad impressions.
For some monetization partners, you have the opportunity to pass justtrack's user ID (or your own) when you configure their SDK. When you integrate their SDK with ours, you should make sure that the user ID is the same for both SDKs. In the context of importing revenue data, this allows us to associate imported revenue data with the ad impression events we receive in real time from the SDK. If the user IDs don't match, we drop the imported revenue data.