Mixpanel Event Drops with RudderStack Ingestion Using Go and Flutter SDKs on Growth Plan

·Apr 02, 2026 02:45 PM·

Hello, team! mixpanel is dropping some events. we ingest using rudderstack from go and flutter sdks there is no drops happening to other destinations. we are on growth plan and our quota is calculated using MAUs(the old pricing) we generate up to 30M events a- month

1 comment

· Sorted by Oldest

kapa.ai
APP
·
·
Hello! There are a few potential reasons why Mixpanel might be dropping events from your RudderStack integration. Here are the most common causes to investigate:
1. Data Residency Mismatch
If your Mixpanel project is set to EU or India data residency, but RudderStack is sending data to the default US endpoint (api.mixpanel.com), events will be rejected and not ingested. Make sure RudderStack is routing to the correct API host for your project's residency setting. [Debugging Guide]
Data Residency
API Host
US
api.mixpanel.com
EU
api-eu.mixpanel.com
India
api-in.mixpanel.com
2. Events Dropped in Lexicon
Someone with project owner permissions may have dropped specific events in Lexicon. Dropped events are intercepted at the ingestion layer and no longer stored — this would explain why drops only appear on the Mixpanel side and not other destinations. [Lexicon Dropping Data]
You can verify this in Lexicon by checking if any events show a "Dropped" status.
3. Rate Limits
At 30M events/month, you're sending a significant volume. Mixpanel's rate limit is ~30k events per second (2GB uncompressed JSON/minute). If RudderStack is sending bursts that exceed this, Mixpanel will return 429 errors and those events may be dropped if RudderStack doesn't retry them properly. [Import Events Rate Limit]
4. Hot Shard Limits
If a large number of events are being sent under the same distinct_id on the same calendar day (over 200K events per distinct_id per day), those events get transformed into $hotshard_events and their distinct_id is cleared. This could make them appear "missing" in your reports. [Hot Shard Limits]
5. Incorrect Project Token
Double-check that RudderStack is configured with the correct Mixpanel project token. An incorrect token would silently route data to the wrong project or cause ingestion failures. [Sending Data FAQs]
Recommended next steps:
1.
Check Lexicon for any events with "Dropped" status.
2.
Verify the API endpoint matches your project's data residency.
3.
Review RudderStack's delivery logs for 429 or 400 error responses from Mixpanel.
4.
Confirm the project token in RudderStack matches your Mixpanel project settings.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
·
Hello! There are a few potential reasons why Mixpanel might be dropping events from your RudderStack integration. Here are the most common causes to investigate:
1. Data Residency Mismatch
If your Mixpanel project is set to EU or India data residency, but RudderStack is sending data to the default US endpoint (api.mixpanel.com), events will be rejected and not ingested. Make sure RudderStack is routing to the correct API host for your project's residency setting. [Debugging Guide]
Data Residency
API Host
US
api.mixpanel.com
EU
api-eu.mixpanel.com
India
api-in.mixpanel.com
2. Events Dropped in Lexicon
Someone with project owner permissions may have dropped specific events in Lexicon. Dropped events are intercepted at the ingestion layer and no longer stored — this would explain why drops only appear on the Mixpanel side and not other destinations. [Lexicon Dropping Data]
You can verify this in Lexicon by checking if any events show a "Dropped" status.
3. Rate Limits
At 30M events/month, you're sending a significant volume. Mixpanel's rate limit is ~30k events per second (2GB uncompressed JSON/minute). If RudderStack is sending bursts that exceed this, Mixpanel will return 429 errors and those events may be dropped if RudderStack doesn't retry them properly. [Import Events Rate Limit]
4. Hot Shard Limits
If a large number of events are being sent under the same distinct_id on the same calendar day (over 200K events per distinct_id per day), those events get transformed into $hotshard_events and their distinct_id is cleared. This could make them appear "missing" in your reports. [Hot Shard Limits]
5. Incorrect Project Token
Double-check that RudderStack is configured with the correct Mixpanel project token. An incorrect token would silently route data to the wrong project or cause ingestion failures. [Sending Data FAQs]
Recommended next steps:
1.
Check Lexicon for any events with "Dropped" status.
2.
Verify the API endpoint matches your project's data residency.
3.
Review RudderStack's delivery logs for 429 or 400 error responses from Mixpanel.
4.
Confirm the project token in RudderStack matches your Mixpanel project settings.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Data Residency	API Host
US	api.mixpanel.com
EU	api-eu.mixpanel.com
India	api-in.mixpanel.com

Data Residency	API Host
US	api.mixpanel.com
EU	api-eu.mixpanel.com
India	api-in.mixpanel.com

1 comment

1 comment

1. Data Residency Mismatch

2. Events Dropped in Lexicon

3. Rate Limits

4. Hot Shard Limits

5. Incorrect Project Token

1. Data Residency Mismatch

2. Events Dropped in Lexicon

3. Rate Limits

4. Hot Shard Limits

5. Incorrect Project Token