Visitor Monitor
Visitor Monitor
What is Visitor Monitor?
Visitor Monitor shows you who is on your website right now — in real time. You can see each visitor's current page, how long they've been on the site, how many pages they've viewed, what browser and country they're from, and whether they're actively chatting with an agent.
The page refreshes automatically every 30 seconds.
How to access it
Go to Visitor Monitor in the left sidebar of the admin portal (admin.velaro.com). It is a top-level menu item — no submenu needed.
If you don't see it in the sidebar, your plan does not include Visitor Tracking. Contact support to enable it.
What you can see
Live stats (top of the page)
| Stat | What it means |
|---|---|
| Online Now | Visitors active on your site at this moment |
| Chatting | Of those online, how many have an open chat |
| Browsing | Online visitors not currently in a chat |
| Visits Today | Total unique sessions started today |
| This Month | Total sessions this calendar month |
| Last 7 Days | Sparkline chart of daily visit volume |
Below the stats: browser breakdown, OS breakdown, and country breakdown with percentage bars.
Active Visitors table
Each row is one live visitor session. Columns:
- Status — Chatting (blue, pulsing) or Browsing (green)
- Current Page — the exact URL path they're on right now
- Context — smart tag if they're on a high-intent page: In Checkout, Cart, Product, Collection, or Search
- From — referral source (where they came from); "Direct" if no referrer
- Browser — Chrome, Safari, Firefox, etc.
- Country — country flag + code
- Pages — number of pages viewed in this session
- Time on Site — total session duration (e.g. 3m 42s)
- Activity — "Active", "Xm ago", or "Idle Xm" (rows go dim after 10 minutes of no activity)
Visitors drop off the list 30 minutes after their last activity.
Page context badges
When a visitor is on a high-intent page, a colored badge appears in the Context column:
- In Checkout (amber) — visitor is in the checkout flow — high urgency for proactive chat
- Cart (orange) — visitor has items in cart
- Product (purple) — viewing a specific product page
- Collection (indigo) — browsing a category or collection
- Search (sky blue) — using site search
Use these to prioritize which visitors to invite to chat proactively.
Requirements
- Subscription: Visitor Tracking must be enabled on your plan
- Embed script: The Velaro chat embed script must be installed on your website — visitor tracking is powered by the same script
- No separate tracking pixel or tag manager setup is needed
Tips
- Sort your attention by the Context column — visitors in Checkout or Cart are most likely to need help
- Dimmed rows (idle 10+ min) are still technically active but haven't navigated recently
- The "From" column tells you which marketing channels are driving traffic — use it to understand where chatters come from
Privacy & consent (GDPR / CCPA)
Visitor monitoring is treated as analytics activity and respects visitor consent automatically:
- Consent-gated: the embed only starts tracking page activity once the visitor grants
Analytics consent in your cookie/consent platform (OneTrust, Cookiebot, Osano, Termly,
Usercentrics, and others are auto-detected). If they decline, nothing is tracked.
- Revocation: if a visitor turns Analytics off later, tracking stops immediately.
- Server-side opt-out: even if the embed is bypassed, the backend independently drops any
visitor who sends Sec-GPC: 1 (Global Privacy Control) or DNT: 1 (Do Not Track), or whose
beacon reports declined consent. No session row, no IP/GeoIP lookup, no agent alert for them.
No configuration is required — this is on by default. See the messaging KB
"Cookie consent (v20)" for the embed-side details.
Bot & scanner protection
The Visitor Monitor and the "new visitor" mobile alerts are automatically shielded from
automated traffic:
- Known crawler/scanner/bot user agents (search bots, uptime monitors, security scanners) are
dropped before a session is ever created.
- A single IP that spawns visitor sessions faster than a human plausibly could has its agent
alerts throttled, so a site being scanned doesn't flood agents' phones.
Real visitors are unaffected; this only suppresses automated noise.
Was this article helpful?