@blotoutio/providers-evo-search-sdk 1.71.0 → 1.72.0

package/README.md

@@ -312,6 +312,25 @@ Call `trackClick(productId)` when a user clicks a result, passing the `id` field
 }
 ```
 
+### Product views and cart contents — `trackProductView` / `setCartProductIds`
+
+Search ranking can use what the shopper has been looking at this visit. The SDK reads the product page it is loaded on by itself, from the storefront platform's own page globals or the page's `Product` structured data, so a themed storefront needs no code. Two cases it cannot see, and both are one call:
+
+```tsx
+import { trackProductView, setCartProductIds } from '@blotoutio/providers-evo-search-sdk/hooks'
+
+// A product page whose markup publishes neither of those, or a client-side
+// route change into one (no page load happens, so the SDK never re-runs).
+useEffect(() => trackProductView(product.id), [product.id])
+
+// The cart, as the COMPLETE current list of product ids — not a delta. The SDK
+// will not fetch it: that would be a request from your storefront on a path the
+// shopper is waiting on. Call this whenever the cart changes.
+setCartProductIds(cart.lines.map((line) => line.productId))
+```
+
+Both take the platform's numeric product id (string or number, the global-id form accepted too) — the same id space as `trackClick`. Both are plain `sessionStorage` writes: safe to call before the SDK has registered, they never throw, and the context dies with the tab. It leaves the browser only on search requests, and only when the merchant has the session-context option enabled.
+
 ### Add-to-cart / purchase — use your existing EdgeTag tags
 
 If you already send EdgeTag `AddToCart` and `Purchase` events via the EdgeTag SDK, you're done — EvoSearch receives them server-side and attributes them to searches automatically.