kapa.ai events post sign up dont show up when i filter my funnel board by utm source. but i can see the events on my events page. and i can see all events on the board when its not filtered. why do they go away when filtered
Please stand by Princess W. as I search the knowledge base. I normally take about 15 seconds or so. 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
When you filter your funnel board by UTM source and post-signup events disappear (even though you see them in the Events page and when the board is unfiltered), the most likely reason is that those events do not have the UTM source property set.Here’s why this happens: - UTM properties are only present if the event was tracked with UTM parameters in the URL. If a user signs up and then continues their session (e.g., navigates to other pages, triggers more events), those subsequent events may not always carry the original UTM source property—especially if your implementation does not persist UTM parameters across all events, or if the user returns later without UTM parameters in the URL. In such cases, those events will not match the UTM source filter and will be excluded from the funnel when the filter is applied Web Attribution.- Filtering by UTM source only includes events where that property is present and matches the filter. If the property is missing (which can happen for organic/direct traffic or if UTM persistence is not configured), those events are filtered out. This is why you see the events when the board is unfiltered, but not when you apply the UTM source filter Filters.- “(not set)” UTM values indicate missing UTM data. If you break down by UTM source and see “(not set)”, it means the event did not have a UTM source property—often the case for organic or direct traffic, or if the property was not persisted Web Attribution.What you can do: - Review your UTM parameter persistence settings. By default, Mixpanel’s JS SDK persists UTM parameters as super properties, but this can be disabled or altered. If you want UTM parameters to be available on all events, ensure persistence is enabled and correctly implemented. - Consider whether your funnel steps rely on events that may not always have UTM properties, and adjust your tracking or filters accordingly.If you need to analyze all users regardless of UTM source, remove the filter. If you want to ensure UTM data is always present, review your implementation and consider how UTM parameters are being set and persisted across user sessions and events Web Attribution.If you need more help, check the raw event data for the presence of the UTM source property on the events in question.
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 We're sending the UTMs for all events whether pre or post signup
Let me check the knowledge base for you again. One moment! 📚
If you are sending UTM parameters for all events—both pre and post signup—then, in theory, filtering your funnel by UTM source should not cause post-signup events to disappear, as long as the UTM source property is present and correctly set on those events.However, based on Mixpanel documentation, here are some possible reasons for the issue you’re seeing: 1. Case Sensitivity and Property Name Consistency:
UTM tracking in Mixpanel is case sensitive and expects property names to be in lowercase (e.g., utm_source, not UTM_Source). If there is any mismatch in property names or casing, the filter may not match the events as expected Track UTM Tags.2. Property Value Presence:
If the UTM source property is missing or set to a falsy value (such as null or undefined) on post-signup events, those events will not appear when you filter by a specific UTM source. This can happen if the UTM parameters are not being persisted or passed correctly for every event, or if the user’s session changes (e.g., after login) and the UTM properties are not re-attached Web Attribution.3. Super Property Persistence Settings:
By default, Mixpanel’s JavaScript SDK persists UTM parameters as super properties, but this can be disabled with the stop_utm_persistence option. If you have disabled persistence, you must ensure that UTM parameters are explicitly included with every event, including those after signup Track UTM Tags.4. Filter Logic in Funnels:
When you apply a filter in a funnel, only events that have the matching property and value will be included. If your post-signup events have a different UTM source value, or if the property is missing, those events will be excluded from the filtered funnel Filters.What to check:
- Inspect the raw data for your post-signup events to confirm that the utm_source property is present and matches the value you are filtering for.
- Ensure that the property name and value are consistent and correctly formatted.
- If you are using custom tracking logic, verify that UTM parameters are being attached to every event, not just pre-signup events.If all of the above are correct and you are still experiencing issues, the knowledge sources do not provide further troubleshooting steps specific to this scenario. In that case, you may want to reach out to Mixpanel support or review your implementation in more detail.
⚠️ The knowledge sources do not mention any other reasons for this behavior beyond property presence, naming, and persistence settings. If you have confirmed that UTM properties are present and correct on all events, but the issue persists, further investigation outside the provided documentation may be required.
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.
