Analytics and performance
Sieve PRO is planned to include reporting for store owners and developers who need to understand how filtering performs and how shoppers use it.
Filter analytics
Section titled “Filter analytics”Useful reports include:
- most-used facets;
- most-used facet values;
- common filter combinations;
- no-results combinations;
- searches that produce no results;
- filter usage by category page;
- clear-all and backtracking patterns.
These reports help decide which facets should be visible, which product data is missing and which combinations deserve landing pages.
Performance dashboard
Section titled “Performance dashboard”The performance view should show:
- indexed product count;
- indexed term/value count;
- index table size;
- last rebuild time;
- average filter response time;
- slowest filter combinations;
- failed or delayed index updates.
Privacy boundary
Section titled “Privacy boundary”Filter analytics should focus on aggregate behaviour. It does not need to store personally identifiable shopper data. A store should be able to disable analytics or reduce retention where policy requires it.
Developer value
Section titled “Developer value”For agencies and developers, performance reporting makes support easier. Instead of guessing whether a slow category is caused by a theme, hosting, product volume or filter setup, the dashboard can show where the index and endpoint spend time.