@xenia-martech/mcp 1.2.0-dev.3 → 1.2.0-dev.5

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.
Files changed (3) hide show
  1. package/README.md +2 -1
  2. package/dist/bin.js +49 -49
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -35,7 +35,8 @@ After you choose how to get the SDK token, the assistant does the rest without s
35
35
  with page patterns), using the SDK's helpers (`@xenia-martech/sdk-js` 1.2+) instead of hand-written
36
36
  code. In Next.js: `xeniaEdgeProxy()` in `proxy.ts`, with your site's own facts and rewrites in its
37
37
  hooks, plus `createManifestRoute()` and `createRevalidateRoute()` for the public manifest and
38
- Xenia's storefront webhook. In any other proxy: `@xenia-martech/sdk-js/edge`. Personalized sections
38
+ Xenia's storefront webhook. The edge client reads that manifest route (`manifestUrl`), so a
39
+ journey published since its last refresh is still decided. In any other proxy: `@xenia-martech/sdk-js/edge`. Personalized sections
39
40
  get `data-xenia-slot` attributes for impressions and clicks. The browser client's `pageViews`,
40
41
  `pageLeave`, `trail`, `navClicks` and `contentClicks` options handle tracking, and
41
42
  `xeniaEdgeProxy({ debug, qa })` with `<XeniaDebugPanel />` shows what was decided on each page,