Increasing current limit of only 1000 dimensions per request for Adobe Real-Time API 2.0
We are currently relying heavily on the Adobe Real-Time API 2.0 to retrieve near real-time readership data for our analysis. I understand that the API is designed for fast processing, which is likely the reason behind the current limit of 1000 on realTimeValuesPerPeriodparameter as mentioned here - https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/reports/real-time#limiting-the-number-of-dimension-return-values-per-period
However, this limit is proving to be too restrictive for our use case. At present:
- We fetch data at a 5-minute interval, where we observe peak volumes of almost 8,000 events per interval
- Even after increasing the polling frequency to 1-minute intervals, we still receive approximately 3,000 events per interval
Due to the current cap of 1000, we are consistently missing a significant portion of events, which impacts the completeness and accuracy of our analysis.
We have explored the option of further increasing the fetch frequency, but this is not feasible due to:
- Processing overhead on our end
- Existing rate limits on Adobe APIs
Given these constraints, increasing the limit from 1000 to 5000 would significantly improve our ability to capture a near-complete dataset. With a higher cap and optimized polling frequency, we can align much closer to our data requirements without placing excessive load on either system.
We completely understand the need for performance safeguards and are not requesting an unbounded increase. However, a reasonable increase (e.g., to 5000) would make the API substantially more usable for high-volume use cases like ours.
This enhancement would help ensure:
- More complete real-time data capture
- Better analytical accuracy
- Reduced data loss due to capping
We appreciate your consideration and would be happy to provide any additional data points or support further evaluation from your side.