Event Visibility and Ingestion Delay in Mixpanel
Are the events in https://eu.mixpanel.com/project/3819808/view/4315644/app/events visible immediately after they were fired, if I refresh? Or is there a delay for the ingestion?
Are the events in https://eu.mixpanel.com/project/3819808/view/4315644/app/events visible immediately after they were fired, if I refresh? Or is there a delay for the ingestion?
Hi Moritz H., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Based on the knowledge sources provided, there can be a delay before events appear in Mixpanel, depending on how you're tracking them:
Mobile SDKs (iOS, Android, React Native, Flutter, Unity)
Events tracked from mobile devices are not sent immediately. According to the documentation, mobile SDKs batch events to preserve battery life and customer bandwidth. Events are sent:
- Every 60 seconds while the application is running
- When the application transitions to the backgroundAs noted in the FAQ section: "If tracking from a mobile device, events may take 1-2 minutes to appear because Mixpanel's mobile SDKs buffer events for 1 minute, or when the app transitions to the background, to conserve battery life and bandwidth."You can call .flush() manually to send events immediately if needed, as documented in the iOS (Swift), Android, React Native, Flutter, and Unity SDK documentation.
Web Tracking
The knowledge sources don't explicitly detail the flush behavior for web/JavaScript implementations in the same way they do for mobile SDKs.
Additional Considerations
The FAQ also mentions that ad blockers and Do Not Track (DNT) browser settings can prevent events from being collected, which could make events appear delayed or missing.So to answer your question: there is typically a delay of 1-2 minutes for mobile events, but you can force immediate sending by calling .flush() in your implementation.
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.
Let me check the knowledge base for you again. One moment! 📚
You're absolutely right - I apologize for not addressing server-side tracking in my previous response.For server-side events, the knowledge sources indicate that events should be ingested in real-time without the batching delays that occur with mobile SDKs.According to the Server-Side Best Practices documentation and various server-side SDK guides (Ruby, Node.js, PHP, Java, Go), server-side SDKs trigger requests to the /track API endpoint immediately when you call the track method. These are described as being "designed for real-time tracking in a server-side environment."The knowledge sources don't mention any intentional buffering or batching delay for server-side events like they do for mobile SDKs. Events should appear shortly after being sent, though there may be minimal processing time on Mixpanel's end.However, the knowledge sources don't provide specific timing guarantees (like "events appear within X seconds") for when server-side events become visible in the UI after ingestion. If you're experiencing delays beyond what seems reasonable for real-time ingestion, you may want to check your implementation or contact Mixpanel support.
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.
Let me check the knowledge base for you again. One moment! 📚
A 20-minute delay for server-side events is unusual, as they should be ingested in real-time. Based on the knowledge sources, here are the most likely causes:
Common Causes of Delayed Server-Side Events
1. Incorrect API Endpoint for Data Residency
According to the debugging documentation, if your project's data residency doesn't match the API endpoint you're sending data to, events may not be ingested properly or could be delayed: - US Data Residency: [api.mixpanel.com](http://api.mixpanel.com) (default)
- EU Data Residency: [api-eu.mixpanel.com](http://api-eu.mixpanel.com)
- India Data Residency: [api-in.mixpanel.com](http://api-in.mixpanel.com)The FAQ section specifically warns: "If your Mixpanel project data residency setting does not match the API endpoint you are sending data to, your data will not be ingested."
2. Timestamp Issues
According to the Node.js SDK documentation, the /track endpoint "will only validate events with timestamps within the last 5 days of the request. Events with timestamps older than 5 days will not be ingested."If you're sending events with custom timestamps that are significantly in the past, this could cause ingestion issues.
3. Check Processing Time
The debugging documentation mentions you can "check the $import property and the mp_processing_time_ms to confirm when data has been ingested." This can help you determine if the delay is in sending or processing.
Recommended Debugging Steps
1. Verify your project's data residency setting matches the API endpoint in your server-side SDK configuration
2. Check the Events view in Mixpanel and examine the mp_processing_time_ms property to see when events are actually being ingested
3. Enable debug mode in your SDK to confirm requests are being sent successfully
4. Verify you're using the correct project tokenIf none of these resolve the issue, the knowledge sources suggest contacting Mixpanel support with your specific implementation details.
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.