| | | | 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” | | |
| | | | Dimension for other (Text type) |
| | | | Dimensions for Column, Pie type charts |
| Support for “Q_Name – Other” Dimension (Enhanced Behavior) | - The “Q_Name – Other” dimension is supported for MCQ questions with content types including Text, Numeric, Email, Phone Number, and Postal Code.
- This dimension supports filtering, plotting, and drill-down analysis, similar to other MCQ dimensions.
Aggregation behavior based on content type: - Numeric, Email, and Phone Number values are aggregated (for example, summed) when used in visualizations.
- Text and Postal Code values are displayed at the individual response level and are not aggregated.
| | |
| | | | |
| | | | |
| | 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. |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | 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. |
| | | | The time at which the user respond in the survey. |
| | | | 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. |
| | | | The specific page where the intercept was triggered or interacted with. |
| | | | The name of the creative trigerred for a recipient. |
| | | | The type of the creative trigerred for a recipient. |
| | | | The user profile that engaged with the user. |
| | | | The time at which the Intercept is shown to the customer |
| | | | IP address identified at the time of user interaction |
| | Live Chat Application Name | | The live chat application associated with the Distribution. |
| | | | |
| | | | 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. |
| | | | |
| | | | Case rule automation-based cases data can be accessed through this bucket. |
| | | | |
| | | | Case generated within Surveys. It will include the subject, ID and description. |
| | | | Platform user to whom the case is assigned. |
| | | | Time stamp when the case was closed. |
| | | | |
| | | | Time stamp when the case was created. |
| | | | Due time for the case, calculated as: Created Time + Rule Escalation Time. |
| | | | Number of cases escalated. |
| | | | The duration for which the case remained escalated before closure. |
| | | | Unique identifier of the case within Sprinklr. |
| | | | Current status of the case. |
| | | | Number of cases created via case rule. |
| | Case closed within SLA count | | Number of cases closed before escalation. |
| | | | Platform user to which the case would be re-assigned when escalated. |
| | | | Time taken to send the first message to the respondent after case creation. |
| | | | Number of engagements between case assignee and respondent. |
| | | | Time taken to resolve the case, calculated from creation to closure. |
| | | | |
| | | | Assignment method associated to the case rule. |
| | | | Name of case rule associated to the case. |
| | | | Escalation criteria associated to the case rule. |
| | | | Escalation method associated to the case rule. |
| | | | Time (in minutes) after which the case is supposed to be escalated, as defined in the escalation policy. |
| | | | |
| | | | |
| | | | |
| | | | |
| | 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. |
| | | | The user profile that engaged with the intercept. |
| | Intercept Trigered Count (Earlier it was creative trigerred count) | | Number of times an intercept was shown to the recipient Feedback Button: To be discussed with engineering. Popup: Numbers of times distribution was trigerred i.e. If any variant is trigerred in a distribution, it shall be considered as Distribution trigerred. |
| | Intercept Engagement Count | | Number of times the intercept was engaged by any user to open the survey. |
| | Intercept Abandoned Count | | Number of times the intercept was closed or dismissed by any user. If the user close on the Cross icon or clicks on the secondary button “Close/No etc“ rejecting the survey request |
| | Intercept Abandonment Rate | | Percentage of intercepts abandoned out of total intercept triggered. |
| | Intercept Completed Count | | Number of times an intercept was completed. |
| | | | Percentage of intercepts completed out of total intercept triggered |
| | 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 |
| | Intercept Triggered Count | | Number of times an intercept was shown to the recipient. |
| | | | Number of times any user who engages with intercept to open the survey. |
| | Intercept Abandoned Count | | Number of times the intercept was closed or dismissed by any user. |
| | Intercept Completed Count | | Number of times an intercept was completed. |
| | Intercept Abandonment Rate | | Percentage of intercepts abandoned out of total intercept triggered. |
| | | | Percentage of intercepts completed out of total intercept triggered. |
| | | | |
| 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. |
| | | | |
| | | | |
Note: You need to ensure that the dimensions used together are compatible, as combining incompatible dimensions can lead to inaccurate or misleading reports.