Search signal tables
Summarize
Summary of Search signal tables
Search signal tables in ServiceNow capture detailed data from users’ search activities, including queries, refinements, and interactions with search results. This data, known as search signals, is crucial for enhancing the relevancy of search results within your instance by analyzing user behavior and search patterns.
Show less
These tables are system tables and are excluded from the Reporting module by default, requiring explicit enablement if reporting on search signals is needed.
Key Search Signal Tables and Their Purpose
- Search Signal Event [syssearchsignalevent]: Records data generated when a user submits a search, such as browser info, user location (latitude/longitude), query intents matched, first-page search results, response time, and query language.
- Search Signal Result Event [syssearchsignalresultevent]: Captures data when users select search results, including the original search query, user info, selected result details (document ID, source table, description), result type, domain, and whether the result is used for AI auto-complete suggestions.
- Search Signal Result Event Action [syssearchsignalresulteventaction]: Logs user interactions with search results, such as clicks, recording the type and value of the interaction and linking back to the selected search result event.
- Search Autocomplete Query Event [syssearchautocompletequeryevent]: Stores data when users select auto-complete suggestions from the search input, including the selected suggestion, its index, user location, and the search profile used.
- Genius Result Event Action [syssearchgeniusresulteventaction]: Tracks user actions on Genius Result answer cards, detailing action types and values, matched NLU intents (if applicable), card type, and linking to the corresponding search result event.
Practical Benefits for ServiceNow Customers
- Enables analysis of user search behavior to optimize search algorithms and improve result relevance.
- Supports enhanced AI-driven features such as auto-complete suggestions and Genius Result cards by providing detailed interaction data.
- Allows localization and context awareness through user location and language data captured during searches.
- Facilitates monitoring of search performance by tracking response times and user engagement with search results.
Considerations
Because these are system tables, they do not appear in standard Reporting by default. Customers wishing to leverage reporting on search signals must enable reporting on system tables to access this valuable data.
Search uses tables to store details from user searches, search refinements, and interactions with search results. These details are called search signals. Data from the search signal tables helps improve the relevancy of search results in your system.
Search Signal Event table
The Search Signal Event [sys_search_signal_event] table stores signal data produced when users submit a search.
| Column | Description |
|---|---|
| Search event | Reference to the record for the search event on the Search Event [sys_search_event] table. |
| Browser | User browser agent string. |
| Latitude | Latitude coordinate of the user location in decimal degrees. |
| Longitude | Longitude coordinate of the user location in decimal degrees. |
| Matched Query Intents | List of query intents matched in the user search query. |
| First page results | JSON array of objects in which each node represents a single result returned in the first page of results for the search. The result order is preserved. Each object includes the unique record identifier
(sys_id) of a result and the table where the result is located. Note: The first page results aren't updated when you refine a search. |
| Search Response Time(ms) | Time taken by the search, in milliseconds. |
| User Query Language | Language of the user search query. |
Search Signal Result Event table
The Search Signal Result Event [sys_search_signal_result_event] table stores signal data for search results that users select.
| Column | Description |
|---|---|
| Search query | Search query that led to the search result selection. |
| User | User that selected the search result. |
| Result DocID | Source table and record names for the selected search result. |
| Description | Short description for the selected search result. |
| Source Table | Source table for the selected search result. |
| AIS DocID | Source table name and record sys_id for the selected search result. |
| Result Type | Type of search result selected. For example, REGULAR for a regular search result or GENIUS for a Genius Result answer card. |
| Search Signal Event | Reference to the record for the search on the Search Signal Event [sys_search_signal_event] table. |
| Number | Record number for the selected search result. |
| Domain | Domain to which the selected search result belongs. |
| Use for Suggestions | Option indicating whether AI Search uses this result selection when computing auto-complete suggestions. For more details, see Auto-complete suggestions in AI Search applications |
| Source URL | URL for the selected search result. |
| Action Data | JSON array of objects representing the search result selection action. |
Search Signal Result Event Action table
The Search Signal Result Event Action [sys_search_signal_result_event_action] table stores signal data for user interactions with search results.
| Column | Description |
|---|---|
| Signal Type | The type of user interaction signal recorded for the search result. For example, CLICK indicates that the user selected a search result. |
| Signal Value | The value for the user interaction signal. For example, when the signal type is CLICK, the signal value is the numeric index for the search result that the user selected. |
| Search Signal Result Event | Reference to the record for the search result on the Search Signal Result Event [sys_search_signal_result_event] table. |
Search Autocomplete Query Event table
The Search Autocomplete Query Event [sys_search_autocomplete_query_event] table stores signal data for auto-complete suggestions that users select from the search input field.
| Column | Description |
|---|---|
| Selected Query | The auto-complete suggested query that the user selected in the search input field. |
| Click Index | The numeric index of the auto-complete suggestion that the user selected in the search input field. |
| Latitude | Latitude coordinate of the user location in decimal degrees. |
| Longitude | Longitude coordinate of the user location in decimal degrees. |
| Search Profile | Reference to the search profile used for the search query. |
Genius Result Event Action table
The Genius Result Event Action [sys_search_genius_result_event_action] table stores signal data for user interactions with Genius Result answer cards.
| Column | Description |
|---|---|
| Action Id | The identifier for this Genius Result event action signal. |
| Action Type | The type of action taken from the Genius Result answer card. |
| Action Value | The value, if any, for the action taken from the Genius Result answer card. |
| Matched Genius Result Intents | List of NLU model intents matched by the action taken from the Genius Result answer card. Note: This field is only populated for Genius Result configurations with NLU triggers. |
| Card Type | The type of Genius Result answer card that the user interacted with. |
| Search Signal Result Event | Reference to the record for the Genius Result answer card on the Search Signal Result Event [sys_search_signal_result_event] table. |