SessionStorage
Definition
This document offers a comprehensive guide on how the Pulse SDK utilizes SessionStorage, detailing the types of data stored and the services that interact with this storage.
The list and porpose of each key in SessionStorage
- paa_first_navigation
- paa_tab_id
- paa_tab_opener
- paa_last_location
paa_first_navigation
The paa_first_navigation record contains data { firstNavigation, astNavigationCount, lastNavigationUrl }, and the SDK updates or sets the record each time it tries to detect an opener or trigger an event.
The paa_first_navigation record can only be set by the Pulse Tracker SDK. The SDK sets this record in two scenarios:
- When the SDK initializes on the page.
- When a navigation occurs on the page.
- When a popup event occurs.
The paa_unpublished data is used exclusively in the TabOpenerDetector.
paa_tab_id
The paa_tab_id record contains a UUID value of the tab. During initialization, the SDK checks if a paa_tab_id record already exists in session storage. If it does not, the SDK generates a new UUID and sets it as the paa_tab_id.
The paa_tab_id record can only be set by the Pulse Tracker SDK.
The paa_tab_id data is used exclusively in the TabManagerService.
paa_tab_opener
The paa_tab_opener record contains an object with values such as { id, type, url, name, group, element }. During initialization, the SDK attempts to detect the tab opener. If the opener is detected, the SDK stores the data in session storage under the paa_tab_opener key.
The paa_tab_opener record can only be set by the Pulse Tracker SDK.
The paa_tab_opener data is used exclusively in the TabOpenerDetector.
paa_last_location
The paa_last_location record contains an object with values such as { locationURL, timestamp }. During navigation or tab closing, the SDK sets the location URL and timestamp in session storage under the paa_last_location key.
The paa_last_location record can only be set by the Pulse Tracker SDK.
The paa_last_location data is used exclusively in the LocationHistoryTracker.