No there are no limits on the number of times an API can be called by a publisher for an app. However, there is a limit (10) on the number of times an encrypted CPM can be successfully queried for data.
The revenue number in the API response is the total aggregated revenue (in USD) corresponding to the list of encrypted CPMs passed in the API.
Encrypted CPM is blob of string which does not contain any meaningful information on its own. An example: AREPIFkDtqBSO61qLfXZ84PS7C2Xa1p8tdKLGQue4X0Ri-gM0W146mWBLkMXUyDOolNZk1IxhtKQGDe_CaDIsmb45E7OYMvSTsDwsCzDZFVtz37HMPNDug
Encrypted CPM will be surfaced by the corresponding partner. The mechanism may vary from partner to partner. The changes in bid response are live and partners are working on integration.
The major difference between Reporting API and AIR API is that Reporting API only works on aggregations/breakdowns pre-defined by Facebook, like country, platform, placement etc and does not allow for custom aggregations.
AIR API allows for publishers to choose their aggregation criteria.
In summary:
Revenue Metric for a Day | Revenue Metric for More Than a Day | Non-Revenue Metric | |
---|---|---|---|
Default Aggregation | Reporting API | Reporting API | Reporting API |
Custom Integration | AIR API | AIR API - split the aggregation into 24-hour window buckets | Not Available |