# Visitor page and product tracking Page tracking shows what a visitor is browsing and adds page, category and product context to their history. *Release 3.3 · developer, operator, visitor* **Floor › History** · **Browsing 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 ### This feature uses - **Requires** [Visitor identity](VIS-001.md): Page activity is associated with a visitor identity for the website. - **Configured in** [Traffic Optimizer for visitor tracking](VIS-019.md): Tracking admission and load limits can affect accepted activity and recorded history. - **Configured in** [Visitor browsing and activity history](VIS-020.md): History persistence and retention determine the browsing records available later. - **Works better with** [Subsites](ADM-003.md): Optional subsites separate tracked page and content context within a website account. - **Works better with** [Visitor and conversation information panels](CON-017.md): Visitor context panels present current browsing and history to operators. - **Works better with** [Visitor event rules and actions](ENG-001.md): Visitor events can respond to page views. - **Works better with** [Visitor data mapping for targeting](VIS-007.md): Custom page data adds integration-defined context to tracked pages. - **Works better with** [Page tags and conversation tags](VIS-009.md): Page tags add labels to the visitor's current browsing context. ### Used by - **Required by** [Browser language and device context](VIS-004.md): The website tracker supplies device, language and timing context with page activity. - **Required by** [Visitor location](VIS-005.md): Website tracking supplies the request context used for geographic information. - **Required by** [Visitor referrers and campaigns](VIS-006.md): Referrer processing uses the tracked page address and supplied referring address. - **Required by** [INSIDE visitor CLI](VIS-024.md): Recording a page view creates the tracking context used for a live test connection. - **Required by** [Session recording references](VIS-025.md): Recording references are carried with tracked page context. - **Required by** [Time-based visitor event triggers](VIS-026.md): Page timing is tied to the current tracked page view. - **Enhances** [Visitor data mapping for targeting](VIS-007.md): Page tracking supplies current-page values for mappings that use View data. - **Enhances** [Page tags and conversation tags](VIS-009.md): Page tracking supplies current-page tags separately from saved conversation and contact tags. - **Enhances** [Live visitors on the floor](VIS-012.md): Page views update the browsing context included in live visitor information. - **Enhances** [Visitor search and filters](VIS-013.md): Recorded category browsing supports Browsing Category filtering. - **Enhances** [Visitor browsing and activity history](VIS-020.md): Page tracking adds browsing entries to a timeline that can also contain conversations and purchases. - **Enhances** [Visitor connection recovery](VIS-022.md): Tracked page views let selected live updates be targeted and buffered for a particular page. - **Enhances** [Floor scenes and industry settings](CON-008.md): Page information and keywords can associate visitor activity with scene areas. - **Enhances** [Visitor and conversation information panels](CON-017.md): Page tracking supplies the current page and page history. - **Enhances** [Visitor event targeting conditions](ENG-002.md): Page information supplies page filters. - **Enhances** [Tracked product search and integrations](COM-018.md): Tracked product views supply the standard catalogue when no custom search result is supplied. - **Enhances** [Chat performance and tab visibility reports](REP-003.md): Recorded page views supply the denominator for chat-tab visibility. - **Enhances** [Event, link and Virtual Assistant reports](REP-013.md): Page Type Summary groups performance using recorded page types. - **Enhances** [Operation Analysis of visitor and sales activity](REP-017.md): 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.