Public endpoints and data flow
Understand collect, ping, script, chat and voice routes, response states, limits and stored records.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Understand the public collect endpoint
Receives validated event batches for a registered site.
Understand the public ping endpoint
Maintains active session state.
Understand the public script endpoint
Serves or supports portable script delivery where used.
Understand invalid_site responses
The collector rejects an unknown or invalid site key.
Understand collection_disabled responses
The collector rejects collection while disabled.
Understand ignored responses
Privacy or staff-exclusion rules can return an ignored result.
Understand restricted public CSRF exclusions
Only the module’s required public collection/chat/voice endpoints are excluded through its filter.
Understand stored Visitor Intelligence records
The installer creates sites, sessions, events, pageviews, conversions, settings, ignored IPs, chat threads/messages and voice records.
Understand session creation and update
The collector creates or refreshes a session and records last activity.
Understand event storage
Supported event payloads are recorded against the visitor session.
Understand page-view storage
Page views are stored separately for journey reporting.
Understand public chat routes
chat_poll, chat_send and chat_close support the embedded visitor interface.
Understand public voice routes
voice_poll, voice_answer and voice_signal support visitor WebRTC signalling.
Understand live_json
The administrator Live Monitor polls this endpoint for KPIs and rows.
Understand administrator chat routes
chat_open, chat_poll, chat_send, unread and thread-open support staff engagement.
Understand administrator voice routes
chat_voice_start, poll and signal support staff WebRTC signalling.