How Yokaify works
The lifecycle of a Yokaify session — from script load to a grounded, behavior-triggered intervention.
The session lifecycle
- Load. The script boots, assigns the visitor a random anonymous ID (stored locally), and shows the mascot.
- Init. It contacts Yokaify to fetch your site configuration and page context.
- Score. Every meaningful event — scroll, dwell, cursor movement, text selection, form focus, cart changes — is fed to a scoring engine that runs in a background Web Worker, off your page's main thread.
- Decide. When the signals add up to a recognized hesitation pattern, Yokaify decides to intervene.
- Answer. The backend generates a reply grounded in your knowledge base and the mascot speaks. From there the shopper can keep chatting.
Privacy by design
Behavior is scored in the browser. Raw signals stay client-side; Yokaify only contacts the server when it has decided to act or to record the outcome. Visitors are identified by a random ID, not personal data.
Built-in restraint
Helpfulness only works if it isn't annoying. Yokaify enforces:
- Cooldowns between interventions so it never spams a visitor.
- A daily cap per visitor, regardless of how many pages they view.
- Bot filtering so automated traffic never triggers a pitch.
- Dismiss and quit controls — if a shopper closes the mascot for the session, it stays quiet.
Works across pages and tabs
Yokaify follows single-page-app navigation and coordinates across browser tabs, so a visitor comparing products in multiple tabs is treated as one person — and an intervention in one tab respects the cooldown in the others.