Every page, every session, in order.
First page, last page, referrer, device, browser, country, city. Returning vs new. Conversion path. Click into any visitor for the full chronological journey.
📍 Visitor intelligence
Know who is visiting, and what they want.
Anonymous visitors, returning leads, signed-in customers, AI chat conversations and revenue events — all stitched into one intelligence layer per visitor. The dashboard tells you who is on your site right now and what they're trying to do.
Real-timesub-second event ingestion
Per-visitortimeline across sessions
Auto-identifiedlogged-in customers
Attributedto revenue events
What it does
Anonymous visit → identified lead → attributed sale.
One continuous intelligence thread per person, even across devices and weeks.
Composite intent score.
Pricing visits, /demo views, chat questions, return cadence — combined into a 0–100 score updated live.
Country, city, ISP.
Resolved from IP. Used for currency, language, support hours.
Anonymous → identified.
When the visitor signs in, every prior anonymous session is linked. Continuous journey, no gaps.
Visit → invoice.
Conversions linked to the journey that produced them.
"Likely comparing plans — offer onboarding help."
For high-intent visitors, the AI suggests a next-step on the dashboard so your team can act in real time.
How identification works
Logged-in customers are auto-identified everywhere.
On any page that exposes the customer to the OpsIQ widget — your account portal, your customer-facing dashboard, your help center — the widget reads window.opsiqConfig.user and propagates the email and customer ID into the visitor log on every beacon. The "Logged-in" count on the dashboard fills automatically.
SaaS portal/accountCustom hookswindow.opsiq.identify
Surface/account portal · custom pages
Triggerwindow.opsiqConfig.user
Storageuser_email + client_id
Linkagevid → email → customer
Re-identifyworks across visits
Privacy by default
No-cookies-needed when consent is denied.
When a visitor declines non-essential cookies via the consent banner, OpsIQ falls back to session-only tracking — IP-anonymised, no localStorage identifier, no cross-session linking. Your analytics still works for engagement signals; the privacy surface stays clean.
Consent-awareGDPRCCPAAudit
Default modeprivacy-on
Opted-outsession-only · IP-anon
Self-serve delete/account → Privacy
Retentioncustomer-set
Common questions
Everything teams ask before they sign up.
Will it work with Cloudflare in front?
Yes — we read the CF-Connecting-IP header for accurate visitor IPs. Same for Akamai, Fastly, and any reverse proxy that sets standard forwarding headers.
Can I export my visitor data?
Yes, CSV export with full timeline. Or query the API for programmatic access.
Does it work on single-page apps?
Yes — the widget exposes a window.opsiq.pageview() hook for SPAs that don't do full page loads.
Visitor intelligence
Know your traffic. Convert it.
First live session in your dashboard within 5 minutes of installing the widget.