personalizationImpact
100
personalizationImpact => personalization_impact
Can be used in these methods:
search,
browseObjects,
searchForFacetValues,
generateSecuredApiKey,
addApiKey,
updateApiKey
search,
browse,
search_for_facet_values,
generate_secured_api_key,
add_api_key,
update_api_key
search,
browse,
searchForFacetValues,
generateSecuredApiKey,
addApiKey,
updateApiKey
search,
browse_objects,
search_for_facet_values,
generate_secured_api_key,
add_api_key,
update_api_key
search,
browse,
searchForFacetValues
search,
browseObjects,
searchForFacetValues,
generateSecuredApiKey,
addApiKey,
updateApiKey
searchAsync,
browseAsync,
searchForFacetValues
Search,
Browse,
SearchForFacetValues,
GenerateSecuredApiKey,
AddApiKey,
UpdateApiKey
Search,
browse,
searchForFacetValues,
generateSecuredApiKey,
addApiKey,
updateApiKey
Search,
BrowseObjects,
SearchForFacetValues,
GenerateSecuredAPIKey,
AddAPIKey,
UpdateAPIKey
search,
browse index,
search into facet values,
generateSecuredApiKey,
add key,
update key
About this parameter
Define the impact of the Personalization feature.
The personalizationImpact parameter sets the percentage of the impact that personalization has on ranking records.
This is set at query time and therefore overrides any impact value you had set on your index.
The higher the personalizationImpact, the more the results are personalized for the user, and the less the custom ranking is taken into account in ranking records.
Usage notes:
- The value must be between 0 and 100 (inclusive).
-
This parameter isn’t taken into account if
enablePersonalizationisfalse. - Setting
personalizationImpactto0disables the Personalization feature, as ifenablePersonalizationwerefalse.
Examples
Enable personalization for the current search
For Android and Swift, you may use the requestOptions parameter during a search to pass the personalizationImpact.
1
$index->search('query', ['personalizationImpact' => 20])
