---
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


---

# Usage Insights client-side storage cookies

# Usage Insights client-side storage cookies {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Usage Insights client-side storage cookies

Usage Insights leverages the SNAnalytics JavaScript SDK embedded in Platform Analytics, Core UI, and Service Portal to track client-side user activity.
This tracking uses browser session storage and local storage to collect and manage analytics data essential for monitoring user interactions and consent.
Show full answer Show less  

## Session Storage

Session storage maintains transient data during the lifespan of a browser tab, facilitating information flow across page refreshes and navigations. Key session storage variables include:

* **srt**: Timestamp of the last successful server communication.
* **data**: Queue of temporarily stored analytics data points awaiting backend transmission.
* **page**: Automatically captured current page name.
* **tab**: Unique identifier for the current browser tab.

Note: Session storage data is cleared when the tab is closed.

## Local Storage

Local storage retains persistent tracking information across sessions, including consent status, user identification, and browser identifiers. Key local storage variables include:

* **browser**: Unique identifier for the browser instance.
* **client**: Server-assigned ID linked to the browser identifier.
* **user**: Hashed user ID provided by the customer.
* **consent**: Boolean indicating user consent for tracking.
* **config**: Application-level configuration settings that persist after logout.

To remove local storage data, customers must clear their browser's cookies and site data.

## Data Storage and Security

Collected analytics data is encrypted at rest and stored in a centralized, multi-tenant ServiceNow repository geographically aligned with the instance region (Canada, Germany, or Japan). Data is anonymized prior to storage and automatically deleted after a two-year retention period.

## Key Structure

All client-side storage keys follow the format **sn:{APIKEY}:{KEY NAME}**, where each portal's unique API key segments data appropriately for that portal's tracking.  
To track client-side user activity, Usage Insights uses the SNAnalytics JavaScript SDK that is embedded in Platform Analytics, Core UI, and the Service Portal.
The SNAnalytics SDK uses a combination of session storage and local storage variables to track the information required to facilitate the analytics tracking.

For more information on session storage and local storage, refer to the [JavaScript.Info](https://javascript.info/localstorage) documentation.

For more information on SNAnalytics SDK, see [SNAnalytics - Client](https://www.servicenow.com/docs/access?context=SNAnalyticsClientAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US)  and [SNAnalytics ](https://developer.servicenow.com/dev.do#!/reference/api/xanadu/client/SNAnalyticsClientAPI)-- in the Developer community.

## Key structure {#uxa-tracked-client-cookies__section_nzy_fwb_gyb}

All locally stored keys are stored using the following structure: `sn:{API_KEY}:{KEY NAME}`

Each tracked portal has a unique API_KEY that is stored on the instance. For example, for the portal with an API key `abcd` and a key name `tab`, the local key value would be:
`sn:abc:tab`

## Session storage {#uxa-tracked-client-cookies__section_jtk_3wb_gyb}

Session storage is used to maintain the flow of information between web page refreshes and user navigations. Information in session storage is transient and kept available only during the lifespan of the current tab. When a tab is
closed, the session storage information is removed.  
The table lists the keys and values stored on session storage.{#uxa-tracked-client-cookies__table_fvp_mwb_gyb__entry__2}

| Key | Description |
|-|-|
| srt | Server Response Time. The last time SNAnalytics successfully communicated with the Usage Insights server. |
| data | Queue of temporary stored analytics data points, which is periodically flushed to the backend. |
| page | The name of the current page, automatically captured by the Usage Insights server. |
| tab | Randomly generated unique identifier for the current tab. |
[ ]

{#uxa-tracked-client-cookies__table_fvp_mwb_gyb}

## Local storage {#uxa-tracked-client-cookies__section_rfv_pwb_gyb}

Local storage is used to maintain tracking consent information, hashed identification of the user (which is cleared when consent is revoked), and randomly generated identifiers for the browser. Local storage variables are
persistent locally and are deleted when you clear your browsing data.  
The table lists the keys and values stored on local storage.{#uxa-tracked-client-cookies__table_bnp_5wb_gyb__entry__2}

| Key | Description |
|-|-|
| browser | Randomly generated unique identifier for the current browser. |
| client | The server assigned ID mapped to the browser key value. |
| user | Hashed user id, supplied by the customer. |
| consent | A Boolean (yes/no) value that indicates whether the user consents to be tracked. |
| config | A persistent key that remains in local storage after you log out of on an instance. Stores non-sensitive application-level configuration settings used to support consistent app behavior across sessions. |
[ ]

{#uxa-tracked-client-cookies__table_bnp_5wb_gyb}

## Deleting local storage {#uxa-tracked-client-cookies__section_erb_xwb_gyb}

To delete local storage variables, you must clear the browsing data. For example, in the Chrome browser, select HistoryShow Full HistoryClear browsing data. In the Clear browsing data window, select Cookies and other site data and then select Clear data.  

## Data storage {#uxa-tracked-client-cookies__uxa_data_storage}

Data is encrypted at rest. It's stored in a central ServiceNow® multitenant repository closest to the instance's region, in either AMS (Canada), EMEA (Germany), or APAC (Japan).

Data is anonymized before it's sent to storage, and deleted at the database level
after a retention period of two years.

*[\>]: and then