Use Audit Log when you need to understand why Layers changed a search query or search outcome. It shows individual engine decisions, the affected query, the anonymous visitor label, the change summary, and the source signals behind the action.Documentation Index
Fetch the complete documentation index at: https://docs.uselayers.com/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Your store must be connected to Layers.
- Your catalog should be synced.
- Search traffic or Lab test searches must have run after audit logging was enabled.
Open Audit Log
- In the Layers dashboard, go to Lab → Audit Log.
- Review the table of logged search decisions.
- Use the search box to find a query, such as “waterproof hiking boots”.
- Use the Action or Source filters to narrow the table.
Action types
Audit Log can show these search actions:- Expansion - Layers added related search terms to improve recall.
- Correction - Layers corrected or rewrote the shopper’s query.
- Redirect - A semantic redirect matched the query and returned a configured URL.
- Intent modifier - Layers applied an intent-based boost or filter.
Source types
The Source column explains what contributed to the decision:- Categorical Attribute - A product attribute helped identify query meaning.
- Feature Attribute - A feature-style attribute contributed to the decision.
- Semantic match - Semantic similarity helped match the query to a concept or redirect.
- Query understanding - Query interpretation detected a correction, route, or intent.
View full details
- In Audit Log, find the decision you want to inspect.
- Click the eye icon.
- Review Visitor, Time, Source, and Search ID when available.
- Review Before, After, and Metadata to see what changed.
Replay a decision
- In Audit Log, find a row with a play icon.
- Click the play icon.
- Review the replayed query in Test Text Search.
- Use Query Understanding and score breakdowns to inspect the search result behavior.
Troubleshooting
You do not see a recent search
Audit rows are created when Layers records a search decision such as an expansion, correction, redirect, or intent modifier. A plain search with no logged decision may not appear.A visitor appears as anonymous
This is expected when the original request did not include session or customer identity. Lab avoids exposing personal customer details.A filter returns no rows
Clear the Action, Source, and query filters, then try a broader date range. Some source types only appear when the relevant engine feature participated in the search.Next steps
- Lab overview - Review recent engine activity.
- Experiments - Find searches that need coverage review.
- Test text search - Inspect ranking and Query Understanding.