Session, pageload & lead

Each widget automatically creates 3 identifiers on every pass through the widget flow. These identifiers are generated automatically and are available as context values.

• Session ID (ses): This refers to the widget's session. Each widget display counts as a new session. If you unmount the widget and then reinsert it into the DOM, the session will be different. This identifier is useful for tracking the user's path within a single widget flow.

• Pageload ID (pgld): This refers to the page session. The Pageload ID is assigned each time the page loads and does not change until the page is reloaded. This identifier is helpful for tracking how the user interacts with your page. For example, if you have two widgets on the page, they will have different session IDs but the same page load ID, making it easy to track scenarios where one widget flow is completed first, followed by the second.

• Lead ID (lead): This refers to your user's identifier. The Lead ID is assigned the first time the widget is encountered (even just the display of the widget) and is saved in the user's browser under the domain name the widget shown on. If the user navigates to another page within the same domain, their Lead ID will remain the same. Note that the Lead ID does not represent an actual person, but rather a device. For instance, if the same person visits from a computer and then from a mobile phone, they will have different Lead IDs.

All these identifiers are passed to all events and collected records, and they allow you to reconstruct the full path of your user using the public API, as well as view results in the Results tab in Studio.

The uniqueness of session ID, page load ID, and lead ID is not guaranteed, but the probability of duplication is extremely low. About 2.27e+57 ids can be generated every millisecond.