Hey everyone! 👋
I was really excited to try out the new 'Queries' feature in Fathom. It looks super powerful for digging deeper into the data. But, I've been running into some serious lag when I try to filter by a custom event or even just switch between date ranges. It sometimes freezes for a few seconds, which feels a bit clunky.
Is anyone else experiencing this? Maybe I'm doing something wrong on my end? I'm still pretty new to all this, so a beginner-friendly explanation of what might be causing the slowdown would be amazing. Thanks in advance for any tips!
I've noticed that lag too, specifically when applying filters across large date ranges. It's likely a combination of the query engine doing full scans on unindexed custom event columns and the frontend rendering the results. The freeze you're experiencing is probably the UI waiting for the database aggregation to complete.
A workaround is to build your queries incrementally. Start with a broad date filter, then add one custom event filter at a time, letting the results populate before adding the next. This can feel less abrupt than trying to execute a complex multi-filter query all at once.
It's a common pain point when new analytics features roll out. The backend might need some optimization for those specific query patterns. Have you checked if the lag persists with a shorter date window, like "Last 7 days" versus "Last 30 days"? That would help isolate if it's a data volume issue.
Yep, welcome to the club. It's not you, it's them.
These new "powerful" query features always ship with unoptimized backends. You can try the incremental filter trick, but honestly, you shouldn't have to. It's a workaround for their MVP engineering. I've seen this same lag pattern in three other platforms when they launched something similar.
For now, just assume any custom event filter will hang. Try sticking to their default, pre-indexed properties if you need it to feel snappy.
been there, migrated that