A-fields
Reporting > Report Helpers > Fields > A-Fields
A-fields, also known as System fields, are Experience Cloud-calculated application fields that contain information about the record or the respondent's interaction with the feedback itself, such as the timestamp when a survey taker completed the survey or information about an Alert associated with record. A-fields can be used in reports, exports (unless otherwise noted), K-fields, analytic reports, conditions, and more.
Some A-fields can be updated during a survey import using Auto Importer by mapping the input (target field) to an alias for the A-field. For example, Alert close time (a_alert_date_closed) can be updated by mapping the input to the special Alert creation time (a_alert_created_timestamp) import field. See the field descriptions for details about those fields that can be updated.
These A-fields record some of the important events in the life of a record:
A-field properties
A-field properties are read-only and for information about the definition of the field.
- Usage
- Either a message saying This field is not in use, or link indicating how many times the field is reference. Click the link to see a list of the references to the field.
- Label
- Field name that identifies the field for programmatic access.
- Name
- Field name for display and reports. Restriction: Name can have a maximum of 63 characters.
- Description
- Text description of the purpose and usage of the field.
- Allowed in data API
- Whether or not the field can be queried by Query API.
- Alternative Set
- Data type (Alt Set) of the field.
- Alternatives
- Lists the valid values when the Alternative set is an Enumeration, Dynamic alt set, Javaenum, or Autoindex text.
Common A-fields
These fields are common to records:
- a_log_notes
- Survey log notes — All the log entries for the record in this format:
[yyyy-MM-dd HH:mm:ss] Title 1; [yyyy-MM-dd HH:mm:ss] Title 2: Content 2; [yyyy-MM-dd HH:mm:ss] Title 3: Content 3 (username) - a_obfuscated_surveyid
- The survey ID used internally by Experience Cloud when masked as Sensitive data, which returns a deterministic random value. For example, if survey ID is 1234, it always shows randomValue.
- a_org_hierarchy
- A JSON structure of the entire organization information for each unit field tied to the record when the survey was created. For more details about this field, including how to update it, see Org hierarchy field and Org hierarchy filtering. Note: Experience Cloud includes the similarly-named
a_org_hierarchy_by_unitfield, which is reserved by for specific customer needs. Contact your Medallia expert before using thea_org_hierarchy_by_unitfield. - a_initial_finish_timestamp
- UNIX timestamp for when the completed survey was first accepted by the reporting application. This value is version of the e_initialfinishdate (Initial finish date) field expressed as an integer value for seconds since epoch. This conversion allows developers to perform incremental pulls from Query API without needing to deal with timezone considerations. Note: "Seconds since epoch" refers to the number of seconds that have passed since the UNIX epoch, which is 00:00 UTC January 1, 1970, minus leap seconds. For more information, see https://unixtime.org/.
- a_static_report_description
- Report description — Description of the static report associated with this record (if any). It is Null when there is not associated static report.
- a_survey_export_*
- Survey export fields describe individual export sessions. For more information, see Monitoring survey exports.
-
a_survey_export_start_date -
a_survey_export_end_date -
a_survey_export_name -
a_survey_export_exported_kbytes -
a_survey_export_exported_records -
a_survey_export_requester -
a_survey_export_requester_details -
a_survey_export_exported_via -
a_survey_export_status -
a_survey_export_retry_seq_number
-
- a_survey_status_display
- Returns the Survey status (e_status) reformatted to replace the underscores '_' with spaces ' '. For example, "AUTO_EXCLUDED" displays as "AUTO EXCLUDED".
- a_survey_type
- Survey type — Type of information stored in the record. For more information, see
e_survey_typeE-field. - a_surveyid
- Internal survey ID — The survey ID used internally by Experience Cloud.Important: Beginning with the Winter 2020 release, the length of Survey IDs is increased to 64 bits (values can be greater than 2 billion). Make sure that your application can handle these values for Survey ID fields. Consider storing these values as text or as a big integer (signed 2's-compliment 64-bit integer).
- a_unit_name
- The name of the unit. May be the ID of the unit when the name has not been set.
- a_unit_identifier
- The ID of the unit.
Action Plans
These fields track information about Action plans:
- a_action_plan_attachments_yn
- Whether or not the Action plan includes attachments.
- a_action_plan_creation_date
- Timestamp when the Action plan is created.
- a_action_plan_creator
- ID of the user who created the Action plan.
- a_action_plan_creator_name
- Name of the user who created the Action plan.
- a_action_plan_description
- Description of the Action plan.
You cannot use this field for filtering.
- a_action_plan_drivers
- List of Action plan Drivers.
- a_action_plan_drivers_alts
- List of Alternative sets for Drivers.
- a_action_plan_id
- ID of the Action plan.
- a_action_plan_impact_analysis_baseline_date
- Timestamp the Baseline period begins for Impact analysis.
- a_action_plan_impact_analysis_control_group_name
- Control group name used in Impact analysis.
You cannot use this field for filtering.
- a_action_plan_impact_analysis_end_test_date
- Timestamp the Test period begins for Impact analysis.
- a_action_plan_impact_analysis_impact_group_name
- Impact group name used in Impact analysis.
You cannot use this field for filtering.
- a_action_plan_impact_analysis_metrics
- List of Action plan Metrics.
- a_action_plan_impact_analysis_metrics_alts
- List of Choice sets for Action plan Metrics.
- a_action_plan_impact_analysis_setup_date
- Date and time the Setup period begins for Impact analysis.
- a_action_plan_impact_analysis_start_date
- Date and time the Test period begins for Impact analysis.
- a_action_plan_impact_analysis_yn
- Whether or not the Action plan has attachments.
- a_action_plan_name
- Name of the Action plan.
You cannot use this field for filtering.
- a_action_plan_owner
- ID of the user who owns the Action plan.
- a_action_plan_owner_name
- Name of the user who owns the Action plan.
- a_action_plan_status
- Status of the Action plan, which can be: Approved same as Not Started in reporting, In progress, Completed, or Canceled.
- a_action_plan_suggested_actions
- List of the Action plan Suggested actions.
- a_action_plan_suggestedactions_alts
- List of Choice sets for Action plans Suggested actions.
- a_action_plan_survey_ids
- Survey IDs set in the Action plan.
You cannot use this field for filtering.
- a_action_plan_task_assignee
- Multi-valued field that stores the assignees of all the Tasks.
- a_action_plan_task_assignee_name
- Name of task assignees.
- a_action_plan_task_completion_date
- Multi-valued field that stores the completion date of all Tasks.
- a_action_plan_task_description
- Description of an Action plan Task.
You cannot use this field for filtering.
- a_action_plan_task_due_date
- Multi-valued field that stores the due date of all Tasks.
- a_action_plan_task_name
- Multi-valued field that stores all the names of Tasks.
You cannot use this field for filtering.
- a_action_plan_task_status
- Multi-valued field that stores the status of all Tasks. Statuses can be Not started, In progress, or Completed.
- a_action_plan_themes
- List of Action plan Themes.
- a_action_plan_themes_alts
- List of Choice sets for Themes.
- a_action_plan_topics
- List of Action plan Topics.
- a_action_plan_topics_alts
- List of Choice sets for Topics.
- a_action_plan_update_date
- Date and time when the Action plan was updated.
Alerts and Rapid responses
These fields track information about Alerts:
- a_alert_assigned_to_groups
- Alert assigned to groups — The names of all the Unit groups (Alert assignees) that have been, and currently are, assigned to the associated Alert instance. Similar to
a_alert_assigned_to_names. - a_alert_assigned_to_minutes
- Alert assigned to minutes — The total number of minutes each group in
a_alert_assigned_to_nameswas assigned the alert.Note: The last assignee is not included until the alert is closed. - a_alert_assigned_to_names
- Alert assigned to names — All users that have been assigned to the associated alert instance.
- a_alert_business_days_excluded_time
- Alert business-days excluded-time — Length of time (milliseconds) this alert has skipped status changes due to business days, as of the last status change.
- a_alert_closed_by
- Alert closed by — List of users who closed the alert (more than one if the alert was re-opened).
- a_alert_date_created
- Alert creation time — Timestamp when the alert instance was created.
This field can be updated during a survey import by mapping the new value to the Alert Creation Time (
alert_created_timestamp) special import field. - a_alert_date_closed
- Alert close time — Timestamp when the alert instance was closed.
This field can be updated during a survey import by mapping the new value to the Alert Closed Time (
alert_closed_timestamp) special import field. - a_alert_date_resolved
- Alert resolved time — Timestamp when the alert instance was closed.
This field can be updated during a survey import by mapping the new value to the Alert Resolution Time (
alert_resolved_timestamp) special import field. - a_alert_date_status_changed
- Alert status changed time — Timestamp when the alert status last changed. Any alert assignment also updates this field.
- a_alert_desc
- Alert description — Description of the Alert (as defined on the Alert type settings screen).
- a_alert_ever_escalated
- Alert ever escalated — Whether or not the alert instance has ever been in the Escalated state.
This field can be updated during a survey import by mapping the new value to the Alert Ever Escalated (
alert_ever_escalated) special import field. - a_alert_ever_escalated2
- Alert ever escalated 2 — Whether or not the alert instance has ever been in the Escalated 2 state.
This field can be updated during a survey import by mapping the new value to the Alert Ever Escalated2 (
alert_ever_escalated2) special import field. - a_alert_ever_overdue
- Alert ever in overdue — Whether or not the alert instance has ever been in the Overdue state.
This field can be updated during a survey import by mapping the new value to the Alert Ever Overdue (
alert_ever_overdue) special import field. - a_alert_num_reopened
- Alert reopen count — Count of times the alert instance was reopened.
- a_alert_owner
- Alert owner — Name of the owner of the alert instance, either the First and Last name of the owner, or the name of the alert assignee. This field is populated after a user is assigned to the alert.
- a_alert_owner_id
-
Important: This field is obsolete.
- a_alert_status
- Alert current status — Current status of the alert instance.
This field automatically includes all translated values. If there is any conditioning that relies on this field, it fails if the translated version of the field is used. For example, if there is a condition
a_alert_status = Closed, and a survey is Closed in reporting while the user is in the Spanish language, the condition fails because the field is not Closed and will instead say Cerrado.To condition based on Alert status, use
a_alert_status_code, below, which does not change with translations.Tip: Thea_alert_statusfield can be updated during a survey import by mapping the new value to the Alert Status special import field (alert_status, named much like thea_alert_statusfield, but without thea_prefix). - a_alert_status_code
- Alert current status code — Current workflow state of the alert instance, such as NEW, IN_PROGRESS, OVERDUE, ESCALATED, and CLOSED.
- a_alert_triggered
- Alert has been triggered — Whether or not the record has an alert instance.
- a_alert_type
- Alert type — Name of the Alert (as specified in the Alert Condition).
This field can be updated during a survey import by mapping the new value to the Alert Type (
a_alert_type) special import field. - a_case_edited_by
- Alert case edited by — List (alphabetical) of Users who edited the alert instance. The users are listed in alphabetical order (not in the order they edited the alert).
- a_case_edited_by_chrono
- Case edited by (chronological) — List of users (chronological) who edited the record via Case Management. The list is in the order of the users who updated the record, where the first entry is the oldest.
- a_case_edited_by_role
- Alert case edited by role — List (alphabetical) of the Roles used by the Users who edited the alert instance. The users are listed in alphabetical order (not in the order they edited the alert).
- a_case_edited_by_role_chrono
- Case edited by role (chronological) — List of roles (chronological) who edited the record via Case Management. The list is in the order of the users who updated the record, where the first entry is the oldest.
- a_has_alert
- Survey has alert — Whether or not (1 or 0) the survey triggered an alert.
- a_has_open_alert
- Survey has an open Alert — Whether or not (1 or 0) the record has an open Alert instance.
- a_subscribers
- Alert subscribers — List of Users who are currently subscribed to the alert instance.
- a_survey_assignee
- Alert Assignee — User currently assigned to the Alert.
This field can be updated during a survey import by mapping the new value to the Alert Assignee (
alert_assignee) special import field.
Rapid response
These fields track information about Rapid response:
- a_rapid_response_all_cc_recipients
- List of CC recipients for each feedback response sent for a particular feedback record.
- a_rapid_response_all_comments
- List of response text for each feedback response sent for a particular feedback record.
- a_rapid_response_all_sent_dates
- List of send dates and times for each feedback response sent for a particular feedback record.
- a_rapid_response_all_subjects
- List of subject lines for each feedback response sent for a particular feedback record.
- a_rapid_response_all_templates_used
- Rapid Response all templates used — List of the names of the Rapid Response Templates used to send one or more Rapid Response emails to respondents.
- a_rapid_response_business_time
- Rapid Response Time — Fractional number of hours elapsed between the Alert being opened (New state) and the first rapid response, excluding non-business days. If the survey has a Social Response, the time is calculated from the opening of the alert and until the received time of the social response. Field is Null when the record has no Alert or Rapid Response.
- a_rapid_response_cc_ recipients
- Rapid Response CC Recipients — List of the CC recipients for the oldest (first) feedback response sent, if any, for a record. Use this field to track and export the email address(es) entered in the CC field of a response.
- a_rapid_response_comment
- Rapid Response Comment — The rapid response text of the oldest (first) response, if any, for a record.
- a_rapid_response_estimated_edit_duration_seconds
- Rapid Response Estimated Edit Duration (seconds) — Duration (in seconds) for which the response editor was opened while editing a response.
- a_rapid_response_send_date
- Rapid Response Sent Date — The oldest (first) response date, if any, for a record.
- a_rapid_response_sent_by
- Rapid Response sent by — List of users who sent one or more Rapid Response emails.
- a_rapid_response_subject
- Rapid Response subject — The oldest (first) subject, if any, for a record.
- a_rapid_response_template
- Rapid Response Template — The oldest (first) response template used for a record.
- a_rapid_response_sent_by_role
- List of the roles used to send one or more Rapid Response emails.
- a_rapid_response_status
- Rapid Response status for this survey (e.g. sent or not) — Whether or not a response was sent for a record.
- a_rapid_response_unacknowledged
- Rapid Response Acknowledged — A response message has been sent to the respondent, and the respondent has not answered. Initially and when the email is sent, the value of this field is No. Once the respondent answers, the value changes to Yes to indicate it is unacknowledged. The value again changes to No when any user clicks Acknowledge client response or replies to the respondent's answer (without clicking Acknowledge client response).
Note the discrepancy between the Field name and identifier: Field name is Acknowledged and field ID is
a_rapid_response_unacknowledged.
These fields track information about Smart response:
- a_is_smart_response
- Is a Smart Response? — Whether or not the comment was generated using Smart response.
- a_smart_response_comment_ edited_yn
- Smart Response comment edited — Whether or not the response content using Smart response was edited before being sent.
- a_smart_response_initial_comment
- Smart Response initial comment — The initial comment generated by Smart Response, only if the oldest (first) response is Smart Response.
- a_smart_response_initial_subject
- Smart Response initial subject — The initial subject generated by Smart Response, only if the oldest (first) response is Smart Response.
- a_smart_response_subject_edited_yn
- Smart Response subject edited — Whether or not the subject generated using Smart response was edited before being sent.
Survey taker interaction
These fields record information about the survey taker interaction with the survey.
- a_elapsed_seconds
- Survey time spent — Time (in seconds) the survey taker spent on the survey.
- a_ipaddress
- Customer IP address — The IP address from which the survey was taken, when the address is provided by the device. If empty, the IP address is missing.
- a_is_adhoc_survey
- Obsoleted. Whether or not the survey was part of an Ad Hoc distribution.
- a_isolated_program_record
- Whether or not the record is from an Ad Hoc survey, Ad Hoc approval, Social Rivals, or Employee program.
- a_isolation_record_type
- The isolation type of a record, which can be from Ad Hoc survey, Ad Hoc approval, Social Rivals, or Employee program.
- a_last_seen_page_name
- Last page seen — The name of the last survey page seen by (sent to) the survey taker for this record.
- a_last_submitted_page_name
- Last page submitted — Name of the last survey page submitted by the survey taker.
- a_page_path_page_numbers
- Survey path in page numbers — List of the survey page numbers (multi-value field) sent to the survey taker.
- a_page_path_timestamps
- Survey path in timestamps — List of timestamps (multi-value fields) when the survey pages were sent to the survey taker. Use the
e_responsedatefield to identify when the survey was submitted (completed) by the survey taker. - a_program
- Program — Program UUID with an Auto-indexed Content Kind. It stores the program mapping logic, which follows these rules:
-
If
e_program_idis present and valid, it shows the value stored in that field. -
If
e_record_schema_mapping_idis present and valid, it shows the program's UUID. -
If none are present, it runs the program rules in priority order and provides the first matching program UUID.
-
- a_program_name
- Program name — Use mainly in Exports. Name for the Experience program or Ad Hoc survey stored in
a_programwith a Text Content Kind. - a_program_schema_id
- Program ID — ID of an Experience program or Ad Hoc survey. Use this field to filter reports, exports, and in Experience program conditions.
- a_startdate
- Survey start date — Timestamp when the first page of the survey was sent to the survey taker. The start date will only get set if the survey page fully loads. This is to ensure email scanners do not inflate the number of started surveys.
- a_survey_is_mobile
- Survey was viewed on mobile — At least one page of the survey was viewed on mobile device.
- a_survey_is_mobile_finished
- Survey was submitted on mobile — The survey taker completed the survey (clicked Submit) on a mobile device.
- a_survey_is_mobile_first
- Survey started on mobile device — Whether or not the survey taker started the survey on a mobile device. This is
truewhen the Survey engine sends the first page of the survey to a device other than a desktop (after the survey taker clicked a link to access the survey). Once this field istrue, it remains true. This field is similar to Survey clicked, which is also betruewhen this field istrue. - a_survey_is_partial
- Partial survey — This field is set
truewhen the survey taker starts the survey, and is later setfalsewhen the survey taker completes the survey, unlike Survey clicked (a_survey_is_started) which always remainstrue.a_survey_is_partialis set tofalsewhen whena_startdateis set, which is when the survey taker opens and fully loads the survey page in their browser. If the survey page is not fully loaded,a_startdateanda_survey_is_partialare not set at all. This is to ensure email scanners do not inflate the number of started surveys. - a_survey_is_started
- Survey clicked — This is
truewhen the survey engine sends the first page of the survey to the survey taker after clicking a link to access the survey. The survey page must fully load for this field to betrue. This ensures email scanners do not inflate the number of started surveys. Unlike Partial surveys, once this field istrue, it remains in this state. - a_survey_language
- Survey language — The language in which the survey was taken (English, Spanish, etc.). For Social media, it stores the language of the Social media feedback.
This field can be updated during a survey import by mapping the new value to the Survey Language (
survey_language) special import field.For Medallia Speech, this field stores the language locale used by the customer.
- a_survey_language_agent
- For Speech, this field stores the language locale used by the agent.
- a_survey_pages_submit
- Total pages submitted — The count of the survey pages the survey taker completed and submitted.
- a_survey_pages_validation_failed
- Invalid pages submitted — The count of page submissions that failed to pass validation, such as when a required question not answered. The counter increments for each invalid page submission, even if it's the same page.
- a_survey_response_date
- Survey response date — Timestamp when the survey taker completed the survey. For internal surveys, this is when the survey taker pressed the finish button on the survey. Same as Response date, except is how it reports the timezone in the K-fields editor:
- Survey response date — Honors time zone setting on Unit Group, but always says PST in K-field editor.
- Response date — Always reports Pacific time in the editor.
- a_survey_sampling_setting
- Survey sampling setting — Name of the survey sampling setting that was used during sampling to create the record.
- a_survey_last_submit_date
- Latest submit date — Timestamp when the last page was submitted by the survey taker.
- a_survey_url
- Survey URL — URL the survey taker uses to access the survey.
- a_survey_spec
- Name (either a short name or specId) of the survey version (previously known as survey spec) if the survey version has a value different than null.
- a_survey_spec_id
- ID of the survey program if the survey version (spec) has a value different than null.
- a_user_agent_brand
- Mobile Device Brand — Brand of the mobile device the survey taker used to complete the survey. Examples include Android, Apple, Archos, HTC, Microsoft, Samsung, T-Mobile, Toshiba, and Verizon. Warning: Device brand information is provided by the device, but is not always available and is not always accurate.
- a_user_agent_browser
- Browser — Browser the survey taker used to complete the survey. Examples include Android Webkit, Chrome, Firefox, Internet Explorer, Mobile Safari, Mozilla, Safari, and Unknown. Warning: Browser information is provided by the browser, but is not always available and is not always accurate. Additionally Microsoft Edge employs User agent switching, which allows it to send misleading information, typically reporting it as Chrome or Mozilla instead of Edge.
- a_user_agent_browser_and_ver
- Browser with Version — Same as Browser, but also includes the browser version ID. Examples include Chrome 42, Internet Explorer 10 10.0, Mobile Safari 10.3, Firefox 4 41.0. Warning: Browser information is provided by the browser, but is not always available and is not always accurate. Additionally Microsoft Edge employs User agent switching, which allows it to send misleading information.
- a_user_agent_os
- Operating System — Operating system the survey taker used to complete the survey. Examples: Android, Linux, Mac OS X, Unknown, Windows, and iPhone OS. Warning: This information is provided by the browser, but is not always available and is not always accurate.
- a_user_agent_os_and_ver
- Operating System with version — Same as
a_user_agent_os, but also includes the operating system version ID. Examples: Android 2.3, Windows 10, and iPhone OS 9.Warning: This information is provided by the browser, but is not always available and is not always accurate.
Ask Now
These fields record information about Ask Now tests:
- a_ask_now_author
- Name of the user who created the Ask Now test.
- a_ask_now_end
- Last day the test was active.
- a_ask_now_id
- The ID of the test.
- a_ask_now_name
- Title of the Ask Now test. If no name is set, it shows the text from first question. When a survey taker skips the Ask Now test, the Ask Now test name is left blank.
- a_ask_now_question_comment_<number>
- Obsoleted. Ask Now question of Comment type that can be used for Medallia Text Analytics.
You cannot use this field for filtering.
- a_ask_now_question_<number>
- Survey taker's answer to each question in the test.
- a_ask_now_question_<number>_wording
- Question text for each question in the test displayed to the survey takers.
- a_ask_now_scope
- Lists of units the author restricted the test to.
- a_ask_now_start
- First day the test was active. If the Ask Now test is inactive, the export will show
NULLinstead of the actual start date. If the test is active, then it will have the actual date the test started. - a_ask_now_status
- Current state and visibility of the test, which can be either Active or Inactive. If the test is activated/deactivated, the value of this field would impact other surveys associated with the test.
Comment and Medallia Text Analytics
These fields record information about survey taker's comments and the Text Analytics processing of those comments.
- a_comments
- All survey comments concatenated — Concatenation of all non-blank record comments, where comments are separated by a new-line character. This includes any field whose Alternative set has a ContentKind of COMMENT and TRANSLATABLE_COMMENT.
- a_has_comment
- Survey has a comment — Whether or not (1 or 0) the survey has one or more comments. This includes any comments in any field types (not just Q-fields) except Ask Now comments (which are not included) and whose Alternative set has a ContentKind of COMMENT and TRANSLATABLE_COMMENT. For example, Case management comments in the record are considered a comment by this field.
- a_has_word_tags
- This field has a value of 1 if its survey has any word taggings, and 0 otherwise.
- a_tagged
- Tagged — This field has either a Yes or No value.
- Yes
- At least one phrase in the record was matched to a Text Analytics topic.
- No
- One of the following conditions is true:
-
No phrases in the record were matched to a Text Analytics topic (that is,
a_untaggedis Yes). -
There were no phrases in the record.
-
- a_topics_for_[field]
- A comma-separated list of the topics that match a specific field.
- a_topics_original_for_[field]
- A comma-separated list of the topics that match a specific field, before any manual changes.
- a_topics_sentiments_for_[field]
- A comma-separated list of the topics and sentiments that match a specific field.
- a_topics_sentiments_latest_for_[field]
- A comma-separated list of the most recent manually-selected topics and sentiments that match a specific field.
- a_topics_sentiments_original_for_[field]
- A comma-separated list of the topics and sentiments that match a specific field, before any manual changes.
- a_topics_sentiments_tagged_after_manual_updates
- A comma-separated list of the topics that match a record, combined with the sentiment matching the same regions. This field lists topics originally discovered by Experience Cloud and those tagged manually by users.
You cannot use this field for filtering.
- a_topics_sentiments_tagged_original
- A comma-separated list of the topics that match a record, combined with the sentiment matching the same regions, as originally discovered by Experience Cloud (excluding topics tagged manually by users).
- a_topics_tagged_after_manual_updates
- A comma-separated list of the topics that match a record. This field lists topics originally discovered by Experience Cloud and those tagged manually by users.
You cannot use this field for filtering.
- a_topics_tagged_original
- A comma-separated list of the topics that match a record, as originally discovered by Experience Cloud (excluding topics tagged manually by users).
You cannot use this field for filtering.
- a_topics_with_hierarchy_for_[field]
- A comma-separated list of the topics and subtopics that match a specific field.
- a_topics_with_manual_sentiments_for_[field]
- A comma-separated list of the manually-selected topics and sentiments that match a specific field.
- a_untagged
- This field has either a Yes or No value:
- Yes
- The record includes one or more comments that were processed by Text Analytics. However, none of the phrases from the record were matched to a topic.
- No
- Either one of the following conditions is
true:-
At least one phrase in the record was matched to a topic (for example,
a_taggedis Yes). -
There were no phrases in the record.
-
Intelligent Summaries
These fields record information from Intelligent Summaries for conversational data:
- a_speech_comment_summary
- Summary of the Speech transcript summary field.
- a_speech_comment_summary_primary_reason
- Primary reason for contact. Consists of one word minimum to four words maximum.
- a_speech_comment_summary_resolved_yn
- Whether or not the primary reason for contact was resolved during this interaction.
- a_speech_comment_summary_outcome
- Outcome of the interaction, including how the primary reason for contact was resolved, or why the primary reason for contact was not resolved.
- a_speech_comment_summarized_yn
- Whether or not the Speech transcript summary field has been summarized.
- a_speech_comment_summarization_datetime
- Date and time when the summarization processing is complete.
- a_speech_comment_summary_status
- Indicates the summarization processing status, which may be:
- Pending
- The referenced field has been marked as summarizable and its record has persisted in the database queue.
- In-queue
- The field's record is queued for summarization processing.
- Completed
- The record was summarized successfully.
- Unexpected_failed
- Summarization failed for the given field because of an internal error or unexpected behavior.
- Expected_failed
- Summarization failed because the record or comment field does not contain valid content. For example, if the comment field contains more than the maximum valid number of characters, the field is not summarized.
- Not_requested
- The record was not queued for summarization processing. For example, a record may not be queued for summarization because the record itself is too old, or because the record's language or comment field is not supported.
- a_conversational_transcript_comment_summary
- Summary of the Conversational transcript comment field.
- a_conversational_transcript_summary_primary_reason
- Primary reason for contact. Consists of one word minimum to four words maximum.
- a_conversational_transcript_summary_resolved_yn
- Whether or not the primary reason for contact was resolved during this interaction.
- a_conversational_transcript_summary_outcome
- Outcome of the interaction, including how the primary reason for contact was resolved, or why the primary reason for contact was not resolved.
- a_conversational_transcript_comment_summarized_yn
- Whether or not the Conversational transcript comment field has been summarized.
- a_conversational_transcript_comment_summarization_datetime
- Date and time when the summarization processing is complete.
- a_conversational_transcript_comment_summary_status
- Indicates the summarization processing status, which may be:
- Pending
- The referenced field has been marked as summarizable and its record has persisted in the database queue.
- In-queue
- The field's record is queued for summarization processing.
- Completed
- The record was summarized successfully.
- Unexpected_failed
- Summarization failed for the given field because of an internal error or unexpected behavior.
- Expected_failed
- Summarization failed because the record or comment field does not contain valid content. For example, if the comment field contains more than the maximum valid number of characters, the field is not summarized.
- Not_requested
- The record was not queued for summarization processing. For example, a record may not be queued for summarization because the record itself is too old, or because the record's language or comment field is not supported.
Action Intelligence
These fields record information discovered and calculated by Action Intelligence:
- a_actionability
- An integer between 0-100 indicating the relative actionability of records that have an Actionability flag value of Yes.
- a_actionability_flag
- Whether Action Intelligence has determined a record contains an actionable suggestion.Options include Yes, No, or Null.
You can use this field in alert rules.
- a_at_risk
- Whether Action Intelligence has determined that a survey taker is at risk of churn. Values may be Yes, No, or Null.
You can use this field in alert rules.
Important: Risk scoring is deprecated, and is replaced by attention scoring, which uses the attention A-fields described in this section. - a_attention_flag
- Whether Action Intelligence has determined that a survey taker needs attention. Options include Yes, No, or Null.
You can use this field in alert rules.
- a_attention_label_churn_intent_flag
- Whether Action Intelligence has determined that a survey taker needs attention to prevent churn. Values may be Yes, No, or Null.
You can use this field in alert rules.
- a_attention_label_eroding_faith_flag
- Whether Action Intelligence has determined that a survey taker needs attention to correct eroding faith in your company. Values may be Yes, No, or Null.
You can use this field in alert rules.
- a_attention_label_legal_action_flag
- Whether Action Intelligence has determined that a survey taker intends to sue your company or report activity to a regulatory agency. Values may be Yes, No, or Null.
You can use this field in alert rules.
- a_attention_label_positive_opportunity_flag
- Whether Action Intelligence has determined that with proper attention your company might realize new revenue from the survey taker, or be able to convert that survey taker to a promoter. Values may be Yes, No, or Null.
You can use this field in alert rules.
- a_attention_label_unresolved_issues_flag
- Whether Action Intelligence has determined that a survey taker needs attention to correct an unresolved issue. Values may be Yes, No, or Null.
You can use this field in alert rules.
- a_attention_score
- An integer between 0-100 indicating the relative urgency of attention required for records that have an Attention flag value of Yes. Action Intelligence uses this field only to provide a ranked order of records in need of attention. Do not interpret the value in this field as a confidence or probability score.
- a_attention_types
- Stores a concatenated list of all attention types needed for the record (Churn intent, Eroding faith, Legal action, Positive Opportunity, and Unresolved issues).
You cannot use this field for filtering.
- a_customer_effort_bucket
- A record-level categorization of the overall effort expended by a customer to achieve his or her goal with your company. Values include Very Hard, Hard, Neutral, Easy, and Very Easy.
You cannot use this field for filtering.
- a_customer_effort_score
- A numeric score from -10 to 10 indicating the record-level effort expended by the customer. The greater the value, the lower the effort. This score is compared to the thresholds defined on Medallia Setup Effort screen to determine which effort categorization to use for the record. You can use this field for filtering.
- a_customer_effort_easy_flag
- Whether or not a record has been flagged as requiring easy customer effort.
You can use this field in alert rules.
You cannot use this field for filtering.
- a_customer_effort_high_flag
- Whether or not a record has been flagged as requiring hard customer effort.
You can use this field in alert rules.
You cannot use this field for filtering.
- a_customer_effort_neutral_flag
- Whether or not a record has been flagged as requiring neutral customer effort.
You can use this field in alert rules.
You cannot use this field for filtering.
- a_customer_effort_veryeasy_flag
- Whether or not a record has been flagged as requiring very easy customer effort.
You can use this field in alert rules.
You cannot use this field for filtering.
- a_customer_effort_veryhigh_flag
- Whether or not a record has been flagged as requiring very hard customer effort.
You can use this field in alert rules.
You cannot use this field for filtering.
- a_negative_recognition_flag
- Whether or not a record has been flagged as containing negative recognition phrases in comments.
You cannot use this field for filtering.
- a_neutral_recognition_flag
- Whether or not a record has been flagged as containing neutral recognition phrases in comments.
You cannot use this field for filtering.
- a_positive_recognition_flag
- Whether or not a record has been flagged as containing positive recognition phrases in comments.
You cannot use this field for filtering.
- a_recognition_flag
- Whether or not a record has been flagged as containing recognition phrases in comments.
You can use this field in alert rules.
- a_speech_comment_summary
- Summary of the Medallia Speech transcript field (
q_speech_comment). - a_conversational_transcript_comment_summary
- Summary of the conversational transcript comment field (
q_conversational_transcript_comment).
Medallia Video
This field helps you filter reports by video and audio media in responses.
- a_media_feedback_file_types
- Whether a piece of media feedback was submitted as video or audio. Use this field in the Filter Columns module of Responses List reports to add an icon to responses that include embedded media. Add this field to Responses Form reports to display a value of VIDEO or AUDIO. Add this field to the Segment Filters of control panels to enable users to search for feedback that includes video and audio feedback.
Medallia Speech
These fields provide information about voice data that can help you understand the interactions between customers and call center agents. For more information, see Medallia Speech.
- a_agent_acoustic_emotion_trend
- The change detected in the agent's acoustic emotion from the beginning to the end of the call.
Possible values include Improving, Similar, Worsening, or Too short if the call is shorter than 90 seconds.
Note: The first 45 seconds of the call are not considered for this calculation because the beginning of a call tends to be limited to standard greetings; omitting those greetings more accurately describes acoustic emotion. - a_media_agent_average_talk_streak
- The average time for all streaks of agent speech, measured in seconds.
A streak is an uninterrupted chain of spoken language by a single speaker. A streak begins with the first word of a call, or with the next word spoken after a pause of three seconds or more. A streak ends with a pause of three seconds or more, or with the end of the call.
- a_agent_clarity
- A number from 0-100 representing the ASR engine's confidence that it correctly transcribed the audio channel with agent speech.
Higher numbers indicate better clarity, which is calculated from a confidence score based on the ASR engine's own estimate of its transcription quality. Clarity is not accuracy, which must be determined using human-generated transcripts, and clarity is not an indicator of the speaker's elocution.
- a_media_agent_longest_talk_streak
- The total time for the longest streak of agent speech, measured in seconds.
A streak is an uninterrupted chain of spoken language by a single speaker. A streak begins with the first word of a call, or with the next word spoken after a pause of three seconds or more. A streak ends with a pause of three seconds or more, or with the end of the call.
- a_media_agent_nonsilence_percentage
- Agent talk time during the call as a percentage of overall call duration.
- a_media_agent_overtalk_incidents
- Number of overtalk incidents by the agent during a call.
- a_media_agent_overtalk_percentage
- Agent overtalk time during the call as a percentage of overall call duration.
- a_media_agent_wpm
- The average rate of agent speech for the entire call, expressed as words per minute. Customer speech and significant pauses in the conversation are not included in this calculation.
- a_media_agent_talk_rate_trend
- The change detected in the agent's talk rate from the beginning to the end of the call. Expressed as a number between 0 and 1.0, where 1.0 represents no change in talk rate and .3 represents a 70% decrease in talk rate.
Calculated by comparing the agent's talk rate during the first third of the call to the agent's talk rate during the last third of the call.
- a_media_agent_customer_wpm_ratio
- The ratio of agent talk rate to customer talk rate.
- a_customer_acoustic_emotion_trend
- The change detected in the customer's acoustic emotion from the beginning to the end of the call.
Possible values include Improving, Similar, Worsening, or Too short if the call is shorter than 90 seconds.
Note: The first 45 seconds of the call are not considered for this calculation because the beginning of a call tends to be limited to standard greetings; omitting those greetings more accurately describes acoustic emotion. - a_media_customer_average_talk_streak
- The average time for all streaks of customer speech, expressed in seconds.
A streak is an uninterrupted chain of spoken language by a single speaker. A streak begins with the first word of a call, or with the next word spoken after a pause of three seconds or more. A streak ends with a pause of three seconds or more, or with the end of the call.
- a_customer_clarity
- A number from 0-100 representing the ASR engine's confidence that it correctly transcribed the audio channel with customer speech.
Higher numbers indicate better clarity, which is calculated from a confidence score based on the ASR engine's own estimate of its transcription quality. Clarity is not accuracy, which must be determined using human-generated transcripts, and clarity is not an indicator of the speaker's elocution.
- a_media_customer_longest_talk_streak
- The total time for the longest streak of customer speech, expressed in seconds.
A streak is an uninterrupted chain of spoken language by a single speaker. A streak begins with the first word of a call, or with the next word spoken after a pause of three seconds or more. A streak ends with a pause of three seconds or more, or with the end of the call.
- a_media_customer_nonsilence_percentage
- Customer talk time during the call as a percentage of total call duration.
- a_media_customer_overtalk_incidents
- The count of overtalk incidents by the customer during a call.
- a_media_customer_overtalk_percentage
- Customer overtalk time during the call as a percentage of total call duration.
- a_media_customer_wpm
- The average rate of customer speech for the entire call, expressed as words per minute. Agent speech and significant pauses in the conversation are not included in this calculation.
- a_media_customer_talk_rate_trend
- The change detected in the customer's talk rate from the beginning to the end of the call. Expressed as a number between 0 and 1.0, where 1.0 represents no change in talk rate and .3 represents a 70% decrease in talk rate.
Calculated by comparing the customer's talk rate during the first third of the call to the customer's talk rate during the last third of the call.
- a_media_luhn
- When redaction is turned on for Speech transcripts. Whether or not the Luhn algorithm (which identifies credit card numbers) was applied to the transcript.
- a_media_duration
- The duration in seconds of the call.
- a_media_overtalk_percentage
- The percentage of the call during which the customer and agent spoke simultaneously.
- a_overall_agent_acoustic_emotion
- The agent's average acoustic emotion during the call.
Options include Strongly positive, Positive, Neutral, Negative, and Strongly negative, or Too short for calls shorter than 90 seconds.
Note: The first 45 seconds of the call are not considered for this calculation because the beginning of a call tends to be limited to standard greetings; omitting those greetings more accurately describes acoustic emotion. - a_overall_customer_acoustic_emotion
- The customer's average acoustic emotion during the call.
Options include Strongly positive, Positive, Neutral, Negative, and Strongly negative, or Too short for calls shorter than 90 seconds.
Note: The first 45 seconds of the call are not considered for this calculation because the beginning of a call tends to be limited to standard greetings; omitting those greetings more accurately describes acoustic emotion. - a_media_silence_incidents
- A count of the times during a call when no speech was detected.
- a_media_silence_percentage
- The percentage of the call during which no speech was detected.
Feed file processing report fields
The information provided by these fields is also available on the Feed Files screen.
- a_feed_file_processing_report_accepted
- Number of records accepted from the feed file.
- a_feed_file_processing_report_created_entities
- Number of new records from the feed file.
- a_feed_file_processing_report_created_related_entities
- Number of created related entities in the feed file.
- a_feed_file_processing_report_deleted_entities
- Number of deleted records because of records in the feed file.
- a_feed_file_processing_report_download_link
- URL to download the feed file. For more information, see Import Processing Reports.
- a_feed_file_processing_report_duplicates
- Number of duplicates (records already with matching records) in the feed file.
- a_feed_file_processing_report_excluded_by_committed_survey_spec
- Number of records excluded due to survey specification filter.
- a_feed_file_processing_report_excluded_by_inactive_unit
- Number of records excluded because the Unit is inactive.
- a_feed_file_processing_report_excluded_by_opt_out
- Number of records excluded due to survey taker opt-out.
- a_feed_file_processing_report_excluded_by_quarantine
- Number of records excluded due to Quarantines.
- a_feed_file_processing_report_excluded_by_quota
- Number of records excluded due to Quotas.
- a_feed_file_processing_report_excluded_by_sample_filter
- Number of records excluded due to Sampling filters.
- a_feed_file_processing_report_excluded_by_survey_program
- Number of records excluded due to survey program filter.
- a_feed_file_processing_report_failed_requests
- Number of failed aggregated requests. For more information, see
a_feed_file_processing_report_report_type. - a_feed_file_processing_report_feed_account
- The primary key of the feed account
- a_feed_file_processing_report_feed_account_type
- The primary key of the Import method account type, which can be:
- Program
- Response ingestion
- Self-service upload
- Web Feed
- a_feed_file_processing_report_filename
- Name of the feed file that was processed. Note that this field does not work in an Export because it is used for feed file-type records, not records. It is possible to stamp a record with the filename by using a JavaScript transform and getting it from the
requestInfoobject such asrequestInfo.filenamein an Importer. - a_feed_file_processing_report_input_size_kbytes
- Size of the feed file, in K-bytes.
- a_feed_file_processing_report_invitations_created
- Count of surveys generated from the records in the feed file. This includes records created but which did not generate invitations, such as one created in the COMPLETED Survey status (e_status).
- a_feed_file_processing_report_processing_end_date
- Timestamp when processing finished.
- a_feed_file_processing_report_processing_start_date
- Timestamp when processing started, and when the processing report was created.
- a_feed_file_processing_report_processing_time_seconds
- Time (in milliseconds) to process the feed file.
- a_feed_file_processing_report_record_processor
- The primary key of the record processor. Positive values are from the Importer, while negative values are Lego.
- a_feed_file_processing_report_records
- Number of records in the feed file.
- a_feed_file_processing_report_rejected
- Number of records rejected from the feed file.
- a_feed_file_processing_report_report_type
-
Type of the processing report, which may be:
- NORMAL — A single feed file.
- AGGREGATED — Aggregated results of multiple feeds. This usually happens, for example, when a Web Feed processes records synchronously or immediately as they arrive. The results are collected, aggregated, and reported hourly instead of immediately after processing the feed.
- a_feed_file_processing_report_requests
- Number of aggregated requests; always 1 for normal (non-aggregated) feed file processing.
- a_feed_file_processing_report_sampling_pending
- Number of records awaiting sampling, when delayed sampling is in effect.
- a_feed_file_processing_report_status
- Status of the processing step, such as Waiting and Processed. For more information, see Status in Feed Files.
- a_feed_file_processing_report_status_message
- Status message of the processing step. For more information, see Description in Feed Files.
- a_feed_file_processing_report_successful_requests
- Number of successful aggregated requests. For more information, see
a_feed_file_processing_report_report_type. - a_feed_file_processing_report_summary_download_link
- URL to download the Processing Report for the feed, if any.
Invitation-opened statistics
These fields report information about opened Survey email. These are populated:
-
For HTML content type (not Plain text):
-
That include the
$TRACK_INVITE_EMAIL_OPEN$variable. -
For devices, browsers, operating systems and/or email clients that permit tracking: the client must allow images to be retrieved from the Survey engine HTTP server.
-
-
For web-based email clients, the agent information might be the cloud proxy that hosted or loaded the email client
For more information, see Track invitation open rates.
- a_email_client_user_agent_brand
- Brand name of the email client.
- a_email_client_user_agent_browser
- Browser name of the email client.
- a_email_client_user_agent_browser_and_ver
- Browser/version of the email client.
- a_email_client_user_agent_device_name
- Device name running the email client.
- a_email_client_user_agent_os
- Operating system running the email client. This is set when the invitation is opened and rendered.
- a_email_client_user_agent_os_and_ver
- Operating system and version running the email client.
- a_email_user_agent_raw
- Complete User-Agent request header sent by the email client.
- a_email_invite_first_opened_date
- Timestamp when the invitation was first opened. Supersedes
a_invite_first_opened_date. - a_invite_first_opened_date
- Deprecated. See
a_email_invite_first_opened_date. - a_invite_first_opened_ip_address
- IP address of the email client that opened the invitation, when the address is provided by the device.
- a_invite_opened_yn
- Whether or not the invitation email was opened. This fields gets updated to Yes when a survey is clicked, even if Tracking invitation open rates is not implemented.
Omni Exporter statistics
Omni Exporter statistics are aggregated per-hour to reduce load. The first Omni Exporter event in an hour creates a record for statistics. All subsequent events in the same hour update these fields in the same record, until the end of the hour. These fields are part of the Omni Exporter statistics:
- a_omni_exporter_event_count_created
-
a_omni_exporter_event_count_failed -
a_omni_exporter_event_count_retry -
a_omni_exporter_event_count_success -
a_omni_exporter_kind -
a_omni_exporter_matched_created_entities -
a_omni_exporter_matched_updated_entities -
a_omni_exporter_name -
a_omni_exporter_received_kbytes -
a_omni_exporter_sent_kbytes
Sampling and invitation process
These fields record information about the Sampling and Inviting processes.
- a_feed_file_id
- ID of the feed-file that created the record. For records created by other means, such as feedless surveys, the value is null. For information about locating feed-files by ID, see Feed Files.
- a_invitation_status
- Invitation status — Descriptive status of the record state. For a list of the messages and how they map to Survey status (e_status) see Invitation status.
- a_sampled_date
- Sampled date — Timestamp when the record completed sampling.
- a_sampling_result_exclusion_cause
- Sampling exclusion reason— For records excluded by sampling, this is the cause of the exclusion.
This field can be updated during a survey import by mapping the new value to the Exclusion Cause (
exclusion_cause) special import field. - a_sampling_result_exclusion_cause_detail
- Sampling exclusion detailed reason— For records excluded by sampling, this is a detailed description of the cause of the exclusion.
This field can be updated during a survey import by mapping the new value to the Exclusion Cause (
exclusion_cause) special import field. - a_sampling_result_quarantined_by_unit_identifier
- Unit ID that matches the quarantine rule that excluded a record. If a record was not excluded by a quarantine rule, the field has no value.
- a_sampling_result_quarantined_by_unit_name
- Name of the unit that matches the quarantine rule that excluded a record. If a record was not excluded by a quarantine rule, the field has no value.
- a_survey_first_bounce_date
- Survey first bounce date — Timestamp when the first invitation bounced (was not delivered). This field uses the survey's bounce history — a list with data about the different bounces of the Invitation/Reminder emails for a survey — and gets the first of those. Each of the bounce's data has the status of the survey, the bounce category, and the timestamp of the Invitation/Reminder email that bounced (that is, the delivery date of the Invitation/Reminder email and not the date when the bounce arrived). This is null if the invitation did not bounce. For more discussion, see Bounced email statusNote: A
nullvalue does not mean the invitation was delivered. - a_survey_sampling_setting
- Survey sampling setting — Name of the survey sampling setting that was used during sampling to create the record.
Sensitive data
This field stores information about records with masked data. For more information, see Sensitive data.
- a_pii_regions_flag
- Whether or not this record contains masked data. It updates to Yes after sensitive data masking process is complete.
Single sign-on (SSO) event statistics
Records statistics of each Single sign-on (SSO) event. These are the common SSO fields:
-
a_sso_attempt_ai_processing_failed -
a_sso_attempt_account_not_found_or_invalid -
a_sso_attempt_account_password_not_set -
a_sso_attempt_date_time -
a_sso_attempt_failure_count -
a_sso_attempt_missing_parameter -
a_sso_attempt_no_units_available -
a_sso_attempt_no_units_passed -
a_sso_attempt_no_such_template -
a_sso_attempt_redirection -
a_sso_attempt_referrer_not_permitted -
a_sso_attempt_saml_assertion_expired -
a_sso_attempt_saml_assertion_processing_failed -
a_sso_attempt_saml_assertion_signature_invalid -
a_sso_attempt_saml_assertion_signature_missing -
a_sso_attempt_saml_attribute_invalid -
a_sso_attempt_saml_attribute_missing -
a_sso_attempt_saml_authentication_failed -
a_sso_attempt_saml_auth_request_assembly_failed -
a_sso_attempt_saml_invalid_audience -
a_sso_attempt_saml_invalid_issuer -
a_sso_attempt_saml_response_creation_failed -
a_sso_attempt_success_count -
a_sso_attempt_unexpected
Social media
These fields record information records from Social media:
- a_overall_score_with_social_media
- Social media overall score normalized — The score of a Social media record, normalized to a an integer from 0 to 100.
This field returns a single score value for both Social media and survey records to aggregate them in reports, as long as the survey record has a set source in
social_media_source_enum. - a_overall_score_with_social_media_0_5
- Social media score normalized for 5-scale — The value
a_overall_score_with_social_media_nativenormalized to a fractional value from 0.0 to 5.0. This field includes both Social and survey data that is on a 5-point scale.This field returns a single score value for both Social media and survey records to aggregate them in reports, as long as the survey record has a set source in
social_media_source_enum.Note: This field might be populated even if thesocial_media_source_enumvalue is null. - a_overall_score_with_social_media_5_buckets
- Social media 5-scale for display — The score from
a_overall_score_with_social_media_nativesocial media record normalized to an integer in from 1 to 5. Use this field for filter dropdowns and satisfaction distribution. Otherwise, usea_overall_score_with_social_media_nativeora_overall_score_with_social_media_0_5.This field returns a single score value for both Social media and survey records to aggregate them in reports, as long as the survey record has a set source in
social_media_source_enum. - a_overall_score_with_social_media_native
- Social media overall score native — The original, un-normalized overall score for a survey or a social media review.
- For surveys, this is a fractional value that corresponds to the raw value.
- For social media reviews, this is a fractional value corresponding to the value found on the website.
Warning: It doesn't make sense to aggregate or compare this field across different sources, because values are on different scales.This field returns a single score value for both Social media and survey records to aggregate them in reports, as long as the survey record has a set source in
social_media_source_enum. - a_social_media_source_enum
- Social media source — Social media source for this survey;
nullwhen the source is not from social media. The list of sources is company-specific and defined on the Social Feedback screen.This field can be updated during a survey import by mapping the new value to the Social Media Source (
social_media_source_enum) special import field. - a_social_original_post_field
- Social Original Post –– Field that captures the link for Original Post shown under the main score in the Responses form and Response feed module.
- a_socialresponse_comment
- Management Response –– The last response for a review when Respond to Social feedback is active.
- a_socialresponse_sent_by
- Management Response Sent By — List of users who submitted one or more management to a review. A new list item is added every time a management response is submitted (that is, if a user submits two management reviews, their name appears twice in the list). Note: This is a multi-valued A-field. Consequently, if you are using this A-field in a K-field, you must specify Backfill required for the SlugAvailability property, and run a backfill.
- a_socialresponse_sent_by_role
- Management Response Sent By Role — List of the roles used to submit one or or more management to a review. When users have access to multiple roles, the list only records the role they used to submit the response. Note: This is a multi-valued A-field. Consequently, if you are using this A-field in a K-field, you must specify Backfill required for the SlugAvailability property, and run a backfill.
- a_socialresponse_status
- Management Response Status –– List of available statuses a management response can have such as Not sent, External Response Sent, External Response Published, and External Response Sent and Published.
- a_socialresponse_send_date
- Management Response Send Date — Date the first management response was sent when the management response status (
a_socialresponse_status) is either External Response Sent or External Response Sent and Published. It isnullwhen management response status is Not sent or External Response Published. - a_socialresponse_publish_date
- Management Response received Date — The last date that Experience Cloud captured and verified the Management response appearing on the social source. For example, this field can be populated and differ from
a_socialresponse_first_publish_datewhen there is an update on the original Management response that was already published. - a_socialresponse_first_publish_date
- Management Response First received Date — The first date that Experience Cloud captured and verified the Management response appearing on the social source.
- a_trip_advisor_popularity_rank_index
- TripAdvisor Popularity Ranking Index — Only used on Unit metric surveys to track the relative importance of a Unit's TripAdvisor rank by making different units comparable given the different benchmark sizes. The rank index range is 0 to 100, where a rank of X means that X% of the competitors are below in the rank (100 is the best rank). For example, if the TripAdvisor index is #9 of 26, this field value is 68 meaning 68% of competitors are below this unit.
User activity statistics
Records the statistics of user activities. For more information, see User activity and Health Check.
- a_user_activity_account_id
- ID of the user.
- a_user_activity_account_name
- User name.
- a_user_activity_application_id
- Application ID that recorded the activity. Possible IDs are Express for Experience Cloud, Mobile for Medallia Mobile, and Voices for Medallia Voices.
- a_user_activity_application_platform
- Application platform that recorded the activity.
- a_user_activity_application_version
- Application platform that recorded the activity.
- a_user_activity_canonical_detail
- Untranslated name of the detail field.
- a_user_activity_count
- Number of times the activity was performed within a single sign-in session.
- a_user_activity_detail
- The detailed name of the user activity performed. For example, the name of the subtab (such as Satisfaction Table or Responses Form) for a Page view activity, or the name of the Feedback (Rapid) response template for a Send Rapid Response activity.
- a_user_activity_ip_address
- IP address of the user, when the address is provided by the device.
- a_user_activity_module
- The top-level menu text of the page, such as Satisfaction or Responses. This field is populated only for Page view activities.
- a_user_activity_num_active_accounts
- Number of active accounts with the same primary role as the user at the time this user was signed in.
- a_user_activity_num_active_units
- Number of active units at the time this user was signed in.
- a_user_activity_primary_role
- Name of the user's primary role.
- a_user_activity_primary_role_type
- The role type of the primary role of the user that interacted with the feedback signal.
- a_user_activity_role
- Role the user was using when the activity was performed.
- a_user_activity_session_length_minutes
- OBSOLETE — removed.
- a_user_activity_type
- The type of user activity performed, from the following actions:
Action Description Page view (PAGE_VIEW) Visited any page in Medallia Web reporting or Medallia Mobile. This type is a default activity type for when others do not apply. Write note (WRITE_NOTE) Added a note to a record. Close alert (CLOSE_ALERT) Closed an alert. Alert assign (ALERT_ASSIGN) Assigned an alert to someone. Resolve alert (RESOLVE_ALERT) Resolved an alert. Reopen alert (REOPEN_ALERT) Reopened an alert that was previously resolved. Social media external response (SOCIAL_MEDIA_EXTERNAL_RESPONSE) Wrote a response to a Social media record. Send rapid response (SEND_RAPID_RESPONSE) Sent a Feedback response. Mobile (MOBILE) Restriction: This type has been deprecated.Ask now (ASK_NOW) Created, modified, or deleted anything in Ask Now. Forward by email (FORWARD_BY_EMAIL) Forwarded a survey by email in Medallia Mobile. Call back (CALL_BACK) Clicked Call Customer in Medallia Mobile. Submit cm form (SUBMIT_CM_FORM) Submitted a Case Management form. For more information, see Case Forms. Expand response (EXPAND_RESPONSE) Expanded a collapsed response. Collapse response (COLLAPSE_RESPONSE) Collapsed an expanded response. Update filters (UPDATE_FILTERS) Changed the report filters in the Control panel. Navigate drill down (NAVIGATE_DRILL_DOWN) Clicked a value in report to open another report with more detailed information.
