what is the difference between filtering by event property for instance iif a user logs in into a paid account vs filtering at the filter level of the report, using a user property level?
Hi Juan I., 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
To answer this question, we need to understand the difference between event properties and user properties, as well as how filtering works at different levels in Mixpanel. Let's break it down based on the information provided in the knowledge sources. The main difference between filtering by an event property (like logging into a paid account) and filtering at the report level using a user property is when and how the filter is applied to the data: 1. Event Property Filtering: - This is applied at the event level, meaning it filters individual events based on their properties. - It's considered a pre-query filter, which means it affects what data is included in the analysis before the report is generated. - In Mixpanel, this is often referred to as an "inline filter" or "per-step filter" in funnel reports. 2. User Property Filtering (at the report level): - This is applied to the entire report and affects all events for users who match the filter criteria. - It's considered a post-query filter, which means it's applied after the initial data is gathered for the report. - In Mixpanel, this is often referred to as a "global filter." The key differences in how these filters affect your analysis are: 1. Scope of Impact: - Event property filters only affect the specific events that match the criteria. - User property filters affect all events for users who match the criteria, regardless of when the property was set. 2. Timing: - Event properties reflect the state at the time the event occurred. - User properties reflect the most recent state of the user. 3. Analysis Results: - Event property filters can give you a more granular view of specific actions. - User property filters allow you to analyze behavior across all events for a subset of users. This distinction is particularly important in funnel analyses. According to the [Mixpanel Funnels documentation](https://docs.mixpanel.com/docs/reports/funnels#what-is-the-difference-between-per-step-filtering-and-global-filtering): "Per-step filters are performed pre-query. Thus, these filters will impact your funnel's conversion by removing events that don't qualify from consideration of being included in a funnel calculation." On the other hand, "Global filters apply your selected filters to the entire report after the Funnels query has been run. Since Funnels will calculate conversions first and then apply your global filters, entire conversions with any part that does not meet these filter requirements will be excluded from the report's results." In your specific example: - Filtering by the event property of logging into a paid account would show you only the login events where the account was paid at the time of login. - Filtering by a user property indicating a paid account status would show you all events for users who currently have a paid account, regardless of when they became a paid user.
It's important to choose the appropriate filtering method based on the specific analysis you're trying to perform and the insights you're seeking to gain.
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.
