Zf

Anonymous Journey

Script anonymous track & page events, then identify a shopper, then send identified events — test how your backend stitches anonymous activity to a known profile.

Anonymous → Identified journey
Test how your backend stitches anonymous activity into identified profiles. Choose a single-user full script or simulate multiple shoppers arriving on load (each gets a fresh anonymous ID, then identify).

Profile used in Phase 2. Reset the flow to change selection after identify.

Initialize SDK first (top right).
Phase 1 — Anonymous

Track & page events fire without identify(). Your backend receives them with an anonymous ID only.

Phase 2 — Identify

identify() links the anonymous ID to a known shopper. Prior anonymous events should merge into this profile.

Phase 3 — Identified

New events attach directly to the identified user. Verify stitching in your engagement platform.

Phase 1 — Anonymous
View Home

Anonymous visitor lands on the storefront.

page("Storefront", "Home", …)
Browse catalog

Anonymous user opens the product catalog.

page("Commerce", "Product Catalog", …)
Product Viewed

Views a product — still no identify call.

track("Product Viewed", …)
Search Performed

Runs a catalog search as anonymous.

track("Search Performed", …)
Added To Cart

Adds item to cart before signing in.

track("Added To Cart", …)
View Cart

Opens cart page — backend should keep anonymous ID.

page("Commerce", "Cart", …)
Phase 2 — Identify
Identify as Ava

Links prior anonymous events to this shopper. Backend should merge anonymous → identified.

identify("shopper_1001", traits)
Phase 3 — Identified
Checkout Started

Post-identify track — should attach to known user.

track("Checkout Started", …)
Checkout page

Checkout page view after identity is known.

page("Commerce", "Checkout", …)
Coupon Applied

Applies discount as identified shopper.

track("Coupon Applied", …)
Order Completed

Completes purchase under identified profile.

track("Order Completed", …)
Order Confirmation

Thank-you page — full journey stitched to one person.

page("Commerce", "Order Confirmation", …)
SDK Configuration
Not initialized
Connect to Zixflow engagement with your write key. API and CDN default to dev-events.zixflow.in.
Activity Log
Live record of every SDK call. The exact payload sent to Zixflow engagement is shown for each event.

No activity yet

Initialize the SDK, then identify and fire events.