Sure, you can handle it. But should you?
Let our experts manage the tech maintenance while you focus on your business.
Let our experts manage the tech maintenance while you focus on your business.
Personalization
Installation and Configuration
Copyright ©
Mindbreeze GmbH, A-4020 Linz, 2024.
All rights reserved. All hardware and software names used are brand names and/or trademarks of their respective manufacturers.
These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services, and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.
For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.
Introduction
Personalization makes it possible to analyze user behaviour on the client and display it in app.telementry. You will find the necessary settings in the menu item “Configuration” under the tab “Client Services”. Activate “Advanced Settings” to specify the desired properties in the section “Personalization Settings”.
Configuration
Definition of properties
For example, to display the data from a user’s saved profiles, add a new property under Personalization Settings.
Setting | Description | Example/Default setting |
Enable Personalization | Enables personalization. | Default setting: Activated |
Properties | ||
Property | Defines the name for the property. This can be identical to the name of the field in the setting „Field“. | Example: my_count |
Source | Defines the source from which the content is to be obtained. The type of source determines whether the setting „Field“ will apply. For example, the value set for „Field“ will not apply, if the selected source does not have this field – for example, the field „count“ in the source „SearchRequest“. The following options are available:
| Default setting: SearchRequest |
Field | Defines the name of the field whose content is to be extracted from the source and saved as a property. | Example:
|
For other fields that can be used for the setting “Field”, see api.v2.search Interface Description.
Analyzing properties in app.telemetry
To use the configured properties, “Custom Property” columns must be added in app.telemetry.
Hint: app.telemetry can display a maximum of ten “Custom Property” columns.
To do this, expand the menu item “Reporting” in the Mindbreeze Management Center. Then open the menu item “Telemetry Details”. After that, open the item in the side navigation “Applications”. Click on “Client Service Query Log” in the section “Mindbreeze”.
To view the data collected by app.telemetry, click on “View Telemetry Data”. You will now see a list of various data. The required “Custom Property” columns can be added using “Columns”.
Add up to a maximum of ten „Custom Property“ columns.
For example, columns such as “Action” and “Result Position” provide information about the action that triggered the personalization in general (e.g. openhref, preview, etc.). Result Position returns the position of the selected hit. Under “Custom Properties” you will now find your information on the configured properties.
Example configuration: Defining the field “count” as property and analyzing It in app.telemetry
To analyse the field “count” in app.telemetry, a corresponding property must be defined first.
A new property is created in the section “Personalization Settings” with “Add Property”. The option “SearchRequest” is selected as the “Source”, since the field “count” is located in search queries. The field “count” is entered as the “Field”. Finally, the property with the name “count” is given a name that is identical to the name of the field.
Click “Save” to save and apply the configured property. It may take a few minutes for the configured property to be applied.
To be able to analyze the configured property in app.telemetry, a “Custom Property” column must be added. As only one property has been configured, adding the column “Custom Property 1” is sufficient.
By submitting a search query or reloading the log, the values of the configured property “count” are now displayed in the column “Custom Property 1”.
These values and the associated user behaviour on the client can thus be further analyzed and monitored.
Features
Voting
The voting feature is another way to get feedback from a user about a specific result.
If this feature is activated in Client Service, all the results are given a thumbs-up or a thumbs-down.
In addition, a comment can be entered.
Links
Beside the common actions like "open", "preview" of a result, simple links are also recorded. For this it is sufficient if links in the searchapp have an "href" attribute like <a href=https://yourdomain.com>Link</a>.