How to Bypass the 3000 Row Limit per Segment in Mixpanel Query Saved Report API?

·Feb 03, 2026 04:53 AM·

Hello Everyone, I am working to build a custom report in Google sheet via Mixpanel data. I am using Query Saved Report API to fetch the data I need. For high dimension reports, the api only outputs 3000 rows per segment. Seems the API has the same segment limitation as the UI. Anyway to bypass this with Query Saved Report API?

4 comments

· Sorted by Oldest

Julianne B.
·
·
Hi Muffaddal- you’re correct that the Query Saved Report API is subject to the same segment limits as the UI. It isn't possible to bypass this limitation. Are you able to break the report into multiple reports? For example, by changing the date range or adding additional filters?
Muffaddal Q.
·
·
For now, the workaround I implemented involves creating four copies of the same report and applying a filter based on the distinct_id. Specifically, each report filters for IDs ending with a specific character. This effectively shards the data, reducing the volume per report to one-fourth. This works for our current volume, but we will have to revisit this once we scale. Feature Suggestion: I recommend the Mixpanel team adds pagination support to the API or removes this limit entirely to avoid the need for manual partitioning. I do lots of custom reporting for clients and we keep hitting this limitations.
Julianne B.
·
·
I'm glad you were able to find a workaround. That is definitely a great suggestion- I'd recommend submitting it as a product gap via the '? > Submit Feedback' selection. This will flag your use case to the Product team. As you scale more, it may make sense to export the raw data for downstream analysis or use a public board.
Muffaddal Q.
·
·
We can employ export raw data but that would be unwanted cost for us for all the extra calculations we have to do that's currently being handled by Mixpanel. But yes as things are right now there is no other option.