I have a dashboard for each CSM with specific metrics and customer selection. For some metrics, I need alerts to be sent. Create Custom Alert is displaying "This segment only has one value" because in the last 7 days for 1 specific CSM only 1 customer did a specific action, but I need to alert when any of the customers (selected on the entire dashboard level) conducted an action. How should I set it?
Hi Ilya L., 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 information in the knowledge sources, it appears you're encountering an issue with setting up Custom Alerts for specific customer segments in your CSM dashboard.The error message "This segment only has one value" suggests that when you're trying to create an alert for a specific CSM's customers, the system is detecting that only one customer performed the action you're monitoring in the selected time period (last 7 days).To set up alerts that will notify you when any customer in a CSM's portfolio performs a specific action, I recommend the following approach: 1. When creating your alert, instead of selecting a specific segment to alert on, choose the option to be alerted "when any segment matches the alert criteria." This is mentioned in the alert creation process: "If your report has a breakdown applied, either select a segment to alert on, or select any segment to be alerted when any segment matches the alert criteria" Alerts: Get notified about anomalies in your data.2. You might need to adjust your time range to be longer than 7 days if you're dealing with low-frequency events. This could help ensure more customers are included in the analysis.3. Consider using Group Analytics for your CSM dashboards, which would make it easier to track and analyze behavior at the account level. This is particularly useful for B2B account teams monitoring customer health How account teams can use Mixpanel to promote customer health.4. If you're on an Enterprise plan, you might also consider using Anomaly Detection alerts instead of Custom Threshold alerts, as these automatically calculate thresholds based on expected ranges and might be more suitable for detecting unusual patterns across multiple customers Alert Criteria Types.Remember that to create an alert, you need to save your report first, and then access the alert creation option through the 3 dots menu.
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! đź“š
I understand your frustration with the segment limitation when creating alerts. Let me clarify what's happening and why you're experiencing this challenge.When you create an alert in Mixpanel with a breakdown applied to your report, Mixpanel limits the number of segments that can be monitored for alerts based on the data available in your selected time period. This is part of Mixpanel's segmentation limits, which are designed to keep the analysis experience responsive for projects of all sizes Segment Limits and Ordering.The error message "This segment only has one value" appears because in your selected time period (last 7 days), only one customer performed the action you're tracking for that specific CSM. Mixpanel is essentially telling you that there's not enough data variation to set up a meaningful segment-based alert.To solve this issue without additional complexity, you have a few straightforward options: 1. As mentioned previously, when creating the alert, select the option to be alerted "when any segment matches the alert criteria" instead of a specific segment. This is the simplest solution.2. Extend your date range to capture more customer activity, which might provide more segment values.3. Consider simplifying your report to remove the breakdown before creating the alert, if that meets your needs.These limitations exist because Mixpanel needs to balance alert functionality with system performance. While it may seem like extra effort, the "alert on any segment" option is specifically designed to address your exact use case - being notified when any customer in a group performs an action, regardless of how many are active in the selected period.Is there a specific part of this process that's still causing difficulty for you?
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! đź“š
I understand your frustration with alerts being disabled when you extended the time period to 3 months. Based on the knowledge sources, there's a specific limitation that might be causing this issue.When working with Mixpanel alerts, the system has certain constraints related to query frequency and time ranges. The alert query frequency is determined by the time bucket of your report visualization. For example, if your chart is hourly, the alert will be checked at an hourly interval.The documentation doesn't explicitly state a maximum time range for alerts, but there are indications that longer time ranges might disable the alert functionality. This could be related to Mixpanel's query result caching behavior, which varies based on date ranges: - For queries with date ranges under 1 month, results are cached for up to 1 day - For queries with date ranges under 2 months, results are cached for up to 2 days - For queries with date ranges under 6 months, results are cached for up to 3 days - For queries with date ranges under 1 year, results are cached for up to 7 days Query Result CachingThis caching behavior suggests that Mixpanel treats different time ranges differently, which might affect alert functionality.To resolve this issue, I recommend: 1. Try using a shorter time range (perhaps 1-2 months instead of 3) 2. If you need to monitor longer periods, consider creating multiple alerts with shorter, overlapping time ranges 3. Reach out to Mixpanel support for specific limitations on alert time ranges, as this information isn't explicitly covered in the available documentationThe alerts feature is designed to notify you of recent changes or anomalies, so it may be optimized for shorter time frames rather than extended historical analysis.Would you like to try setting up the alert with a shorter time range to see if that resolves the issue?
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.
