很抱歉,知識來源中並沒有足夠的資訊可以解釋為什麼某些 project 到 6 月才開始受到影響。 可能的原因包括分批推出(rolling rollout)等,但我無法根據現有知識來源確認這一點。建議您直接聯繫 Mixpanel Support 詢問您的 project 具體的遷移時間,他們能提供更準確的說明。
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
根據知識來源,這項改動是在 2026 年 4 月推出的。 原本 Classified Data Access 是透過 Project Users 頁面上獨立的 per-user toggle 來管理,管理員可以單獨為每位使用者開啟或關閉查看敏感資料的權限。Custom Roles 推出後,Classified Data Access 改為 Data Access, Exports, and Alerts 類別下的一個權限項目,統一在 role 的設定中管理,不再是獨立的 toggle。[Classified Data Access 變更] 值得注意的是,改動後任何預設 role(包含 Owner 和 Admin)預設都不具備查看 Classified Data 的權限,必須透過 Custom Role 明確授予。因此您看到的 Consumer + Sensitive Access 顯示方式,本質上就是 Consumer role 加上透過 Custom Role 明確賦予的 Classified Data Access 權限。[Classified Data Access 變更]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
There are a couple of ways to visualize this in Mixpanel:
Option 1: Funnel with Exclusion Step
You can build a funnel that excludes users who performed "Subscription Cancelled" before reaching your target event:
Go to the Funnels report.
Add Subscription Cancellation Requested - Server as a funnel step.
Expand the Advanced menu and click "Exclude users who did…".
Select Subscription Cancelled and set it to be excluded between all steps (or before your target step).
This will show you only users who went through the funnel without triggering "Subscription Cancelled" in between. [Exclusion Steps]
Option 2: Cohort Filter in Insights
You can create a cohort of users who match your criteria and then use it to filter a report:
Go to the Cohort Builder (Users section).
Define the cohort as:
Did "Subscription Cancellation Requested - Server" (at least once)
AND did not "Subscription Cancelled" (zero times in the relevant time window)
Save the cohort.
Use this cohort as a filter in an Insights report to visualize the behavior of these users. [Cohorts]
Viewing the Actual Users
Once you have your funnel or cohort set up, you can click any data point and select "View Users" to see the specific users contributing to that metric, save them as a cohort, or export them to CSV. [View Users] The Funnel + Exclusion Step approach is likely the most direct visualization, as it clearly shows conversion rates and the impact of excluding users who cancelled.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
You can achieve this using Custom Events. By combining "Product X Viewed" and "Product Y Viewed" into a single custom event, that custom event can then serve as Step 2 in your funnel. Here's how to do it:
Option 1: Create a Custom Event (Recommended)
Open the Funnels report and click "Select Step/Events" for Step 2.
Select "Create New", then choose "Custom Event".
Add both "Product X Viewed" and "Product Y Viewed" as the events in the custom event definition.
Name it something like "Product X or Y Viewed" and click Save.
Use this custom event as Step 2 in your funnel.
Any user who fires either event will be counted as having completed Step 2. [Custom Events] [Funnels FAQ] Your funnel would then look like:
Step 1: Home Page Viewed
Step 2: Product X or Y Viewed (custom event)
Option 2: Use Event Comparison
If you want to compare conversion rates to each event separately (rather than combining them), you can use the Event Comparison feature. Click the "…" menu on a funnel step and select "Event Comparison" to add multiple events at the same step and see segmented results. [Comparison Events]
Note: Custom Events are the right choice if you want users completing either event to count toward the same step. Custom Events can also be reused across other reports like Retention, Flows, and cohort definitions. [Custom Events]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
The knowledge sources don't provide a dedicated pros/cons breakdown specifically for the RudderStack–Mixpanel integration, but based on the general CDP and tracking method information available, here's what can be gathered:
Integrating Mixpanel via RudderStack
Pros
Single SDK collection: RudderStack collects all your data through one SDK and routes it to multiple downstream destinations, including Mixpanel. Enabling Mixpanel is as simple as adding it as a destination in your RudderStack settings. [CDP integration]
Easy migration: If you're switching to Mixpanel from another analytics tool, RudderStack can help migrate historical data into Mixpanel. [CDP integration]
Data governance: Once connected, you can configure which events and properties to send, apply mappings/filtering, and control data quality. [CDP integration]
Not susceptible to ad-blockers: Since data flows server-to-server through RudderStack's cloud mode, it avoids the ad-blocker issues associated with pure client-side tracking. [Tracking methods]
Session Replay support: RudderStack's JavaScript SDK can be integrated with Mixpanel's Session Replay by binding RudderStack's anonymousId to Mixpanel's device_id. [Session Replay with CDP]
Cons
ID management complexity: When using server-to-server integrations, the partner (RudderStack) may send data with its own ID, which can differ from the IDs you use elsewhere in Mixpanel, potentially disconnecting user data. [Mobile attribution]
Less configurability: Events and properties are sent with defaults set by RudderStack, which may limit customization compared to direct SDK implementation. [Mobile attribution]
Race condition risk with Session Replay/Heatmaps: When using heatmaps alongside RudderStack, care must be taken to avoid a race condition where heatmap click events fire before the custom identity binding completes, which can create orphaned anonymous profiles. [Session Replay with CDP]
Additional infrastructure dependency: Routing through a CDP adds another layer to your data stack, which introduces an additional point of failure and potential latency.
For detailed setup instructions, refer to the RudderStack documentation or Mixpanel's RudderStack integration page.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Based on the knowledge sources, this sounds like you want to use the if function in a Custom Property formula. Here's how:
Basic Syntax
if(condition, value if true, value if false)
Your Example
If you want: "If Property 1 = True, then True":
if(<Property 1> == true, true, false)
More Complex Example with Multiple Conditions
You can chain conditions using and / or:
if(<Property 1> == true and <Property 2> == "some value", true, false)Or use ifs for multiple checks:
ifs(
<Property 1> == true, "Condition A",
<Property 1> == false, "Condition B"
)
Key Notes
Replace <Property 1> with your actual property by typing period (.) in the formula bar to browse and select available properties. [Custom Properties]
The == operator for strings is case-insensitive. [Comparison Operators]
Available constants are true, false, and undefined. [Constants]
Note: Custom Event Properties can reference both event and user profile properties in the formula. Custom Profile Properties can only reference user profile properties. [Custom Properties]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
A few things to check:
Your role/plan — The ability to create custom properties (beyond saving for self) requires at least an Analyst role. If you're a Consumer, you can only save custom properties for yourself. Verify your project role with your admin. [Roles & Permissions]
Where you're clicking — The plus (+) button for custom properties appears to the right of the property search bar, not the event search bar. Make sure you're in the right context — for example, when adding a breakdown or filter, not when selecting an event metric. [Custom Properties]
Which report you're in — Custom event properties are available in reports like Insights, Funnels, Retention, and Flows. If you're in a different context, the option may not appear.
Beyond that, the knowledge sources don't provide more detail on why "Custom Event Property" might be missing as an option specifically. I'd recommend checking Mixpanel's support or community forums for further troubleshooting if the above doesn't resolve it.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Creating a Custom Event Property in Mixpanel
You can create a custom event property directly within a report using the property builder:
Open the property builder — Click the plus (+) button to the right of the search bar in your report, then select "Custom Event Property". [Custom Properties]
Give your property a name — Enter a descriptive name for the new property.
Define the formula — Click the formula bar and write your calculation using Mixpanel's Excel-like formula language:
Press Ctrl + Space to see available functions.
Type a period (.) to browse and select event or user profile properties to include.
Use Insert Example from the dropdown to start with a pre-built use case.
Note: the formula cannot exceed 20,000 characters.
Apply or Save:
Click Apply to use the property locally within the current report only.
Click Save to make it permanently available across all reports and to other project members (Growth and Enterprise plans only).
Use Save and Share to share it with specific colleagues, teams, or your entire organization.
Note: Free plan users can create custom properties locally within a report. Saving globally for reuse requires a Growth or Enterprise plan. [Custom Properties]
Bonus: Borrowed Properties
If you need a property from a prior event to appear on a future event (e.g., using a "Search term" from a "Product Searched" event on a "Purchase Completed" event), you can use the Borrowed Property feature when creating your custom event property. Each project supports up to 20 borrowed properties. [Borrowed Properties]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
I want to be upfront that the knowledge sources don't contain enough detail to confirm the exact steps for creating a grouped bar chart with two simultaneous breakdown levels (Step 1 value AND Step 2 value) in a single Insights report. What the knowledge sources do confirm is relevant here:
In Funnels, property attribution lets you attribute a breakdown to a specific step (e.g., Step 1 or Step 2). [Property Attribution]
Breakdowns in Insights segment data by a property, and you can display results as a bar chart. [Breakdowns]
What I'd suggest trying
The closest approach within what the knowledge sources describe would be:
Build a Funnel report (choice_selected → choice_selected → choice_selected).
Add two breakdowns:
First breakdown: choice_selected attributed to Step 1 (this gives your groupings: Red, White, etc.)
Second breakdown: choice_selected attributed to Step 2 (this gives your bars within each group)
However, I'm not confident that Funnels supports a grouped bar chart output in the same visual style as Insights bar charts, or that two simultaneous per-step breakdowns are supported in the way you're describing.
My honest recommendation
Given the complexity of what you're describing — a grouped bar chart with two different step-attributed property values — I'd suggest reaching out to Mixpanel Support or consulting the Mixpanel Community directly, as this goes beyond what the available knowledge sources can definitively confirm.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Changing Property Data Type from String to Number (Typecasting)
You can handle this directly in Mixpanel using Typecasting, without needing to change anything in your integration (e.g. Userflow). [typecasting]
How to Typecast a Property in Reports
Open any report (Insights, Funnels, or Retention)
Add your property as a filter or breakdown
Click the overflow menu (⋯) next to the property
Select "Data Type"
Change the type from String → Number
This forces Mixpanel to interpret the string value as a numeric type, enabling calculations like sum, average, median, and percentile. [typecasting]
Important Caveats
Point | Detail |
Report-level only | Typecasting applies only within that specific report view — it does not change how the data is stored |
String must be numeric | The string value must be interpretable as a number (e.g. "4" → 4). If it cannot be parsed, the value becomes undefined [segmentation expressions] |
Not persistent | You need to reapply the typecast each time you build a new report |
For Your Star Rating Use Case
If star_rating is being sent as a string (e.g. "4") by Userflow:
Add star_rating as your breakdown or measurement property
Typecast it to Number
Then select Aggregate → Average to get your average rating trend
For a Permanent Fix
If you want the property to always behave as a number without manually typecasting each time, the best options are:
Fix it at the source — configure Userflow to send star_rating as a numeric value rather than a string, if the integration allows it
Use a Custom Property in Mixpanel to permanently define the transformation [custom properties]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
