Syncing Over 60 Mixpanel Recurring Cohorts with Webhooks

Avinash K. · 2025-04-22 17:49:52.903908+00

I have use-case where i need to sync more than 60 mixpanel recurring cohorts using *WEBHOOKS,* is there any different pricing plan to achieve this or this is the Technical limitation, is there any way we i can sync more than 60 recurring cohorts at a time I got to know mixpanel has limited this number to 60:

Mixpanel is headed to Money20/20 October 26 - 29 in Las Vegas, Nevada!

Syncing Over 60 Mixpanel Recurring Cohorts with Webhooks | Mixpanel Community

7 comments

· Sorted by Oldest

kapa.ai
APP
·
·
The 60 dynamic (recurring) cohort sync limit is indeed a technical limitation in Mixpanel, not a pricing tier restriction. According to the documentation: > Each project is limited to 60 dynamic (recurring) cohort syncs across all destinations. This limit helps ensure that syncs are fast and reliable. We recommend pruning older unused syncs to stay within the limit.Mixpanel DocsFor your specific use case with webhooks, there are a few potential workarounds: 1. Create multiple connections: The documentation suggests that "Cohort syncs under one connection are executed in a sequential order; to increase parallelism, you should create multiple connections covering different types of sync." This might help with sync performance but doesn't directly address the 60 cohort limit.Mixpanel Docs2. Prune unused syncs: Review your existing cohort syncs and remove any that are no longer needed to stay within the limit.3. Consolidate cohorts: Consider if some of your cohorts can be combined into fewer, more comprehensive cohorts.4. Use static syncs: The documentation mentions "There are no limit on the number of cohorts for static, or 1-time, syncs." If your use case allows for it, you could use one-time syncs instead of recurring ones.Mixpanel DocsThis appears to be a hard technical limit rather than a pricing tier restriction, so upgrading your plan would not increase this limit. If this limitation significantly impacts your workflow, I'd recommend reaching out directly to Mixpanel's support team to discuss your specific use case and see if they can offer any custom 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.
Avinash K.
·
·
We can not extend it at any cost?
Avinash K.
·
·
kapa.ai
kapa.ai
APP
·
·
Sorry Avinash K., I'm not sure what you mean. Please try again. 👋
Avinash K.
·
·
We can not extend it "the limit of 60"at any cost? kapa.ai
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Based on the knowledge sources provided, there is no explicit information indicating that the limit of 60 dynamic (recurring) cohort syncs can be extended through any pricing tier or special arrangement.The documentation is quite clear about this being a technical limitation: > Each project is limited to 60 dynamic (recurring) cohort syncs across all destinations. This limit helps ensure that syncs are fast and reliable. We recommend pruning older unused syncs to stay within the limit.Mixpanel DocsThe documentation doesn't mention any exceptions to this rule or any way to purchase additional capacity. Unlike some other features in Mixpanel that have different limits based on pricing tiers, this appears to be a fixed technical constraint designed to maintain system performance and reliability.Your best options remain: 1. Pruning unused syncs 2. Using static (one-time) syncs which have no limit 3. Consolidating cohorts where possibleIf this limitation is critical for your business needs, I would recommend contacting Mixpanel's sales or support team directly to discuss your specific use case. While the documentation doesn't indicate flexibility on this limit, only their team can definitively confirm whether any exceptions might be possible for your particular situation.I'm sorry I couldn't provide a more favorable answer regarding extending the 60 cohort sync limit.
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.

kapa.ai
APP
·
·
The 60 dynamic (recurring) cohort sync limit is indeed a technical limitation in Mixpanel, not a pricing tier restriction. According to the documentation: > Each project is limited to 60 dynamic (recurring) cohort syncs across all destinations. This limit helps ensure that syncs are fast and reliable. We recommend pruning older unused syncs to stay within the limit.Mixpanel DocsFor your specific use case with webhooks, there are a few potential workarounds: 1. Create multiple connections: The documentation suggests that "Cohort syncs under one connection are executed in a sequential order; to increase parallelism, you should create multiple connections covering different types of sync." This might help with sync performance but doesn't directly address the 60 cohort limit.Mixpanel Docs2. Prune unused syncs: Review your existing cohort syncs and remove any that are no longer needed to stay within the limit.3. Consolidate cohorts: Consider if some of your cohorts can be combined into fewer, more comprehensive cohorts.4. Use static syncs: The documentation mentions "There are no limit on the number of cohorts for static, or 1-time, syncs." If your use case allows for it, you could use one-time syncs instead of recurring ones.Mixpanel DocsThis appears to be a hard technical limit rather than a pricing tier restriction, so upgrading your plan would not increase this limit. If this limitation significantly impacts your workflow, I'd recommend reaching out directly to Mixpanel's support team to discuss your specific use case and see if they can offer any custom 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.
Avinash K.
·
·
We can not extend it at any cost?
Avinash K.
·
·
kapa.ai
kapa.ai
APP
·
·
Sorry Avinash K., I'm not sure what you mean. Please try again. 👋
Avinash K.
·
·
We can not extend it "the limit of 60"at any cost? kapa.ai
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Based on the knowledge sources provided, there is no explicit information indicating that the limit of 60 dynamic (recurring) cohort syncs can be extended through any pricing tier or special arrangement.The documentation is quite clear about this being a technical limitation: > Each project is limited to 60 dynamic (recurring) cohort syncs across all destinations. This limit helps ensure that syncs are fast and reliable. We recommend pruning older unused syncs to stay within the limit.Mixpanel DocsThe documentation doesn't mention any exceptions to this rule or any way to purchase additional capacity. Unlike some other features in Mixpanel that have different limits based on pricing tiers, this appears to be a fixed technical constraint designed to maintain system performance and reliability.Your best options remain: 1. Pruning unused syncs 2. Using static (one-time) syncs which have no limit 3. Consolidating cohorts where possibleIf this limitation is critical for your business needs, I would recommend contacting Mixpanel's sales or support team directly to discuss your specific use case. While the documentation doesn't indicate flexibility on this limit, only their team can definitively confirm whether any exceptions might be possible for your particular situation.I'm sorry I couldn't provide a more favorable answer regarding extending the 60 cohort sync limit.
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.