Exploring Alternatives for Mixpanel Rate Limits in Marketplace Analytics

Hello, I am working on implementing mixpanel on my marketplace to track listing views, shares, and saves. All of the tracking is setup and working and now I want to show the listing analytics to the suppliers on my platform. I went ahead and setup a custom JQL query but I realized that the rate limits are too low. 60 queries an hour wouldn't make it possible to display real time analytics to my users. Anyone have any thoughts on alternatives? I was thinking of rewriting it to bulk query all of the listings and storing them in my DB and run a function periodically to pull the latest information. Using Raw Data Export API might make more sense... any thoughts?

1 comment

kapa.ai
APP
·
·
You're right to be concerned about the rate limits for the JQL API. Let me provide some information and suggestions based on the Mixpanel documentation.The JQL API indeed has strict rate limits, as mentioned in the Query API documentation: - 60 queries per hour - Maximum of 5 concurrent queries - 2-minute timeout for each queryThese limits make it challenging to provide real-time analytics to multiple users on your platform.Your idea of using the Raw Data Export API is a good alternative. According to the Rate Limits documentation, the Raw Data Export API has the following limits: - Maximum of 100 concurrent queries - 60 queries per hour - 3 queries per secondWhile these limits are still restrictive, they offer more flexibility than the JQL API.Your approach of bulk querying all listings and storing them in your database is a solid strategy. Here are some thoughts on implementing this: 1. Use the Raw Data Export API to periodically fetch the latest data for all listings. 2. Store this data in your database. 3. Update your database periodically (e.g., hourly or daily) to keep the analytics current. 4. Serve the analytics to your suppliers from your database instead of querying Mixpanel directly.This approach has several advantages: - It respects Mixpanel's rate limits. - It allows you to serve analytics to your suppliers quickly, without being constrained by Mixpanel's API limits. - You can optimize the data for your specific use case and query patterns.Additionally, you might want to consider using Mixpanel's Data Pipeline feature if you need more frequent updates. As mentioned in the Data Pipeline documentation, Mixpanel supports hourly and daily exports, which could be useful for keeping your local database up-to-date.Remember to be mindful of the data volume you're dealing with, as the Raw Event Export API documentation mentions that there are use cases where custom analysis might be required. If you find that your needs exceed what's possible with the available APIs, it might be worth reaching out to Mixpanel support to discuss your specific use case and potential solutions.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.