On the filter modal, there is a "submit" button I could use to track truly manual actions, but if I do that, I lose the cases where a user changes a filter and then closes the modal without validating
Is the user changing filters in a modal actually triggering a search in the modal too? I.e. if they don't "validate", will they still see results?
We had a very aggressive debounce before. From memory it was 100ms. It triggered a lot of unnecessary searches and that created load on both our search infra, but also noise in Mixpanel. We've since increased this to 300ms and are now removing it altogether in certain parts of our app. I know it changes the UX quite drastically, but our change from 100ms to 300ms went pretty much unnoticed by users. I believe most users still hit enter anyway tbh. But we'll see once we make this change.
I don't have feedback from other companies, but my tech lead and I joined a Slack community about OpenSearch as we've transitioned our search to OS and are now dealing with other search UX related challenges, like how lenient we should be with typos 🙂 This helped us figuring out what to do with OS and some of it translates into search UX too.
Are you just looking for a solution on pushing events into Mixpanel, or general advice on search UX?