A query signal records a user’s submitted search query at a particular time. It anchors the subsequent interaction sequence, including returned results, clicks, cart additions, and purchases. section 4.1.3
A generic signal record uses query_id, user, type, target, and signal_time. The query event stores the submitted keywords; separate result and interaction events retain a consistent, extensible structure while linking back to the originating query_id. section 4.1.3
Query signals support several search-quality workflows:
- Normalize and deduplicate queries before analyzing user language. section 6.5.2
- Tokenize queries, remove stop words and numbers, and count recurring terms. section 6.5.2
- Extract domain-specific phrases and alternative labels for query interpretation. section 6.4.2
- Learn spelling corrections by comparing infrequent variants with frequent, similarly spelled terms. section 6.5.2
A linked search journey
A user searches for “ipad,” receives doc1, doc2, and doc3, clicks doc1 and doc3, and adds doc3 to a cart. A later “ipad cover” query produces another linked sequence. Query signals identify both submitted queries, while query_id connects each result and interaction to its originating search. section 4.1.3
Table 4.1 Example signals format
|
query_id
|
user
|
type
|
target
|
signal_time
|
|---|---|---|---|---|
|
1
|
u123
|
query
|
ipad
|
2024-05-01-09:00:00
|
|
1
|
u123
|
results
|
doc1,doc2,doc3
|
2024-05-01-09:00:00
|
|
1
|
u123
|
click
|
doc1
|
2024-05-01-09:00:10
|
|
1
|
u123
|
click
|
doc3
|
2024-05-01-09:00:29
|
|
1
|
u123
|
add-to-cart
|
doc3
|
2024-05-01-09:03:40
|
|
2
|
u123
|
query
|
ipad cover
|
2024-05-01-09:04:00
|
|
2
|
u123
|
results
|
doc4,doc5
|
2024-05-01-09:04:00
|
|
2
|
u123
|
click
|
doc4
|
2024-05-01-09:04:40
|
|
2
|
u123
|
add-to-cart
|
doc4
|
2024-05-01-09:05:50
|
|
1
|
u123
|
purchase
|
doc3
|
2024-05-01-09:07:15
|
|
2
|
u123
|
purchase
|
doc4
|
2024-05-01-09:07:15
|
Use the signal table to inspect how query, results, click, cart, and purchase events are represented and timestamped. section 4.1.3
