Requirements for reports and dashboards
Although there are many fields that are relevant to signals, this topic describes which fields are required for each type of signal. Without these fields, reports and dashboards may not function as expected.
Report | Signal Types Used | Required Field | Type | Description | Example |
---|---|---|---|---|---|
Search queries |
✘ Annotation ✅ Click ✘ Login ✅ Request ✅ Response |
|
string |
Terms of the query. |
|
Facets used |
✘ Annotation ✘ Click ✘ Login ✅ Request ✘ Response |
|
array of string |
List of filters associated with the query, which in turn is associated with signal. |
|
Facet filters applied |
✘ Annotation ✘ Click ✘ Login ✅ Request ✘ Response |
|
array of string |
List of applied filters associated with the query, which in turn is associated with signal. |
|
Application servers |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Host name of the server that is hosting the app, which in turn is generating the signal. |
|
Response times |
✘ Annotation ✘ Click ✘ Login ✘ Request ✅ Response |
|
number |
Response time (in milliseconds). |
|
URLs clicked |
✘ Annotation ✅ Click ✘ Login ✘ Request ✘ Response |
|
string |
URL of the page that was selected from the search results. This typically results from a click signal. |
|
Search pages |
✘ Annotation ✘ Click ✘ Login ✅ Request ✘ Response |
|
string |
Title of the page that the signal originated from. |
|
Search platforms |
✘ Annotation ✅ Click ✘ Login ✅ Request ✅ Response |
|
string |
Name of the search platform. |
|
Visitor countries |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Originating country of the user. |
|
Visitor cities |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Originating city of the user. |
|
Browsers |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Name of the browser that generated the signal. |
|
Operating System |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Name of the operating system used by the user. |
|
Device types |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Type of the device used by the user. |
|
Websites people are coming from |
✘ Annotation ✅ Click ✘ Login ✘ Request ✘ Response |
|
string |
URL of the page that the signal originated from. |
|
Users |
✘ Annotation ✅ Click ✘ Login ✅ Request ✘ Response |
|
string |
Unique ID for the user that generated the signal. |
|
User domains |
N/A |
|
string |
Domain of the user that generated the signal. |
|
Types of event |
✅ Annotation ✅ Click ✅ Login ✅ Request ✅ Response |
|
string |
Type of the signal. |
|
Head Tail analysis |
✘ Annotation |
This report is populated by running a head tail job in Managed Fusion. With a collection called |
N/A |
||
✅ Click |
type |
string |
N/A |
||
✅ Click |
query |
string |
N/A |
||
✘ Login |
N/A |
||||
✘ Request |
N/A |
||||
✅ Response |
count_i |
number |
N/A |
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.