Issue
Why does the "Top Searches with Zero Results" report in Fusion Analytics include search terms that appear to return results in testing?
Diagnosis
This issue can occur when:
A search term initially returns results, but the user applies facet filters or other constraints that reduce the result set to zero.
Security trimming is in place, and some users do not have access to the documents returned for a particular query, leading to a zero-result scenario for those users.
The Fusion analytics report aggregates search interactions and records “zero results” based on the final query state — after all filters, security policies, or faceting are applied.
For example, a user may search for a term that returns results initially. However, after applying one or more facet filters, the result set becomes empty. Fusion records this last query as a zero-result search because the final state of the query did not return any results.
Environment
Fusion 5.x
Applicable to all environments where Fusion Signals and Analytics are enabled and facet filtering or security trimming is in use.
Cause
Fusion logs zero-result queries based on the final query state as processed by the query pipeline. Any user interaction (such as applying filters or facets) that results in no documents being returned is counted as a zero-result event.
If security trimming is configured, users without access to the documents retrieved by a query will also register a zero-result search, even though other users may see results for the same query.
Resolution
To better interpret and troubleshoot zero-result entries in analytics reports:
Confirm whether filtering is the cause
Run the same query twice:
Once without any filters applied.
Again with the same filters that the user would have used (facets, range filters, etc.).
If the filtered query returns no results, that query is logged as a zero-result search in analytics even though the base query returns documents.
Consider security trimming effects
If security trimming is enabled:
Check whether the querying user has the necessary permissions to access the documents that would be returned.
A query that returns results for some users may return zero for others, based on access control.
Validate with logs and UI behavior
Observe query requests and responses via browser dev tools or query logs.
Compare timestamps and filter parameters used in zero-result interactions.
Understanding how the final query is structured in the query pipeline — including filters and security policies — will help reconcile unexpected entries in the zero-result report.
If necessary, additional filtering or security policy auditing can be performed to further isolate causes of empty result sets.