| | | | Description/Compatibility information |
| | | | Fields marked as Favourite |
| | | | |
| | | | All the dimensions and measurements created for the survey questions added in each survey. |
| | | | Shows all types of survey questions. |
| | Q_Name is being used in place of “Question Name” | | |
| | | | Dimensions for Column, Pie type charts |
| | | | Dimension for other field |
| | | | |
| | | | |
| | Q_Name - Level 1 Category | | Dimension for Level 1 text analytics based Attribute |
| | Q_Name - Level 2 Category | | Dimension for Level 2 text analytics based Attribute |
| | | | Dimensions for Sentiment associated with the response phrases. |
| | Q_Name - Phrase Word Cloud | | Dimensions for each of the phrases identified for the text response via text analytics. This can be used for tables as well as word cloud |
| | Q_Name - Experience Score | | Experience Score is a numerical value that represents the sentiment attached to open-text responses. |
| | | | Number of phrases created for that text dimension. |
| | | Dimension (Only for Filtering) | This dimension is only available for filtering. No support for Plotting and Drilldown. This dimension has values as ”True”/”False”, it can be used to filter in or filter out “Not Answered” entries for the text question dimension plotted in a widget. |
| | | | |
| | | | Exact value of NPS response is considered, For Counter Average |
| | | | Values are stored as strings and are treated as options of an MCQ, For Column Chart |
| | | | This is a value ranging from -100 to 100, calculated as ((Number of promoters - Number of detractors)/Survey response count) |
| | | | Dimension for NPS groups (Promoter, Detractor, Passive) |
| | | | |
| | | | Computes the response-level average by averaging all statement values within a single response. This yields one overall score per response, not per statement. |
| | | | Values are stored as strings and are treated as options of an MCQ, For Column Chart |
| | Q_Name - Statement_Name - CSAT Score | | This is a value ranging from -100 to 100, calculated as ((Number of 4,5)/Survey response count). This is calculated for all statements. |
| | Q_Name - Statement_Name - Rank | | Exact value of each statement added for Multi line CSAT question response is considered, For Counter Average |
| | | | Display names of the statements added in the multi-statement question. |
| | | | Options available for respondents for that particular multi-statement question. |
| | Q_Name - Statements - Rank | | Computes the statement-level average by taking the average of each statement’s value across all responses. This reflects the true aggregated score for each individual statement.
Only compatible with the same question’s “Statements” dimension. |
| | | | |
| | | | Exact numeric value of Slider response is considered. In case of multi statement Slider this measurement would give the overall average of all statements. For widgets like Counter Average |
| | | | Values are stored as strings and are treated as options of an MCQ, For Column Chart |
| | Q_Name - Statement_Name - Rank | | Exact value of each statement added for Multi line Slider question response is considered, For Counter Average |
| | | | Display names of the statements added in the multi-statement question. |
| | Q_Name - Statements - Rank | | Computes the statement-level average by taking the average of each statement’s value across all responses. This reflects the true aggregated score for each individual statement. Only compatible with the same question’s “Statements” dimension. |
| | | | |
| | | | Exact numeric value of rating response is considered. In case of multi statement rating this measurement would give the overall average of all statements. For widgets like Counter Average |
| | | | Values are stored as strings and are treated as options of an MCQ, For Column Chart |
| | Q_Name - Statement_Name - Rank | | Exact value of each statement added for Multi line Slider question response is considered, For Counter Average |
| | | | Display names of the statements added in the multi-statement question. |
| | | | Options available for respondents for that particular multi-statement question. |
| | Q_Name - Statements - Rank | | Computes the statement-level average by taking the average of each statement’s value across all responses. This reflects the true aggregated score for each individual statement. Only compatible with the same question’s “Statements” dimension. |
| | | | |
| | | | |
| | | | This measurement stores the ranks assigned to each option added in the Rank order question for each response. For plotting in counter type widgets. |
| | | | This dimensions stores the values of all unique options of the rank order question. |
| | | | This dimensions stores the ranks assigned to each option added in the Rank order question for each response. Allowing user to plot in pie, column and table type widget. |
| | | | Note: Always use Rank and Option together for rank order result analysis. |
| | | | |
| | | | Exact numeric value of matrix response is considered. In case of multi statement matrix this measurement would give the overall average of all statements. For widgets like Counter Average |
| | | | Values are stored as strings and are treated as options of an MCQ, For Column Chart |
| | | | Display names of the statements added in the multi-statement question. |
| | | | Options available for respondents for that particular multi-statement question. |
| | | | |
| | | | |
| | Q_Name - Transcript - Level 1 Category | | Dimension for Level 1 text analytics based Attribute |
| | Q_Name - Transcript - Level 2 Category | | Dimension for Level 2 text analytics based Attribute |
| | Q_Name - Transcript - Sentiment | | Dimensions for Sentiment associated with the response phrases. |
| | Q_Name - Transcript - Phrase Word Cloud | | Dimensions for each of the phrases identified for the text response via text analytics. This can be used for tables as well as word cloud. |
| | Q_Name - Transcript - Experience Score | | Experience Score is a numerical value that represents the sentiment attached to open-text responses. |
| | Q_Name - Transcript - Insights Count | | Number of phrases created for that text dimension. |
| | | Dimension (Only for Filtering) | This dimension is only available for filtering. No support for Plotting and Drilldown. This dimension has values as ”True”/”False”, it can be used to filter in or filter out “Not Answered” entries for the text question dimension plotted in a widget. |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | Standard fields survey metadata saved automatically with each response. |
| | | | |
| | | | |
| | | | Total count of responses. |
| | | | Distribution channel used for sending out invites. |
| | | | Name or title given to the specific distribution. |
| | | | The survey type used for filling the survey. |
| | | | Status of Response with possible values as Completed, Partially Completed. |
| | | | Sprinklr users who have access to the response. |
| | | | Name of connector used for ingesting the response. |
| | | | Indicates the date timestamp when the survey was responded by the customer |
| | | | Indicates the date timestamp when the survey was responded by the customer with aggregation support. |
| | | | Unique identifier of the response saved within Sprinklr. |
| | | | The language in which the survey was filled by the respondent. |
| | | | The name of the calendar month based on the response time/sent time such as January, February and so on. |
| | | | The name of the day of the week based on the response time/sent time such as Monday, Tuesday and so on. |
| | | | The hour of the day based on the response time/sent time such as 01:00, 03:00 etc (based on 24h clock format and time zone). |
| | | | Indicates the date timestamp when the survey was sent to the customer |
| | | | Indicates the date when the survey was sent to the customer. |
| | | | |
| | | | Survey Agnostic Text Analytics fields are compatible with standard survey fields as well custom fields. |
| | Survey Response Insights - Phrase Sentiment | | Phrase level sentiment predicted by the Sprinklr PI Model. |
| | Survey Response Insights - Level 1 Category | | Broad product attributes identified by custom machine learning model. Level 1 categories have multiple level 2 categories under it. |
| | Survey Response Insights - Level 2 Category | | Moderately granular product attributes identified by custom machine learning model. |
| | | | Survey Response Insights Count |
| | | | |
| | | | Overall response quality assigned to the response. |
| | | | Overall response quality score assigned to the response. |
| | | | Total count of Bot responses. |
| | High quality response count | | Total count of High responses. |
| | Medium quality response count | | Total count of Medium responses. |
| | Low quality response count | | Total count of Low responses. |
| | | | Time taken by the respondent for filling the survey. With possible values as Very Fast, Very Slow. |
| | | | Overall response quality score assigned to the open text response. |
| | | | Overall response quality score assigned for logicall correctness of the response. |
| | | | |
| | All fields Fetched via IP | | Saved while receiving response. |
| | | | |
| | List of Response Custom Fields | | |
| | | | |
| | | | Full name of the respondent. |
| | | | First name of the respondent. |
| | | | Last name of the respondent. |
| | | | Email Id of the respondent. |
| | | | Phone Number of the respondent. |
| | | | Primary contact information of the respondent. |
| | | | |
| | List of Profile Custom Fields | | |
| | | | |
| | | | |
| | | | Unique identifier of the transaction created within a transaction group. |
| | | | User ID associated to a transaction created within a transaction group. |
| | | | Name of the transaction group. |
| | | | Type of Transaction group, with possible values as Workflows, Manual. |
| | | | |
| | List of Transaction Custom Fields | | |
| | | | |
| | | | Only compatible with Transaction custom fields apart from the fields present in the same bucket. |
| | | | Unique identifier of the transaction created within a transaction group. |
| | | | User ID associated to a transaction created within a transaction group. |
| | | | Name of the transaction group. |
| | | | Type of Transaction group, with possible values as Workflows, Manual. |
| | | | Total count of transaction created. |
| | | | |
| | | | Hierarchy fields linked to different hierarchies. |
| | | | User fields linked to different hierarchies at different levels. |
| | | | |
| | | | Response Case rule automation-based cases data can be accessed through this bucket. |
| | | | Case generated within Surveys. It will include the subject, ID and description. |
| | | | Unique identifier of the case within Sprinklr. |
| | First Response Time (Response Case) | | Time taken to send the first message to the respondent after case creation. |
| | Response Case Triggered Count | | Number of cases created via case rule. |
| | Response Case Escalated Count | | Number of cases escalated. |
| | | | Current status of the case. |
| | Response Case Creation Time | | Time stamp when the case was created. |
| | Response Case Closed Count | | |
| | | | Time stamp when the case was closed. |
| | Number of Interaction (Response Case) | | Number of engagements between case assignee and respondent. |
| | Resolution Time (Response Case) | | Time taken to resolve the case, calculated from creation to closure. |
| | | | Platform user to whom the case is assigned. |
| | | | Shows the date when the case was closed. |
| | Response Case Creation Date | | Shows the date when the case was created. |
| | | | Due time for the case, calculated as: Created Time + Rule Escalation Time. |
| | Response Case Escalated time | | The Duration for which the case remained escalated before closure. |
| | Response Case Escalation Assignee | | Platform user to which the case would be re-assigned when escalated. |
| | Response Case closed within SLA count | | Number of cases closed before escalation. |
| | | | |
| Response Case Rule Fields | | | Assignment method associated to the case rule. |
| | | | Escalation criteria associated to the case rule. |
| | | | Escalation method associated to the case rule. |
| | | | Name of case rule associated to the case. |
| | | | Time (in minutes) after which the case is supposed to be escalated, as defined in the escalation policy. |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | Distribution cases, i.e the cases on which the survey was distributed. |
| | | | |
| | | | Case generated within Surveys. It will include the subject, ID and description. |
| | | | Platform user to whom the case is assigned. |
| | | | Count of messages associated with the case (include fan, and brand message both). |
| | | | Count of messages associated with the case (include fan, and brand message both). |
| | | | The Histogram with the date when the case was marked close. |
| | | | Duration of the case - (Time difference between the first message of the case and the last message of the case). |
| | | | The timestamp with the date when the case was marked close. |
| | | | |
| | | | The time the case was created. This is a histogram dimension and can be used when we want to see cases at daily/weekly etc level. |
| | | | Time stamp when the case was created. |
| | | | Measures the time difference between first fan message and first brand response. If SLA preset is applied, this metric will give time based on working hours. |
| | | | Unique identifier of the case within Sprinklr. |
| | | | Current status of the case. |
| | | | This shows the summary of the case entered while case creation. |
| | | | Indicates whether the case is being managed by the Sprinklr case module or a third party CRM (when an integration is enabled). |
| | | | Number of engagements between case assignee and respondent. |
| | | | |
| | | | |
| | List of fields originated from datasets | | List of fields originated from datasets |
| | | | |
| | | | |
| | Custom Metrics created in CFM analytics | | Custom Metrics created in CFM analytics |
| | Custom Metrics created in CFM surveys. | | Custom Metrics created in CFM surveys. |
| | | | |
| | | | |
| | | | Only compatible with the fields in this sub-bucket. |
| | | | Name or title given to the specific distribution. |
| | | | Sprinklr user who created the distribution. |
| | | | Date time stamp of when the distribution was created. |
| | | | Number of distributions grouped by their current status (e.g., Active, Scheduled, Expired). |
| | Distribution Schedule Type | | Distribution Schedule type with possible values as Scheduled, Trigger Based, Instantly Sent |
| | | | Distribution channel used for sending out invites. |
| | | | Data time stamp of when the distribution link would expire. |
| | | | Type of expiry configured for the distribution with possible values as Static, Dynamic. |
| | Potential Recipient Count | | Total recipients available for the survey, including unsubscribed/quarantined contacts. (Excludes duplicates) |
| | | | Number of valid recipients after removing unsubscribed, quarantined, or invalid entries. |
| | Creatives Triggered Count | | Number of times the survey creative (popup/button) was triggered. |
| | | | Total number of invites successfully sent to recipients. |
| | | | Number of invites that failed due to invalid addresses, blocked domains, or technical errors. |
| | | | Total number of invites links generated for distribution. |
| | | | Total number of invites opened by respondents. |
| | | | % of recipients who opened the invite. Formula: (Invites Opened Count / Invite Sent Count) |
| | | | Recipients who opted out from receiving future surveys. |
| | | | Number of recipients who received the survey (mainly in social distributions). |
| | | | Recipients who clicked and opened the survey page. |
| | | | % of recipients who opened the survey after receiving the invite. Formula: (Survey Opened Count / Invites Generated Count) |
| | | | Number of users who began answering the survey after opening it. |
| | | | % of users who started the survey after opening it. Formula: (Survey Started Count / Survey Opened Count) |
| | | | % of users who completed the survey after starting it. Formula: (Response Count / Survey Started Count) |
| | | | % of users who started but didn’t complete the survey. Formula: (1 – Survey Completion Rate) |
| | | | % of recipients who responded out of those who received an invite. Formula: (Response Count / Invite Sent Count OR Invites Generated Count OR Reach Count) |
| | | | Count of distributions that are currently set up. |
| | | | Count of responses received for the survey |
| | | | |
| | | | |
| | | | |
| Invite Performance Metrics | | | Only compatible with Transaction, Response , Profile and Case fields |
| | | | Total number of invites successfully sent to recipients. |
| | | | Number of invites that failed due to invalid addresses, blocked domains, or technical errors. |
| | | | Total number of invites links generated for distribution. |
| | | | Total number of invites opened by respondents. |
| | | | % of recipients who opened the invite. Formula: (Invites Opened Count / Invite Sent Count) |
| | | | Recipients who opted out from receiving future surveys. |
| | | | Recipients who clicked and opened the survey page. |
| | | | % of recipients who opened the survey after receiving the invite. Formula: (Survey Opened Count / Invites Generated Count) |
| | | | Number of users who began answering the survey after opening it. |
| | | | % of users who started the survey after opening it. Formula: (Survey Started Count / Survey Opened Count) |
| | | | % of users who completed the survey after starting it. Formula: (Response Count / Survey Started Count) |
| | | | % of users who started but didn’t complete the survey. Formula: (1 – Survey Completion Rate) |
| | | | % of recipients who responded out of those who received an invite. Formula: (Response Count / Invite Sent Count OR Invites Generated Count OR Reach Count) |
| | | | Count of responses received for the survey |
| | | | Indicates the date timestamp when the survey was sent to the customer |
| | | | Indicates the date when the survey was sent to the customer. |
| | | | |
| | | | The channel used to trigger the Intercept for the distribution. |
| | | | Name or title given to the specific distribution for which the intercept activity is being processed. |
| | Intercept Abandoned Count | | Number of times the intercept was closed or dismissed by any user. |
| | Intercept Abandonment Rate | | Percentage of intercepts abandoned out of total intercept triggered. |
| | | | The time at which the Intercept is shown to the customer. |
| | | | Number of times an intercept was completed. |
| | | | Percentage of intercepts completed out of total intercept triggered. |
| | | | The name of the creative triggered for a recipient. |
| | | | The type of the creative triggered for a recipient. |
| | | | Number of times any user who engages with intercept to open the survey. |
| | | | The user profile that engaged with the intercept. |
| | Intercept Engagement Rate | | Percentage of intercepts engaged out of total intercept triggered. |
| | | | The Sprinklr ID for the Intercept. |
| | Intercept Live Chat Application Name | | The live chat application associated with the Intercept. |
| | | | The specific webpage where the intercept was triggered or interacted with. |
| | Intercept Triggered Count | | Number of times an intercept was shown to the recipient. |
| | | | |
| | | | |