Skip to main content

Hi there,

I’m curious if there is a chance of data being pruned or failing to response due to massive chart data when using Dashboard API’s Results from an Existing Chart endpoint.

I’m implementing a feature something similar to:

  • a feature where users can view their profile’s page view counts.
  • users can view who viewed their profile within the last few days, etc.

So the chart I’ve created is basically page view events grouped by profile ID which will scale as more profile (users) are created.

Thanks,

Hey @json 

Yes. There is a possibility of chart results getting pruned in the Dashboard REST API responses and it may vary depending on the chart type.

I tried looking at this by creating a simple segmentation chart grouped by user id and calling that chart id on  https://amplitude.com/api/3/chart/CHART_ID_HERE/query

The CSV export of that chart gave me a list of ~ 1300 users whereas the chart api response (seriesLabel) had ~1000 user ids. We sometimes get a prunedResult key in that response, but not sure how that gets set.

Hope this helps.

Hi @Saish Redkar ,

How to get full chart result without pruning in REST API?

I am also working on similar tasks and stuck at chart result data getting pruned which we don’t want to happen.

Do we have any solution to this problem?

Thanks in advance for you support. 

Answered in this post on an alternative if you are querying on Event Segmentation chart: 

 

Reply


Terms & ConditionsCookie settings