Skip to main content
A number of Managed 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.
querycount_itypetimestamp_tdtuser_iddoc_idsession_idfusion_query_id
Created by default
COLLECTION_NAME_click_signals_aggregation✅✅✅✅✅[1]
COLLECTION_NAME_phrase_extraction✅✅✅
COLLECTION_NAME_spell_correction✅✅✅
COLLECTION_NAME_synonym_detection✅✅✅✅
COLLECTION_NAME_head_tail✅✅✅
COLLECTION_NAME_user_item_prefs_agg✅✅✅✅✅
COLLECTION_NAME_user_query_history_agg✅✅✅✅✅
Created when recommendations are enabled
COLLECTION_NAME_bpr_item_recs✅✅✅✅✅
Created when experiments are enabled
Experiments✅✅✅✅✅✅✅✅
Created manually
Query-to-Query Collaborative Similarity✅✅✅✅✅
Query-to-Query Session-Based Similarity✅✅[2][3][4]✅✅
Trending Recommender[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 NameExample ValueDescription
count_i1Number of times an interaction event occurred with this item
doc_idNMDDVProduct ID or Item ID
queryxwearabletechA query string from the user
session_id91aa66d11af44b6c90ccef44d055cf9aId for session in which user generated the signal
typequick_view_clickType of session the user used to interact with the platform
user_id11506893ID of user during the session
timestamp_tdt2018-11-20T17:58:57.650ZTime when signal was generated
Some signal types, including custom signal types, may include additional fields.