--- sourceDocument: Australia Platform Analytics sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence Release : - australia ft:locale : - en-US ft:publication_title : - Australia Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Page properties analytics # Page properties analytics {#ariaid-title1} Release version: Australia Updated August 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Page properties analytics Page properties analytics enhances usage data by capturing metadata attributes (page properties) that describe a page, such as page name, owning team, language, or category. These properties enable ServiceNow customers to segment and analyze user activity more meaningfully than by page identifier alone. Page properties are captured from URL parameters or record metadata on each page view and are associated with both pages and events, allowing detailed insights into user interactions within specific page contexts. Show full answer Show less ## Key Features * **Page Properties Capture:** Automatically collect named, filterable attributes on every page view, distinguishing pages sharing a single identifier (e.g., different knowledge articles or catalog items). * **Integration with Events:** Events (user interactions on a page) carry page properties alongside event properties, enabling combined filtering and analysis of where events occur. * **Filtering and Analytics:** Use page properties as filters in Usage Insights---including the page filter bar, sessions, events, advanced filters, and conversion funnels---to analyze user behavior based on page attributes. * **Visual Distributions:** Property value distributions are displayed as charts, showing segment counts and percentages, facilitating quick understanding of usage patterns. * **Customization:** Default system properties are captured automatically, with options to add custom properties for more relevant data segmentation. ## Why It Matters Without page properties, analytics only show generic page identifiers, making it difficult to differentiate between multiple pages using the same view template (e.g., all knowledge articles appear as the same page). Page properties solve this by attaching meaningful attributes, enabling precise analysis such as: * Counting specific catalog requests by page category. * Tracking comments on a particular knowledge article. * Listing dashboard visits by name over a period. ## Practical Application ServiceNow customers can leverage page properties to: * Filter usage data by meaningful page attributes alongside event data. * Build advanced conditions to analyze specific subsets of page visits or funnel steps. * Gain actionable insights on how different pages perform and how users interact with them. ## Requirements and Availability Page properties support requires Usage Insights from Brazil patch 0 and Australia patch 6 onward. This feature extends event property capabilities to pages, providing consistent analytics across user interactions and page views. Page properties are metadata attributes that describe a page, such as the page name, owning team, language, or category. By enriching pages with properties, you can segment usage data by attributes that are meaningful to your organization instead of by page identifier alone. ## Pages and events A page property is a named, filterable attribute captured from the URL parameters or record metadata of a page on every page view. Page properties let you distinguish pages that share a single page identifier, so that you can analyze usage by the resource a person actually viewed. Usage Insights represents user activity as pages and events: * A page is a view that a user opens. * An event is an interaction that a user performs on that page, such as adding a comment, selecting a link, or liking an article. Opening a page generates page data. Every subsequent interaction on that page generates events. Because events occur on a page, every event now carries page properties alongside its own event properties. This is why page properties are available even when a filter condition is built on an event: the combination answers questions such as which pages a given event is being raised from. ## The problem page properties solve Many pages share one page identifier. Every knowledge article opens in the same article view, every catalog item in the same catalog view, and every dashboard in the same dashboard view. Without page properties, a page view records only that identifier, so all of those visits are indistinguishable in analytics. So, anyone analyzing the data must perform a separate lookup to learn what the article is. Page properties record the attributes that differentiate one visit from another, such as the article title, the page category, or the page owner. With those attributes available as filters, you can analyse: * How many password reset requests were submitted by people who visited the password reset catalog page? * How many comments were added to the knowledge article titled Usage Insights MCP? * Which dashboards did people visit last quarter, listed by name? Important: Support for event properties has been available since the initial release of Usage Insights. Page properties extend the same capability to pages. Minimum version required is Brazil patch 0 and Australia patch 6. ## Where page properties are available Filter bar : A Page filter has been added. Select a page, and then filter by that page's properties alongside events. Properties section : The value distribution for each page property renders as a chart, below the event property distributions and in the same format. Sessions : Page properties are available as filter fields, including when the condition is built on an event. This combination answers questions such as which pages a particular event is being raised from. Events : Page properties are available as filter fields, so that you can identify the pages that generated a given set of events. Pages menu : A dedicated page properties view shows the distributions for a single page and lets you filter that page by an individual property. Advanced filters : Select a page, and then choose its properties from the field list to build a condition. Conversion funnels : When a funnel step is set to a page, that page's properties is set to available for the step, so that drop-off is calculated for the filtered subset. For example, a step can be limited to visits where the article title is Password reset. ## How to read a page property distribution Each chart represents one property. The segments show the distinct values recorded for that property, and the legend shows the count and percentage for each value. The center of the chart shows the total number of occurrences in the selected date range. ## Default and custom properties Usage Insights captures a set of properties for each page by default, including the page identifier and selected system parameters. You can customise additional properties to retrieve more relevant data. * **[Using page properties](https://www.servicenow.com/docs/mvjU39oH3JS7TRBjHKma~A)** Filter a page detail page by one or more page properties to see how usage differs across page attributes such as owner, category, or load time.