Josh C.

For open organizations, I'd love lower friction login process. Context: Today, new Mixpanel users hit this (false) access wall (screenshots in 🧵). This is a confusing experience and causes new users to ask for access when they don't need it or give up because they think they have to bug someone in IT for access. Hypothesis: Moving login (with Google) up a page would make it much easier for new folks to access Mixpanel and would likely help with new user adoption and engagement!

Question: Is there a way to hide (not set) properties from events? Context: My team has MP set up via data export and all events show the same properties regardless of whether or not they're relevant to that specific event (example in thread). It would make Mixpanel more user friendly if we could only display event properties that are actually set on that event

Does anyone know if it's possible or have any experience using Hold constant on a funnel for a property that's a List of Objects? Context: As of now, my team has implemented each item displayed on a page as a separate load event with card_type showing what is in that display (screenshot in 🧵). This makes it easy to split up but also means we're firing a bunch of events for the same thing. I'm wondering if we could bundle a few properties (e.g. card_type, card_title ) into one property and still track conversion broken out by that nested property