Request Transform Filters Kept Separate From Shopper Filters
Request transforms' Add filter group action used to merge its injected filters into the shopper's own filter group. On stores that lean on transforms to scope whole searches, like federated storefronts, that disabled zero-result recovery and leaked into facet state.
Layers now keeps injected filters in their own group, combined with the shopper's filters by AND only when the query runs. Facets only show the shopper's own selections, and the Applied Filter targeting condition ignores injected filters too.
Zero-result recovery, like retry and query expansion, now runs on transform-scoped searches instead of treating them as already handled. The zero_results metric counts shopper filters only, so a transform-scoped miss still counts as a zero-result search.
Two new LayersQL metrics track how much traffic your transforms constrain: transform_scoped_requests and transform_scoped_rate, in the Search (text) dataset.