# Columns/Data Dictionary

On demand reports contain the following data:

<table><thead><tr><th>Data</th><th width="272.3333333333333">Definition</th><th>Sheet</th></tr></thead><tbody><tr><td>Survey Name</td><td>The name of the survey included in the report.</td><td>Survey Metadata</td></tr><tr><td>Author</td><td>Name of the user that generated the report.</td><td>Survey Metadata</td></tr><tr><td>Reporting Dates</td><td>The date range included in the report.</td><td>Survey Metadata</td></tr><tr><td>Report Generated</td><td>Date when the report was generated.</td><td>Survey Metadata</td></tr><tr><td>Date</td><td>Date of activity.</td><td>Aggregate Results by Day</td></tr><tr><td>Impressions</td><td>Number of times the survey was returned to be displayed on a page.<br><br>Impressions are used in the aggregate Submission Rate if viewed impressions are NOT enabled for the entirety of the report date range.</td><td>Aggregate Results by Day</td></tr><tr><td><p>Viewed Impressions </p><p><em>(if feature is enabled)</em></p></td><td>Number of times a survey was returned and seen by a user.<br><br>Viewed Impressions are used in the aggregate Submission Rate calculation if enabled for the entire report date range.</td><td>Aggregate Results by Day</td></tr><tr><td><p>Blended Impressions </p><p><em>(if Viewed Impressions are enabled for a portion, but not all of the date range)</em></p></td><td><p>Blended impressions combine regular and viewed impressions for a date range when the Viewed Impression feature was not enabled for the entirety of that range. </p><p></p><p>The "Blended" total is used in the aggregate Submission Rate calculation for the date range.</p></td><td>Aggregate Results by Day</td></tr><tr><td>Submissions</td><td>Number of times at least one question from the survey was answered</td><td>Aggregate Results by Day</td></tr><tr><td>Submission Rate</td><td><ul><li><strong>submissions/impressions</strong> <em>(if viewed impressions are not enabled for report date range)</em></li><li><strong>submissions/viewed impressions</strong> <br><em>(if enabled for full report date range)</em></li><li><strong>submissions/blended impressions</strong> <br><em>(if viewed impressions are enabled for only part of the report date range)</em></li></ul></td><td>Aggregate Results by Day</td></tr><tr><td>Questions &#x26; Possible Answers</td><td>Question and response text that is displayed to the user.</td><td>Questions </td></tr><tr><td>Responses</td><td>The number of submissions per question and per response.</td><td>Questions</td></tr><tr><td>Share</td><td>The percentage (or share) that a particular response has in comparison to total responses.</td><td>Questions</td></tr><tr><td>Date</td><td>Date of submission.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Time</td><td>Time of submission.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td><p>Survey Group Name </p><p>(<em>only applies to surveys in a Survey Group)</em></p></td><td>The name given to the group of surveys.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Survey Name</td><td>The name given to the sets of questions. The name given to the Survey ID.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Question</td><td>Question text that is displayed to the user.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Response</td><td>Text version of the user response.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td><p>Question Base </p><p><em>(only applies to surveys in a Survey Group)</em></p></td><td>The base value/short hand name given for the question for survey groups.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td><p>Response Base </p><p><em>(only applies to surveys in a Survey Group)</em></p></td><td>The base value/short hand name given for the response for survey groups.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Translated Free Text Response</td><td>The English translation of a user's open ended feedback.</td><td>Individual Rows</td></tr><tr><td>Tags</td><td>Relevant to Open-Ended responses, and manually created by users in Pulse Insights reporting page</td><td>Individual Rows</td></tr><tr><td><p>Language Code </p><p><em>(only applies to surveys in a Survey Group)</em></p></td><td>The language code applied to a localized survey. </td><td>Individual Rows</td></tr><tr><td><p>Locale Code </p><p><em>(only applies to surveys in a Survey Group)</em></p></td><td>The locale code applied to a localized survey.</td><td>Individual Rows</td></tr><tr><td>Survey Group ID<br><em>(only applies to surveys in a Survey Group)</em></td><td>ID representing the sets of surveys grouped in a survey group. </td><td>Individual Rows<br>Devices</td></tr><tr><td>Response Group ID<br><em>(only applies to surveys in a Survey Group)</em></td><td>ID represents each user response.</td><td>Individual Rows<br>Devices</td></tr><tr><td>Next Question Group ID<br><em>(only applies to surveys in a Survey Group)</em></td><td>If surveys have multiple questions, this represents the ID of the question group that could be shown next. </td><td>Individual Rows</td></tr><tr><td>Survey ID</td><td>Sets of questions are grouped in each survey. This survey ID represents the survey</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Question ID</td><td>ID representing each question that is being displayed.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Response ID</td><td>ID represents each user response</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Next Question ID</td><td>If surveys have multiple questions, this represents next question that could be shown. </td><td>Individual Rows</td></tr><tr><td>Pageview Count</td><td>Number of pages viewed by the user.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Visit Count</td><td>Number of visits.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>IP Address</td><td>The IP Address of the user. </td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Device Type</td><td>Device type that is assigned by Pulse Insights (e.g. desktop, mobile, tablet).</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Device UDID</td><td>ID assigned to each user based on the device they used. This is assigned by Pulse Insights</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Client Key</td><td>A persistent, anonymous, and unique User ID that you assign to a user. The value is typically passed to Pulse Insights upon an authentication event and used to tie a response back to an individual or to tie multiple devices/browers together. See <a href="../../../implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/client-key">Client Key</a> for more details.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Completion URL</td><td>URL that the survey was taken on if web. Native mobile, API/email responses, and Dynamic Email responses don’t include this value.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>View Name</td><td>For native mobile/SDK-based responses, the View Name is the equivalent of a Page or Screen name in web-based apps. It is defined by the app developers and typically the same value that gets passed to SDK-based analytics packages as the Page Name.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Event</td><td>Optional value that tells Pulse Insights what occurred to trigger a survey. It is captured via <code>pi('present', 'alias');</code><br><br>Please refer <a href="../../../../implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/presenting-a-specific-survey#by-using-a-present-alias">here</a> for more details on presenting specific surveys. </td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Context Data</td><td>Context Data is meant to provide additional details about the user’s current context that typically isn’t immediately observable from the page or screen itself. For example, the category of product the user is viewing or the variant of an A/B test that a user was sorted into. It is explicitly passed to Pulse Insights via JavaScript or API methods during implementation.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Device Data</td><td>Device Data is meant to provide additional details about the device (which is often a proxy for the user) that persist across multiple pageviews and sessions. For example, a customer’s loyalty/membership tier, internal model segmentation value or score, or Persistent IDs from other services work well as device data. Device data is expected to change infrequently (since it describes the customer/device, not the current context). Device Data is explicitly passed to Pulse Insights via JavaScript or API methods during implementation.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Previous Surveys</td><td>null of 0 if user is taking survey for the first time, if not count of surveys previously taken</td><td>Individual Rows</td></tr><tr><td>Sentiment Score</td><td>The result of Google’s NLP API for open-ended/free text responses. Score ranges between -1.0 (negative) and 1.0 (positive) and corresponds to the overall emotional leaning of the text</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Sentiment Magnitude</td><td>The result of Google’s NLP API for open-ended/free text responses. Magnitude indicates the overall strength of emotion (both positive and negative) within the given text, between 0.0 and +inf. Unlike score, magnitude is not normalized; each expression of emotion within the text (both positive and negative) contributes to the text's magnitude (so longer text blocks may have greater magnitudes).</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Entity</td><td>The result of Google’s NLP API for open-ended/free text responses. Entity Analysis inspects the given text for known entities (proper nouns such as public figures, landmarks, etc.), and returns information about those entities</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>OS</td><td>The operating system the user was using when responding to the survey. </td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Browser</td><td>The browser the user was using when responding to the survey.</td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Browser Version</td><td>The version of the browser the user was using when responding to the survey. </td><td><p>Individual Rows</p><p>Devices</p></td></tr><tr><td>Channel</td><td><p>Mapped based on the type of response: Web/Browser, Mobile SDK, Direct Submission API/Link, or Dynamic Email. </p><p></p><p><em>Note that traditional email survey responses use Direct Submissions (Links), so appears in reporting as such while Dynamic Email utilities its own API to classify it as such.</em> </p></td><td><p>Individual Rows</p><p>Devices</p></td></tr></tbody></table>