@encorekit/web-sdk 2.1.4 → 2.2.1

package/README.md

@@ -334,6 +334,26 @@ round trip.
 > thing that blocks serving, and it is deliberate — it is how a live surface is
 > stopped without a deploy. A switched-off surface no-ops exactly as below.
 
+### Per-placement reward variants (opt-in)
+
+Encore can serve a different reward variant per placement label, for example a
+code screen for `'email_code'` and the plain gift picker for `'email'`. The
+variant prefetched at `configure()` cannot carry that choice, so ask for it:
+
+```typescript
+Encore.configure({ apiKey: 'your-api-key-here', resolveVariantsByPlacement: true });
+
+// One GET /config?useCase=post-action-reward&placementId=email_code before the
+// sheet renders; the variant it names is presented and reported.
+await Encore.placement('email_code', { useCase: 'rewardUsers' }).show();
+```
+
+A settled answer is reused for that label for the rest of the session (until
+`reset()`), while a failed or discarded request is retried on the next
+presentation. A failed or slow request falls back to what the SDK does with the option off (the
+prefetched variant, or the on-demand fetch when there is none); it never blocks
+or breaks the presentation. Off (the default), the SDK's requests are unchanged.
+
 ### When nothing presents
 
 A use case that cannot be served resolves `{ status: 'unavailable' }`, reports