Visitor Analytics & Journey Tracking
A JavaScript snippet is copied from the admin panel and pasted onto the website — the same copy-paste approach as the chat widget.
How is the analytics JavaScript snippet installed on a site?
A JavaScript snippet is copied from the admin panel and pasted onto the website — the same copy-paste approach as the chat widget.
How is page-to-page navigation tracked for every visitor?
The snippet tracks page-to-page navigation for every visitor — each page view and the path between pages is recorded as a visitor event, grouped into a session.
How is an anonymous visitor resolved to a real identity on purchase?
Visitors are tracked anonymously by an id while browsing; on purchase, that anonymous id is resolved to the real identity (the customer), linking the whole prior browsing journey to a…
What does the full pre-purchase journey reveal (pages, time, path)?
Once resolved, the full pre-purchase journey is revealed: which pages the customer visited, how many, how long they spent on each, and the path they took.
How is aggregate behaviour analyzed (where people spend time, exit pages)?
Beyond individual journeys, the analytics aggregate behaviour across visitors: where people spend time, which pages they leave from (exit pages), and patterns in how they move.
How are bots and crawlers excluded from counts?
Bots and crawlers (Google's and others') are detected and excluded from the counts (events carry a bot flag).
How is traffic source attributed (social, referral, organic, AI search)?
Each visit is attributed to a traffic source — social media, referral sites (and individual referrers), organic search, and AI search — plus direct.
How are daily summaries pre-aggregated for performance?
To keep analytics fast at scale, daily summaries are pre-aggregated — a background process rolls raw events up into daily summary data, and a refresh action can rebuild them.