TL;DR

Eloqra turns an anonymous chat visitor into a contextual record by capturing their page, device, browser, OS, location, and UTM data on the first message.

Key Points

✓

On the first message, Eloqra captures the visitor's page URL and hostname, user-agent string, parsed device (type/browser/OS), and IP-based location (country/region/city) [1][3].

✓

The User-Agent header is what reveals the browser, version, and operating system on each request, so Eloqra parses it into readable device fields [1].

✓

Identification is anonymous by default; an optional [[pre-chat-form]] (collectVisitorInfo) adds a name and email to the [[website-visitor]] record [2].

✓

[[utm-parameters|UTM parameters]] are stored on the visitor record, linking the [[conversation]] back to the campaign or channel that drove the visit.

✓

All captured context rides along to the project owner over [[telegram-integration|Telegram]], so the operator sees who they are replying to without leaving the chat.

✓

Eloqra does not resolve IPs to companies or auto-enrich social profiles like some [[help-desk]] tools do; it captures self-reported and request-level signals only.

What Eloqra captures

When a Website Visitor sends their first Chat Message, the widget records a snapshot of context: the current page URL and hostname, the raw User-Agent string, and the device type, browser, and operating system parsed from it ^[1]^[3]. It also performs IP-based geolocation to estimate country, region, and city, and stores any UTM parameters present on the page so the Conversation can be tied to its acquisition source. This data is attached to the visitor record automatically, with no extra configuration, giving the operator immediate context the moment a thread opens.

Anonymous by default, identified on request

By default Eloqra treats every visitor as anonymous, much like how Intercom uses a first-party cookie to recognize a returning browser without knowing who the person is ^[4]. To attach a real identity, enable the optional Pre-Chat Form (collectVisitorInfo), which asks for a name and email before the chat starts. Those fields are saved to the Website Visitor profile and surface alongside the technical context. Eloqra stops there: it does not auto-enrich profiles from public social data, so what you see is the signals the browser sent plus whatever the visitor chose to share.

How it differs from B2B visitor tracking

Many marketing tools frame visitor identification as IP-to-company resolution or identity-graph matching across a Customer Journey. Eloqra is narrower and more honest: it parses request-level signals such as the User-Agent string ^[1] and IP location ^[3], and records explicit lead data from the Pre-Chat Form. There is no cross-domain tracking, no reverse company lookup, and no continuous session monitoring feed. The goal is to give a Support Operator enough context to answer well, not to build a sales-intelligence dossier. For founders this keeps the data footprint small and easier to reason about for GDPR Compliance.

Sources & References

User-Agent header - HTTP | MDN ↗

Tracking user data in Intercom | Intercom Help ↗

User-Agent Parser API Documentation | IPGeolocation.io ↗

Intercom Messenger Cookies | Intercom Help ↗

Last updated: June 25, 2026

Related Terms

Website Visitor

A website visitor is any person browsing a site where a live-chat widget is installed, tracked as an anonymous session until they send a message or identify themselves. In Eloqra, the visitor is the end-user on the other side of the chat bubble, distinct from the operator who answers from Telegram.

IP Geolocation

IP geolocation is the practice of estimating a device's approximate physical location (country, region, city) by looking up its public IP address in a database that maps IP ranges to places. In Eloqra it runs server-side on the first visitor message to attach location context to a conversation.

Pre-Chat Form

A pre-chat form is a short form shown before a live chat starts that asks the visitor for a small amount of identifying information, typically their name and email. In Eloqra it is the optional collectVisitorInfo step that gates the chat input until the visitor submits their details.

UTM Parameters

UTM parameters are tags appended to a URL's query string (utm_source, utm_medium, utm_campaign, utm_term, utm_content) that record which marketing campaign, channel, and source sent a visitor to your site. The acronym comes from Urchin Tracking Module, the analytics software Google acquired in 2005.

Visitor Tracking

Visitor tracking is the practice of collecting context about the people browsing a website, such as the pages they view, their device and browser, where they came from, and an approximate location. In Eloqra this context is captured on a visitor's first chat message and shown to the operator answering in Telegram.

Telegram Integration

Telegram Integration is the mechanism by which Eloqra routes every website chat into the project owner's Telegram, forwarding visitor messages to a Telegram bot and flowing operator replies back to the widget. It turns Telegram into the operator inbox, so there is no separate agent console to keep open.

Collect testimonials that build trust

Eloqra gives you a lightweight live chat widget that routes every visitor message to your Telegram — free while in early access.

Get Started Free

Visitor Identification