System fields

System fields (previously known as A-fields) are generated by Medallia Experience Cloud and contain information about an event or the survey taker's relationship with the survey itself, such as the timestamp when respondents completed the survey or when they opened the invitation email. System fields can be used in reports, exports (unless otherwise noted), Formula fields, analytic reports, conditions, and more. Some System fields also record and calculate specific, internal information from different Medallia products. System fields break down into these sub-categories based on the Experience Cloud area they are part of:

Action Intelligence
Action Plans
Alerts
Ask Now
Case forms
Integration processing metadata
Sampling
Social Feedback
Survey metadata
Text Analytics
User activity

There are other System fields that might not be part of those categories, as well as some described in this topic that fall under the Uncategorized category.

Restriction: System fields cannot be translated; instead, create a Formula field.

Action Intelligence

These fields record information discovered and calculated by Action Intelligence powered by Medallia AI.

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.

Actionability score

An integer between 0-100 indicating the relative actionability of records that have an Actionability flag value of Yes.

At risk flag

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.

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.

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.

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.

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.

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.

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.

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.

Attention type

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.

Customer effort bucket name

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.

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.

Easy effort 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.

High effort 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.

Neutral effort 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.

Very easy effort 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.

Very high effort 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.

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.

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.

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.

Recognition flag

Whether or not a record has been flagged as containing recognition phrases in comments.

You can use this field in alert rules.

Speech transcript summary

Summary of the Medallia Speech transcript field (q_speech_comment).

Conversational transcript summary

Summary of the conversational transcript comment field (q_conversational_transcript_comment).

Action plans

These fields track information about Action plans:

Action plan creator: ID of the user who created the Action plan.
Action plan creator name: Name of the user who created the Action plan.
Action plan name: Name of the Action plan.
You cannot use this field for filtering.
Action plan description: Description of the Action plan.
You cannot use this field for filtering.
Action plan owner: ID of the user who owns the Action plan.
Action plan owner name: Name of the user who owns the Action plan.
Action plan status: Status of the Action plan, which can be: Approved same as Not Started in reporting, In progress, Completed, or Canceled.
Action plan survey IDs: Survey IDs set in the Action plan.
You cannot use this field for filtering.
Action plan has attachments: Whether or not the Action plan includes attachments.
Action plan drivers: List of Action plan Drivers.
Action plan drivers alternative sets: List of Choice sets for Action plan Drivers.
Action plan suggested actions: List of the Action plan Suggested actions.
Action plan suggested actions alternative sets: List of Alternative sets for Action plan Suggested actions.
Action plan themes: List of Action plan Themes.
Action plan themes alternative sets: List of Choice sets for Action plan Themes.
Action plan topics: List of Action plan Topics.
Action plan topics alternative sets: List of Choice sets for Action plan Topics.
Action plan has Impact analysis: Whether or not the Action plan has attachments.
Action plan impact analysis baseline Begins date: Date and time the Baseline period begins for Impact analysis.
Action plan impact analysis baseline Setup date: Date and time the Setup period begins for Impact analysis.
Action plan impact analysis start Test date: Date and time the Test period begins for Impact analysis.
Action plan impact analysis end Test date: Date and time the Test period ends for Impact analysis.
Action plan impact analysis metrics: List of Action plan Metrics.
Action plan impact analysis metrics alternative sets: List of Choice sets for Action plan Metrics.
Action plan impact analysis Control group name: Control group name used in Impact analysis.
You cannot use this field for filtering.
Action plan impact analysis Impact group name: Impact group name used in Impact analysis.
You cannot use this field for filtering.
Action plan number of tasks: Number of Tasks associated with the Action plan.
Action plan task name: Multi-valued field that stores all the names of Tasks.
You cannot use this field for filtering.
Action plan task description: Description of an Action plan Task.
You cannot use this field for filtering.
Action plan task assignee: Multi-valued field that stores the assignees of all the Tasks.
Action plan task assignee name: Name of task assignees.
Action plan task completion date: Multi-valued field that stores the completion date of all Tasks.
Action plan task status: Multi-valued field that stores the status of all Tasks. Statuses can be Not started, In progress, or Completed.
Action plan task due date: Multi-valued field that stores the due date of all Tasks.
Action plan ID: ID of the Action plan.
Action plan creation date: Date and time when the Action plan was created.
Action plan updated date: Date and time when the Action plan was updated.
Action plan completion date: Date and time when the Action plan was completed.

Alerts

These fields track information about Alerts:

Alert Business days excluded time

The time in milliseconds this alert has skipped due to excluded business days. This field can't hold a value bigger than 24 days; it will clamp to zero after that. Use Alert Business Days Excluded Time (seconds) when possible to avoid issues.

Alert Business days excluded time (seconds)

The time in seconds this alert has skipped due to excluded business days.

Alert assigned to groups

Similar to Alert assigned to names, but it contains the names of all the Unit groups (Alert assignees, not individual users) that have been, and currently are, assigned to the associated Alert instance.

Alert assigned to minutes

The total number of minutes each group in Alert assigned to names was assigned the alert.

Note: The last assignee is not included until the alert is closed.

Alert assigned to names

List of users that have been assigned to the associated alert.

Alert assignee

User currently assigned to the Alert. This field can be updated during an import by mapping the new value to the Alert Assignee (alert_assignee) special import field.

Alert close time

Date and time when the alert was closed. This field can be updated during an import by mapping the new value to the Alert closed time (alert_closed_timestamp) special import field.

Alert closed by

List of users who closed the alert (more than one if the alert was re-opened).

Alert creation time

Date and time when the alert was created. This field can be updated during an import by mapping the new value to the Alert creation time (alert_created_timestamp) special import field.

Alert description

Description of the alert (as defined on Settings).

Alert ever escalated

Whether or not the alert has ever been in the Escalated state. This field can be updated during an import by mapping the new value to the Alert ever escalated (alert_ever_escalated) special import field.

Alert ever escalated 2

Whether or not the alert has ever been in the Escalated 2 state. This field can be updated during an import by mapping the new value to the Alert ever escalated2 (a_alert_ever_escalated2) special import field.

Alert ever in overdue

Whether or not the alert has ever been in the Overdue state. This field can be updated during an import by mapping the new value to the Alert ever in overdue (alert_ever_overdue) special import field.

Alert owner ID

User ID of Alert owner.

Alert owner

Either the First and Last name of the Alert owner, or the name of the Assignee(s). This field is populated after a user is assigned to the the alert.

Alert reopened

Number of times the alert was reopened. It is 0 if there is no alert.

Alert resolution time

Date and time when the alert was closed. This field can be updated during an import by mapping the new value to the Alert resolution time ( alert_resolved_timestamp) special import field.

Alert status changed time

Date and time when the alert status last changed.

Alert type

Name of the Alert specified in the Alert rule condition. This field can be updated during a import by mapping the new value to the Alert type (alert_type) special import field.

All log notes combined (if any)

All the log entries for 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)

Current status of alert

Status of the alert. This field can be updated during a import by mapping the new value to the Alert Status (alert_status) special import field.

Tip: This field automatically includes all translated values. If there is any condition 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 reports while the user is in the Spanish language, the condition fails because the field is not close' and instead says cerrado. To condition based on Alert status, use a_alert_status_code.

Current status of alert (untranslated)

Workflow state of the alert, such as New, In progress, Overdue, Escalated, and Closed.

Survey has alert

Whether or not a record has an alert.

Survey has alert (1 or 0)

Whether or not (1 or 0) a survey triggered an alert.

Survey has open alert (1 or 0)

Whether or not (1 or 0) the record has an open alert.

Feedback responses

These fields track information about Feedback responses:

Rapid Response acknowledged: A response has been sent to a respondent, who has not responded. Initially and when the response is sent, the value of this field is No. Once there is a response, the value of this field 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 .
Rapid response CC recipients: List of 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.
Rapid Response comment: The response text of the oldest response, if any, for a particular feedback record.
Rapid Response Estimated edit duration (seconds): Duration for which the response editor was opened while editing a response.
Rapid Response Sent date: The oldest (first) response date, if any, for a particular feedback record.
Rapid Response subject: The oldest (first) subject, if any, for a particular feedback record.
Rapid Response template: The oldest (first) response template used for a particular feedback record.
Rapid Response time: Hours elapsed between the Alert being opened (status New) and the first response, excluding non-business days. If the feedback comes from Medallia Social Feedback, the time is calculated from the opening of the alert and until the received time of the response. Field is Null when the feedback has no Alert or response tied to it.
Rapid Response all CC Recipients: List of CC recipients for each feedback response sent for a particular feedback record.
You cannot use this field for filtering.
Rapid Response all Comments: List of response text for each feedback response sent for a particular feedback record.
You cannot use this field for filtering.
Rapid Response all Sent Dates: List of send dates and times for each feedback response sent for a particular feedback record.
You cannot use this field for filtering.
Rapid Response all Subjects: List of subject lines for each feedback response sent for a particular feedback record.
You cannot use this field for filtering.
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.
Rapid Response sent by: List of users who sent one or more responses.
Rapid Response sent by role: List of the roles used to send one or more responses.
Rapid Response status for this survey (e.g. sent or not): Whether or not a response was sent for a feedback record.

These fields track information about Smart response:

Restriction: This feature is inactive by default. Ask your Medallia expert to file a Feature activation request with Medallia Support.

Is Smart response?: Whether or not the response was composed using Smart response.
Smart Response comment edited: Whether or not the comment generated using Smart response was edited before being sent.
Smart Response initial comment: The initial comment generated by Smart Response only if the oldest response is Smart Response.

Important: Medallia Experience Cloud retains records for up to one year, after which they are no longer accessible.
Smart Response initial subject: The initial subject generated by Smart Response only if the oldest response is Smart Response.

Important: Medallia Experience Cloud retains records for up to one year, after which they are no longer accessible.
Smart Response subject edited: Whether or not the subject generated using Smart response was edited before being sent.

Ask Now

These fields track information about Ask Now:

Ask Now author: Name of the user who created the Ask Now Test.
Ask Now end date: Last day Ask Now is active.
Ask Now ID: The ID of Ask Now.
Ask Now name: Name of the Ask Now. If no name is set, it shows the text from first question. When a survey taker skips Ask Now, the Ask Now name is left blank.
Ask Now comment question #: Obsoleted. Ask Now question of Comment type that can be used for Medallia Text Analytics.
You cannot use this field for filtering.
Ask Now question #: Survey taker's answer to each question.
Ask Now question # wording: Question text for each question displayed to the survey takers.
You cannot use this field for filtering.
Ask Now scope: Lists of Units Ask Now is distributed to.
You cannot use this field for filtering.
Ask Now start date: First day Ask Now is active.
Ask Now status: Status of Ask Now. The value of this field impacts the surveys associated with Ask Now.

Case management

These fields track information about Case Forms:

Case edited by: List of users who edited one or more Case forms. The users are listed in alphabetical order.
Case edited by (chronological): List of users who edited one or more Case forms.The list is in the order of the users who updated the record, where the first entry is the oldest.
Case edited by role: List of the roles used by users the who edited a Case form. The users are listed in alphabetical order.
Case edited by role (chronological): List of roles who edited the record via Case form. The list is in the order of the users who updated the record, where the first entry is the oldest.

Integration processing metadata

These fields track information about fields used in Integrations:

Default feed date

Default import date as defined in TimeFieldConfig.

Feed File Program ID

ID of the program the import file is associated with.

Feed file ID

ID of the import file that created a record. For records created by other means, such as Anonymous surveys, there value is Null.

Feed file processing report accepted

Number of records accepted from the import file.

Feed file processing report created entities

Number of new records from the import file.

Feed file processing report created related entities

Number of created related entities in the import file.

Feed file processing report deleted entities

Number of deleted records because of records in the import file.

Feed file processing report download link

URL to download the import file. For more information, see Import Processing Reports.

Feed file processing report duplicates

Number of duplicates (records already with other matching records) in the import file.

Feed file processing report end date

Date and time when processing finished.

Feed file processing report excluded by committed survey spec

Number of records excluded due to survey version filter.

Feed file processing report excluded by inactive unit

Number of records excluded due to an inactive unit.

Feed file processing report excluded by Opt-out

Number of records excluded due to survey takers Opt out.

Feed file processing report excluded by Quarantine

Number of records excluded due to Quarantine.

Feed file processing report excluded by Quota

Number of records excluded due to Quota.

Feed file processing report excluded by sample filter

Number of records excluded due to Sampling filters.

Feed file processing report excluded by survey program

Number of records excluded due to program filter.

Feed file processing report failed requests

Number of failed aggregated requests. See Feed file processing report report type for details on aggregated processing.

Feed file processing report feed account

The primary key of the Import method account.

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

Feed file processing report filename

Name of the import file that was processed. Note that this field does not work in an Export because it is used for feed file-type records, not survey records. It is possible to stamp a record with the filename by using a JavaScript transform and getting it from the requestInfo object such as requestInfo.filename in an Importer.

Feed file processing report input size kbytes

Size of the import file, in Kilobytes.

Feed file processing report invitations created

Number of surveys generated from the records in the import file. This includes records created but which did not generate survey invitations, such as one created in the COMPLETED survey status.

Feed file processing report processing time seconds

Duration (in milliseconds) it took to process the import file.

Feed file processing report record processor

The primary key of the record processor. Positive values are from Importer while negative values are Lego.

Feed file processing report records

Number of records in the import file.

Feed file processing report rejected

Number of records rejected in the import file.

Feed file processing report report type

Type of the processing report, which can be:

NORMAL — A single import file.
AGGREGATED — Aggregated results of multiple import types. This usually happens, for example, when Medallia API processes records synchronously or immediately as they arrive. The results are collected, aggregated, and reported hourly instead of immediately after processing the import file.

Feed file processing report requests

Number of aggregated requests. It is always 1 for Normal report type.

Feed file processing report sampling pending

Number of records awaiting sampling. When delayed, sampling is in effect.

Feed file processing report start date

Date and time when processing started and when the processing report was created.

Feed file processing report status

Status of the processing step, such as Waiting and Processed.

Feed file processing report status message

Status message of the processing step.

Feed file processing report successful requests

Number of successful aggregated requests. See Feed file processing report report type for more details of aggregated processing.

Feed file processing report summary download link

URL to download the processing report for the import file, if any.

Feed file processing report updated entities

Number of updated records from the importer file.

Is an isolated feed file program record

Whether or not the import file is an isolated record.

Number of Omni Exporter 'Created' events

Number of Omni Exporter events that transitioned to 'Created' status.

Number of Omni Exporter 'Failed' events

Number of Omni Exporter events that transitioned to 'Failed' status.

Number of Omni Exporter 'Force retry' events

Number of Omni Exporter events that transitioned to 'Force retry' status.

Number of Omni Exporter 'No retry' events

Number of Omni Exporter events that transitioned to 'No retry' status.

Number of Omni Exporter 'Queued' events

Number of Omni Exporter events that transitioned to 'Queued' status.

Number of Omni Exporter 'Response generator failed' events

Number of Omni Exporter events that transitioned to 'Response generator failed' status.

Number of Omni Exporter 'Response handler failed' events

Number of Omni Exporter events that transitioned to 'Response handler failed' status.

Number of Omni Exporter 'Response handler running' events

Number of Omni Exporter events that transitioned to 'Response handler running' status.

Number of Omni Exporter 'Response handler success' events

Number of Omni Exporter events that transitioned to 'Response handler success' status.

Number of Omni Exporter 'Retry' events

Number of Omni Exporter events that transitioned to 'Retry' status.

Number of Omni Exporter 'Running' events

Number of Omni Exporter events that transitioned to 'Running' status.

Number of Omni Exporter 'Success' events

Number of Omni Exporter events that transitioned to 'Success' status.

Number of matched created entities

Number of created entities that triggered Omni Exporter events.

Number of matched deleted entities

Number of deleted entities that triggered Omni Exporter events.

Number of matched updated entities

Number of updated entities that triggered Omni Exporter events.

Omni Exporter kind

Processing mode of the Omni Exporter that generated the events, which can be either Active or Pretend.

Omni Exporter name

Name of the Omni Exporter that generated the events.

Omni Exporter received kbytes

Number of Kilobytes received due to Omni Exporter events execution.

Omni Exporter sent kbytes

Number of Kilobytes sent due to Omni Exporter events execution.

SSO Attempt request failed

Number of the SSO attempt failures of type AAA_REQUEST_FAILED.

SSO Attempt status error

Number of the SSO attempt failures of type AAA_STATUS_ERROR.

SSO Attempt xpath expression

Number of the SSO attempt failures of type AAA_XPATH_EXPRESSION.

SSO Attempt account not found or invalid

Number of the SSO attempt failures of type ACCOUNT_NOT_FOUND_OR_INVALID.

SSO Attempt account password not set

Number of the SSO attempt failures of type ACCOUNT_PASSWORD_NOT_SET.

SSO Attempt AI processing failed

Number of the SSO attempt failures of type AI_PROCESSING_FAILED.

SSO Attempt date time

Date and time (floor hour) of the SSO attempt.

SSO Attempt failure count

Number of the SSO attempt failures.

SSO Attempt missing parameter

Number of the SSO attempt failures of type MISSING_PARAMETER.

SSO Attempt no such template

Number of the SSO attempt failures of type NO_SUCH_TEMPLATE.

SSO Attempt no units available

Number of the SSO attempt failures of type NO_UNITS_AVAILABLE.

SSO Attempt no units passed

Number of the SSO attempt failures of type NO_UNITS_PASSED.

SSO Attempt redirection

Number of the SSO attempt failures of type REDIRECTION.

SSO Attempt referrer not permitted

Number of the SSO attempt failures of type REFERRER_NOT_PERMITTED.

SSO Attempt referrer null

Number of the SSO attempt failures of type REFERRER_NULL.

SSO Attempt SAML assertion expired

Number of the SSO attempt failures of type SAML_ASSERTION_EXPIRED.

SSO Attempt SAML assertion processing failed

Number of the SSO attempt failures of type SAML_ASSERTION_PROCESSING_FAILED.

SSO Attempt SAML assertion signature invalid

Number of the SSO attempt failures of type SAML_ASSERTION_SIGNATURE_INVALID.

SSO Attempt SAML assertion signature missing

Number of the SSO attempt failures of type SAML_ASSERTION_SIGNATURE_MISSING.

SSO Attempt SAML attribute invalid

Number of the SSO attempt failures of type SAML_ATTRIBUTE_INVALID.

SSO Attempt SAML attribute missing

Number of the SSO attempt failures of type SAML_ATTRIBUTE_MISSING.

SSO Attempt SAML auth request assembly failed

Number of the SSO attempt failures of type SAML_AUTH_REQUEST_ASSEMBLY_FAILED.

SSO Attempt SAML authentication failed

Number of the SSO attempt failures of type SAML_AUTHENTICATION_FAILED.

SSO Attempt SAML invalid audience

Number of the SSO attempt failures of type SAML_INVALID_AUDIENCE.

SSO Attempt SAML invalid issuer

Number of the SSO attempt failures of type SAML_INVALID_ISSUER.

SSO Attempt SAML no account affected

Number of the SSO attempt failures of type SAML_NO_ACCOUNT_AFFECTED.

SSO Attempt SAML response creation failed

Number of the SSO attempt failures of type SAML_RESPONSE_CREATION_FAILED.

SSO Attempt success count

Number of the SSO attempt successes.

SSO Attempt token broken

Number of the SSO attempt failures of type TOKEN_BROKEN.

SSO Attempt token timestamp off

Number of the SSO attempt failures of type TOKEN_TIMESTAMP_OFF.

SSO Attempt unexpected

Number of the SSO attempt failures of type UNEXPECTED.

Survey export elapsed seconds

The amount of seconds the export has been running.

Survey export end date

The date the export finished.

Survey export exported kbytes

Number of exported kilobytes.

Survey export exported records

Number of exported records.

Survey export exported via

Type of export interface used for exporting and storing the data, such as:

FTP
Email
SFTP (Password)
SFTP (Public keys)
FTPS (explicit)
Responses filter
Feed file
Invitations filter
Ask Now
Manual
Amazon S3
GCS
None

Survey export name

Name of the export.

Survey export requester

How the export is triggered. Options include Manually triggered, Schedule, or Feed account.

Survey export requester details

Detailed information about how the export is triggered.

Survey export retry seq number

Sequence number of (re)tries. 1 for first try and Null for manually triggered exports.

Survey export start date

Date the export was launched.

Survey export status

The current status of the export, such as Running, Successful, and Failed.

Medallia Video

This field filters reports by video and audio media in responses:

Associated Media feedback 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 use audio data to describe the interactions between customers and call center agents:

Note: Agent- and customer-specific metrics apply only to stereo calls because speakers are classified by audio channel. Speaker-specific fields with numeric values have a value of 0 for all other types of calls.

Important: Medallia Speech has altered our acoustic emotion calculation to comply with new regulations in the EU per the EU AI Act. Currently, acoustic emotion is calculated using text-based emotion recognition only, and voice-based processing to determine emotion is discontinued.

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.
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.
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.
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.
Agent non-silence ratio: Agent talk time during the call as a percentage of overall call duration.
Agent overtalk incidents: Number of overtalk incidents by the agent during a call.
Agent overtalk ratio: Agent overtalk time during the call as a percentage of overall call duration.
Agent talk rate: 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.
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.
Agent vs Customer talk rate: The ratio of agent talk rate to customer talk rate.
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.
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.
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.
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.
Customer non-silence ratio: Customer talk time during the call as a percentage of total call duration.
Customer overtalk incidents: The count of overtalk incidents by the customer during a call.
Customer overtalk ratio: Customer overtalk time during the call as a percentage of total call duration.
Customer talk rate: 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.
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.
Luhn presence: When redaction is turned on for Speech transcripts. Whether or not the Luhn algorithm (which identifies credit card numbers) was applied to the transcript.
Media duration: The duration in seconds of the call.
Overtalk: The percentage of the call during which the customer and agent spoke simultaneously.
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.
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.
Silence (incidents): A count of the times during a call when no speech was detected.
Silence (percentage): The percentage of the call during which no speech was detected.

Sampling

These fields track information about fields connected to Sampling:

Tip: Some fields connected to the Sampling process are part of the Survey metadata section.

Restriction: System fields are not supported in the Sampling pretend mode for Importers.

Quota management completed responses: Number of completed responses within a Quota.
Sampled date: Date and time when the record completed sampling.
Sampling result exclusion cause: Reason of exclusion for records excluded by sampling.
This field can be updated during a import by mapping the new value to the Exclusion Cause (exclusion_cause) special import field.
Sampling result exclusion detail: Detailed description of the cause of the exclusion.
This field can be updated during a import by mapping the new value to the Exclusion Cause (exclusion_cause) special import field.
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.
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.

Sensitive data

This field stores information about records with masked data. For more information, see Sensitive data.

PII regions flag: Whether or not this record contains masked data. It updates to Yes after sensitive data masking process is complete.

These fields store information from Social media records. For information on source fields, see Source fields. For information on specific source fields, see Customer Review sources.

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.

Overall Score (Fractional)

The value Overall score (Normalized) normalized 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.

Note: This field might be populated even if the Overall Score (Normalized) value is null.

Overall Score (5 buckets)

The score from Overall score (native) record normalized to an integer in from 1 to 5. Use this field for filter dropdowns and satisfaction distribution. Otherwise, use Overall score (Native) or Overall score (Fractional).

Overall Score (Native)

Original, un-normalized overall score for a review.

For surveys, this is a fractional value that corresponds to the raw value.
For Social feedback reviews, this is a fractional value corresponding to the value found on the source site.

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.

Note: Do not aggregate or compare this field across different sources, because values are on different scales.

Overall score color

Combines the Overall score field on surveys with the one of social review source, whose color scheme is defined in Social media colors.

Social media source

Social Feedback sources; Null when 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.

Social original post

Field that captures the link for Original post shown under the main score in the Responses form report and Response feed module.

Management response

The last response for a review when Respond to Social feedback are active.

Management response sent by

List of users who submitted one or more management responses 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 field. Consequently, if you are using this field in a Formula field, you must set the calculation mode to During a field refresh.

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 field. Consequently, if you are using this field in a Formula field, you must set the calculation mode to During a field refresh.

Management response status

List of available statuses a Management response can take, such as Not sent, External Response Sent, External Response Published, and External Response Sent and Published.

Management response send date

Date the first management response was sent when Management response status is either External Response Sent or External Response Sent and Published. It is Null when management response status is Not sent or External Response Published.

Management response first received date

The first date that Experience Cloud captured and verified a Management response appearing on the social source.

Management response received date

The last date that Experience Cloud captured and verified a Management response appearing on the social source. For example, this field can be populated and differ from Management response first received date when there is an update on the original Management response that was already published.

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.

Survey metadata

These field track information about survey interaction and survey emails:

Attachment file names

List of file names attached to the survey.

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

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.

Detected language

Language detected from open-ended question responses.

Email client browser

Email client browser.

Email client browser with version

Same as Email client 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.

Email client device brand

Brand name of the email client.

Email client device name

Device name running the email client.

Email client operating system

Operating system running the email client. This is set when the Invitation email is opened and rendered.

Email client operating system with version

Operating system and version running the email client.

Email client user-agent

Complete user-agent request header sent by the email client.

HTTP client cookies

Cookie created by the Survey engine while the survey taker takes the survey.

Highest page seen (internal index)

Page number of the furthest page seen by the survey taker.

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

Invalid pages submitted

Number of page submissions that failed to pass validation, such as when a required question not answered. The number increments for each invalid page submission, even if it's the same page.

Invitation email opened date

Date and time the invitation email was first opened by the survey taker. This supersedes Invitation opened date.

Invitation error message

Any error message associated with the invitation email.

Invitation opened

Whether or not the invitation email was opened. This fields gets updated to Yes when a survey is clicked, even if Tracking invitation open rate is not implemented.

Invitation opened date

Deprecated. See Invitation email opened date.

Invitation status

Descriptive status of the record state.

Is Ad Hoc Survey

Obsoleted. Whether or not the survey was part of an Ad Hoc distribution.

Is an isolated record

Whether or not the record is from an Ad Hoc survey, Ad Hoc approval, Social Rivals, or Employee program.

Isolation record type

The isolation type of a record, which can be from Ad Hoc survey, Ad Hoc approval, Social Rivals, or Employee program.

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.

Last page seen

Name of the last seen page by the survey taker.

Last page seen (internal index)

Page number of the last page seen by the survey taker (Integer data type). For example, 3.

Last page seen (internal index)

The page number of the last page seen by the survey taker (Indexed data type). For example, Page 3.

Last page submitted

Name of the last page submitted by the survey taker.

Latest submit date

Date and time for the last page submitted by the survey taker.

Link to Invitation

Direct link to the Invitation form report for a given record.

Link to Invitation (SSO)

Direct link to the Invitation form report for a given record with Single sign-on enabled.

Link to response

Direct link to the Response form report for a given record.

Link to response

Direct link to the Response form report for a given record Single sign-on enabled.

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.

Number of reminders sent

Number of reminder emails sent. It is 0 when only the Invitation email has been sent.

Operating system

Operating system the survey taker used to complete the survey. Examples include 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.

Operating system with version

Same as Email client 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.

Page path page numbers

List of survey page numbers that were displayed to the survey taker.

Page path timestamps

List of date and time when the survey pages are displayed to the survey taker.

Partial survey

Set to Yes if the survey is not completed by the survey taker.

Program ID

ID of an Experience program or Ad Hoc survey. Use this field to filter reports, exports, and in Experience programs conditions.

Program name

Name for the Experience program or Ad Hoc survey.

Reminder error message

Any error message associated with the Reminder email.

Status of survey reminder

Status of the reminder email displayed as text to be used in reports.

Status of survey/invite

Status of the survey or invitation email displayed as text to be used in reports.

Subscribers

List of subscribed users.

Survey has comment (1 or 0)

Whether or not (1 or 0) the survey has one or more comments. This includes any comments in any field types except Ask Now comments (which are not included) and whose Data type is Comment. For example, Case management comments in the record are considered a comment by this field.

Survey first bounce date

Date and time when the Invitation email bounced (not delivered). This field uses the survey's bounce history — a list with data about the different bounces of the Invitation and/or 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). It is Null if the invitation did not bounce.

Note: A null value does not mean the invitation was delivered.

Survey likes amount

Number of likes this survey has received.

Survey program

Name of the program if the survey version has a value different than null.

Survey program ID

ID of the survey program if the survey version (spec) has a value different than null.

Survey sampling setting

Name of the sampling setting used during sampling to create the survey record.

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.

Survey spec ID

ID of the survey version (previously known as survey spec) if the survey version has a value different than null.

Survey status

The status of the survey and/or Invitation email as a choice set. Choice set items include:

Completion pending
Completed
Ready for SE
Survey engine only
Excluded
No invite
Ready for Broadcaster
Junked
Delivered to Broadcaster
Retry delivery later
Delivery failed
Delivery bounced
Delivered
Delivered and reminded
Delivered no reminded
Reset
Expired
Ready for SE
Invitation resent
Resent pending
Partially completed
Partially completed and reminded
Delivered reminder to Broadcaster
Completed not loaded by Slug
Auto-excluded
Exit Auto-excluded
Not sampled
No Survey engine
Awaiting sampling

Survey type

Type of information stored in the survey record. Type include:

Survey
Static report
Unit metric
Feed file processing report
Quota management report
User activity
Survey export stats
Omni exporter stats
SSO event stats
Action plan

Survey URL

URL the survey taker uses to access the survey.

Survey clicked

Whether or not the survey taker started the survey. This is Yes when the Survey engine sends the first page of the survey to the survey taker after clicking a link to access the survey. Unlike Partial survey, once this field is Yes, it remains Yes.

Survey custom ID

ID configured from the Custom Survey ID screen in Medallia Setup, which provides a pretty format for the survey ID.

Survey custom ID without prefix

Custom survey ID without the prefix value set in Custom Survey ID screen.

Survey finished on mobile device

Whether or not the survey taker completed the survey (clicked Submit) on a mobile device. This is Yes when the Survey engine sends the last page of the survey to a mobile device. It has Null for surveys completed before this field was added.

Survey has comment (1 or 0)

Whether or not (1 or 0) the survey has one or more comments. This includes any comments in any field categories except Ask Now comments, which are not include). For example, if any Case Forms comments in the record are considered a comment by this field.

Survey language

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

Survey start date

Date this survey was first accessed by the survey taker

Survey started on mobile device

Whether or not the survey taker started the survey on a device other than desktop. This is Yes when the Survey engine sends the first page of the survey to a mobile device (after the survey taker clicked a link to access the survey). Once this field is Yes, it remains Yes. This field is similar to Survey clicked, which is also Yes when this field is Yes.

Survey taken on an IP Address that requires confirmation before setting cookies

Whether or not the survey was taken on a IP address that prompts the survey taker to confirm cookies.

Survey taker location at the start of the survey (latitude)

Latitude of the survey taker when starting the survey, if any.

Survey taker location at the start of the survey (longitude)

Longitude of the survey taker when starting the survey, if any.

Survey viewed on mobile device (on any page)

At least one page of the survey was viewed on mobile device.

Survey ID for external use

The survey ID for external use, such as for Medallia Technical support.

Survey ID for external use (prepended by a dot)

The survey ID for external use, prepended by a dot (.)

Survey ID for internal use

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

Textual status of survey reminder

Status of the Reminder email displayed as text.

Textual status of survey/invite

Status of the survey or Invitation email displayed as text.

Thank You email sent

Whether or not a Thank-you email is sent after completing a survey.

The IP address from which the invitation was opened

IP address of the email client that opened the invitation, when the address is provided by the device.

The IP address from which the survey was taken

IP address from which the survey was taken, when the address is provided by the device. It is empty if the IP address is missing.

Time (in seconds) the survey taker spent on the survey

Time (in seconds) the survey taker spent on the survey. It is empty if either start or completion date is missing.

Total pages submitted

Number of pages the survey taker completed and submitted. It does include invalid pages, such as empty required questions.

True if the survey was taken from an open proxy IP

Whether or not a survey was taken from an open proxy IP. If Yes, this field is set to 1, otherwise it is set to No (0).

Text Analytics

These fields record information for Text Analytics:

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 Data type is Comment.
Combined Topics and Sentiment 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.
Combined Topics and 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).
Manual Sentiment override applied: Whether or not manual sentiment tagging has been applied to a record.
Manual Topic override applied: Whether or not manual topic tagging has been applied to a record.
Tagged: Whether or not a topic is tagged. If Yes, at least one phrase in the record matches to a Text Analytics topic (field value is set to 1). It is set to No (0) if either no phrases in the record matches to a Text Analytics topic or if there are no phrases in the record.
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.
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.
Topic for [field]: A comma-separated list of the topics that match a specific field.
Topic for [field] original: A comma-separated list of the topics that match a specific field, before any manual changes.
Combined Topics and Sentiments for [field]: A comma-separated list of the topics and sentiments that match a specific field.
Combined Topics and Sentiments for [field] latest: A comma-separated list of the most recent manually-selected topics and sentiments that match a specific field.
Combined Topics and Sentiments for [field] original: A comma-separated list of the topics and sentiments that match a specific field, before any manual changes.
Topics with hierarchy for [field]: A comma-separated list of the topics and subtopics that match a specific field.
Topics with manual sentiments for [field]: A comma-separated list of the manually-selected topics and sentiments that match a specific field.
Untagged: Whether or not a topic is untagged. If 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 Text Analytics topic. It is set to No (0) if at least one phrase in the record matches to a Text Analytics topic or if there are no phrases in the record.
Survey has word tags: This field has a value of 1 if its survey has any word taggings, and 0 otherwise.

Intelligent Summaries

These fields track information for Intelligent Summaries for conversational data:

Medallia Speech transcript summary

Summary of the Speech transcript summary field.

Medallia Speech transcript primary reason

Primary reason for contact. Consists of one word minimum to four words maximum.

Medallia Speech transcript resolved?

Whether or not the primary reason for contact was resolved during this interaction.

Medallia Speech transcript outcome

Outcome of the interaction, including how the primary reason for contact was resolved, or why the primary reason for contact was not resolved.

Medallia Speech transcript is summarized?

Whether or not the Speech transcript summary field has been summarized.

Medallia Speech transcript summarization date

Date and time when the summarization processing is complete.

Medallia Speech transcript summarization 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.

Conversational transcript comment summary

Summary of the Conversational transcript comment field.

Conversational transcript comment primary reason

Primary reason for contact. Consists of one word minimum to four words maximum.

Conversational transcript comment resolved?

Whether or not the primary reason for contact was resolved during this interaction.

Conversational transcript comment outcome

Outcome of the interaction, including how the primary reason for contact was resolved, or why the primary reason for contact was not resolved.

Conversational transcript comment is summarized?

Whether or not the Conversational transcript comment field has been summarized.

Conversational transcript comment summarization date

Date and time when the summarization processing is complete.

Conversational transcript comment summarization 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.

User activity

These fields track statistics of user activities:

User account ID

ID of the user.

User account name

User name.

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.

User activity application platform

Application platform that recorded the activity.

User activity application version

Application version that recorded the activity.

User activity canonical detail

Untranslated name of the detail field.

User activity count

Number of times the activity was performed within a single sign-in session.

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.

User activity IP address

IP address of the user, when the address is provided by the device.

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.

User activity number of active accounts

Number of active accounts with the same primary role as the user at the time this user was signed in.

User activity number of active units

Number of active units at the time this user was signed in.

User activity primary role name

Name of the user's primary role.

User activity primary role type

The role type of the primary role of the user that interacted with the feedback signal.

User activity role

Role the user was using when the activity was performed.

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.