# Data that Pulse Insights stores Pulse Insights evaluates & stores data from your end-users to perform its core functions of: * Determining if and how a survey should be served * Capturing explicit user responses to survey questions * Analyzing the responses to generate insights for your business * Performing QA of data and user experience ## The following is a list of data that Pulse Insights stores along with how it is used. | Data | How it is used | Comments | | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **DEVICE-RELATED** | | | | Device UDID | Random identifier assigned to the device used as key to store impressions and submissions | | | User Agent | Analysis and QA of survey data by device characteristics such as mobile vs. desktop responses. | | | Operating System | Inferred from user agent | | | Browser & version | Inferred from user agent | | | Screen Resolution | Analysis and QA of survey data | | | Device Type | Inferred from screen resolution | | | IP Address | QA of survey data such as potential bot or testing traffic | This field is an account-level option with settings to turn off, obfuscate the last octet, or store the full IP address. | | | | | | **USAGE-RELATED** | | | | Submission URL | Targeting and analysis such as 'serve only on X URL' or 'compare user satisfaction by URL' | | | Number of visits | Targeting and analysis | | | Number of pageviews in current session | Targeting and analysis | | | | | | | **DATA YOU MAY OPTIONALLY EXPLICITLY PASS TO PULSE INSIGHTS TO STORE** | | | | Client Key | Used to store a persistent anonymous (to Pulse Insights) identifier to link survey data with your internal user data | | | Contextual Data | Used to store contextual data about the user, experience, or behavior | | | Events | Used to indicate that a user did something of note such as converted, so that the event data can be correlated with survey responses. | | | | | | | **EXPLICIT RESPONSE DATA** | | | | Response details | What was served to the user and the actual explicit response such as a satisfaction score | | | Timestamp | The date and time of the response | | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/privacy-features/data-that-pulse-insights-stores.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.