@xenia-martech/mcp 1.2.0-dev.2 → 1.2.0-dev.4
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 +9 -0
- package/dist/bin.js +49 -49
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -31,6 +31,15 @@ After you choose how to get the SDK token, the assistant does the rest without s
|
|
|
31
31
|
timeout and circuit breaker, consent from your cookie banner, and form conversions.
|
|
32
32
|
- **Each journey** you name, in your real components: server-side with `{ fallback: null }` so an
|
|
33
33
|
outage renders your default content; `track()` for event triggers.
|
|
34
|
+
- **Edge personalization** for a storefront whose journeys target pages (Personalization Resolve
|
|
35
|
+
with page patterns), using the SDK's helpers (`@xenia-martech/sdk-js` 1.2+) instead of hand-written
|
|
36
|
+
code. In Next.js: `xeniaEdgeProxy()` in `proxy.ts`, with your site's own facts and rewrites in its
|
|
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
|
|
39
|
+
get `data-xenia-slot` attributes for impressions and clicks. The browser client's `pageViews`,
|
|
40
|
+
`pageLeave`, `trail`, `navClicks` and `contentClicks` options handle tracking, and
|
|
41
|
+
`xeniaEdgeProxy({ debug, qa })` with `<XeniaDebugPanel />` shows what was decided on each page,
|
|
42
|
+
in development and QA only.
|
|
34
43
|
- **Checks** — a type-check/build and `xenia_verify`, plus warnings about the journey itself (an
|
|
35
44
|
A/B split that would show the same visitor different variants, a journey that's stopped) with the
|
|
36
45
|
dashboard fix.
|