Columns/Data Dictionary

On demand reports contain the following data:

DataDefinitionSheet

Survey Name

The name of the survey included in the report.

Survey Metadata

Author

Name of the user that generated the report.

Survey Metadata

Reporting Dates

The date range included in the report.

Survey Metadata

Report Generated

Date when the report was generated.

Survey Metadata

Date

Date of activity.

Aggregate Results by Day

Impressions

Number of times the survey was returned to be displayed on a page. Impressions are used in the aggregate Submission Rate if viewed impressions are NOT enabled for the entirety of the report date range.

Aggregate Results by Day

Viewed Impressions

(if feature is enabled)

Number of times a survey was returned and seen by a user. Viewed Impressions are used in the aggregate Submission Rate calculation if enabled for the entire report date range.

Aggregate Results by Day

Blended Impressions

(if Viewed Impressions are enabled for a portion, but not all of the date range)

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.

The "Blended" total is used in the aggregate Submission Rate calculation for the date range.

Aggregate Results by Day

Submissions

Number of times at least one question from the survey was answered

Aggregate Results by Day

Submission Rate

  • submissions/impressions (if viewed impressions are not enabled for report date range)

  • submissions/viewed impressions (if enabled for full report date range)

  • submissions/blended impressions (if viewed impressions are enabled for only part of the report date range)

Aggregate Results by Day

Questions & Possible Answers

Question and response text that is displayed to the user.

Questions

Responses

The number of submissions per question and per response.

Questions

Share

The percentage (or share) that a particular response has in comparison to total responses.

Questions

Date

Date of submission.

Individual Rows

Devices

Time

Time of submission.

Individual Rows

Devices

Survey Group Name

(only applies to surveys in a Survey Group)

The name given to the group of surveys.

Individual Rows

Devices

Survey Name

The name given to the sets of questions. The name given to the Survey ID.

Individual Rows

Devices

Question

Question text that is displayed to the user.

Individual Rows

Devices

Response

Text version of the user response.

Individual Rows

Devices

Question Base

(only applies to surveys in a Survey Group)

The base value/short hand name given for the question for survey groups.

Individual Rows

Devices

Response Base

(only applies to surveys in a Survey Group)

The base value/short hand name given for the response for survey groups.

Individual Rows

Devices

Translated Free Text Response

The English translation of a user's open ended feedback.

Individual Rows

Tags

Relevant to Open-Ended responses, and manually created by users in Pulse Insights reporting page

Individual Rows

Language Code

(only applies to surveys in a Survey Group)

The language code applied to a localized survey.

Individual Rows

Locale Code

(only applies to surveys in a Survey Group)

The locale code applied to a localized survey.

Individual Rows

Survey Group ID (only applies to surveys in a Survey Group)

ID representing the sets of surveys grouped in a survey group.

Individual Rows Devices

Response Group ID (only applies to surveys in a Survey Group)

ID represents each user response.

Individual Rows Devices

Next Question Group ID (only applies to surveys in a Survey Group)

If surveys have multiple questions, this represents the ID of the question group that could be shown next.

Individual Rows

Survey ID

Sets of questions are grouped in each survey. This survey ID represents the survey

Individual Rows

Devices

Question ID

ID representing each question that is being displayed.

Individual Rows

Devices

Response ID

ID represents each user response

Individual Rows

Devices

Next Question ID

If surveys have multiple questions, this represents next question that could be shown.

Individual Rows

Pageview Count

Number of pages viewed by the user.

Individual Rows

Devices

Visit Count

Number of visits.

Individual Rows

Devices

IP Address

The IP Address of the user.

Individual Rows

Devices

Device Type

Device type that is assigned by Pulse Insights (e.g. desktop, mobile, tablet).

Individual Rows

Devices

Device UDID

ID assigned to each user based on the device they used. This is assigned by Pulse Insights

Individual Rows

Devices

Client Key

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 Client Key for more details.

Individual Rows

Devices

Completion URL

URL that the survey was taken on if web. Native mobile, API/email responses, and Dynamic Email responses don’t include this value.

Individual Rows

Devices

View Name

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.

Individual Rows

Devices

Event

Optional value that tells Pulse Insights what occurred to trigger a survey. It is captured via pi('present', 'alias'); Please refer here for more details on presenting specific surveys.

Individual Rows

Devices

Context Data

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.

Individual Rows

Devices

Device Data

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.

Individual Rows

Devices

Previous Surveys

null of 0 if user is taking survey for the first time, if not count of surveys previously taken

Individual Rows

Sentiment Score

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

Individual Rows

Devices

Sentiment Magnitude

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

Individual Rows

Devices

Entity

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

Individual Rows

Devices

OS

The operating system the user was using when responding to the survey.

Individual Rows

Devices

Browser

The browser the user was using when responding to the survey.

Individual Rows

Devices

Browser Version

The version of the browser the user was using when responding to the survey.

Individual Rows

Devices

Channel

Mapped based on the type of response: Web/Browser, Mobile SDK, Direct Submission API/Link, or Dynamic Email.

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.

Individual Rows

Devices

Last updated