Understand Your Visitors with Widget Page Tracking

When a visitor opens your chat widget, wouldn't it be helpful to know which pages they've already viewed on the way? Converge's widget records a lightweight, page-view-only timeline for every visitor — no behavioural fingerprinting, no third-party cookies, and nothing to configure.

What's Tracked

The widget records exactly one event type:

Event	When it fires	Data collected
page_view	Each page load and every SPA route change	URL, page title, referrer hostname, session ID, visitor ID

Pro Tip: There is no scroll tracking, click tracking, section tracking, or custom event API. If you previously used data-cv-track, data-cv-section, or window.Converge.track(), those are no-ops now and can safely be removed.

Success Check: Page views start recording automatically once the widget is installed — no configuration needed.

Privacy & Compliance

Page tracking is designed to collect the minimum data needed to give your support team useful context:

Do Not Track respected

If the visitor's browser sends a Do Not Track signal, no page-view events are recorded or sent.

No third-party cookies

The visitor ID lives in first-party storage on your domain. Nothing is shared with third parties.

First-party data only

Page views are stored on your Converge instance and tied only to the visitor's session and the conversation they eventually open.

Data minimization

Only URL, page title, and referrer hostname are collected. No keystrokes, no form contents, no mouse movement.

Note: You should still include analytics disclosure in your site's privacy policy and implement cookie consent banners as required by your jurisdiction.

Success Check: Tracking respects Do Not Track and stores all data on your Converge instance only.

How It Works

On every URL change the widget posts a single page_view to your Converge backend. No batching, no queue, no localStorage buffering — one navigation, one HTTP request.

SPA (Single Page Application) support

If your site is a React, Vue, Next.js or other SPA, the widget detects virtual page changes by:

Listening to popstate events (browser back/forward)
Intercepting history.pushState and history.replaceState

Pro Tip: No configuration needed for SPAs. Each route change is recorded as a separate page_view.

Viewing the Session Timeline

Page views appear inside each customer's profile as a session-grouped timeline, giving your team context the moment a conversation starts.

1
Open a conversation with a widget customer
Click any customer who contacted you through the chat widget.
2
Open the activity tab
Click the activity icon in the customer details panel.
3
Review the session timeline
Each session expands into the ordered list of pages they viewed, with timestamps and total duration.

Activity tab showing sessions and the pages a visitor viewed before starting a conversation

Success Check: You can now see the visitor's browsing path directly inside the conversation.

Best Practices

Keep page titles meaningful

The timeline displays the page title for each view. Use descriptive <title> tags so the timeline tells a clear story.

Use clean URLs

Avoid tracking-only query strings on internal links — they make the timeline noisier without adding value.

Respect user privacy preferences

Converge respects Do Not Track automatically. If your site uses a consent banner, you can hold off loading the widget script until consent is granted.

What's Next?

Explore related features:

Widget Guide — Install and customize the chat widget on your website
Leads Guide — Turn tracked visitors into scored leads automatically
Inbox Guide — Master the unified inbox where the activity tab lives