@active-reach/web-sdk 1.45.0 → 1.45.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -499,6 +499,8 @@ Content you render yourself is left alone. If the slot already has children (a `
499
499
 
500
500
  **`GET /v1/in-app/slot-shapes`**: for server renderers. It takes the same write-key headers as `/v1/in-app/active` (`X-Aegis-Write-Key`, optional `X-User-ID` / `X-Contact-ID` / `X-Property-Id`). The query parameters are `property_id` (used when the header is absent), `surface`, `screen`, `page_url` (path + search), `location_id`, `device_type`, `geo` and `is_new_user`. The response carries `Cache-Control: private, max-age=60` and the body is `{"shapes": [SlotShape, …]}`, one shape per slot that **will** fill. A slot that is absent will not fill. Each campaign in `/v1/in-app/active` also carries its own `slot_shape`.
501
501
 
502
+ **Hosts that print shells themselves.** The ACS storefront renders them from `display.inapp_slot_shapes`. The Shopify theme app extension renders them from the shop metafield `aegis.slot_shapes`, which the cell keeps in sync (`shopify-plugin/theme-app-extension/snippets/aegis-slot-shell.liquid`). Both mark their shells `data-aegis-slot-shell` + `data-aegis-shell-owner="host"` and print the inline shapes, so the SDK adopts them as described above.
503
+
502
504
  `SlotShape`:
503
505
 
504
506
  | Field | Meaning |