Product Selector

Fusion 5.11
    Fusion 5.11

    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

    COLLECTION_NAME_click_signals_aggregation

    required

    required

    required

    required

    required

    [1]

    COLLECTION_NAME_phrase_extraction

    required

    required

    required

    COLLECTION_NAME_spell_correction

    required

    required

    required

    COLLECTION_NAME_synonym_detection

    required

    required

    required

    required

    COLLECTION_NAME_head_tail

    required

    required

    required

    COLLECTION_NAME_user_item_prefs_agg

    required

    required

    required

    required

    required

    COLLECTION_NAME_user_query_history_agg

    required

    required

    required

    required

    required

    Created when recommendations are enabled

    COLLECTION_NAME_bpr_item_recs

    required

    required

    required

    required

    required

    Created when experiments are enabled

    Experiments

    required

    required

    required

    required

    required

    required

    required

    required

    Created manually

    Query-to-Query Collaborative Similarity

    required

    required

    required

    required

    required

    Query-to-Query Session-Based Similarity

    required

    required

    [2]

    [3]

    [4]

    required

    required

    Trending Recommender

    [5]

    required

    required

    required

    required

    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

    count_i

    1

    Number of times an interaction event occurred with this item

    doc_id

    NMDDV

    Product ID or Item ID

    query

    xwearabletech

    A query string from the user

    session_id

    91aa66d11af44b6c90ccef44d055cf9a

    Id for session in which user generated the signal

    type

    quick_view_click

    Type of session the user used to interact with the platform

    user_id

    11506893

    ID of user during the session

    timestamp_tdt

    2018-11-20T17:58:57.650Z

    Time when signal was generated

    Some signal types, including custom signal types, may include additional fields.