Required Signals for Jobs
A number of Fusion jobs ingest signals. Make sure your signals include the fields required by the jobs you plan to use. The table below shows which jobs require specific fields in your signals.
query |
count_i |
type |
timstamp_tdt |
user_id |
doc_id |
session_id |
fusion_query_id |
|
|---|---|---|---|---|---|---|---|---|
Created by default |
||||||||
|
|
|
|
|
[1] |
|||
|
|
|
||||||
|
|
|
||||||
|
|
|
|
|||||
|
|
|
||||||
|
|
|
|
|
||||
|
|
|
|
|
||||
Created when recommendations are enabled |
||||||||
|
|
|
|
|
||||
Created when experiments are enabled |
||||||||
|
|
|
|
|
|
|
|
|
Created manually |
||||||||
|
|
|
|
|
||||
|
|
[2] |
[3] |
[4] |
|
|
||
[5] |
|
|
|
|
||||
1 Required if you are using response signals.
2 Required if you want to weight types differently.
3 Required if you want to use time decay.
4 Required if no session_id field is available. Either user_id or session_id is needed on response signals if doing any click path analysis from signals.
5 Required when identifying trending queries instead of trending items.
The fields mentioned above are defined as follows:
| Field Name | Example Value | Description |
|---|---|---|
|
1 |
Number of times an interaction event occurred with this item |
|
NMDDV |
Product ID or Item ID |
|
xwearabletech |
A query string from the user |
|
91aa66d11af44b6c90ccef44d055cf9a |
Id for session in which user generated the signal |
|
quick_view_click |
Type of session the user used to interact with the platform |
|
11506893 |
ID of user during the session |
|
2018-11-20T17:58:57.650Z |
Time when signal was generated |
Some signal types, including custom signal types, may include additional fields.