Visitor page and product tracking
Page tracking shows what a visitor is browsing and adds page, category and product context to their history.
What it is
Page tracking tells INSIDE which page a visitor is viewing. It can include the page name, content type, category and product details. Operators can use this context to help without asking the visitor to describe every page they have opened.
Who uses it and why
- Operators check current browsing and earlier pages before offering help.
- Developers supply meaningful page descriptions and navigation updates.
- Visitors receive help informed by the pages and products they are viewing.
Where to find it
Select a visitor on the floor to see their current browsing context. Open History in desktop visitor details, or Browsing History in the mobile interface, to inspect recorded activity.
How it works
The website integration sends the visited URL and page description. It can also send a canonical URL, category, image, product SKU, price, subsite, page tags and custom page data.
INSIDE recognises product, product category, article, search, homepage, checkout, page-not-found, login, order-confirmation and lead-related activity. Other named page types use ordinary page handling.
A page view updates the visitor's current position and browsing context. INSIDE reuses shared content descriptions within the website, subsite and content type, and refreshes their URL, image and metadata when supplied again.
The standard tracker also handles pages restored through the browser's Back and Forward cache by reconnecting and sending a fresh view.
Configure it
Your developer should supply both a meaningful page name and page type, together with the correct URL. Add product and category details where relevant. Use consistent names for the same content.
For a website that changes pages without a full browser reload, send an explicit page-tracking update for navigation. Check that each route change updates the operator's view.
Limits and good to know
- Normal content recording needs both a page name and a type. A URL alone does not provide a complete named content record.
- Page names are limited to 150 characters. A newly recorded shared content URL is limited to 2,048 characters.
- Current browsing can update even when load controls suppress a history entry. A live change is not proof that a corresponding history row will be available later.
- INSIDE removes some recognised referral parameters from tracked URLs. This is not general removal of sensitive URL content.
- Product viewing, basket updates and completed purchases are separate activities.
Depends on and works with
+11 more · used by
- Visitor connection recoveryEnhances
Tracked page views let selected live updates be targeted and buffered for a particular page.
- INSIDE visitor CLIRequires
Recording a page view creates the tracking context used for a live test connection.
- Session recording referencesRequires
Recording references are carried with tracked page context.
- Time-based visitor event triggersRequires
Page timing is tied to the current tracked page view.
- Floor scenes and industry settingsEnhances
Page information and keywords can associate visitor activity with scene areas.
- Visitor and conversation information panelsEnhances
Page tracking supplies the current page and page history.
- Visitor event targeting conditionsEnhances
Page information supplies page filters.
- Tracked product search and integrationsEnhances
Tracked product views supply the standard catalogue when no custom search result is supplied.
- Chat performance and tab visibility reportsEnhances
Recorded page views supply the denominator for chat-tab visibility.
- Event, link and Virtual Assistant reportsEnhances
Page Type Summary groups performance using recorded page types.
- Operation Analysis of visitor and sales activityEnhances
Page and product tracking supplies visitor activity and the product views shown in Trending Now.
View all connections as a list
This feature uses
- SubsitesEnhances
Optional subsites separate tracked page and content context within a website account.
- Visitor and conversation information panelsEnhances
Visitor context panels present current browsing and history to operators.
- Visitor event rules and actionsEnhances
Visitor events can respond to page views.
- Visitor identityRequires
Page activity is associated with a visitor identity for the website.
- Visitor data mapping for targetingEnhances
Custom page data adds integration-defined context to tracked pages.
- Page tags and conversation tagsEnhances
Page tags add labels to the visitor's current browsing context.
- Traffic Optimizer for visitor trackingConfigured by
Tracking admission and load limits can affect accepted activity and recorded history.
- Visitor browsing and activity historyConfigured by
History persistence and retention determine the browsing records available later.
Used by
- Browser language and device contextRequires
The website tracker supplies device, language and timing context with page activity.
- Visitor locationRequires
Website tracking supplies the request context used for geographic information.
- Visitor referrers and campaignsRequires
Referrer processing uses the tracked page address and supplied referring address.
- Visitor data mapping for targetingEnhances
Page tracking supplies current-page values for mappings that use View data.
- Page tags and conversation tagsEnhances
Page tracking supplies current-page tags separately from saved conversation and contact tags.
- Live visitors on the floorEnhances
Page views update the browsing context included in live visitor information.
- Visitor search and filtersEnhances
Recorded category browsing supports Browsing Category filtering.
- Visitor browsing and activity historyEnhances
Page tracking adds browsing entries to a timeline that can also contain conversations and purchases.
- Visitor connection recoveryEnhances
Tracked page views let selected live updates be targeted and buffered for a particular page.
- INSIDE visitor CLIRequires
Recording a page view creates the tracking context used for a live test connection.
- Session recording referencesRequires
Recording references are carried with tracked page context.
- Time-based visitor event triggersRequires
Page timing is tied to the current tracked page view.
- Floor scenes and industry settingsEnhances
Page information and keywords can associate visitor activity with scene areas.
- Visitor and conversation information panelsEnhances
Page tracking supplies the current page and page history.
- Visitor event targeting conditionsEnhances
Page information supplies page filters.
- Tracked product search and integrationsEnhances
Tracked product views supply the standard catalogue when no custom search result is supplied.
- Chat performance and tab visibility reportsEnhances
Recorded page views supply the denominator for chat-tab visibility.
- Event, link and Virtual Assistant reportsEnhances
Page Type Summary groups performance using recorded page types.
- Operation Analysis of visitor and sales activityEnhances
Page and product tracking supplies visitor activity and the product views shown in Trending Now.
FAQ and troubleshooting
Why does the current page stay the same after navigation?
Check that the integration sends a new view when the website changes pages, especially on websites that navigate without reloading.
Why is a product shown as an ordinary page?
Check the supplied page type and name. Product context also needs the relevant product details from the integration.
Why is the history shorter than the activity I saw live?
History retention and tracking load controls can affect what is saved. Ask Powerfront to review those controls if the difference is unexpected.
Does viewing an order-confirmation page record every purchase detail?
Purchase processing has its own integration requirements. A page description alone does not replace purchase tracking.