From 306c6a4a48360bfcab74a4a5d42b5bc8e060c9fb Mon Sep 17 00:00:00 2001 From: Julian Wittorf Date: Fri, 6 Mar 2026 16:02:44 +0100 Subject: [PATCH] Reference sessionParams hybrid for GraphQL with personalization via JS Lib --- .../implement-search-using-api/analytics-ab-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/implementing-nosto/implement-search/implement-search-using-api/analytics-ab-testing.md b/implementing-nosto/implement-search/implement-search-using-api/analytics-ab-testing.md index 35fa049..61f3e4f 100644 --- a/implementing-nosto/implement-search/implement-search-using-api/analytics-ab-testing.md +++ b/implementing-nosto/implement-search/implement-search-using-api/analytics-ab-testing.md @@ -8,7 +8,7 @@ The workflow for search and categories is generally the same. This article descr ## Limitations -* Individual personalization with user-specific affinities is currently not available with a pure API approach to search. If this is a critical requirement, consider using the [JavaScript library](../search/). +* Individual personalization with user-specific affinities is currently not available with a pure API approach to search. If this is a critical requirement, consider using the [JavaScript library](../search/) for a client-side integration or a [hybrid-integration by passing the sessionParams](./using-the-search-api.md#session-params). * An `API_APPS` authentication token is necessary to implement API requests related to session management and tracking. ## General workflow